222 karma · joined August 19, 2026
If you are taking steps to protect your brain maybe in a way you are also protecting your job?
Who knows how this all turns out years from now.
There absolutely should be a fool proof undefeatable mechanism that identifies or watermarks code that was completely LLM generated.
If you use LLMs, own it.
I think a possible solution on both fronts (maintaining software quality, preventing skill atrophy) may be implementation of strict token budgets. Make the individual programmer choose how they are going to spend their limited tokens for the day/week. Provide just enough to use it as a plan/development/review tool, but nowhere near enough to just go full send AI vibe coding software factory slop mode all day long.
Step 1 is "surrendering" to AI-driven coding.
Beyond that, the new competitive edge for developers everywhere is mastering AI tooling for maximum productivity and velocity.
Setting aside the "capability" of the tools, I knew it was the wrong direction after a couple months or so in. I specifically remember during a large feature implementation running out of tokens for my 5 hour window or whatever, and I just couldn't continue on my own. Mostly due to laziness (I'll just wait till tomorrow when my limit resets!), but I also picked up on my first big whiff of skill rot / atrophy brewing, and that made feel uncomfortable.
I just don't see this fully agentic approach going well long term. Talk about the ultimate dependency!! If the lights are "turned off" for whatever reason - outages, cost increases, or the agentic velocity finally reaches a complexity tipping point and you've lost control and understanding of your system to the point the agents are making things worse, whatever it is - do you really expect to be able to turn back the clock and step in to code at the productivity level and output you used to when you actually... wrote code?
CT scans emit ionizing radiation.
MRI contrast can buildup and be retained in the body over repeated administrations.
The scans can produce false positives, surface benign abnormalities which result in a wild goose chase, cause severe patient anxiety and healthcare burden, and result in over-treatment.
And of course doing this on a whole population level is not cost or time effective.
Though I never specifically asked, I sincerely doubt they would have footed the bill to construct a detached building in my backyard that I could work from instead.
Why start and invest in a construction project for a building that may not be staffed long term? Perhaps renting a small coworking space in town is the safer financial move. And have your employer pay for it.
While it sucks to have blown a lot of money and accept they've been duped to get a degree in something that is now "worth" a small fraction of what it once was, time is on their side. There is plenty of time to go back to school, or apprentice, or learn a trade or go to trade school in something else with better long term career prospects.
On the opposite side of this, senior level devs should (hopefully) be on target financially and theoretically should be fine, especially if they make adjustments now (lower COL, layoff preparation, prepare for accelerated retirement timeline).
The folks who are really going to suffer are those early to mid level developers. Not as much of a network, not enough traditional expertise, not enough savings, not as much time to invest and pull the trigger on a career change.
Besides your first point, the rest can be delegated to AI as well. And you don't need to be a "software engineer" to spec out requirements and user needs.
Because, almost certainly, it's not your source code.
I'd move to the middle of nowhere and work multiple jobs on a farm and in construction. Learn how to grow food, and build things. Meet the farmer's daughter, and marry her. Then, buy my own land, grow my own food, and build my own things.
1. Embrace the AI and continue working and earning for as long as you can. Bank as much savings as possible. Lower your cost of living. Hopefully you've already been doing this over the past decade plus, when times were good. FIRE.
2. Don't use AI to write code. Write code yourself, as you've always done. Then, just see how long you last at work. If AI truly progresses, then long term most programmer jobs as we know them today are going to disappear. So worst case you will be let go a little earlier than your peers.
The devs using AI to write all their code are going to suffer major or complete atrophy of their coding skills. It's only been about a year of this and we're already seeing it occur. Maybe this doesn't matter long term and manual coding is truly dead, or maybe it comes full circle and we get back to programmers programming, in which case you will have a massive leg up on the NPC "programmers" who haven't written code in years because they surrendered their craft -and brain- to AI agents.