

I got a hot take on this. People are treating AI as a fire and forget tool when they really should be treating it like a junior dev.
Now here’s what I think, it’s a force multiplier. Let’s assume each dev has a profile of…
2x feature progress, 2x tech debt removed 1x tech debt added.
Net tech debt adjusted productivity at 3x
Multiply by AI for 2 you have a 6x engineer
Now for another case, but a common one 1x feature, net tech debt -1.5x = -0.5x comes out as -1x engineer.
The latter engineer will be as fast as the prior in cranking out features without AI but will make the code base worse way faster.
Now imagine that the latter engineer really leans into AI and gets really good at cranking out features, gets commended for it and continues. He’ll end up just creating bad code at an alarming pace until the code becomes brittle and unweildy. This is what I’m guessing is going to happen over the next years. More experienced devs will see a massive benefit but more junior devs will need to be reined in a lot.
Going forward architecture and isolation of concerns will be come more important so we can throw away garbage and rewrite it way faster.






They also introduced a critical security vulnerability into notepad where they just had the markdown links shell execute
open linkwhich allowed just installing arbitrary software as long as the link was valid instead of just opening a browser.If you managed to get the file onto a person’s you could execute it by having the person click on the link.