Hypervelocity Engineering (HVE) is Great -- But what About Scaling it?

The traversal of easily generating or fixing a "program" is OK – but orchestrating at higher levels is still way beyond the tools – Not to forget about the "enterprise" stuff. The evolution of AI in the context of Software Development is just following many other industrial growth patterns. The humans still need to understand the big picture – and it's been big all the time, but now we have greater tools and automation at the lower levels.

But right now, it's at a really LOW level - for the most part just the "program" – maybe stretching it to the "application".

When we try to understand what is possible now with the tools (HVE) and the people it really helps to look at the levels of "code" and applications – program → application → solution → enterprise

A good post from Mark Russinovich, which got me down this quick reminder of my past with so many Enterprise Frameworks, essentially states this as well. Much of these concepts of scale of "code" is credited to Brooks, Zachman, et.al.

EPISODE 31 - Scott & Mark Learn To...Pilot Coding - Vibe Coding for Real | Mark Russinovich | 21 comments

We keep hearing about “vibe coding,” but does it actually work on 30-year-old legacy C++ Win32 code? In this latest episode with Scott Hanselman, I discuss how I used AI (specifically GitHub Copilot and Opus) to modernize ZoomIt, including adding a video trimmer, volume controls, DPI scaling support and the requisite Dark Mode. The result? It’s complicated. The Good: It’s a massive accelerant. Features that would have taken me hours of UI layout toil took minutes. Overall, I estimate a 5-10x boost. The Bad: The AI still needs close oversight. It hallucinates fixes, blames the unit tests for its own failures, and occasionally pats itself on the back for “working too well” when it creates bugs. We even tried to fix a bug in the show, with Opus trying to gaslight us into thinking a registry key was fixed. If you want to see what “vibe coding” looks like in the real world (outside of a perfectly rehearsed demo), check it out and leave a comment. https://lnkd.in/g3zdWp4h | 21 comments on LinkedIn

LinkedInMark Russinovich

Evolution of a Software Architect

When you look at humans, the idea of evolving over time the span of understanding and the breadth of complexity grows as we go from program → application → solution → enterprise.