r/softwareengineer • u/Secret_Quote_5941 • Sep 24 '26
Anyone Still Manual Coding?
My company still lets employees manually code because they want people to understand the codebase. We have Claude accounts which we can use as much as we want, for generation, testing and reviewing. The one rule we have is all code must be capable of being reviewed by a human (so no several thousand line PRs, where the only solution is to let AI review).
Given the increasing use of AI (as perpetuated by the media and all CEOs who claim to have fired their engineers), how many of you are working like this? I feel like it's very rare now.
EDIT: quite surprised at how many people still manually code and are loving it (acknowledging this is a minuscule sub-set of all SWE out there). The meat proxies are growing though under corporate pressure to ship fast. I shall enjoy while I can!
3
u/coldfeetbot Sep 25 '26
Nowadays instead of making you leet code in interviews they should show you a 30 file AI-generated PR with a hidden bug, ask you to describe what it does exactly, how to improve/simplify it and why it wouldn't work.
1
45
35
u/arihoenig
Sep 24 '26
•
Of course. If anthropic or openai are the only ones who understand the code base, then they can essentially charge whatever they want.
9
u/Frequent_Bag9260 Sep 24 '26
They’ll be undercut by cheap AI models like deep seek. The frontier models are faaaaar more advanced that what almost every developer needs. There’s no reason to pay for it when you don’t need it
→ More replies (3)→ More replies (5)4
u/muuchthrows Sep 24 '26
Just because no one understands the code base doesn’t mean no one could, given some time.
6
u/arihoenig Sep 24 '26
Sure, but most companies can't just go quiescent for a few months while a bunch of devs learn the code base.
→ More replies (33)
17
u/em07892431 Sep 24 '26
My company gives us a a fixed amount of credits and requires that all production code is reviewed by a human. I really appreciate it.
I use my ai credits to create better developer tooling, neat dashboards, and fancy proof of concepts, and to generate tests. It makes my job feel more creative instead of less.
Im sort of confused by people who only vibe code at a their jobs. Was the only thing you did before ai just writing code for tickets? Does your company spend thousands on your AI bill every month?
→ More replies (1)5
u/start_select Sep 24 '26
I think it’s wild how people fail to manage themselves (I’m not talking about you).
I have effectively unlimited credits across my tools. But that’s because I don’t use AI for everything and am a principal. So when I burn $2000-4000 on something it was worth it lol.
Some days Claude writes all my code. Not all days.
0
12
u/Flashrob01 Sep 24 '26
Yup. If you can't read and understand it, you don't own it.
And AI will NEVER have ultimate responsibility for anything (unless you want to create more problems).
4
u/Frequent_Bag9260 Sep 24 '26
That’s all well and good but you’re forgetting that the majority companies genuinely don’t care.
→ More replies (2)3
u/brelen01 Sep 24 '26
Yep. My personal rule is little to no LLM use until I can tell my boss "claude did it" if something breaks
→ More replies (15)2
u/idreaminecmascipt Sep 25 '26
Its weird to think if you produce enough bad code, you can be fired, but the AI will not. What a time to be alive...
10
u/HarryBalsagna1776 Sep 24 '26
We are still manual coding where I work. We are programming PCUs and machinery though. We do not have massive amounts of code.
6
u/jeffry_7 Sep 24 '26
That's awesome. I manually code to learn and not lose touch. For work, it's blended, I need to know what the LLM changed/updated.
6
u/Advokat_Huld Sep 30 '26
Yes, we do. Our codebase has 17 Million lines of code and 6 people are able to understand what is going on. I am one of them😎
2
10
u/boringfantasy Sep 24 '26
Yes, since it's a million times cheaper and sometimes just as fast. Why is anyone spinning up Claude to change a couple lines is beyond me.
I'm still noticing a huge diff between those who fully vibe code and those who do at least some manual coding. The ones still manual coding are always raising really good issues in reviews that nobody else manages to see (including AI!).
7
u/start_select Sep 24 '26
There is also a huge difference between vibe coding and AI assisted coding.
Vibe coding is simply describing the desired end result while throwing execution semantics to the wind. Which is what people don’t get about how prompts and spec based generation are not the next abstraction over programming languages. Natural language is not discrete. It doesn’t define execution/instruction semantics well or ever better than code does. Not without requiring way more text than code.
There is a middle path between that and manual coding. If you ride the middle path then the occasional vibe prompt is perfectly fine along with some manual coding too.
→ More replies (1)3
u/sehrgut Sep 25 '26
Vibe coders are incapable of understanding code, which is why they can't even effectively review the shit that results from their prompts.
2
u/stop_deleting_plz Sep 25 '26
It's not cheaper. The AI firms are $3.3 trillion in debt. You're still in the free trial period. Enshittification is coming with the IPO.
5
5
u/Exyui Sep 24 '26
I do it for small targeted changes. If it takes as long to type a prompt for the ai as it would for me to just write it, then I just write it.
5
u/mightshade Sep 24 '26
Yes, almost always.
Just this week I released two new features for an internal project, 100% hand-written, and they just worked. I felt so proud, and that's what motivates me. I'm not worried about being "left behind" with quality software engineering. I enjoy this.
4
u/Civil_Fee_7862 Sep 24 '26
I still need to review the code. Most of my time is spent doing that, (and waiting for the agents to finish). But in terms of manually coding stuff? Almost non-existent now.. The agent does it better and faster and I run out of reasons to type it manually.
→ More replies (3)
4
u/stop_deleting_plz Sep 25 '26
Every single day as a freelancer and hobbyist. I'm not anti-ai, I use it all the time, I just don't let it write code because its stupidly hard to maintain.
4
u/LopsidedTwo4867 Sep 25 '26
I write around 90% of the code with no LLM. Even though my company blindly push for it, I have luck that we are not micro-managed. Also, some people that I work with are not really fast or are slackers, hence I have time to plan and do my part by hand. Some people that know me may call me "anti-ai", but the truth is that I tried - so many times - to comply with company policy and prompt my way towards feature or use harness. And it is always over-complicated - a lots of unnecessary lines of code etc.
However, I find LLMs very useful for code reviews - they find some bugs that just escaped me.
The mental model I use is as follows:
Never outsource thinking:
Example: I needed to transform some data with Array.reduce. I knew exactly what I needed and could just tell LLM to do it for me, but then I would lost opportunity to push myself mentally. Hence I spent 20 minutes doing it, and felt like I am getting better by straining my brain. If I don't do this, I enter brain rot state in a matter of days.Use it only to do the work that will not be beneficial to me and would only waste my time:
Examples: put parameters in object instead of plainly passing them and make interface for them in types dir; fix the css; write me a function that returns some range etc etc. This way, I am less tired because I don't need to look into this LLM code a lot because it is simple.Use it for implementing some library I am not very familiar with, in situations when I have deadline:
Example: I needed to implement rich text editor on client-side and LLM did it all because this was expected to be done fast. I asked it to explain every facet to me, briefly looked at docs and shipped it. I'm not satisfied with using it in these instances, because I never really learned this lib but it was urgent. If implementation was more encompassing I would not have used LLM to write but would request more time to be sure what I am shipping.
The reasons I write by hand is due to too many examples I've seen recently of how LLM work can brain rot me or make me slower or make hell for code reviewer or for the QA
→ More replies (1)
4
u/Low_Tune7301 Sep 25 '26
Just joined a legacy org that hasn't fully adopted ai after being ai native for the last few years, an enter button meat proxy if you will
Holy fucking shit do I love it, just spent the afternoon wrestling and refactoring naming conventions in a 3000 line file, it's like I've found my old friend again.. how I'll miss what this profession used to be when this is over, I'm only here on contract.
4
u/Any-Woodpecker123 Sep 25 '26 edited Sep 25 '26
I still do everything 100% manually. I don’t understand the PR restriction though, if I get several small PR’s for one feature I won’t review it till it’s in one big PR, I want all the context in one spot.
→ More replies (3)
4
1
u/-PM_me_your_recipes Oct 01 '26
I would love that kind of work environment.
For us, we are required to have at least 95% of our code be AI generated. They told us to even use it for typos and simple one line fixes. Because of metrics or whatever.
The head of engineering fell for the "AI makes all developers 10x developers" linkedin garbage, and is very upset that we aren't meeting that impossible standard and are ruining his timeline. Our CEO is promoting vibe coding classes for non engineers to make internal tools for the company. What can go wrong?
Trying to jump ship but job hunting is pretty rough right now.
1
u/Secret_Quote_5941 Oct 01 '26
That sounds tough...
Don't know what kind of places you're looking at, but if it helps, there's so much competition for fully remote roles, it really opens up doors if you're willing to go in the office.
3
u/LRCM Sep 24 '26
I'm still manually coding, but mostly because I work in a very niche industry.
→ More replies (8)
3
u/Curious-Function7490 Sep 24 '26
Yeh, this is pragmatic.
We are about to go into fixed quotas per engineer via Github Enterprise also.
3
u/start_select Sep 24 '26
The gist you should get from reddit isn’t that you need to write everything with AI. It’s that most people posting here work for sweatshops.
Everyone at my work uses Claude Code and GitHub Copilot. No one uses it 100% of the time. Because we are talented. And we don’t work for a sweatshop.
→ More replies (1)
3
u/Squidalopod Sep 24 '26
Sounds like your company has figured out that producing a greater amount of code does not, in and of itself, translate to a greater number of happy customers who are willing to pay more money.
3
u/pazProgrammer Sep 25 '26
Um, are you hiring?? Because I would love to still be manually coding haha.
3
u/the_glutton17 Sep 25 '26
I almost only manual code. The only thing I've ever asked ai to write was 1 or 2 bat files for a special project.
3
u/MangoTamer Sep 25 '26
Letting AI do all of the coding is like giving a 5-year-old a machine gun and telling them to shoot the target. Like yeah, they're going to hit it.. but it's going to look like crap when they're done. And they're going to use way too many bullets.
I'm getting really tired of seeing multi hundred file pull requests that nobody bothered to spend time reading through.
→ More replies (9)2
u/djamp42 Sep 25 '26
I think the mind set of "What the code looks like" is going to be the hardest thing for professional developers to forget in the age of AI Coding. Code structure was insanely import for humans, i'm not sure it matters at all for AI.
→ More replies (4)
3
u/Key-Lie-364 Sep 25 '26
I write manual code and just rinse through LLM review.
I can't imagine switching my brain off and letting auto complete do it for me.
And frankly the kind of code I do, embedded, kernel, bootloader, BIOS I don't really think generative AI is very good at.
Analysis yes fantastic tool.
Generative?
Nope still ultimately crap, people seem to confuse "prima face" correct with actually correct.
Sadly it seems corporate software is exactly as bad as you'd expect and any old standard of hallucinatory word salad passing as code will do.
3
3
u/Shadow_Mite Sep 25 '26
Yeah we aren’t mandated into AI we’re stepping it back if anything. Just acting like it’s not there and requirements need to be shipped however that happens and if you ship the code you own the code however good/bad it has to fit the agreed upon standards
3
u/LetscatYt Sep 25 '26 edited Sep 25 '26
I don't believe outsourcing thinking, essential knowledge and essential business processes to a machine controlled by big tech has and ever will be a good idea.
If you're not manually coding you're not in control, loose your skills and become even more dependent on this technology. So while your brain rots away unused your company has to foot the bill as soon as ai actually starts to charge their actual running costs.
And for anyone saying I'll get left behind: Coding is just a really accurate way of writing specification , even if ai were perfect in every way. The Specification for my apps would have to be reaaaaly precise - to the point where structural language wouldn't be accurate enough. At that point I might aswell just write the code.
I really don't get this whole ordeal.
3
u/Pozeidan Sep 26 '26
Manual coding no. AI assisted coding yes. AI assisted reviews yes.
Code still needs to be reviewed and approved by a human. Not everyone is able to produce security compliant code that is maintainable even withh AI, many produce slop. No one wants a sloppy codebase.
3
u/AromaticImpression37 Sep 26 '26
I still have to manually code. We have the highest level AI agents at my company and they still make mistakes even for small one line changes. One time a more advanced model tried to delete an entire application that I was working on. if I did not see it doing that and didn’t understand the technical terms it was using while it was doing that I would not been able to stop it. I was telling it to fix one line in a junit btw
I have to manually update the code frequently if I don’t there tends to be issues. My company encourages use of AI but doesn’t force you to so you can technically manually code everything if you want to. I would say if you don’t know how to code without AI you probably would be cooked at my company and we’re not that technically based.
3
u/Lheanarda Sep 26 '26
the workflow i am doing usually is code manually, and let the ai do the unit tests. while some times depending on the project i ask it to audit my implementation or help search for a bug root cause and at the same time i am also searching for one (like racing for a solution).
whenever i delegate my coding fully to ai, i felt not in the flow and felt disconnected with whatever the project i am in. And I do not like these feelings
3
u/----Antonio---- Sep 27 '26
Yes, for the areas I'm responsible for at work. CloudFormation and Python, mostly by hand.
With infra the danger isn't ugly code, it's one property change that makes CloudFormation replace a resource instead of updating it. If that resource holds data, you find out the hard way. I want to have typed that line myself and know exactly why it's there.
Funny enough I use AI a lot on a side project. Different deal though, if that breaks the only person I let down is me.
→ More replies (3)2
u/matt_127 Sep 27 '26
AI is so good at cloudformation, especially if you tell it exactly what to implement. Always look at the change set when updating a stack regardless
3
u/----Antonio---- Sep 27 '26
I understand, however sometimes infrastructure is so critical, so it's reeally risky to blindly trust AI. I need to understand and know where each of code piece is.
Even if use AI to generate a couple of snippets quickly, I go manually line-by-line.
3
u/povlhp Sep 27 '26
Most devs still code at work. Some light AI asssist. But they are vibe coding at home.
Their opinion is, they can’t feel responsibility for what the AI wrote. It is like outsourcing/consulting. When they deliver shit you are left with a mess to clean up.
3
u/pencilking2002 Sep 27 '26
I code completely manually. I work on indie games though so I don’t have anyone telling me to use AI.
I love keeping my mind sharp and figuring out my own problems. Sure it’s frustrating sometimes but I like knowing that I solved the issues on my own.
2
u/Mystical-Turtles Sep 30 '26
Same thing here. I've tried using AI just out of curiosity, and I usually run into one of two scenarios
The training data it has on unity/unreal is... frankly not great. It likes to blend together features from different versions or suggest things that apply to general c++/c#, but not really the way the engines use it. It'll often suggest some roundabout method not knowing that there's a built-in solution for that problem now.
A lot of the time systems are already built and of course it's not going to know about local systems built by one of my teammates. So it comes up with some "almost perfect but not quite" solution. Often requiring so much debugging that I may as well just write it myself from the get-go.
3
u/lnxrootxazz Sep 29 '26
Anyone who don't wanna forget coding should write code by hand. Just reading code will not keep your skills. And my guess is that many will also get worse in reading th3 code without practicing because we learn the best by doing. Reading a book about Linux High Availability Clusters gives me nice theory knowledge but I wouldn't know where to start just by reading. You lose the knowledge you only get by doing stuff. Why you think universities had programing exams on paper long after 2010? New studies show that outsourcing thinking will decrease our cognitive levels over time. And the time is just a few years. I experienced it after a few months of llm usage. I had to stop because I felt my brain melting. I struggled getting things done without prompting the issue. That's a bad development in general. Its definitely the case for coding. So my advice is for everyone to code at least 10 to 20% by hand. At least fix the bugs by hand, keep the feel for the code. Otherwise we will lose some brilliant minds
5
u/TrustyFishCantor Sep 24 '26
All manual. So far it still looks like the professional vibe coders are a vocal minority. AI searches are quicker than digging through docs though.
7
u/abrandis Sep 24 '26
Hand coding is realistically over, it lasted a good 50+ years..
Today the AI systems will code everything and you'll just guide it and adjust its output
→ More replies (2)4
u/Small_Dog_8699 Sep 24 '26
Maybe for plumbing business apps. Youre not building a new novel service like redis vibe coding.
6
1
u/CreamyCornBoy Sep 24 '26 edited Sep 25 '26
[removed]
1
u/Secret_Quote_5941 Sep 24 '26
Is it really 95% of what SWE are doing though? Not saying it isn't because I don't know the actual figure, but I think AI companies are massively overselling it's capability and how many people are using it, just so people jump ship and join in (with the exact concern that you've said).
→ More replies (1)2
u/CreamyCornBoy Sep 24 '26 edited Sep 25 '26
[removed]
2
u/Secret_Quote_5941 Sep 24 '26
Tbh big tech / faang is where I'd expect 100% gen code. They've really gone all in on it. Arguably this is why Microsoft have had so many critical issues this year.
→ More replies (1)2
u/Beginning_Basis9799 Sep 25 '26
I don't think it's 95% either I think it's like 45 - 50% and lessening as token budgets get tighter.
2
u/throwaway-research1 Sep 24 '26 edited Sep 25 '26
Haven’t written manual code in the last several months. For context we build and maintain tons of services probably between 50 to 100 repos are under the responsibility of the team I work with, its mostly latest tech stacks and some legacy codebases plus a lot of cloud infrastructure which is manual work at the moment but we are in the middle of converting it into code as infrastructure and once thats done, ai agents will take over those repos as well so cloud infrastructure would also be mostly maintained by prompting instead of manual changes.
We have also introduced some workflows with the help of ai which I am pretty amazed and surprised to see
2
u/MeatspaceVR Sep 24 '26
Yes, i write 100% of my code the old fashioned way. My least favorite part of this job is reading and understanding other people's code, especially if its garbage.
2
u/Bangoga Sep 24 '26
Most of my code is manual, AI is for search and rubber ducking, or PR review (aid only)
2
u/MissinqLink Sep 24 '26
I code manually often because I want the benefits of keeping my skills sharp and I enjoy it. My job mostly encourages generating code.
2
2
u/Pravejxlab Sep 25 '26
I think your company is doing right. For large scale projects, human are still relevant. Me also manual coding.
2
2
u/Mori-Spumae Sep 25 '26
Yes. Many people mainly code manually at my company (in finance). Management is trying to push AI without providing the resources (tight token limit, outdated models). Some people use it a lot but agents are not very integrated yet.
I think it will take a while for people to not write code here. And for me personally, I do write my code by hand when doing new things. I trust my agents mainly when fixing narrow issues in a codebase I know well and where I can understand the fixes it proposed. Still I often find myself rolling back changes and telling it do to it differently because it missed some important part.
2
u/Fit_Aioli_7238 Sep 25 '26
Almost 60% still manual coding, due to complex ui designs(lots and lots of), weird backend business logics (that varies from project to project under a specific program). Things just cannot get messy.
2
2
2
u/Fit-Notice-1248 Sep 25 '26
Mix of both. Majority ai when I'm doing large features, but still intimately reviewing output. But ultimately I don't understand why this is such a flex for people that they need to repeat it every day. There are so many scenarios where asking an agent/spinning up an LLM is infinitely worse than just doing the change yourself, especially if you already know the change and how to complete the task.
2
u/LookAtYourEyes Sep 25 '26
Yeah, we have copilot in our IDE. But people can code however they want. I will usually use my credits for more repetitive, easy to explain chunks of code like setting up large classes or records that represent JSON. If I used my credits for everything I'd be out in the first week and have to code manually for the rest of the month.
2
u/scrowdum Sep 25 '26
no unfortunately. my company expects things way too fast now. of course i will still do smaller things without ai assistance and do my own manual qaqc of longer scripts but for the most part I am using ai 90% of the time for my dev tasks.
2
u/tara_tara_tara Sep 25 '26
I do because I don’t even work as a software developer anymore, but it’s fun.
I’m celebrating my 40th anniversary of learning to code. It was Fortran on a VAX mainframe in September 1986 during my first semester at university.
I can’t remember all of the languages I’ve learned since then but it’s fun.
I’m involved in a court case and I could have an Excel spreadsheet or a Google sheet to trek everything but I decided to make it fun and build a little program in python and Postgres.
2
u/Appropriate_Ad_4076 Sep 25 '26
From what I have seen, most of the folks at my company site are manually coding with some AI assistance. A lot of the code-bases are for military purposes and have to be developed in closed environments. Hint, I work at a big aircraft company. I like tinkering at home with AI agents though. At least I am employed, for now. 😅
2
2
u/Neppptoon Sep 25 '26
My company only gives us like a thousand tokens per month. So we have to be smart when we decide to use AI
2
u/Nearing_retirement Sep 26 '26
My company refuses to let Claude see our code for proprietary reasons. They don’t trust the license agreement. So we literally have to get management sign off on any code we make visible to Claude.
→ More replies (1)
2
u/Mrio7878 Sep 26 '26
Sometimes you just can't use a GUI and have to code in a terminal. No AI, no IDE. That's why raw coding skills matter. And honestly, that's pretty common when you're messing with the OS kernel.
2
u/9sim9 Sep 26 '26
Any industry that needs security or where mistakes cost money is still mostly coding as normal, with typically some AI for low risk tasks. I find that Juniors especially have bit hit hard with the rise of AI but the really high level coders still have decent career paths thankfully.
2
u/Any_Sense_2263 Sep 26 '26
AI is not a software engineer. It doesn't think or understand yhe code. It's an algorithm and as such in some situations can be very wrong. And can't take rensponsibility for its mistakes.
The company I work for, allows vibe-coded prototyping. The production code must be written, understood, and well reviewed by humans. PRs are limited to 300-500 lines. It means we have to plan well and consider time our colleagues spend on reviewing our PRs.
2
u/triflers_need_not Sep 26 '26
We have a legacy system that they're trying to replace and I still get to code old style on it when there is some emergency. I'm looking at getting a new career entirely, I fucking hate using ai.
2
u/Colt2205 Sep 26 '26
I still write code even with LLMs. We're in the wild west at the moment with using the technology and everyone is going to end up using it differently. It mostly comes down to what techniques work best for designing, learning, validating, etc.
2
u/Colt2205 Sep 26 '26
I'm manually coding and also using AI coding tools. I don't think this is the same kind of jump as high level languages were from lower level ones like C/C++ since it's still a bit loose. Claude produces working answers but it is a working answer based on what it interprets from the developers input, and when prototyping we often don't know completely what we're doing yet.
2
u/diegotbn Sep 26 '26
My company, or at least MY team manager, started enforcing AI usage. Like, I got asked why my token usage was lower than others on my team. So I've started using it more.
I might be old-school and I might need to change my mentality, but unless it's a monotonous task that I can generally trust an AI to perform without oversight, I prefer to work on a problem myself, give it 30 minutes, and only then if I need help I ask Claude. I use him as a pair programmer, or a rubber ducky, and not as an agent that writes code for me or performs any tasks. Other than first round of code review before I hand my PR off to a human.
For me it's a combination of lack of trust in the AI, and me not wanting to form bad habits and get brain atrophy. I like writing code. I like problem solving. It's good for my brain to work through problems. And I can be proud of myself when I do. The code feels like it's mine.
This attitude might eventually make me unemployable without changing my mindset. Which, I think is sad and it will probably result in me adopting AI more and brain atrophy be damned.
→ More replies (1)2
u/Own_Might_1262 Sep 27 '26
I remember during college, when learning to code we were asked to use the Windows notepad instead of the IDEs. The goal was to not depend on auto completion and suggestions. Rather, train the brain to understand the pattern and look for a solution yourself that matures your thinking process.
With the rush, deadlines, and what comparable colleagues do at work, I cannot continue to use Notepad anymore. Now, the next challenge is looming where everyone starts to use AI to do faster development.
2
u/theUnknown777 Sep 26 '26
Yes, we still do. In our team we are expected to know how the features work under the hood so you really can't defer everything to AI.
Personally, I use AI mainly for debugging, writing tests and code reviews in that way I still keep my skills sharp but still take advantage of it.
2
2
2
u/mredding Sep 30 '26
Yes, I still manually code. AI generated code is still inferior to my hand written code - AI seems to have no concept of type safety and cannot be convinced otherwise, there's never enough abstraction.
To be fair, I work with colleagues who are not master software developers, and they're focused on process and delivery, so they're happy to let the AI write better code than they can by hand, which is saying something.
We have a client that singularly keeps our doors open, and they put us on a PIP. Their business is word wide, everyone everywhere recognizes their brand, and we are their only supplier for a thing.
The meat proxies are growing though under corporate pressure to ship fast.
The software sucks. But it's not the fault of AI - the code base is older than that. It's a problem with management. They've run a skeleton crew, we have ZERO QA, and they pressure product development with deadlines - everything is a rush. So they get what they pay for and their incompetence has put the company and everything at risk.
All this is to say technical debt will always catch up. AI will happily generate a lot of slop. I don't know of anyone who prompts the AI: "Now do all this in half the lines of code."
So let the meat proxies generate all the slop. If the company wants to survive, they'll have to hire a guy like me who can actually code to clean it up. We're seeing the beginnings of a whole industry of just refactoring and un-fucking messes.
→ More replies (1)
2
u/AX862G5 Oct 01 '26
Yes, I tune all the AI bullshit out. I worked too fucking hard for this career to have the circus of AI CEOs tell me I’m going to be left behind.
2
2
u/ResolutionThat248 Oct 01 '26
Game dev, major publisher, worldwide studio. We still manually code. We have access to copilot but absolutely nothing agentic. I love it.
2
u/Any_Sense_2263 Oct 16 '26
It's exactly how I work. AI is great for research, brainstorming, eliminating options, rapid testing against theories and prototyping. It helps in splitting features into smaller tasks and with spotting ad hoc refactorings. But fails miserably at producing high-quality and reliable code.
So I use its strengths, not weaknesses.
1
u/cobbly8 Sep 25 '26
This whole thing about needing to know the codebase is nonsense.
Most commercial codebases out live (in a work sense) the devs who wrote it. Do you really think the company just stops changing the code you wrote when you leave in 2 years?
Of course not, a new dev comes in and figures it out.
With or without ai that hasnt changed.
Numerous times ive found and fixed a bug in a codebase i had never looked at before.
Sure knowing it inside and out might make it a bit easier, provide a shortcut of sorts, but it can also be a hinderence as you make assumptions, and its certainly not a necessity.
1
u/stop_deleting_plz Sep 25 '26
In my experience AI code is much more difficult to figure out than human written code.
1
u/Secret_Quote_5941 Sep 25 '26
Yeah, this is more what I was referring to. Yes, it helps if people know the codebase but people do indeed leave companies. It's more so the many LoC AI produces and the rate at which AI does this which makes maintaining it difficult. AI can turn a good codebase into shit if you let it, making it much more difficult to maintain and adding technical debt which the maintainers overlook in the favor of speed.
3
u/Affectionate-Aide422 Sep 24 '26
I haven’t written code since early this year. I do review it, although I expect I won’t by early 2027.
5
u/boringfantasy Sep 24 '26
Seriously, in just a few months? Even Astra still writes egregious code sometimes
→ More replies (3)
2
1
u/BobJutsu Sep 24 '26
Yes. Very similar workflow. I keep the AI usage very tightly controlled. I’m an old curmudgeon, and my guardrails reflect as such.
1
u/TheBigCicero Sep 24 '26
I’m the CPO of a growing tech company and have instructed our teams to code the way you are describing, manually with AI assistance.
BUT…I can see my competitors are picking up speed. I can also see that my team will fall behind in personal skill development.
So I’m about to experiment having the team to move to an AI centric model with these guardrails:
PRDs and specs cannot be AI generated
Shift to emphasis on test cases
Second AI model review of code
Limit PRs to XXX lines of code (# is TBD)
TL needs to understand all lines of code
If any of you have suggestions I’d love to hear them.
→ More replies (2)
1
u/spiderzork Sep 24 '26
I occasionally use AI for some random python scripts. But anything else I write manually.
1
u/QuarterGeneral6538 Sep 24 '26
Ive been taking a bit of a hybrid approach for any bigger tasks
I'll start it off by creating the classes / high level methods and writing some psudo code. Then I can point the AI at what ive started and ask it to implement it.
I find this works well cause I can control the structure. Otherwise AI will just throw code everywhere and it gets messy quick.
→ More replies (1)
1
1
1
u/JeanRalphioTheSecond Sep 24 '26
Not really much manual coding. I try to get the code pretty much like as if I wrote it though. Unlike before, there seems to be no default way as a software engineer anymore, so this is the operating point I have chosen
1
u/dzogchenism Sep 24 '26
I do some manual coding. I have to use Claude though as well but as long as I can keep Claude busy with PR reviews and planning, I can code. I do use Claude to increase code coverage for tests too.
1
1
1
u/Instalab Sep 25 '26
Basically, here is Claude, use it if you want.
Some people seem to exclusively use Claude now, some still code by hand. Not one is really forced to do it specific way.
1
u/AcExSev Sep 25 '26
Honestly it sounds like your company has the best workflow for it ive seen so far. Most either are appaled by the idea of ai being part of their business and the other half want to use as much of it as they possibly can. This balances both
1
1
u/Far_Zone_9864 Sep 25 '26
i do for fun but since all manual programming is basically just as irrelevant i went back to programming for the c64 and Amiga. extremely fun
1
1
1
u/wolfblaze0 Sep 25 '26
Still coding manually on personal projects. Heavily using AI on my daily job, though.
1
u/cherrypickme Sep 25 '26
Hell no. Manual coding is dead and it's never coming back. Anyone who thinks otherwise is living in a mirage. Even Uncle Bob is telling people not to write code manually anymore.
1
1
u/Immediate_Fig_9405 Sep 25 '26
Do you stay up at night thinking you dont understand the compiler generated binary code or the compiler optimizations? I think AI will get to the point where no one will be reading or writing code. Complex problem solving will still require humans but writing code by hand is almost dead.
→ More replies (1)
1
u/andrewharkins77 Sep 25 '26
Just because AI spit out everyline of code, it does not make it less manual. You still have to craft the business logic for te code. No one writes math code, they use a library instead. This is just more of it. You can call it automatic when your project managet can do all of your job. Remember, plenty of PMs cant even write usesful acceptance criterias on their own.
1
u/xerxesdarius Sep 25 '26
Yup same here - we have a human PR review gate. In our case devs don’t feel the pressure and instead spend the necessary time to review AI-generated code.
1
1
u/Additional_Candy_400 Sep 25 '26
Nope. It just doesn't make sense at this point, held out for as long as I could but there's no point.
1
u/soundman32 Sep 25 '26
Only because i'm running out of tokens. I spent 4 days writing 4 new API endpoints, old skool, then kiro did the UI for it in about 30 minutes.
1
u/Rigamortus2005 Sep 25 '26
I've never been employed, but I still work on all my projects by hand because I need to gain domain knowledge
1
u/satansxlittlexhelper Sep 25 '26
I write the spec and tests alongside an agent, then have the agents build the app/feature slice by slice. Each slice is submitted as a PR that requires manual review and blocks any further work based on that PR.
1
u/Internal_Sky_8726 Sep 25 '26
No, but I understand all the code I ship. Because we have the same rule. Humans have to review.
1
u/qrzychu69 Sep 25 '26
I do a bit of both. I of course have the AI plugin in my IDE and ask it to do stuff for me, help me find stuff I don't really remember, sometimes ask it to finish applying the pattern I started.
I use it to get the initial implementation also quite often, see if it works at all and if I like it, sure, I will just commit it. Usually I then start from scratch and do it "properly". As the models get better and better, they do things "properly" the first time more often - worth metnioning.
I cannot overstate the value of AI review though. I wrote in the instructions I absolutely need a release notes line with ticket number from the branch name with a regex I provided, I want to bump the version in the project properties and things like that - general maintenance that has to be done but I don't find interesting at all.
When I am done I jsut say "fresh agent review and fix" - and I can open another worktree and go do something else. That's amazing for me.
I am still not ready to be like "here is a ticket number, do and push, no mistakes" - that doesn't work for me. And we still do human reviews so I have to be able to answer questions
1
1
u/ValHallen96 Sep 25 '26
Sometimes but as time goes on, I don't believe anyone will be unless it's a hobby you enjoy doing outside of work. Companies will not want you if you resist the new workflows.
1
u/FreshFishGuy Sep 25 '26
I do sometimes, depending on the task. When using claude code, I work through a plan with it first, then review the actual edits it suggests, and look at the lines it wrote after as well
1
u/Extra-Ad5735 Sep 25 '26
Tell me you don't have to answer for the mess you pushed to prod without telling me that.
1
u/throawaycscareer Sep 25 '26
Honestly we mostly code the old way, but yesterday I told ai to analyze our code base for the ccs styles we use and apply it to the code I just wrote. Man probably saved me hours of swearing complaining crying and letting imposter syndrome take over
1
u/PickledCloud999 Sep 25 '26
I try to code manually as much as I can and only ise Claude when it's something I've already done or can't figure out a better way to do. But even then, I go ahead and modify things to my liking and if it's gonna be duplicated over and over, then I tell Claude to do it for me or clean it up or make it reusable. I find coding manually is more fun than trying to read whatever garbage any ai spits out
1
1
u/VeryAmaze Sep 25 '26
F500, we don't have an AI mandate but we do get a 500$ budget for Claude Code and 1000whatevers for Devin/Windsurf. Tbh I almost never even come close to the limit 😅(except the month I was prompting like crazy generating unit tests). I probably prompt 90% of my actual coding work, I spend most of the time doing the HLD for features.
1
u/QuackQuackImTheDuck Sep 25 '26
A minority coding manually ? Based on what metric ? The ones given by the shovel sellers ?
1
u/tastygames_official Sep 25 '26
found another pro-AI shillbot
literally every human programmer still programs. Only managers who don't actually know how to program use AI to make shit but they don't know what they don't know so as long as it seems like it works to them, they're OK with it.
1
u/redbull_coffee Sep 25 '26
Sure. Manual reviews, whiteboarding, scaffolding, writing css …
The bots are useful assistants, but we use them with suspicion and lots of oversight
1
1
1
u/jeffvanlaethem Sep 26 '26
I use ChatGPT as a better Google. That's it. I encourage everyone else to use as much AI as they want.
1
u/TheDivinityOfOceans Sep 26 '26
Not really as in manually typing. Just doing the same practice of: small feature changes + reviewing + testing but delegated to AI (as the token limit permits). That way I understand the code without having to manually type it.
1
1
u/RaveHunter05 Sep 26 '26
I'm still coding manually, in personal projects and in leetcode, I got no job so, I guess that's the reason I don't have a job in this era
1
u/tyommik Sep 26 '26
I stopped writing code at the start of 2026. I used to manage people who wrote code, now I manage agents instead: I set the tasks, talk through the logic, and check the specs. Claude does the code review. In practice, critical bugs have dropped to zero. When you're getting around 20k lines of code a month and you also have to actually think through the problem, reading all of it just got way too hard.
1
1
1
u/inductiverussian Sep 26 '26
We don’t have a mandate; we get access to the best models with quite a high budget (4k per tool).
I find that some weeks I lean on AI a lot and other weeks I barely touch it. Complex diffs I will typically implement most of myself; in depth refactors I might set up the interfaces and ensure the prompt is pretty detailed and let it take over. Small and well scoped implementations I’m comfortable fully handing over. I review every line that’s generated.
I don’t understand those that don’t review any code; English is not perfectly compact and most people don’t get all of the specs right in the first prompt. So unreviewed code will make mistakes, will drift from original intent and will cause an outage (not to mention the absolute maintenance mess it will cause in the codebase)
1
1
u/Classic_Chemical_237 Sep 26 '26
I totally understand the purpose of this policy. However, way before AI, human PR is an inefficient process which often result in nick picking and conflict from different opinions and coding preferences.
Also, understanding one PR doesn’t really help. In the old days, you probably get 4 or 5 well scoped PR everyday, so you can truly dive in to understand the code. A big feature is implemented in a series of PRs so you will understand the whole thing, from data modal to UX to analytics.
Now, you can easily get 20 to 30 per day. Even if the PRs are well scoped, do you have time to dive in 30 PR per day? Do you have the mental capacity to do so? And would you remember the next day?
Unfortunately, I don’t think this policy, however well intended, helps human to understand the code.
1
u/MackPooner Sep 26 '26
We are mostly designing the architecture of each app and reviewing 'most' key areas of code but not writing anything manually. We have noticed Claude doing some stupid stuff and have to re-prompt often.
1
u/_some_asshole Sep 26 '26
Yup. I let one shot my prototype. Then I spent three months making it actually work. I’m not convinced ai speeds up actually getting anything useful done that is useful.
1
1
u/DoStopBelieving Sep 26 '26
I manually code changes that are either so small or so niche that prompting AI would make it take longer.
Also, I have thoroughly reviewed a PR over 10k lines. It was part of a much larger set of PRs (that I also reviewed) which was riddled with security issues, data corruption, performance regression, sensitive data exposure, broken features, and astonishing tech debt.
I know people would say just reject the PR, but that was not an option. The original submitter was fired and the boss would not take no for an answer. Everybody on my team wanted to flat-out reject the changes. I decided that since we were being forced to keep the changes that I would review the PR and build a remediation plan. Hundreds of PR comments later (and commit comments since one of the PRs couldn't even show the diff), and ~6 bulk remediation (Epic-size) tickets later, we successfully remediated the issues and got it merged and deployed.
The code had so many issues that an AI review would have had to iterate many times to spot them all, not to mention that spotting some issues required specialized domain knowledge unlikely to have been indexed by AI. IOW - AI can certainly assist in those thousand-line PRs but you still need to look at the changes yourself. Or if you have the option, reject the PR and ask for a smaller one.
1
u/the_data_must_flow Sep 26 '26
It’s not that rare. I’m a consultant and most of our clients haven’t yet dipped their toes in. Many are looking for help figuring it out. They are worried about slop code and worried about security and cost.
1
1
1
u/nanaimo_couple Sep 26 '26
My company gives us thr option, but any generated code must be reviewed/owned by the submitter, who is responsible for the effects of that code. I personally do 95%+ manual coding, I just prefer it.
1
u/Kusamakura0467 Sep 26 '26
I think the important distinction isn’t manual coding versus AI-assisted coding. It’s whether the team still understands the system and takes responsibility for its design.
Frameworks and IDEs have made it easy to produce code without making the underlying design choices explicit. AI can accelerate that pattern if we use it only to generate more code. But it also gives us a chance to shift more effort toward defining the problem, constraints, models, architecture, and trade-offs—the parts of engineering where human judgment matters most.
AI can help implement, test, and review within that design. But when a change is too large for a person to understand, code generation has outrun the team’s ability to engineer the system. Keeping changes reviewable helps people stay engaged with both the codebase and the design behind it.
1
u/Rich-Hovercraft-1655 Sep 26 '26
I dont see manual coding being part of a job anymore, I also dont understand how to program in punch cards, but that hasn't affected my job
1
1
u/Sufficient_Shine8311 Sep 27 '26
interviews still rely on manual coding for now (leetcode, code up a small feature). I also did an interview where claude coded up the feature after I completed the design choices and tradeoffs, leaving that awkward 5 mins where the clanker was clanking and everyone was waiting to 'validate' the generated code.
1
u/makemenuconfig Sep 27 '26
I usually let Claude prototype something for me, maybe a few times, then I end up re writing the final thing based on the learnings from these prototypes. That way I understand it, and I think I end up with a solution better than either me or Claude would have done on our own.
1
u/oskaremil Sep 27 '26
Yes. Mostly. Use AI for test, prototyping and suggestions.
The suggestions works-ish most of the time.
More like copy-pasting parts of the code from Stackoverflow.
1
1
u/JohnVonachen Sep 27 '26
Yes but my google searches have been much better in the last few years. So tangentially I use AI assistance. I do not like my ide constantly suggesting code I don’t want.
1
u/Strict_Research3518 Sep 27 '26
So honestly I miss manually coding a bit.. but I dont miss the being stuck on issues and spending hours to days sometimes unable to solve something. What is worse though is that I've now been full AI coding/review/test mode for over a year now and I am using a couple of languages I don't know well since AI basically codes in any language the same more or less. But lately I've been thinking.. my project/MVP/prototype being done in AI is great to eventually get it working/demoable. BUT.. because some of it has to be super tight/fast/high quality code that if it were to work out could be used/relied upon by banks/govts/etc.. I fear letting AI own all that code. Therefore, my thought right now is to finish MVP/etc, try to get funding, and then I/team will rewrite the "core"/heart/most important bits by hand with AI assisting in reviews/hints/suggestions and controlling that ourselves. I think that would give me the highest confidence that what we're asking others to trust when they use it, is stuff we own/know and can maintain/fix.
1
u/gwenbeth Sep 28 '26
I'm still coding by hand. It's easier for me to express what I want in code than to write it out in prose. This is why I wasn't an English major.
1
u/xlpacman805 Sep 28 '26
No but with the amount of specifics I have to give AI to build what I want sometimes I feel like I might as well have coded it manually. Other times when the pattern is well defined in the codebase it can do it fast and well.
1
u/Hopeless_Engineer01 Sep 28 '26
since i work in the banking industry, where everything is highly regulated, yes, i still do it manually.
→ More replies (4)
1
1
1
u/Hostman_com Sep 28 '26
The rule about keeping PRs small enough for a human to review sounds pretty sane. The worrying bit is when “I understand this change” quietly becomes “CI is green, ship it.”
Someone should still be able to explain what went into production without asking the model that wrote it.
1
u/awildmanappears Sep 28 '26
I'm all manual for religion and fun.
My workplace absolutely has heavy LLM users and the company is pushing adoption. However, I haven't been "caught" yet. My boss likes my pace, and my colleagues like the quality of my outputs. I'm regarded as a domain expert, and other teams consult me when they are uncertain about how to approach a new feature. I know folks who limit themselves to LLM chat, but I'm not aware of anybody else who is zero-LLM like me and still in software. Folks I know with that disposition shifted careers.
1
u/mpersico Sep 28 '26
I’ll bet the the less scrupulous among us will let AI handle the job stuff so they can play with the handcoded side projects.
1
u/Automatic_Coffee_755 Sep 28 '26
I try to but some of the code i am working with is far too ai slopped to be saved.
Like imagine frontend code “written” by full stacks (backend crud people who know what state is in react)
Imagine several components declared in the same file, endless ternary functions, no variable naming,
Things like
if (
response.data.results[response.data.results.length - 1].user.profile.settings.notifications.email.enabled &&
response.data.results[response.data.results.length - 1].user.profile.settings.notifications.email.frequency ===
response.data.config.defaults.notifications.email.frequency
) {
sendEmail(
response.data.results[response.data.results.length - 1].user.profile.contact.emails.find(
(e) => e.id === response.data.results[response.data.results.length - 1].user.profile.contact.primaryEmailId
).address,
response.data.results[response.data.results.length - 1].user.profile.firstName + " " +
response.data.results[response.data.results.length - 1].user.profile.lastName,
[...response.data.results[response.data.results.length - 1].user.orders]
.sort((a, b) => b.createdAt - a.createdAt)[0]
.items[
[...response.data.results[response.data.results.length - 1].user.orders]
.sort((a, b) => b.createdAt - a.createdAt)[0].items.length - 1
].product.id
);
}
1
u/theJohnsie Sep 28 '26
We also have a fixed amount of credits and all PR's are reviewed by at least 2 human peers.
1
u/jwmay Sep 28 '26
Yes. I am biased but I hear a lot of people talking about productivity gains yet I struggle to see them. Have recent versions of tools/websites I personally use got better - I would say not really and subjectively they may have got worse/slower. There was some stat about how many more versions of Spotify got shipped. I look at that a bit like measuring productivity with lines of codes.
1
u/solmead Sep 29 '26
While normally I manually code, lately I’ve been using ai to do the coding, but I do it in small batches, and I only check it in once I fully understand what the generated code is doing and why.
1
u/Alarmed-Tell1315 Sep 29 '26
AI executes, humans plan and approve. AI nowadays is better at coding than anyone I know, it still a stupid stateless machine, but with a solid harness and a competent engineer behind it can produce good enterprise grade products. Execution phase is reduced a lot but the planning and review phase grows significantly, basically resulting in no speed increases in general, but pushing people to the left of the process (strategy, planning and design) has measurable benefits.
→ More replies (6)
1
u/ElectricSmaug Sep 29 '26
I do as a scientist. I don't have to adhere to particular workflows or practices so I just code in the way I find most transparent for myself.
1
u/FaygoMakesMeGo Sep 29 '26
I don't code to create product to be consumed.
I code because I have an idea and I enjoy the art of creative problem solving, especially in a field with so much history, philosophy, and nuanced skill.
Asking another entity to do it for me defeats the entire purpose. If it comes to that, I'll find something less braindead to do.
1
u/DeadInFiftyYears Sep 29 '26
I manually code because it's the only way that makes sense. I can tell when people have been extensively using LLMs because there's no discernable architecture, and tons of fundamental, lingering issues that you would not expect to find in a codebase written manually.
Those teams may have enjoyed going extremely fast in the beginning, but now face difficulty making changes, and tracking down the numerous bugs is a slog that the LLMs often can't effectively help them with. Working on those codebases feels like being stuck wading through a muddy swamp with no end in sight.
1
u/AWildTyphlosion Sep 29 '26
I work on a team that contains vibe coders. I often have to correct their PRs, and I typically outpace them on tasks due to that fact. While they can usually hash out slop, getting the slop working or appropriate tends to cost as much time as it would for them to just do the task themselves. It also has led to the unfortunate affect of them not understanding the overall data model.
1
u/samxsxiao Sep 30 '26
I do both - AI-gen and human review, but my leadership is start to think about taking that away too. May I ask which company is yours? Because it would be one I would love to work for!
22
u/unhappymagicplayer Sep 24 '26 •
Similar to mine. I’ve heard of places giving a fixed dollar amount per month per engineer. I like that as well for differing reasons.