We should brace ourselves to find less and less satisfaction from the process as we become more comfortable embracing AI. At least, that's what the first chapter in the evolution of the AI-assisted software developer role has taught me.
Author sounds like they are missing meaning in what they do. If they had a life mission, AI is just an aid in accomplishing that mission, and they wouldn't get sidetracked by all the unfulfilling projects (modulus the ADHD, that has its own bearing on the experience using AI, and is the most interesting part of this post to me).
Perhaps at a population scale AI inhibits people from finding fulfillment.
But on an anecdotal basis, "just go find something meaningful". For some of us that "hate the AI timeline", we are still finding purpose and fulfillment by applying AI toward our personal missions.
You're describing frontline management, not middle management. My 2 cents is that frontline management is the worst job in engineering, for the reasons you describe and more.
When work was chill I went to decaf for the morning espresso on weekdays, and enjoyed real coffee on weekends. I took glee in withholding energy from work that I redirected to my personal time.
Then when work picked up, I went back to regular coffee everyday.
I don’t think there’s a hole in my soul though. And caffeine degrades my personality a little bit (to my own judgment).
IA makes the most sense in the spirit of preservation.
Etree (https://www.etree.org/ ) is the longest running torrent site for tapes. It looks like only about 5% of the hundred thousand torrents have any seeders at all. Not sure how reliable requesting a seed is. I’d expect long tail stuff to get “effectively lost”. Versus IA whose purpose and funding is preservation, in addition to sharing.
Indeed. I directly ask my reports to discover and surface conflicts, especially disagreements with me, and when they do I try to strongly reinforce the behavior by commending and rewarding them. Could anyone recommend additional resources on this topic?
The real reason not to become an EM in 2026 is because AI makes our jobs 10x harder.
This is true, but our job was getting kind of boring anyway. Time to lead, not manage. We should be having just as much fun as the ICs, and the best I know are having the time of their lives.
While I too am only seeing a boost on the order of 20% so far, I think there are more creative applications of LLM beyond writing code, that can unlock multiples of net productivity in delivering product end to end. People are discovering these today and blogging about them, but the noise about dark factories and agents supervising agents supervising agents, etc, is drowning out their voices.
Every one of us is a pioneer if we choose to be. We have only scratched the surface as an industry.
Again, not security theater. Signs of general dysfunction yes. Embarrassing. Fun to tease about for sure.
Aside: the more times I re-read the article the more annoyed I am with the self-righteous tone. It feels like the author is mimicking the style of legendary Usenet posts, but the story just isn’t that interesting and the writing not that witty, it falls flat.
Tests are not free, over proliferation of AI-touched tests is itself a problem, similar to the problem duplicative and verbose AI-generated code.
And tests are inherently imperfect, they may not test the perfect layer, so they break when they shouldn't, and they certainly don't capture every premise.
I'm on board with the tactics you suggest, but they are only incrementally helpful. What we really need is AI that removes duplicative code and unnecessary tests.
I love this article but don't understand the conclusion. Heroku is dead as a doornail, of course.
Salesforce's core product was on bare metal up to a couple years ago. What they should have done is adopt Heroku as their internal Platform-as-a-Service. That would have solved three problems: 1) provided a ready and proven foundation for cloud adoption by Salesforce business units, 2) stimulated Heroku's product roadmap by giving it a very large and loyal design partner, and 3) eliminated the opportunity cost in terms of headcount, developer productivity, and poor imitation that came with the alternative "Falcon" aka "Hyperforce" project that became Salesforce's albatross and black hole for developer energy and goodwill going on 7+ years now.
It’s more than just money, it’s how you set up your life to be resilient to contingencies. For example finding a compatible life partner. For example finding happiness without lifestyle inflation and breaking free from the hedonic treadmill. Or perhaps having a good lifestyle business for some people. Or having extended family support nearby. I call these things unfuckwithability. Money is a big part of it, but may not be the biggest missing piece for many people.
“Manual” has a negative connotation. If I understand the article correctly, they mean “human coding remains key”. It’s not clear to me the GitHub CEO actually used the word “manual”, that would surprise me. Is there another source on this that’s either more neutral or better at choosing accurate words? The last thing we need is to put down human coding as “manual”; human coders have a large toolbox of non-AI tools to automate their coding.
Because the old machine is still useful intact. I don’t see a difference between laptop and desktop here. I agree I don’t see myself ever swapping in an upgraded motherboard.