Why I haven't even started using AI ☝️
Its a strange feeling. I kinda get it, its easy to turn off your brain. But thats KINDA why I get paid. To think right? To solve the issue whatever it is.
Yeah. It's not why I became a programmer, to tell something else to program for me. Might as well find another job in that case.
Our job is to think of logic patterns that solve problems, not necessarily to manually type them out ourselves.
Its valid that the typing part means something to you, im just saying it is possible to integrate it without turning your own brain off.
The reason why I like the typing part is because it forces me to really think about my code. Often enough I realise that the model I had in mind for my code is not perfect and that it makes sense to change it now, so that future development gets easier. If I would have outsourced the typing to the AI, its possible, that I would have not realised that. This is especially important, when thinking about how I want to integrate a subsystem into the rest of my codebase, because that is nothing I would outsource to AI.
I enjoy the typing part as well, yes.
i disagree with this take, when i type code out i start to see flaws in my own logic and am able to adapt it because i can start to see the bigger picture as it comes together. also when i start to see code smells i can decide to change my approach and refactor it to fit the problem better.
AI just gives you what you ask sometimes. sure it does it quickly but it doesn't care about those logic bugs while introducing more through misunderstanding of intent. good luck finding it in review, especially when you have 10 PRs of 5-10k lines to review in a day because your manager has lost their mind and other developers appear to forget libraries exist. oh and you had feedback on one of those PRs? well lets just regenerate a complete new codebase and start from scratch.
i forget who said it but they mentioned it's a DDOS on human intelligence and energy and i really have to agree.
Thats the skill, finding them in review.
Its valid to think that sucks and is perhaps less enjoyable than doing it yourself, but I think a lot of things are going to head that way over the next decade or so.
These coding LLMs are essentially like a vacuum that sucks your brain dry. Anything you do with it is used to train: those comments you leave in a PR, the instructions you give within the chat thread, the manual fixes you make to the broken output, etc. So you lose ability, while the models gain ability.
The logical extreme here is that, in the future, the only way humanity will be able to code/write/design/whatever is through LLM products, because everyone forgot and stopped learning.
Whether or not you think that's progress, I think everyone can agree that what is definitely bad is that those models are centralized and controlled by a small group people (who also happen to be the worst people). It is the ultimate tech bro monopoly strategy, to win complete control over 100% of the high skill sectors of our economy. Any child not born to a billionaire family circle will only be able to make a living from physical labor.
the only way humanity will be able to code/write/design/whatever is through LLM products, because everyone forgot and stopped learning
Not very extreme from what I see.
It regularly happens for a lot of things to smaller extents (who can make a computer to run their code? I'll hypothetically give you RISC V source and lots of money for materials and see if you can manage without giving said money to the company that creates fabrication machines) and AI just reduced the bar for the user, in a way that enough people might just want to give up trying to understand how stuff works.
Use it to skip the part where you type it all out yourself, and go straight to the part where you review the draft code.
Its not a 'do my job for me' imo its predictive text on roids.
The part where I type it out is the part where I come up with better ways to do it, though.
Also the part where I store a mental map of it so I know where to look when something breaks.
Thats valid but likely not the only way you're capable of doing it, just the way you're used to.
You are most emphatically not.
AI is as good as the human in the loop. Two rules would help in the long run: accountability (AI proposes, dev accepts, therefore dev gets the 2AM call when it hits the fan) and understanding (thou shalt not commit code thou cannot explain). If you have the power to push these, you have a fighting chance. Otherwise ask Claude to polish your CV.
Good luck with that when management is dumb and only looks at number of lines committed and PRs reviewed. Then those who commit with reckless abandon and rubber-stamp PRs are seen as superstars while those who take care are seen as slow and holding up the process.
I remember when the numbers of lines of code per developer were a thing. Or fix in one go, where test failures counted against devs ratings. This is neither the beginning nor the end of shitty KPIs mandated by clueless management.
I cant event call it iterations because no one learned anything making the last project.
You got the right point.
It's a really mixed bag. I was a bit of an AI laggard for work stuff, while most of my org went all-in. Some stuff worked, most stuff didn't. Things that didn't work:
- Everyone is an engineer now (lol)
- Replacing engineers
- "Software factories"
- "Agentic product design"
- Intern + Claude = senior
But some stuff did work, and most of it was our more senior and technical staff's usage of claude. I'll admit that after I saw my peers hop on board and truly accomplish impressive (functional) things, I dabbled more and I think I have a rule of thumb that helps me. If I'm already a SME, claude may turn me into a super dev. I can smell bad smells, stop it early, and generally know what decisions I need to make up front. If I don't already know what I want, I NEVER let claude drive. Letting claude make decisions is a BAD IDEA.
So honestly I think it depends on who's using it and how.
My problem is that it's killing the next generation. When used properly, AI is replacing junior work. In a decade, all the current seniors will be a decade older and burning out and there won't be any new ones to take their places.
Oh I agree with that as well. I have no idea how I would be a junior on this industry now, nor do I even know how to manage juniors anymore given management's expectations. We're gonna have a real dearth in some years and I don't know what's gonna happen.
This was an issue before LLMs, Senior developers just doing all the work because it was easier and they were under pressure of a deadline. Maybe if a Senior over committed and they had to YOLO with a junior to do a small part to have any chance of meeting expectations, that would be easier to replace with a LLM. But in that case, is a junior really learning anything that they couldn't by self learning anyway?
If you really think the answer is still yes. There is usually, always something to throw someone at and seeing what sticks, It will just fall in the maintenance realm and not on some critical path. That's how I was "trained", got almost no feedback because it wasn't important, and ultimately failed because I was mislead and had to do it twice.
Training someone up has always been intentional IMO, LLMs just makes "necessary" accidental "training" easier to avoid.
Worse case if a junior is hired, there is work to find for them, and throw them at.
Its pretty good at SQL that already exists! And it of course heavily depends on the model. And theres the rub. I think we spend 1.5x for devs now cause of the tokens haha.
Claude can do some crazy stuff thats for sure. But I recall there was code generators that did entire apps before the AI boom. And they were more reliable but more static. And it keeps making like .75 of what you ask, then you have to spend twice as long to debug. At least in my opinion. And worse is that no one can read the code so they dont know what it does. The devs just go, well ill ask cluade to do it instead of taking responsibility. (old man noises)
I also think org rot is real and is a different problem. Or at least... related but distinct.
Corpo leadership is completely brainrotted by promises of LLM sentience and firing half the company and I have no idea how to manage upwards on that front.
Its pretty good at SQL
Eh 🤷♂️. Call it anecdotal if you want, but this is my experience:
The imbeciles who manage our ERP silently pushed some update that must have removed some indexes because suddenly several complex queries were one or two orders of magnitude slower.
While I got to work on optimizing them, a colleague who's outsourced most of his thinking to LLMs got what according to him was “the most powerful model” (some flavour of claude, I assume) to take a look at one particular affected query relevant to the project he was working on.
To be fair it went for more or less the same approach I was taking (storing intermediate results in table variables, spending memory to save speed, though it used temporary tables instead for some reason), but in a significantly more inelegant and inefficient way than I would have (for instance, it put SELECT *s — from tables with hundreds of columns! — into the temporary tables, when we only needed a few columns; an absurd waste of memory; it also missed several other optimizations, being apparently happy with “good enough” instead of trying to be thorough).
Happy with the result he pushed it into production, while I kept working on the rest of the queries, managing to also bring them back to reasonable times.
Couple days later, ticket comes in about that specific query being slow again, for particular parameters. I'm not sure what was wrong (the design of the database is absolute unadulterated shit, but it belongs to the ERP anthropoids and we can look but not touch, and have to work around it), but in some specific cases some joins produced many duplicate results, leading to massive slowdowns. While diagnosing that I also noticed that some of the values it produced weren't correct.
So I rewrote the whole thing based on the work I'd done with the other queries, and now it works properly and efficiently, and significantly faster (at least until the ERP assholes break something again).
TL;DR, sure, the machine quickly produced an apparently working solution (I don't know what the cost of the tokens was, though), in much less time than I could, but the result was ugly, poorly thought out (which, I mean, since it was made by something that can't think and just statistically processes language, I'm not sure to which extent can be a criticism of the technology, but is a criticism of those using it), less efficient than mine (and I wouldn't call myself any kind of SQL master or guru, I just meddle), and failed in some particular cases. I was not impressed.
Don't you have tests for all that 😰?
Like a CI pipeline with tests? You just push stuff?
Didn't catch the cases in which it failed.
And the ERP troglodytes don't seem to have tests, no. Obviously not for our stuff (unless they're testing to make sure it breaks), and it certainly doesn't look like they do any kind of testing for theirs either.
Good luck my dude!
Thanks.
Hope is at some point they'll break something important enough that the boss will consider that it's costlier to keep doing business with them than to migrate everything. 🤷♂️
Meanwhile we're porting as much as we can to in-house solutions. Trying to minimise the amount of work needed to transition away from them.
But some stuff did work, and most of it was our more senior and technical staff’s usage of claude.
Almost as if the senior staff sees it as a tool in a toolbox instead of a subcontractor.
It comes down to knowing what a UX is, and how everything underneath works together. This is "computers" all over again. Growing up alongside the evolution of the stack gives you a special background in what goes wrong, why it goes wrong, and how to fix it. Jumping into it when it's gotten so abstracted it's not possible to understand the stack from the ground up is where this sort of slop comes from.
MFW when management discovers the rapid prototyping technique, but forgets that they’re only prototypes.
There's a reason the term "protoduction" was coined.
It's a story as old as time itself.
Just see if you can get it to work; don't worry, we'll make it right before we ship.
Honest question, in your opinion, how experienced was the development team prior to AI being introduced? What level of code quality could be expected? And what was the average velocity for development projects?
I have substantial development experience prior to AI and after. I also have spent the last eight years at of the the lagest technology companies advising a wide variety of our customers on implementation.
I can tell you that both my own experience and what I see at customers is that if you already produce low-quantity code and/or are not truly development minded, then the AI tools will largely reflect that. They are tools and require proper direction just like a human. If I give it a three paragraph prompt to create some app it will probably do it and it might even work, but it likely won't be reliable as you have experienced. However, if I put on my software architect hat and give it a detailed instruction file which coding standards, architectural patterns, frameworks, etc. It will usually produce a pretty good product.
As the age old computer adage goes: Garbage in, garbage out.
Honest question, in your opinion, how experienced was the development team prior to AI being introduced?
At work you have to have a college degree and at least 5 years of experience. Generally thats the case. I think at most we have one person 20ish years of experience. all the way to two years straight out of college.
What level of code quality could be expected?
Well we had CI/CD, testing,etc... in prior projects. Now its just a toss up what does what. Its better now actually haha. Because docker and other containerization tools mostly rather than AI.
And what was the average velocity for development projects? No idea. I can say we accelerated like mad after beginning of this year. So 10x projects at least.
I get that giving it a VERY specific detailed prompt can get better responses...but at that point, I can just prompt myself and call it good. I am the AI/worker at that point.
I'm in the same boat, although the vibe coders where I'm at are a bit more put together so sometimes they do get something out that's not entirely half baked but generally only CRUD apps.
They are however using it A LOT for research which is a huge fucking problem. I've had to read a bunch of "vibe papers recently" and it's been a mess.
Very unhappy.
Your not alone, Ive stopped using LLMs for any of my work. It's doesn't have any net value gains for me. The work is shittier, more expensive in the long run, less secure, I don't grow as a developer, and locks us in to using LLMs more.
Edit: and to add I am not old by any means
Just wait until they make your PMs "engineers" because "Claude can do the work" so they literally just prompt Claude all day and raise the shittiest PRs without know how to even use Git or Virgin, Claude does it all for them.
I tried to AI a project at work. Once.
Yes it did the job but it had poor error handling, logging and zero standardization/structure.
I tried again with writing a template file with my own code snippets and blocks.
It did better. Still nowhere near done, but I used that as a first draft. I'd say half done to my standard. Deleted/reworked/added code.
I guess it saved time at that point. Still can't see a whole ass project being full AI gen.
What is your question exactly? Do you guys test and review the code? It sounds like you don't.
Ask Experienced Devs
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient