Thank you, I did write this and appreciate you enjoyed it. It's derived from a presentation I made to other Engineering Leaders about the future of product development and how are roles are going to change and how we need to adapt.
I agree, "people" still want something done with a high quality level and with additional speed (sometimes breakneck speed expectations). The challenge is balancing that expectation of faster while maintaining a similar level of diligence on the results. I
am seeing two camps of product managers now, some that want it all released now and some that are nervous to release anything with with AI at all (because of quality concerns). A more rapid decision process is needed to determine if it is stable enough to release and valuable enough to be worth including in our product (not just because we can do it, but that users will find value in the addition)
Gustav Morving
Building automation for smaller businesses in Zealand, Denmark.
I don't know how much you wrote yourself. Either way, it was a truly enjoyable read. Good job. I started to learn programming because I was confident that my skills as an architectural visualization artist were over. Now, when I started my own IT business doing automation for local firms. I actually got a client who needed some 3D rendering. Wait what?! - AI can't even do that properly?
Turns out people are still willing to pay for having something real built, not just slopped into existence. We are all adapting to agentic coding and whatnot. But your points hold very true.
If I did not understand the code. I'd be super terrified to deliver code to clients.