IT'S HERE! 💫 Aspire 17, our latest major release, has arrived. You've streamlined your stack, and now Aspire is your platform team's favorite tool too! Plus, a new dashboard, Go AppHosts, and lots more.
Blog 👉🏻 https://t.co/lncmJsyoKq
Full What's New 👉🏻 https://t.co/VZJ3atxr5Z
The future of software engineering is not task boards. It’s a mix of being able to organize work “in the small” and “in the big.” There will be times when you want to work on something deeply with an agent, and there will be times when you want to be completely hands-off. This will vary from team to team, and new ways of working will grow out of it.
In the year 2000, Joel Spolsky (founder of Stack Overflow) wrote a famous article titled “Things You Should Never Do, Part I.” In it, he talks about how rewriting your code from scratch is the single worst strategic mistake any software company can make. However, times have changed.
The cost of writing software is dropping exponentially and that has changed the math entirely on if it is worth rewriting your codebase. For instance, this year Anthropic’s Jarred Sumner ( @jarredsumner ) rewrote Bun in Rust in 11 days leading to many performance and correctness benefits.
Likewise, Stephen Toub (Distinguished Engineer at Microsoft, @stephentoub ) rewrote the GitHub Copilot runtime (400,000-line codebase) in Rust by himself. I thought it’d be interesting to lay out everything he learned in the process. So I interviewed him about how and why he did it.
In this episode:
• Why he choose Rust of all languages
• Rollout strategies (incremental vs all at once)
• How he prevented regressions
• Steering agents and which models he used
• Career lessons and engineering advice
Where to watch:
• YouTube - https://t.co/9Yj6kBj0ix
• Spotify - https://t.co/wa3my5QeBb
• Apple Podcasts - https://t.co/jOYDGtGVnt
• Transcript - https://t.co/rI3rkhxsgG
Thank you to the sponsor of this episode for supporting my work:
• WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at https://t.co/y8noBzFEem
Chapters:
00:00 Intro
01:06 Why the Copilot runtime needed a Rust port
05:38 Why he chose Rust
11:28 Discussing rollout strategies
21:57 How he caught regressions
32:08 Guiding the agents
42:11 Catching regressions before prod
45:16 Which models he used
50:03 The end benefit and costs
01:03:24 When to do a full rewrite
01:06:40 Career learnings on the way to Distinguished
01:16:00 Top technical book recommendation
01:17:49 Advice for young engineers
01:21:00 Outro
🚨It's release day!!!🚨 Hello Aspire 13.6, and hello dashboard persistence👋🏻 One of the longest awaited Aspire features has now landed, along with plenty of other goodies.
🪶 Read the blog: https://t.co/81R8XXiKYG
📜 See the full What's New: https://t.co/vVkSCYnDeW
Another huge update from the team. The dashboard supports persistence to SQLite, and has been native AOTed. Maybe the first example of anything Microsoft has shipped that is pushing Native AOT to the edge.
Initially Copilot was just a brand that multiple (some may argue too many) adopted in our products. Each implementation was unique and product experiences varied widely. Now, company wide, we are using the same harness, the GitHub Copilot SDK.
This is a monumental achievement for a company the size of Microsoft.