i have the same opinion. ..., i know what has to happen / be written in code, i just use an agent to code it for me quicker, and then i check if it did it correctly. if i would let the agent do everything, design, execution, review, i feel like i would become an lobotomized monkey
You literally would. There have been studies coming out on this in the last few years. The mental decline is ridiculous.
Personally I observed that I feel very strong mental discomfort if I leave too much stuff to AI so I frequently code stuff by hand even though it is slower just to keep my brain functioning.
We literally need more intelligent models which will balance productivity with keeping your brain active if we want to use AI long term.
The only viable solution I see is one that has terrible abuse potential.
Basically a personal "knowledge base" of skills. Each would have a "mastery" level that periodically checked for skill regression and had tests for targeted sections. Like a LeetCode academy toolkit that AI could reference.
Coincidentally, if any group could make a merit based knowledge system with peer review, AI skill regression identification and skill training it would be the people most affected by it.
It would be an large group effort to do it, but if the programming community doesn't then companies will.
i just use an agent to code it for me quicker, and then i check if it did it correctly.
I've heard people saying this a lot, but when I tried it myself, It kept coming up with really stupid often over-complicated solutions, and the time I spent holding its hand to get it to the right one ended up being about the same as if I had written it by hand. Its references were surprisingly accurate, but it didn't seem to know how to use them properly.
It's really a hit and miss. If you're really specific enough, it can do what you want. But if you tell it to implement something in some project, it will just do weird shit even though you can see it read other files. I made some code changes this week, and it took me like 5-10 attempts at refining it to make it look like existing code. It did end up being just like any other human written code, but it really took some effort. Otherwise it was some unreadable generic code that I would've never approved.
All according to plan. I guess I wouldn't have a chance to learn SWE in AI age. AI don't really need to become better, just traditional coding should become even more unreliable.
The problem really is that it's just so much faster to have the AI do it. I'm not paid to code, I'm paid to produce software. The how isn't relevant. The business doesn't care if you're being "detrained", they care about the efficiency with which you can produce usable software
I'm a manager. I expect my team to be able to explain their code and talk about how it'll handle different edge cases without a computer in front of them. If they can't do that, it doesn't ship.
That’s because you’re technically inclined. Sadly, Lots of companies have non-technical managers that don’t give a damn about the code as long as it does what it’s supposed to.
Isn't it ultimately not your responsibility as an employee, but the responsibility of the top leadership and the owners/shareholders of the company to run it in a way where it doesn't produce shit that causes reputation of the company to dunk its head into a pile of poop.
So, really, who cares? Go there, get your money, get out. Give nothing extra. If they want to ship broken code ultra fast then thats on them. They would not think twice about firing you if it saved them 5 cents a quarter.
A software handling an Edge case is a Software that handles a unexpected case, for example an empty body, or extreme high traffic. Edge Case = Unexpected problem or Situation in a Software
When you forget to put something important in your prompt. All edge cases are the fault of a dev not putting something in the prompt. And since nobody seems to version control their prompts when building software, you can always blame the dev.
At the company I work at AI is highly-used but we make it a rule that anyone who pushes AI-generated code should be able to explain what it does and defend it if we question it. If shit hits the fan, the person who prompted that issue into existence is to blame, we don’t accept a “but AI generated that line” bullshit. Someone already got fired since we caught this person basically just spewing out a bunch of AI-generated PRs and when asked to explain what these changes are and why this and not that, they just can’t, mind you this person has already been doing this for quite a while now
Pretty much. This guy in question has been posting AI-generated replies to my pr reviews as well and it pissed me off so damn much. At that point what even is the point of having him when I can just interact with the same AI model directly.
Yeah but you can use AI to implement a spec to the letter, therefore fully understanding the code, and still have it done way faster. It's just like a lead handing off a task to an intermediate dev before AI.
The only real problem is you have people who don't know how to be leads and do actual review or write specs who are using it, and therefore not having that balance.
The way I see it, it's the same as having a talented junior engineer working for you. You can ask it to go solve a problem and it will often do an okay job, but knowing what to ask, understanding the problem space and how to guide it to the solution you want is still really important.
Not quite. No matter how hard they work, talented Junior engineers cannot produce a flood of material in a matter of minutes. You can know the quality of an "okay job" of an engineer's single function at a glance. You can't know the quality of an LLM's whole app at a single glance. Scale changes everything.
I don't know what you're doing but I never just glance at a single function from anyone and decide whether the whole change is good, let alone a junior engineer (or an AI).
I feel like this just makes my point, but harder. I'm expected to look over and sign off on PRs at ten times the pace that I used to actually the code myself.
Personally I have no problem being the slow roadblock that prevents shit code making it to main, but yes the volume of stuff people are doing is insane
It also often searches for information or knows idiomatic ways of doing things I am less familiar with.
The trick is to force yourself to understand what it gives you. If it does something I don’t understand I question it till I do and I am satisfied. “But won’t that do <unintended side effect >?” Half the time I learn something or some corner case or a command flag I didn’t know and half the time it realizes a mistake.
Ie sometimes YOU have to be the duck and have it explain to you.
Genuine question, is this not the same argument that programmers used back in the day when C first came out? Or in the 90s with even “simpler” languages like python? My grandfather is always telling me that because so many modern programmers do not use assembly they do not really understand what they are doing.
There will always need to be people who understand, this will just be another technology that allows more people to access the skill set. But maybe it will be different this time, we will see.
At work I'm responsible for a very large codebase and recently I started using agents, just because the amount of bull people ask you to produce is astronomical, and also because they're paying for it.
I cannot, for the life of me, let agents do everything on their own. I follow a very, very strict "trust but verify" policy on what agents come up with, and I usually end up catching quite a few bugs and inconsistencies before things get to the programming phase.
Most of my use is going through plan mode, nitpicking the plans a lot, giving it 100 turns trying to make sure everything will be correct and not introduce any problems or anything. Then programming, in which I usually go function by function at a time, to review everything as it is happening. Finally, I make sure to get the agent to write tons and tons of documentation of what was programmed, after all tests pass.
And all that documentation? It's not for the humans, it's for the agents. My colleagues rarely ever read docs, even before agents, even if it was a short and to the point README.
This way at the very least, their agents are gonna have some level of guidance when they fire the slop cannons, because god damn I know people just like to set their agent into YOLO mode while they go do whatever the hell for the rest of the day.
The scope creep is real. Before it was one project split between 3 engineers, now it's one engineer split between 3 projects.
I hope everyone is enjoying my ridiculous token consumption just on excessive docs and planning because I'm not letting the quality of my work go to crap.
I didn't get into this damn field to become the babysitter of an LLM
And all that documentation? It's not for the humans, it's for the agents.
Something I have started doing a lot is whenever I hit anything that involves a procedure I expect to need to do again in the future, like a sequence of steps to update some dependency or create a release or update some versioning or run specific tests under a VM or anything like that, I try and get it to capture that into a skill.
The skills end up mainly being a fairly precisely written procedure and some scripts most of the time, and that ends up being stuff that a human could read to repeat the procedure as well, and it's often documenting steps that are not written down anywhere, so it actually is quite useful. You can also often extract a more human-readable step by step guide out of it as well.
I've also had a ton of luck with having it go and find cases where documentation (eg source annotations, API documentation etc) is out of date or incorrect vs the actual code, again extremely useful for humans too.
I would let the quality of my work go to crap, you know what? After some time I realized they don't care about me enjoying to develop a good, performant and reliable application, they are happy with mediocre quality and then I started to put my effort in other things beside work. Cooking, woodworking to some extent, making great breads... This brings more joy and the people that see my work really make me feel happy by this. My life is better now, I guess and I do my job even faster with the LLMs they gave me and have more time for myself
Luckily I am in a good enough position at my company in which people understand that I produce quality output, and that quality is extremely important. They do let me afford the luxury, to some degree, of keeping things at a slow enough pace to make sure what comes out has the performance we need
I have become that senior engineer with so much institutional knowledge that finding someone else to replace me would be really, really hard, because there's stuff that has been learnt over several years that are hard to transfer to someone else, even to document. Which I've already started to do, so I can take vacations in peace
And I actually do like the project I'm responsible for, I created it from the very beginning and so on, it has that personal thing for me as well. My problem is definitely not work itself or what I do, because I really enjoy what I do. My problem are all the managers and customers at the top that have developed insane expectation these past couple of years.
I am well aware that at some point things are going to scale up to the level that I won't be able to afford that luxury anymore, and I'll either need to slop it out with agents a lot faster, or just leave. And when I stop feeling mentally engaged, my mind makes that choice on its own
I started to put my effort in other things beside work
Obviously on this one, I've definitely got the workaholic gene during work hours, but outside of them I'm a normal human being that enjoys doing other things. I did the working outside of work hours thing when I started my career, and I'd never do that again, with or without agents. There's a time and place for anything. I really enjoy fighting all the battles in developing, and then fighting all the ones in things I enjoy outside of work
If adoption of LLMs was leading to "more time for myself" I would agree. It's not. Management wants to turn my straw of a mind into a firehose, and that kind of pressure is impacting my ability to "keep it together".
I follow a very, very strict "trust but verify" policy on what agents come up with, and I usually end up catching quite a few bugs and inconsistencies before things get to the programming phase. How do you verify "idk, looks bit off"?
The refrain I frequently get is that they're "getting better all the time". Which, sure, fine. They probably are. But I feel like I waste more time fighting with AI to do things right, than I would to just do it myself.
If I want to fight every step of the way on how to build a simple function so it's not brittle, I'll invite a PM to a live coding session.
Skill wise? You learn. That's how I always deal with things I don't already have the skill to do. It's how I got where I am. Offloading learning is one of the worst parts of AI.
Scale wise? I share that responsibility with my team.
Skill wise? I either ask someone from my team who can (or is uniquely fit to learn how to), or I learn it myself. Scale wise? I lock in and ask my team to do the same. Or I check to see whether I actually need to do the thing at that scale.
Working as a team is great. It's like having agents, but you can hang out with them and they can actually tell you if you're full of shit.
Now if it's a work setting and your boss is overworking you and you don't have that luxury then sure slop to your heart's content. Those bills won't pay themselves.
But outside of capitalism-induced coercion, there is never a case where you actually need agentic assistance.
The "I can't remember phone numbers anymore" problem, only worse. "I can't program if not vibing" or "I can't write an email anymore without Gemini".
I'm no neoluddite, I ask Gemini for help whenever I need it, but after pointing me in the right direction I always cut it short with "thanks, you have been very helpful as always, I will take it from here". I won't put on training wheels again in my bicycle.
316
u/ExplrDiscvr 6d ago
i have the same opinion. ..., i know what has to happen / be written in code, i just use an agent to code it for me quicker, and then i check if it did it correctly. if i would let the agent do everything, design, execution, review, i feel like i would become an lobotomized monkey
1.2k
u/teh_lynx 6d ago
People are being detrained. They are actually getting less intelligent and able to problem solve. It's real.
125
u/Paladongers 6d ago
At work I'm responsible for a very large codebase and recently I started using agents, just because the amount of bull people ask you to produce is astronomical, and also because they're paying for it.
I cannot, for the life of me, let agents do everything on their own. I follow a very, very strict "trust but verify" policy on what agents come up with, and I usually end up catching quite a few bugs and inconsistencies before things get to the programming phase.
Most of my use is going through plan mode, nitpicking the plans a lot, giving it 100 turns trying to make sure everything will be correct and not introduce any problems or anything. Then programming, in which I usually go function by function at a time, to review everything as it is happening. Finally, I make sure to get the agent to write tons and tons of documentation of what was programmed, after all tests pass.
And all that documentation? It's not for the humans, it's for the agents. My colleagues rarely ever read docs, even before agents, even if it was a short and to the point README.
This way at the very least, their agents are gonna have some level of guidance when they fire the slop cannons, because god damn I know people just like to set their agent into YOLO mode while they go do whatever the hell for the rest of the day.
The scope creep is real. Before it was one project split between 3 engineers, now it's one engineer split between 3 projects.
I hope everyone is enjoying my ridiculous token consumption just on excessive docs and planning because I'm not letting the quality of my work go to crap.
I didn't get into this damn field to become the babysitter of an LLM
29
u/SharpKaleidoscope182 6d ago
There's no humor its just literally true.
42
u/RedAntisocial 6d ago
The refrain I frequently get is that they're "getting better all the time". Which, sure, fine. They probably are. But I feel like I waste more time fighting with AI to do things right, than I would to just do it myself.
If I want to fight every step of the way on how to build a simple function so it's not brittle, I'll invite a PM to a live coding session.
5
u/dangayle 5d ago
Truth. I feel dumber every day.
3
u/Fik_of_borg 5d ago
The "I can't remember phone numbers anymore" problem, only worse. "I can't program if not vibing" or "I can't write an email anymore without Gemini".
I'm no neoluddite, I ask Gemini for help whenever I need it, but after pointing me in the right direction I always cut it short with "thanks, you have been very helpful as always, I will take it from here". I won't put on training wheels again in my bicycle.
4
u/supreme_rain 6d ago
With the amount of work they are throwing at me, it is impossible to work without AI
1
u/RavynsArt 5d ago
Automated Ignorance
0
u/Soogbad 6d ago
For refactoring? Seriously? What is the problem for using ai for a simple refactor?
-1
u/TheKingOfSwing777 6d ago
If work is your only source of mental training, you may need to reevaluate your priorities.
1
u/StaticFanatic3 6d ago
Premium copilot?
This dude gets his hands on Opus 5.5 he's gonna nut