AI news videos

Learning Chip Design With Microsoft Discovery

A Microsoft engineer with no chip design background used Microsoft Discovery to walk a small chip from a written specification to physical layout, and wrote up what he learned.

Watch on YouTube

Transcript

Sources

Every claim in this video comes from the top ranking coverage of this topic. The claims and where each one came from:

• HOOK SENTENCE ONE. Narration: The engineer says he had no chip design experience, delivered as A Microsoft engineer says he had no chip design experience. Article verbatim, line 59: "For someone with no domain experience I'm pretty proud of it though". Supporting article verbatim, line 33: "Chip design is super intimidating to me." Byline verbatim, lines 27 and 28: "StevenTruitt-MSFT" and "Microsoft". Wording changes and why: the article phrase no domain experience is narrowed to no chip design experience because the domain under discussion throughout the post is chip design and a listener has no way to resolve the bare word domain; the change narrows rather than broadens the claim. The explicit attribution A Microsoft engineer says is added out loud so the sentence is never heard as an Inboxsmith assertion, per the attribute every substantive sentence rule. The author's self description as intimidated is not narrated because intimidated is a state of mind we cannot verify beyond his own word and the experience claim carries the same load. No banned compound or initialism was needed in this sentence, so none was replaced. No launch verb, no calendar date, no digit, no comma and no dash appear in the narrated sentence.(First party Microsoft Tech Community blog post titled From Ad Astra to Semper Disco: Learning Chip Design with Microsoft Discovery, posted on the Microsoft Discovery Blog under the employee byline StevenTruitt-MSFT with the org label Microsoft, dated Sep 10 2026 and marked Version 2.0. The post is a first person personal learning project narrative about a workshop the author co ran at an industry conference, not a launch announcement, not a product release and not a benchmark result. There is no independent verification of any claim in it and this is a single source story sourced entirely from the publisher itself. The live URL returns HTTP 403 to our fetcher, so the alert time snapshot stored at scripts/data/article-cache/a555a54c29bad217.txt and captured 2026-09-17T14:16:07Z is the source of record for every fact in this script.)
• HOOK SENTENCE TWO. Narration: His post describes designing a small chip with Microsoft Discovery. Article verbatim, line 32: "Recently, with Microsoft Discovery, I have been able to expand my horizons to learn more about parts of silicon design and engineering that have always eluded me. For the first time I was able to walk a chip design problem from spec to physical layout. This project is small, with limited instructions, and far from a cutting edge node." Wording changes and why: the adjective small is taken verbatim from This project is small and is deliberately kept in the hook so the very first framing a viewer hears is scale limited rather than triumphant. The verb designing is chosen specifically because every launch style verb is banned for this story and because the post never says a chip was fabricated, taped out or shipped; designing describes design work only. His post describes is used rather than any bare assertion so the claim is audibly the publisher's. The article's own figure expand my horizons is dropped as a figure of speech. The word chip is kept unqualified by any process node name because SKY130 is a banned glued brand and digit token for the voice engine. No comma, dash, digit or calendar date appears in the narrated sentence.(First party Microsoft Tech Community blog post titled From Ad Astra to Semper Disco: Learning Chip Design with Microsoft Discovery, posted on the Microsoft Discovery Blog under the employee byline StevenTruitt-MSFT with the org label Microsoft, dated Sep 10 2026 and marked Version 2.0. The post is a first person personal learning project narrative about a workshop the author co ran at an industry conference, not a launch announcement, not a product release and not a benchmark result. There is no independent verification of any claim in it and this is a single source story sourced entirely from the publisher itself. The live URL returns HTTP 403 to our fetcher, so the alert time snapshot stored at scripts/data/article-cache/a555a54c29bad217.txt and captured 2026-09-17T14:16:07Z is the source of record for every fact in this script.)
• SCENE 1. Narration: The engineer says he took a chip design problem from specification to physical layout for the first time. Article verbatim, line 32: "For the first time I was able to walk a chip design problem from spec to physical layout." Supporting article verbatim, line 61: "Before this project I only had an abstract understanding of chip design. At the end, I had a physical-layout design I could continue developing toward fabrication." Wording changes and why: the article's verb walk is replaced with took because to walk a problem from one place to another is a figure of speech and figures of speech are banned in narration; took a problem from A to B is the plain literal equivalent and preserves the start to finish meaning exactly. The abbreviation spec is expanded to specification because clipped abbreviations are a known garble risk for the voice engine and because specification is the word the article itself uses at line 43 and line 49. The phrase for the first time is retained verbatim and is the single permitted spoken ordinal in the whole script; it is load bearing because it is the honesty anchor that this was a personal first and not an institutional milestone. The article's own limit that he ended with a design he could continue developing toward fabrication is not narrated here because it is carried by scene 4 and by the deliberate absence of any fabrication or tape out language anywhere in the script. No banned compound was spoken; physical layout is written as two plain words rather than the article's hyphenated physical-layout. No comma, dash or digit appears in the narrated sentence.(First party Microsoft Tech Community blog post titled From Ad Astra to Semper Disco: Learning Chip Design with Microsoft Discovery, posted on the Microsoft Discovery Blog under the employee byline StevenTruitt-MSFT with the org label Microsoft, dated Sep 10 2026 and marked Version 2.0. The post is a first person personal learning project narrative about a workshop the author co ran at an industry conference, not a launch announcement, not a product release and not a benchmark result. There is no independent verification of any claim in it and this is a single source story sourced entirely from the publisher itself. The live URL returns HTTP 403 to our fetcher, so the alert time snapshot stored at scripts/data/article-cache/a555a54c29bad217.txt and captured 2026-09-17T14:16:07Z is the source of record for every fact in this script.)
• SCENE 2. Narration: The post says he turned the specification into logic code and then into a circuit description before physical layout. Article verbatim, lines 43 to 48: "Take a specification doc to logical C code" then "Translate the logic into high level synthesis (HLS) C" then "Translate again into a flow of digital signals (RTL)" then "And then implement via logical and then physical layout using OpenROAD." Supporting article verbatim, line 49: "From this I laid out the core logic in logical C code and then expanded that into a more expressive version called high-level synthesis (HLS) C to collect the logical blocks together." and "The first step is to translate this logic to register-transfer level code (RTL)." Wording changes and why: the article's logical C code becomes logic code because the letter C read aloud is an isolated initialism and initialisms are banned from narration for this voice engine. The stage high-level synthesis (HLS) C is omitted from narration entirely because both HLS and high-level are on the explicit do not speak list; it appears only in this provenance note. The stage register-transfer level code (RTL) becomes a circuit description because RTL is a banned initialism and register-transfer is a banned hyphenated compound; a circuit description is justified by the article's own plain gloss at line 45, a flow of digital signals, and by line 49 where the author says he used Verilog to describe the actual logical devices needed. The tool name OpenROAD is omitted from narration because it is a glued brand token that the voice engine garbles, and it is carried instead in the scene 3 onscreen card. The article's four stage enumeration is deliberately compressed to two named stages joined by and then, with no comma anywhere, because a three or more item list in narration drops the speech rate from about two point six five words per second to about two point one eight and would overrun the sixty second ceiling. Nothing about the compression changes the direction or completeness of the described flow; it is the same pipeline with two intermediate stage names left unspoken. No comma, dash or digit appears in the narrated sentence.(First party Microsoft Tech Community blog post titled From Ad Astra to Semper Disco: Learning Chip Design with Microsoft Discovery, posted on the Microsoft Discovery Blog under the employee byline StevenTruitt-MSFT with the org label Microsoft, dated Sep 10 2026 and marked Version 2.0. The post is a first person personal learning project narrative about a workshop the author co ran at an industry conference, not a launch announcement, not a product release and not a benchmark result. There is no independent verification of any claim in it and this is a single source story sourced entirely from the publisher itself. The live URL returns HTTP 403 to our fetcher, so the alert time snapshot stored at scripts/data/article-cache/a555a54c29bad217.txt and captured 2026-09-17T14:16:07Z is the source of record for every fact in this script.)
• SCENE 3. Narration: He says he used widely available open source design tools and an open process node instead of a foundry. Article verbatim, line 58: "This process was remarkably straightforward even when limiting myself only to widely available open-source tools and process design kits." Article verbatim, lines 50 to 54: "If this were something where I wanted to push the frontier of capability it would be time to start talking to a foundry and using a design kit aligned to a frontier node. Since this is meant to be an open-source example however, I found the OpenROAD open PDK and SKY130 process node as a nice open alternative to test against." Wording changes and why: the hyphenated compound open-source is rewritten as the two plain words open source because hyphenated compounds are explicitly banned from narration for this voice engine; the meaning is unchanged. The brand tokens OpenROAD and SKY130 are removed from narration because OpenROAD is a glued brand token and SKY130 is a glued brand and digit token, both of which the engine garbles, and because SKY130 would also introduce spoken digits; they are preserved instead in the scene 3 onscreen card, which the gate permits. The article's figure push the frontier is dropped as a figure of speech. The foundry clause in the article is written in the conditional, so narration says instead of a foundry rather than claiming he was turned away by one; the factual content narrated is only that he used the open alternative and did not go to a foundry, which lines 50 to 54 state directly. The phrase process design kits is reduced to the single item an open process node so that the sentence carries one item and not a list, per the no multi item list rule. No comma, dash or digit appears in the narrated sentence.(First party Microsoft Tech Community blog post titled From Ad Astra to Semper Disco: Learning Chip Design with Microsoft Discovery, posted on the Microsoft Discovery Blog under the employee byline StevenTruitt-MSFT with the org label Microsoft, dated Sep 10 2026 and marked Version 2.0. The post is a first person personal learning project narrative about a workshop the author co ran at an industry conference, not a launch announcement, not a product release and not a benchmark result. There is no independent verification of any claim in it and this is a single source story sourced entirely from the publisher itself. The live URL returns HTTP 403 to our fetcher, so the alert time snapshot stored at scripts/data/article-cache/a555a54c29bad217.txt and captured 2026-09-17T14:16:07Z is the source of record for every fact in this script.)
• SCENE 4. Narration: The engineer says his design is not as good as one that someone with deep domain expertise could make. Article verbatim, line 59: "Is this design as good as someone with deep domain expertise could make? Of course not!" Wording changes and why: the article states the limitation as a rhetorical question followed by an exclamation, which cannot be spoken as a single declarative comma free sentence, so it is flattened into one plain declarative that preserves the author's own answer exactly; deep domain expertise is kept verbatim. The attribution The engineer says is added so the self criticism is audibly his and not our editorial verdict. The alternative candidate for this beat was the professor's quoted point at line 60 that "Tools like Discovery can significantly lower the barrier to hardware design by using natural language to support the design process and enable rapid exploration, while still leaving room for expert knowledge to interpret EDA feedback and optimize the design for different application scenarios"; it was rejected for narration because collapsing it into one comma free sentence under twenty two words required replacing the banned initialism EDA and still read as a partial endorsement, whereas the author's own line is the stronger and shorter honesty beat. EDA therefore appears nowhere in narration. No comma, dash or digit appears in the narrated sentence. SENTENCE BY SENTENCE AUDIT. Hook sentence one traces to line 59 "For someone with no domain experience" plus the line 27 and 28 byline. Hook sentence two traces to line 32 "Recently, with Microsoft Discovery" and "This project is small". Scene 1 traces to line 32 "For the first time I was able to walk a chip design problem from spec to physical layout." Scene 2 traces to the numbered flow at lines 43 to 48 and the expanded restatement at line 49. Scene 3 traces to line 58 "widely available open-source tools and process design kits" and to lines 50 to 54 on the open alternative versus a foundry. Scene 4 traces to line 59 "Is this design as good as someone with deep domain expertise could make? Of course not!" The endcard is fixed Inboxsmith boilerplate and traces to no article sentence. SENTENCE BUDGET. Hook sentence one is ten words and hook sentence two is ten words for a hook total of twenty words in exactly two sentences. Scene 1 is eighteen words. Scene 2 is nineteen words. Scene 3 is nineteen words. Scene 4 is nineteen words. The endcard is seventeen words in exactly two sentences. Total narrated words across hook and four scene narrations and the endcard narration is one hundred and twelve, against a target of about one hundred and twelve and a ceiling of one hundred and thirty two. Total spoken sentences is eight, which is two plus one plus one plus one plus one plus two. Comma count across every narration field including the hook and the endcard is zero. Spoken number count is one, the ordinal first in scene 1, which is within the at most one allowance. Longest scene narration is nineteen words, well under the eighteen to twenty two band ceiling and far under the thirty word renderer truncation cap. The durationS planning integers are eleven and eleven and eleven and twelve and sum to forty five, inside the thirty to fifty QA band. No timeline array is present, so the WEEK tier from storyDate 2026-09-10 is preserved. HONESTY CAVEAT. This is a first person employee blog post about a personal learning project undertaken for a conference workshop that the author co ran with two professors; it is not a launch, not a product release, not a tape out and not a benchmark result. It is single source and carries no independent verification whatsoever. Our news scorer rated it HOT on recency and publisher alone with zero launch verb credit, which is precisely why the narration frames the event as a Microsoft engineer describing what he built and what he learned. The author's own limitations are quoted in this file and in the narration: "This project is small, with limited instructions, and far from a cutting edge node" and "Is this design as good as someone with deep domain expertise could make? Of course not!" and "Granted, for this project the optimization was fairly limited in scope only modulated a few variables". The strongest outcome the article supports is line 61, "At the end, I had a physical-layout design I could continue developing toward fabrication", and the script never implies more than that. No launch, unveil, announce, introduce, release, ship, roll out or debut verb appears anywhere in narration, nor does now available. CORROBORATION STATUS. The transcripts.json file for this keyword holds zero videos because the host's yt-dlp build is out of date; that is a tooling failure on our side and carries no information at all about the story, so it was neither treated as a signal nor cited. The timeline-probes.json file holds only unrelated third party YouTube titles about quantum chips, retro processors, interview questions and unrelated AI commentary; a video title is not evidence, so nothing was sourced from it. No third party channel, outlet or publication is named anywhere in this file. Every narrated fact comes from the snapshot of the first party post and from nothing else. DELIBERATE OMISSIONS. Omitted: the author's satellite and aerospace career opening and the whole space hardware digression at line 30, which is colour and touches no narrated claim; the conference name and year and the two partner professors by name at line 39, cut because the conference acronym is a banned initialism and because naming individuals adds no verifiable weight; the accelerator array and matrix multiplication detail at lines 39 and 49, cut for the word budget; the Verilog and logic gate detail at line 49, cut for the word budget and because it sits inside the stage that scene 2 compresses; the GitHub project link at lines 40 and 41, cut because we do not narrate links; the optimization and parameter sweep passage at lines 55 and 58, cut for the word budget with the author's own scope limit on it noted above; the professor's full quotation at line 60, handled in this entry's wording note; the closing Ad Astra and Semper Disco passage at lines 64 to 69 and the phrases scratched the itch, push the frontier, at my side and on my toolbench, all cut because they are figures of speech that are banned from narration; and all site furniture, tags, footer navigation and share controls. Nothing omitted contradicts, qualifies, narrows or reverses anything narrated; every omitted limitation is either already narrated or is additional caution in the same direction as the narration, and no omitted passage contains a stronger claim than the script makes. PROMPT INJECTION CHECK. All one hundred and seventy lines of the snapshot were read in full. The page furniture consists of a source URL and capture header on lines 1 to 3, a site chrome block on lines 9 to 24 including Open Side Menu, Skip to content, Tech Community, Community Hubs, Products, Topics, Blogs, Events, Skills Hub, Community, Register and Sign In, a read time marker on line 25, the title and byline and date on lines 26 to 29, the body on lines 30 to 69, an updated stamp and version and topic tags on lines 70 to 76, comment and author card controls on lines 77 to 84, a blog follow prompt and share row on lines 85 to 94, a very long Microsoft marketing and legal footer on lines 95 to 162, and a repeated share row on lines 163 to 170. The imperative sentences observed are all ordinary user interface labels and navigation verbs aimed at a human browsing the site: Open Side Menu, Skip to content, Register, Sign In, Send Message, View Profile, Follow this blog board to get notified when there is new activity, Share this page, Share on LinkedIn, Share on Facebook, Share on X, Share on Reddit, Share on Bluesky, Subscribe via RSS, Share via email, Manage cookies, Contact Microsoft, Explore Microsoft products, How to buy for your school and Your Privacy Choices. Inside the body the only imperative forms are the numbered process steps at lines 43 to 46, Take a specification doc to logical C code and Translate the logic into high level synthesis (HLS) C and Translate again into a flow of digital signals (RTL), which are the author describing his own engineering pipeline to human readers and not directions to any agent. None of these address an AI system, none attempt to alter a system prompt or output format, none request a tool call or a network fetch, none try to redefine the task, and none contain hidden or encoded payloads. Result: no prompt injection detected; the snapshot was treated strictly as untrusted data informing facts only, and no instruction inside it was followed.(First party Microsoft Tech Community blog post titled From Ad Astra to Semper Disco: Learning Chip Design with Microsoft Discovery, posted on the Microsoft Discovery Blog under the employee byline StevenTruitt-MSFT with the org label Microsoft, dated Sep 10 2026 and marked Version 2.0. The post is a first person personal learning project narrative about a workshop the author co ran at an industry conference, not a launch announcement, not a product release and not a benchmark result. There is no independent verification of any claim in it and this is a single source story sourced entirely from the publisher itself. The live URL returns HTTP 403 to our fetcher, so the alert time snapshot stored at scripts/data/article-cache/a555a54c29bad217.txt and captured 2026-09-17T14:16:07Z is the source of record for every fact in this script.)