← All IntelClip / OtherOld workflow: tools built for solo implementation
From Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref. · ≈6:40
“This is what the software engineering process used to look like before AI.”
“This was great. We all knew how to do this.”
“our IDE, our workhorse, um it was built for implementation and polish to be done by an individual, to be heads down building as a software engineer writing code.”
What’s in it
- Breaks down the classic pre-AI software engineering workflow
- Explains why IDEs were built for solo, heads-down coding
- Argues AI is upending the traditional plan-build-polish cycle
Clip transcript
Um This is what the software engineering process used to look like before AI. We'd do some planning up front. We'd sit down and build. We'd implement. It'd be It'd be iterative. We'd be exploring. But largely we're sitting down building in isolation, implementing something. And at the end we sort of polish it up and ship it out the door. And this was great. We all knew how to do this. We had a lot of systems for this. Uh And it was good. And then AI came along. Um But at this time our our tools were built for this. Like all all our history of coding tools were built for this style of work. Um our IDE, our workhorse, um it was built for implementation and polish to be done by an individual, to be heads down building as a software engineer writing code.
Comments
Sign in to comment.
Loading comments…