In my side hustle time, I use coding agents to explore what if projects I would otherwise never get to build.
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 exactly what the article highlight might actually put your "competitors" (if you see others like that) in front of you, as focus and "what you actually did" becomes more important. Might be that while you shipped and experimented with 50 different APIs, your "competitor"/peer just did 3, but they were more carefully considered so the payoff ended up bigger/better, in whatever way that could be.
Ya this is exactly how I use it, the LLM does everything i don't want to do. Which is basically everything except the exact code im writing. Its very freeing to not have to worry or touch a jira ticket ever again. The LLM just does it for me.
Appreciate the quote of the Essentialism book by Greg McKweon, which I am currently reading. Funnily enough I decided the book when I found out (on Imprint app) that one of the key values of the “essentialist” is playfulness. I was sold.
It's wild we're seeing people rediscover the same solution to the same problems we've had forever: being precious about your darlings.
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.
> So logically, if AI can help us complete tasks 2-100x faster than before, we should be UNDERWORKED and experiencing ZERO burnout, right?
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
In my side hustle time, I use coding agents to explore what if projects I would otherwise never get to build.
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 exactly what the article highlight might actually put your "competitors" (if you see others like that) in front of you, as focus and "what you actually did" becomes more important. Might be that while you shipped and experimented with 50 different APIs, your "competitor"/peer just did 3, but they were more carefully considered so the payoff ended up bigger/better, in whatever way that could be.
That's how I understood the article at least.
Ya this is exactly how I use it, the LLM does everything i don't want to do. Which is basically everything except the exact code im writing. Its very freeing to not have to worry or touch a jira ticket ever again. The LLM just does it for me.
Appreciate the quote of the Essentialism book by Greg McKweon, which I am currently reading. Funnily enough I decided the book when I found out (on Imprint app) that one of the key values of the “essentialist” is playfulness. I was sold.
It's wild we're seeing people rediscover the same solution to the same problems we've had forever: being precious about your darlings.
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.
> So logically, if AI can help us complete tasks 2-100x faster than before, we should be UNDERWORKED and experiencing ZERO burnout, right?
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