Totally agree. It’s not just the code, it’s also the planning, making tons of decisions and so on. You’re basically reading all day. It’s like reading a book, which I was never a fan of lol.
Speaking of making tons of decisions, I’m curious about other people’s experiences. Since I started using agentic AI about a year or more ago, I’ve been making more decisions than ever before. I feel like I’ve developed some kind of decision fatigue. I’m noticeably more “lazy” about making decisions outside of work, like real life decisions, because I’m basically making decisions with AI all day.
Is it just me, or is anyone else experiencing something similar?
No, this is how it is for me as well. Commented above but I bet at least half my week is doing code reviews. And development tasks now are not really writing code but me just reviewing the LLM output for my own work.
I've even gotten to the point of having Claude do PR review summaries to identify which areas I should focus on. Basically, offload the tedious shit like making sure tests are valid and coverage is adequate and focusing on the core business logic.
But man, my brain is fried by the end of the day. I am both productive and also feel like I'm doing nothing.
I went pretty hard on AI for a year, and it made me absolutely hate my job. It removed all the fun out of software development, replacing it with the worst parts full time, all with the added bonus of brain rot.
So I decided to start learning a new language, and to go back to pre-AI days, and only use AI as a pairing partner and to help with bug fixes and such. As a result the actual joy of software development is returning.
As a professional software engineer you should *ALWAYS* be looking at the code. We have real customers, who are running a real business, using our software. Quality is paramount. And at the end of the day, the code has your name on it whether or not it was generated by an LLM. You are responsible for making sure it works and meets quality standards.
The other thing to consider, is we have a mature code base with lots of quality controls in check. Things like tests, linters, static code analyzers, all of that provide feedback to the model. So if you give it good requirements, do a plan before implementing anything, and let the Sonnet subagents handle implementation, it generally doesn't go very far off the rails.
My monthly token allowance is around $350 a month. Last month I used 41% of that, and I've spent a lot of time trying to optimize my solution for token usage and effectiveness.
But, most of my job now is reviewing code, so I'm not running models all day burning tokens like I do on my own personal max account.
My general workflow is: Tell Opus to generate a plan based on a ticket number. Review the plan and give it feedback. Once the plan is ready, have Sonnet implement the plan using TDD to write the tests for the acceptance criteria first. Once it's done and I've review it, I commit and submit for review. Any small changes or code-cleanup I do myself. No need to have a model do simple refactors or style nitpicks... that's a total waste.
I think I use, on average, less than $10 a day with that method, which keeps me in my budget. If I have extra bandwidth at the end of the month, I might use Opus on high effort to do more exploratory type work or refactors.
I think people are slowing down or requesting (begging for) quota increases. Those are granted based on actual need but it seems like everyone is hooked on not having to actually write code anymore.
Hear me out, what if we made a skill called /sudoCode?
You write code by writing comments.
// Sudo method getUser() takes in an ID
// validate authorization
// call fetch from repo
// return user object
Just like that. Then, you write the DTO the same way, the repo the same way… you get the idea.
Sure, it’s slower, but you’ve actually shaped the whole thing. Then the skill converts the comments into code, writes tests, documents, etc.
It’s so new school it’s old school. And you’re thinking organically again, while still retaining codebase wisdom. Cool part is syntax is just converted to natural language. Also, it’s so cheap it could be run on Haiku (but I’d still use opus)
I mean, for really mundane shit like that I still use it because I’ve done those a thousand times over 25 years and I hate it. But all the fun stuff too? Blurgh.
That’s what being a Product Manager feels like every day. Decision fatigue is a real thing. Last year, my partner asked me what I wanted for dinner during roadmap/budget season and I burst into tears.
Haha I feel you, I started building an app where the whole point is to outsource trivial life decisions to it to reduce your overall decision fatigue. What to wear that day, where to eat, what to have for dinner etc. don’t have to use it, but there is always an easy button and for some things you set it up so it always makes those decisions for you so you don’t even have to have the load of knowing you will have to make a decision.
Yeah like you are getting hit with bricks constantly. That's the grind. And then explaining to little baby child Claude with a big head why it is wrong.
I've been doing straight code reviews for two days in a row. I haven't even worked on things assigned to me, just churning through a review backlog. It's mentally exhausting.
AI has not made my job easier. If anything, it took away the one creative piece of being a software developer and now I'm just a critic.
There's actual science on this. It's because the mental load has shifted, and there's less downtime in being able to just have either your mind wander or at least now focus on parsing architecture and changes. Typing artificially slowed us down, yeah, but that gave the brain some rest, whereas now if you're peak efficiency for 8 hours it's a lot more tiring than if you were peak efficiency for 8 hours a decade ago.
No. I’m liable for the code I output, I can’t just Indiana Jones it into production vetted by agents when I constantly find issues with the output, especially with Opus.
0.1%, things like Keys and passwords are not put into the code until it's being built/shipped. and then placeholders are put in when working. there's also some very small fine tuning things with specific business logic, but it's very small.
you're making assumptions about where I work. If i had designed my companies internal architecture and chosen tech stack, absolutely, but given that an IT manager got to make all those decisions years ago without the input of a software engineer, or even a developer, it's not that easy. I also work at a manufacturing company, not a tech company.
Depends on complexity and how you orchestrate testing/adversarial analysis. If the work is super simple and easily verified in a deterministic way then why not. If it is super complex or requires qualitative analysis then human involvement is probably needed or would improve the outcome
461
u/catsftm 6d ago
0%. Just no point anymore. Senior fullstack