At my day job, I use AI to fix config, container, and installation issues so I can spend my time coding instead of struggling to fix mostly other people's mistakes. And really, in this age of python wheels, containers, virtual environments, and fragmented APIs, the cognitive load of doing this by hand would shut me down for the day.
1.5 years in and I haven't burnt out. If anything, I'm ramping up. I'm no longer afraid of adding a web UI, or insane numbers of unit tests, or deploying other people's software.
What I'm not doing is using it to build products, but instead just doing so to augment the supporting stack. All of this is subject to change as the AI landscape evolves.
That's how I understood the article at least.
I believe you misspelled "rip it off."
I guess I shouldn't be surprised that people are using the tools built by ripping off the collective creative works of humanity to rip off individual things, too.
I think it was a mistake to add this much complexity to the world of software in the first place, so I'd view AI as a bandaid to a problem rather than addressing the underyling issue. But on the whole, the cost of all this extra complexity, data centers to run AI to fix layers of crud and buildup don't seem to provide much of a net benefit to society (except to those who are at the top and need to see growth to pad their retirement portfolios).
I would suggest not concluding the end of this movie from the first 5 minutes of the story. But then, I really fought against complexity over my career and lost hard. One can either check out as a fossil of the good old days or adapt to the new reality. 6 months ago, AI was about to replace all the engineers and then reality slapped the C-suite hard on that subject as just one recent plot twist.
Code generators reduced the friction for implementing every shitty idea someone has ever had, but because developers seem to have never experienced throwing shitty ideas away (because if it was written in code it _has_ to be important right?) they treat everything coming out of the Codegen as a precious idea that eventually builds up to clutter one's brain leading to Implementation Fatigue the author experienced. The solution? Go through that same process but focus on one idea at a time and make it good.
It does make me wonder if the people experiencing this had hobbies outside of software engineering (let's say, anything creative) they'd be able to spot the signs earlier.
Edit: Reveler vs Revealer
What things, why, and how did you measure this?
I love it. Will any of them succeed? It’s early days, but seeing potentially life changing growth in multiple areas at once gives me a lot of energy.
No. you got lied to by AI bros. 100x times the code (that if you burn enough tokens that you could actually hire someone to go thru your ideas and make them...) is not 100x times the productivity
Long story short, I think we’re in a phase where the organizational value function is lagging behind the tech. A “proof of concept” used to be correlated with “proof of work” and some amount of domain understanding, but I think now what we need is a focus on “proof of understanding” or else you’re probably just wasting tokens on a baby version of the problem. A decent proxy right now is that if you have zero external dependencies then your solution is probably a toy.