I Am a Programmer, Not a Rubber-Stamp That Approves Copilot Generated Code
Mood
heated
Sentiment
negative
Category
other
Key topics
The author expresses frustration with being forced to use AI-powered coding tools like Copilot, feeling it undermines their role as a programmer, and the discussion reflects a broader debate on the impact of AI on programming.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
38m
Peak period
149
Day 1
Avg / period
40
Based on 160 loaded comments
Key moments
- 01Story posted
Oct 15, 2025 at 1:09 AM EDT
about 1 month ago
Step 01 - 02First comment
Oct 15, 2025 at 1:47 AM EDT
38m after posting
Step 02 - 03Peak activity
149 comments in Day 1
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 23, 2025 at 11:09 AM EDT
about 1 month ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Or clones a template repo and only tweaks a few files
Or imports libraries with code I've never read
Programmers wrote the StackOverflow answer and wrote that library.
But according to your definition, I'm a script kiddy.
- Check stackoverflow only for very niche issues, never finds what he needs but reaches a solution reading multiple answers and sometimes used to post a better solution for his issue
- Have his own templates if he does repetitive and boring stuff (common), implements the complex logic if any first and get the rest done as fast as possible being mildly disgusted.
- Imports libraries and often take a look at the code noticing stuff that could be improved. Has private forks of some popular opensource libraries that fix issues or improve performance fixing silly errors upstream. Sometimes he is allowed/has time to send the fixes back upstream. When using those libraries sometimes he finds bugs, and the first thing he does is checking the code and try to fix them directly, no tickets to the maintainers, often opens a PR with the fix directly.
Really? This sounds absurd. "Instead of" means it doesn't matter how shit your work is as long as you're burning tokens? Or it doesn't matter how good your work is if you're not burning tokens? Name and shame
I guess it's great for AI companies that they've managed to bait and switch "this will improve your productivity" to "this is how much time you're sinking into this, let's not care about if that was useful"
I heard a rumor recently that AWS are doing this, and managers are evaluated based on what percentage of their direct reports used an LLM (an Amazon-approved model) at least once over a given time period.
I'm pretty sure Cursor also has something similar?
[ ] Yes
[ ] Maybe later
If I'm familiar with something (or have been) but not done it in a while, 1 - 2 line autocomplete saves so much time doing little syntax and reference lookups. Same if I'm at that stage of learning a language or framework where I get the high level concepts, principals, usescases and such, but I just haven't learned all the keywords and syntax structures fluently yet. In those situations, speedy 1 - 2 line AI autocomplete probably doubles the amount of code I output.
Agents is how you get the problems discussed in this thread: code that looks okay on the surface, but falls apart on deeper review, whereas 1 - 2 line autocomplete forces every other line or 2 to be intentional.
I'm making a comment precisely because it's not obvious when reading the code, and the AI will make up some generic and completely wrong reason.
It is like having an obnoxious co-worker shoving me to the side everytime i type a new line and complete a whole block of code and asking me if it is good without regards to how many times I rejected those changes.
I still use AI, but favor a copy paste flow where I at least need to look at what i am copying and locating the code I am pasting to. At least i am aware of the methods or function names and general code organization.
I also ask for small copy paste changes so that I keep it digestible. A bonus point is that ChatGPT in firefox when the context gets too big, the browser basically slowsdown locks and it works as a form extra sense that the context window is too big and LLM is about to start saying non-sense.
That said AI, is an amazing tool for prototyping and help when out of my domain of expertise.
Write a comment first on what you intend to do, then the AI generally does a good job auto-completing below it. I mean you don't have to "sketch everything out", but just that the AI is using the page as context and the comment just helps disambiguate what you want to do and it can autocomplete significant portions when you give it a nudge with the comment.
I've almost fully converted to agentic coding, but when I was using earlier tools, this was an extremely simple method to get completions to speed you up instead of slow you down.
Every time Visual Studio updates, it’ll turn back on the thing that shoves a ludicrously wrong, won’t even compile, not what I was in the middle of doing line of garbage code in front of my cursor, ready to autocomplete in and waste my time deleting if I touch the wrong key.
This is the thing that Microsoft thinks is important enough to be worth burning goodwill by re-enabling every few weeks, so I’m left to conclude that this is the state of the art.
Thus far I haven’t been impressed enough to make it five lines of typing before having to stop what I’m doing and google how to turn it off again.
I don't even think it saves me much time, but it saves me some keystrokes, which I appreciate due to having arthritis in my wrists.
The autocomplete, I find it useful. Specially doing menial, very automatic stuff like moving stuff when I refactor long methods. Even the suggestions of comments looks useful. However, the frequency with it jumps it's annoying. It needs to be dialed down somehow (I can only disable it). Plus, it eats the allowed autocomplete quota very quickly.
The "agent" chat. It's like tossing a coin. I find very useful when I need to write a tests for a class that don't have. At least, allows me to avoid writing the boiler player. But usually, I need to fix the mocking setup. Another case when it worked fine, it's when helped me to fix a warning that I had on a few VUE2 components. However, in other instances, I saw miserable falling to write useful code or messing very bad with the code. Our source code is in ISO8859-1 (I asked many times to migrate it to UTF8), and for some reason, sometimes Copilot agent messes the encoding and I need to manually fix all the mess.
So... The agent/chat mode, I think that could be useful, if you know in what cases it would do it ok. The autocomplete is very useful, but needs to be dialed down.
For those on VS, this is how to hide it, if using 17.14 or later,
https://learn.microsoft.com/en-us/visualstudio/ide/copilot-n...
like ... you expect people to actually be committed to "the value of a hard day's work" for its own sake? when owners aren't committed to value of a hard day's worker? and you think that your position is the respectable/wise one? lol
And are you assuming the alternative involves not clocking out? Because "clock out, finish when there's more time" is a very good option in many situations.
Back in the days of SVN, I'd have to deal with people who committed syntax errors, broken unit tests, and other things that either worked but were obviously broken, or just flat out didn't work.
Taking a bit of pride in your work is as much for your coworkers as it is for yourself. Not everything needs to be some silly proles vs bourge screed.
There's a very large number of cases where that's the right choice for the business.
Actual code/projects? Detrimental
[1] E.g. I spent an evening on this: https://github.com/dmitriid/mop
No opinion on whether or not this applies to the current moment. But maybe someone should try forcing Dvorak layout on everyone or something like that for a competitive edge!
I would guess that interest, passion, and motivation all play a role here. It's kind of like programming itself. If you sit people down and make them program for awhile, some will get good at it and some won't.
And, to use less pointed language, people’s brains are wired differently. What works for one doesn’t necessarily work for another, even with similar interest, passion, and motivation.
I'd rather learn almost any other of the myriad of topics related with software development that the quirks of an opinionated editor. I especially hate memorising shortcuts and commands.
I was using emacs for a while, but when I switched to vim, something about the different modes just really meshed with how I thought about what I was doing, and I enjoyed it way more and stuck to it for a couple of decades.
I see people that I'd say are more proficient with their emacs, VS Code, etc setups than I am with my vim setup, so I don't think there's anything special about vim other than "it works for me".
And that time when I changed vim to a symlink to emacs on a shared login server and sat back and enjoyed the carnage. (I did change it back relatively quickly)
Are you aware that there are people that think that even now AI can do everything you describe?
The reason crappy software has existed since...ever is because people are notoriously bad at thinking, planning and architecting systems.
When someone does a "smart decision", it often translates to the nightmare of someone else 5 or 10 years down the line. Most people shouldn't be making "smart decisions"; they should be making boring decisions, as most software is actually a glorified crud. There are exceptions, obviously, but don't think you're special - your code also sucks and your design is crap :) the goal is often to be less sucky and less crappier than one would expect; in the end, its all ones and zeros, and the fancy abstractions exist to dumb down the ones and zeros to concepts humans can grasp.
A machine can and will, obviously, produce better results and better reasoning than an average solution designer; it can consider a multitude of options a single person seldom can; it can point out from the get-go shortcomings and domain-specific pitfalls a human wouldnt even think of in most cases.
So go ahead, try it. Feed it your design and ask about shortcomings; ask about risk management strategies; ask about refactoring and maintenance strategies; you'd probably be surprised.
> So go ahead, try it. Feed it your design and ask about shortcomings; ask about risk management strategies; ask about refactoring and maintenance strategies; you'd probably be surprised.
Answers to this and other kinds of questions are in my opinion just a watered down version of actual thinking currently. Interesting but still too simple and not that actionable. What I mainly use LLMs for is exploring the space of solutions, that I will then investigate if there is something promising (mainly deep research of topics or possible half broken/random solutions to problems). I'm not really interested in an actual answer most of the time but more avenues for investigation that I didn't consider. Anyway, I'm not saying that AI is useless right now.
For people who are so confident (which, I'm not), it's an obvious step; developers who don't want to use it must either be luddites or afraid it'll take their jobs. Moving sales people to digital CRMs from paper files, moving accountants to accounting software from paper ledgers and journals, moving weavers to power looms, etc etc -- there would have been enthusiasts and holdouts at every step.
The PE-bro who's currently boasting to his friends that all code at a portfolio has to be written first with Claude Code and developers are just there to catch the very rare error would have been boasting to his friends about replacing his whole development team with a team that cost 1/10 the price in Noida.
Coding agents can't replace developers _right now_, and it's unclear whether scaling the current approach will allow them to at any point, but at some point (and maybe that's not until we get true AGI) they will be able to replace a substantial chunk of the developer workforce, but a significant chunk of developers will be highly resistant to it. The people you're complaining about are simply too early.
And if they really tied their livelihood to working at the same company for next decade because they maxed out their lifestyle relative to the income generated by that company, then that falls all on them and I don't actually feel that bad for them.
When you dig down into it, there's usually some insane luxury that they're completely unwilling to give up on.
If you're a software engineer in the United States, or in London, you can almost certainly FIRE.
Absolutely not enough to retire early but easily enough to not live paycheck to paycheck. Making 6 figures in the USA and not being able to afford life is so cryptic to me.
I'd say that there's some room for nuance there. Tech hiring has slowed significantly, such that even people in senior roles who get laid off may be looking for a long time.
If you work for Microsoft you're not getting top tier comp already (at least as compared with many other tech companies), and then on top of that you're required to work out of a V/HCOL city. Add in the expenses of a family, which have risen dramatically the last few years, and it's easy to find examples of people who are starting to get stretched paycheck to paycheck who weren't having that issue a couple of years ago.
Check the prices in Seattle, SF, LA, DC, and NYC metro areas for 2-4 bedroom rentals and how they've jumped the last few years. You're looking at 35%-45% of their take home pay just on rent even before utilities. I'm not sure the math works out all that well for people trying to support a family, even with both parents working.
If you maxed out your lifestyle relative to your income then yes, that is the case. It will always be, no matter how much you make.
It's also the case for the guy stocking the shelves at your local Walmart if he maxes out his lifestyle. But if you compare both in absolute terms, there are huge differences.
Which lifestyle you have is your choice. How big of a house, what car, where to eat, hobbies, clothes, how many kids, etc. If you max that out, fine, enjoy it. But own that it was your choice and comes with consequences, i.e., if expenses rise more than income, then suddenly your personal economy is stretched. And that's on you.
If my kid places his hands on a hot stovetop then I feel a lot of empathy and will obviously comfort him. But I won't run around claiming to the world that external forces made him do it. It was his choice. If it was his first time and/or nobody told him that it's a bad idea then there is limited responsibility, but otherwise it's squarely on him. Despite me feeling and expressing empathy.
Many German companies are not, in fact, unionized, and tend to pay 'übertariflich / außertariflich' - instead of union protection, they just pay you significantly more than you'd get with an union job. Which is a good thing 9 out of 10 times.
Which - incidentally - is why such companies advertise paying 'außertariflich' in their job adverts.
Situation might be different for low- and non-skilled workers.
The answer probably isn't American work ethics inspired by American compensation schemes, but rather Chinese ingenuity and grit. But seriously, why can you build so much on 35 hours per week and a mid-five-figure salary?
Usually over here we don't dream of making it big with big villas and a Ferrari on the garage, we work to live, not live to work.
Google Gwangju.
Let's work 90 hours a week and retire at 80, imagine the growth, big numbers get bigger makes bald monkey happy
that is all you heard in the 80-90s, people over the pond showing off how many hours per week they worked. like... how is that something to be proud of? So wauw, you spend 12hrs+ per day working , had no free evenings, zero paid holidays. And that is supposed to impress who?
please.
Hell, it has been going much longer than only 40 years ago, on "In Praise of Idleness" Bertrand Russell talked about how industrialisation with its automation should be helping workers to work less 90 years ago.
EU decided to distribute the productivity benefits instead of hoarding it into stock market gains like US does.
Btw, you do realize that US commodified investing in Us stocks? Whole world can easily invest in US stock market. Basically, instead of taking care of their own citizens, US economy is paying out gains to foreigners.
Personally I want my MSFT position to increase, so I’m cool with whatever the company does to increase the share price.
Or perhaps that's the problem, lacking it.
It's not just Microsoft. Other smaller employers are aping those guys.
My employer has an utterly ridiculous PowerBI dashboard tracking how much every employee uses LLM-based tools. Make sure to enable the Premium models, because otherwise you won't get credit! There are naughty lists for people whose usage is too low. Luckily the usage goals (for now) aren't very high.
However, they're also getting anal about tracking tasks, and the powers at be have asserted control over all aspects of story creation and work process. There's speculation they're going to start tracking story completion rates, and demanding measured productivity increases.
People hate learning new tools, even if they are more efficient. People would rather avoid doing things than learning a tool to do it efficiently.
Even in this thread you can see simeone who is / was a Vim holdout. But the improvement from Vim to IDE will be a fraction of the difference compared to AI integrated IDEs.
I know there are people still using PHP 5 and deploying via FTP, but most people moved on to be better professionals and use better tools. Many people are doing this to AI, too, me included.
The problem is that some big companies and influential people treat AI as a silver bullet and convince investors and customers to think the same way. These people aren't thinking about how much AI can help people be productive. They are just thinking about how much revenue it can give until the bubble pops.
Today you have "frontend programmers" that couldn't implement a simple algorithm even if their life depended on it; thats not necessarily bad - it democratizes access to tech and lowers the entry bar. These devs up in arms against ai tools are just gatekeepers - they see how easy is to produce slop and feel threatened by it. AI is a tool; in most cases will improve the speed and quality of your work; in some cases, it wont. Just like everything else.
If one person writes code only in react and another only in vue, in the same product, you have a mess.
If one person writes their react code in vim and another writes it in an IDE, you don't have a mess.
Huh? quick example - a customer-facing platform with a provisioning dashboard, and a user dashboard; they can (and should, for several reasons) be developed as separate applications, and will depend on different APIs. Are you saying having 2 distinct technologies on 2 distinct components of a product is a mess? Without any other details on the product?
A good example on the type of products with these separations are e-commerce systems; payment gateways; cloud-native SaaS solutions, etc etc etc.
I'm sorry to tell you this, but your comment just shows how deep your lack of experience is; any reasonable complex product using frontend technology will have different interfaces with different requirements, different levels of polishing and - frequently - maintained by completely different teams.
Actually, yes; People forced React (instead of homegrown or different options) because its easier to hire to, than finding js/typescript gurus to build your own stuff.
People forced cloud infrastructure; even today, if your 10-customer startup isn't using cloud at some capacity and/or kubernetes, investors will frown on you; devops will look at you weird (what? Needing to understand inner workings of software products to properly configure them?)
Microservices? Check. 5 years ago, you wouldn't even be hired if you skipped microservices; everyone thinks they're gooogle, and many startups need to burn those aws credits; thats how you get a dozen-machine cluster to run a solution a proper dev would code in a week and could run on a laptop.
I've worked with people using vim who wildly outproduce full teams using IDEs, and I have a strong suspicion that forcing the vim person to use an IDE would lower their productivity, and vice versa
This is not due to the editor. Vim is not a 20x productivity enhancer.
>forcing the vim person to use an IDE would lower their productivity
Temporarily, sure. But there productivity should actually go up after they are used to it. This idea of wanting to avoid such a setback and avoiding change is what keeps people on such an outdated workflow.
Saying that the people are the problem instead of the tool is a lazy argument IMO. "Its not the companies fault, its the customer"
Useful tools, but I think the idea that they'll replace programmers is (wishful? eek) thinking.
Mass produced clothing exists in many industrialized countries - typically the premium stuff; the sweatshop stuff is quite cheaper, and customers are happy paying less; its not capitalism, its consumer greed. But nice story.
It’s a bit like returning to the office. If it’s such an obvious no-brainer performance booster with improved communication and collaboration, they wouldn’t have to force people to do it. Teams would chomp at the bit to do it to boost their own performance.
Similarly, many people don't like learning new tools, and don't like changing their behavior. Especially if it's something they enjoy vs something good for the business. It's 2025 and people will have adamantly used vim for 25 years; some people aren't likely to change what they're comfortable with. Regardless of what is good for productivity (which vim may or may not be), developers are picky about their tools, and its hard to convince people to try new things.
I think the assumption that people will choose to boost their own productivity is questionable, especially in the face of their own comfort or enjoyment, and if "the business" must wait for them to explore and discover it on their own time, they risk forgoing profits associated with that employee's work.
Your argument also hinges on "business" knowing what is good for productivity, which they generally don't. Admittedly, neither do many programmers, else we'd have a lot less k8s.
With LLMs, I'm not so sure. Seems more like an individual activity to me. Are some people resistant to new tools, sure. But a good tool does tend to diffuse naturally. I think LLMs are diffusing naturally too, but maybe not as fast as the AI-boosters would like.
The mistake these managers are making is assuming it's a good tool for work that they're not qualified to assess.
Fair point! It was just the first recent example of "it's obviously better but we'll force you to do it" I could think of.
In case of RTO I think it should have been left to individual small team. If one is so clearly it would have been clear in a few years time which teams work better and which didn't and how it depended on them being in the same office.
I think it could have been left to individual small teams or smaller units. After some time it would have been obvious that teams who went to the office delivered better results. If the benefits are really that obvious as they are usually touted, it shouldn't take long (a year or two).
> It's 2025 and people will have adamantly used vim for 25 years
But if they are productive and delivers results they can still use vim. I can see controlling the APIs used, the programming languages allowed etc. But if they are productive with vim, let them use vim.
> I think the assumption that people will choose to boost their own productivity is questionable, especially in the face of their own comfort or enjoyment,
That's fair. I guess it depends on the types of people. I had in mind motivated people who would be glad to be more productive and deliver results quicker. Yeah, if people are not like that and are trying to do the least amount of work and just coast then it's a bigger issue. Office or not office, AI or no AI probably won't shift the needle by much.
If the AI tools actually worked how they are marketed I’d use them because that’s less work for me to have to do. But they don’t.
I agree with the second paragraph. I seek out ways to be more productive, whether you call that work ethic or laziness. I wish AI or heck any tool could 100x me. But somehow AI is the first tool that's ever been forced on me by an MBA
And even if it was, that's also assuming this benefit would be superior to the benefit of remote work for the individual.
GPT-5: Typesetting and paste-up, film prepress/stripping, CMYK color separations, halftone screening, darkroom compositing/masking, airbrush photo retouching, optical film compositing/titling, photochemical color timing, architectural hand drafting, cartographic scribing and map lettering, music engraving, comic book lettering, fashion pattern grading and marker making, embroidery digitizing and stitching, screen-print color separations
That's not a career-switching issue, that's a company-switching issue. Most people will work for at least one company in their career where the people in charge are dickheads. If you can't work around them, go find a different company to work for. You don't have to throw away an entire career because of one asshole boss.
Also fwiw, resistance is more effective than you think. You'd be surprised how often a dickhead in charge is either A) easy to call the bluff of, or B) needs someone to show them they are wrong. If you feel like you're going to quit anyway, put your foot down and take a stand.
120 more comments available on Hacker News
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.