r/Python • • Jan 28 '26 • This 2 Bravo 1

Meta (Rant) AI is killing programming and the Python community

I'm sorry but it has to come out.

We are experiencing an endless sleep paralysis and it is getting worse and worse.

Before, when we wanted to code in Python, it was simple: either we read the documentation and available resources, or we asked the community for help, roughly that was it.

The advantage was that stupidly copying/pasting code often led to errors, so you had to take the time to understand, review, modify and test your program.

Since the arrival of ChatGPT-type AI, programming has taken a completely different turn.

We see new coders appear with a few months of experience in programming with Python who give us projects of 2000 lines of code with an absent version manager (no rigor in the development and maintenance of the code), comments always boats that smell the AI from miles around, a .md boat also where we always find this logic specific to the AI and especially a program that is not understood by its own developer.

I have been coding in Python for 8 years, I am 100% self-taught and yet I am stunned by the deplorable quality of some AI-doped projects.

In fact, we are witnessing a massive arrival of new projects that are basically super cool and that are in the end absolutely null because we realize that the developer does not even master the subject he deals with in his program, he understands that 30% of his code, the code is not optimized at all and there are more "import" lines than algorithms thought and thought out for this project.

I see it and I see it personally in the science given in Python where the devs will design a project that by default is interesting, but by analyzing the repository we discover that the project is strongly inspired by another project which, by the way, was itself inspired by another project. I mean, being inspired is ok, but here we are more in cloning than in the creation of a project with real added value.

So in 2026 we find ourselves with posts from people with a super innovative and technical project that even a senior dev would have trouble developing alone and looking more closely it sounds hollow, the performance is chaotic, security on some projects has become optional. the program has a null optimization that uses multithreads without knowing what it is or why. At this point, reverse engineering will no longer even need specialized software as the errors will be aberrant. I'm not even talking about the optimization of SQL queries that makes you dizzy.

Finally, you will have understood, I am disgusted by this minority (I hope) of dev who are boosted with AI.

AI is good, but you have to know how to use it intelligently and with hindsight and a critical mind, but some take it for a senior Python dev.

Subreddits like this are essential, and I hope that devs will continue to take the time to inquire by exploring community posts instead of systematically choosing ease and giving blind trust to an AI chat.

1.8k Upvotes

478 comments sorted by

View all comments

401

u/chunkyasparagus Jan 28 '26

On the other hand, let's be thankful that we were born before AI and had to learn how to code properly without the crutch that a lot of new programmers will use to skirt around bits that they don't understand or have time for.

AI can be incredibly useful for otherwise mind-numbing tasks, but I'm not sure it can be truly innovative at its current level. So let's keep innovating and leave the boring stuff for AI.

57

u/grady_vuckovic Jan 28 '26

I started writing my first lines of code in the 90s, I was doing web dev and C++ by 00s. I've spent my entire life feeling like I'm desperately trying to catch up to all the things the industry was telling me I need to learn, the laundry lists of skills, tools and experience every job said you needed to be even a junior developer. I've only just in the past maybe 4 years felt like I'm finally on top of everything I 'need' to know, with still plenty of room for growth in many areas.

And let me tell you I enjoyed every bit of it. Programming is imo one of the most enjoyable things to do in life. I feel grateful for the fact I got a chance to do it and learn well before all this latest crap started happening.

And now a bunch of people, many of which hated programming, or sucked at it, or simply didn't do it just 12 months ago, are now telling me that programming is "solved", and that grandmas are gonna be able to vibe code their own phone apps within another 2 years.

Needless to say... I'm very doubtful. I'm doubtful that such a complex and knowledge intensive industry, that a difficult skill, something so technical and which requires so many kinds of discipline and experience, a field of work rooted in complex problem solving, ... Suddenly, apparently, is about to be so easy that literally anyone can just say "hey computer make Photoshop for me" and an hour later it's done?

.. ( X ) Doubt

Yes things change. But they don't change that quickly. And I do not believe for one moment that having 20+ years of experience with understanding the deep inner workings of software and experience writing software entirely from scratch is somehow going to be no advantage.

I could be wrong.

But if they're right we'll all be jobless anyway, including the AI Bros, so even if I'm wrong I doubt the people telling me so will be laughing either when they have to debug their grandmas weather app.

16

u/mfitzp mfitzp.com Jan 29 '26

Somehow it’s always people who don’t do the job (and have very little understanding of what the job involves) that predict it’s solved.

Remember to be this skeptical when you hear some CEO predicting the end of doctors, architects, graphic designers, and on and on.

6

u/grady_vuckovic Jan 29 '26

I am in fact sceptical of such claims for those types of jobs. And I am actually dual skilled as a product viz designer too so I know it all too well and I'm seeing the exact same stuff happening there too. I'm seeing doctors and lawyers and architects all expressing the same frustrations as I am about everyone just assuming their jobs are now fully automated just because an LLM can produce text that seems coherent.

It's also in particular managers who more often than not just seem to assume everyone else's job is easy and everything is a simple 3 step process. Makes me wonder how much actual work they do. Maybe they assume everyone else is not really doing that much work because they aren't.

4

u/TastyIndividual6772 Jan 29 '26

Yea, theres so much to it. A few people i know that happen to be very old school devs are mostly of the mindset the software industry comes up with “we are about to replace programmers” once every few years.

Anytime i mention you can’t go fully autonomous on building software the average vibe coder who build a 4-page website up will come to reply with “skill issue”.

But the issue is not them or how juniors abused llm to make a pr with 4 regexes that you need to spend 50 minutes to understand. The main issue is the experienced devs who should have known better, who should have done due diligence and should have used it enough and studied enough before go on and post in euphoria “software is dead”.

I haven’t seen a single person lay out the most basic logical question: if writing easy software can be done by an llm but writing complex software needs lot of human effort still, does the world need more in terms of quantity or complexity.

My guess is if all those vibe coders ever manage to build the next google or the next facebook (which is possible but i doubt) and they grow so big they will have to hire eventually anyway.

4

u/IWasGettingThePaper Jan 29 '26

I remember when they said 'software was dead' because 'C is easier than ASM'. Again when Python became popular, because 'it's so easy my grandmother could do it in Python'. And again when low/no code platforms showed up. Now they say it because of LLMs. What actually happened in every case is the software itself became far more complex and the job of engineering it ultimately more difficult, because the scope of what software could actually do expanded and it became feasible to build much more complex systems.

4

u/TastyIndividual6772 Jan 29 '26

Yea. There is a probability “this time Is different” i dont deny that. But beyond that its SOS (same old story)

→ More replies (1)

4

u/fbe0aa536fc349cbdc45 Jan 29 '26

When I was a CS undergrad in the 90s, we were all never going to get jobs because managers were going to be able to use 4GLs to transform requirements directly into software. It turns out the 4GLs weren't terrible but they required so much expertise at defining the requirements that it was easier just to write the code. Also they cost a fortune.

Then we were all going to lose our jobs and be replaced with people who had learned OOP because they'd be able to do everything 10x faster.

These cycles of hype happen over and over again like clockwork, and while this one is the most insane ever on account of how many VC people are willing to bet a significant fraction of the economy on it, it only seems viable because we're in the trial-period in which these companies essentially give away their service for free to get the hooks in. At some point the gravy train will dry up and when people see the actual pricing necessary to make the services profitable with the actual market size, somebody will have to foot the bill for it. Also the moment any of these companies actually start making money and tech bros lose control of the the regulatory agencies, the owners of the stolen IP ingested by these things are going to demand a cut, and lawyers are gonna lawyer.

"But I can run my own model!" people will exclaim, and I know a handful of people who do this, but most development shops I've ever been in don't want to spend a penny more than they have to on whatever shitty laptop they foist on developers.

The collective level of outright fantastical, delusional thinking by people looking to become billionaires right now on AGI snake oil and humanoid robots would be hilarious if not for the fact that they're inevitably going to wreck the US economy in their lust pay information workers less.

My advice to young programmers is the same as its always been. Put in the hours, do the work, read every book and paper you get your hands on, and do something else if you don't love it. Find or write tools to automate stuff that would make you miserable to do manually. I'm sure some people are going to find a way to get an LLM to do most of their work, but if that's actually easier than doing it the old way, it means you'll be in a race to the bottom on your value as a worker.

→ More replies (2)

9

u/greshick Jan 29 '26

I’m working on some very mind numbing code atm at work and AI has been a god send. After spending a few days refining the process, getting good clean PRs out in a fraction of the time. PRs I’m of course reviewing before posting them. I’m bootstrapping a customized shadcn library from Figma into code. Doing all the tedious setup required per component would have sucked.

2

u/Peregrine2976 Jan 30 '26

I've found ChatGPT invaluable for those obtuse Docker errors I always seem to generate that literally no one on Earth has ever experienced.

It's a damned powerful tool. So is a jackhammer. It doesn't mean you haul out the jackhammer to paint the living room. People need to understand when and why its appropriate to use any given tool.

39

u/henrydtcase Jan 28 '26

This didn’t start with AI. I knew CS grads in the 2010s who couldn’t code a basic sort in C but still became backend/full-stack devs. Frameworks already made it possible to work at a high level without deep fundamentals.

27

u/SimplyRemainUnseen Jan 29 '26

Out of curiosity why should they have known C?

The fundamentals they learned in college definitely covered asynchronous programming, state, database transactions, and distributed systems. Those are the actual fundamentals they would need to be an effective engineer.

I don't know about you but where I work rolling your own sorting algorithms in C is bad practice.

12

u/henrydtcase Jan 29 '26

It’s not about C, it’s about algorithmic thinking. I saw many CS students struggle in intro programming courses that focused on problem-solving and logic. I’ve been at three different universities, and even when the course was taught in C#, Java etc. instead of C, the outcome was the same. The language wasn’t the issue, the real gap was in fundamental algorithmic thinking.

11

u/SimplyRemainUnseen Jan 29 '26

The issue here is assuming that a student struggling in an intro course defines their career potential. That 'gap' you saw often closes once they leave the artificial constraints of a classroom and start solving real problems.

We shouldn't judge professional engineers by how they performed on a sophomore year midterm, that would be silly.

18

u/No_Application_2927 Jan 29 '26

Right!? And so many assholes have not wire-wrapped their own computer.

If you cannot make the tools from scratch go work at McDs!

→ More replies (1)

2

u/axonxorz pip'ing aint easy, especially on windows Jan 29 '26

I knew CS grads in the 2010s who couldn’t code a basic sort in C

I am struggling to find the learning journey here.

If you're looking to get a SWE role, fundamental algorithms are important to have in your head, but imo only at a 30,000ft view. Application in class is simply to teach idiosyncracies of C using an algorithm that has more complexity than a basic imperative flow. Better sort algos exist, coded by much smarter people than you or I, and you will universally reach for those in your career, so why not teach those C idiosyncracies with more approachable (nee: real-world) examples?

Can those graduates code a basic sort in Java, C#, Python, etc etc? I'd bet money they could, given the verbal description of sort algos available on wikipedia, because the algorithm isn't actually what's being taught, it's the thought process.

Full disclosure: I probably wouldn't be able to write a basic sort in C (I can write C, but it's a disaster of trial and error, an LLM could do way better than me), but in opposition to your point, my lineage goes back past your CS grad acquaintances. I've been doing this job professionally since 2004 and my lack of fundamental C algorithms has come up precicely zero times.

If your focus is more pure CS, then sure, it's much more important to understand, but that's a wholly different career path than a back-full-end-stack dev.

imo, lambasting abstractions (as a general class of [thing]) is a neo-ludditeism. I don't think it's unfair to say that >99.9% of professional programmers use some level of abstraction. Drawing arbitrary lines of good-abstraction/bad-abstraction purely based on the degree to which it enables poor developers to create passable work misses the point.

16

u/zaccus Jan 28 '26

Idk man even the mind numbing stuff it manages to get wrong somehow.

11

u/Successful_Creme1823 Jan 28 '26

If you know what’s good and what’s bad it’s an awesome tool.

That’s kinda the end of the story for now.

6

u/zaccus Jan 28 '26

It's good at being conversational and flattering you, that's about it.

10

u/Successful_Creme1823 Jan 29 '26

I guess I’ve had better luck.

I’ll tell it to scaffold out stuff and it generally does it right. Saves my typing.

I tell it to generate a data driven unit test for some code. It does it like I would. If it needs tweaks, I tweak.

Write a one liner that does this in bash. No problem.

All stuff I can do and have done for years, just does it faster.

→ More replies (1)

19

u/Pezotecom Jan 28 '26 edited Jan 28 '26

So the problem here is that people that are skilled at something, programming in this case, are well beyond the junior or more intro jobs, which encompass MOST jobs, and can't understand why this helps someone who isn't you.

5 juniors that suddenly have access to python + sql + excel + pbi is MASSIVE. It's not mind-numbing when it was literally out of reach for, say, a business major, a psych major, a sports organization. You went from crunching spreadsheets because you didn't know better and that's the way it's always been to automating entire hours of the day, which saves time+money, and enables more creativity, more production, more of everything.

I seriously don't get the AI hate it's like people on reddit has never worked a day in their life honestly

38

u/MrZakalwe Jan 28 '26

The hate is from short-sighted management not understanding the limitations of AI, and people having to deal with the consequences.

My irritation with it is precisely because I do work.

In a few years i think it will be pretty great, to be fair, but more because people are used to using it and when not to use it (if that makes sense?).

7

u/The_KOK_2511 Jan 28 '26

The main limitation of AI comes when you realize that AI cannot work entirely on its own. Simply put, AI is "an advanced algorithm capable of making decisions and replicating human processes in a software environment." Therefore, if AI progresses by "imitating" humans, it means that it will never achieve the results of people with average knowledge. However, the knowledge and practical experience of experts are necessarily at a higher level than that of AI. If you think about it, the highest possible level of quality for AI would be that of a human with specialized expertise... and that's assuming there's someone who knows more about the subject and also develops AI to create a system capable of reaching that level.

Because of this major limitation, although things will be more difficult for programmers for a while, there will inevitably be a tipping point where AI can no longer keep pace with the growing industry.

→ More replies (2)
→ More replies (3)

11

u/1kn0wn0thing Jan 29 '26

The hate is not for the people, the hate is for the devaluation of the skill of actual developers just because AI can spit out code that works and the person who doesn’t understand what the code does is all of a sudden a developer.

An analogy would be let’s say a company created a robot that can diagnose and fix engines and gave it away or sold it for low monthly payments of $20 a month. You all of a sudden have millions of people claiming they are mechanics even though they have no clue about engines or how cars work under the hood in general. The robot diagnoses problems but because the person has no clue about engines they don’t know if it’s right versus an actual mechanic might say “wait a minute, this doesn’t sound right or it may be something else, let’s diagnose a bit more to validate the problem.” The new “mechanics” are simply shrugging and pointing the robot at the car and have it fix whatever it diagnosed. To top it off, they have no clue what types of nuts and bolts to use, when washers are supposed to be used, which belts and hoses are better quality, which spark plugs are better quality, they just buy and give the robot the cheapest parts to use on repairs.

So imagine you went to one of those mechanics and think to yourself “man, instead of paying $1500 to a skilled mechanic for a repair, I’ll just go to this other one that has the robot and pay only $500, they’re going to do the same thing anyway but way cheaper.” Then you get into your car after it was repaired and find out the brakes are not working while doing 70mph on a highway and you die in a burning wreck.

Not a perfect analogy, but that is essentially what is happening in coding. People who have dedicated to learn their craft and hone their skills to have code optimized and run under stress, which libraries to use and dependencies to import versus writing their own functions, those people are being effectively told that some dipshit who knows nothing about code can use AI and replaces the need for all the knowledge the experienced developer has. That all that knowledge and experience is worth nothing in the market place. The hate is for corporations using this as an opportunity to devalue the knowledge of people and all those people who happily pick up this rhetoric when in actuality it is simply a tool that still requires knowledge of at least fundamentals of computer programming, machine efficiency, and security to truly be effective.

→ More replies (2)
→ More replies (4)

2

u/catr_adorapls Feb 01 '26

As someone who is currently learning how to code (in my CS BS program right now) this is so scary. I genuinely want to learn how to cose properly and be able to debug my own code but so many internships Ive looked at are literally telling me that Ill be coding using chatgpt and my professors are requiring we use AI softwares to debug our code FOR US. How am I suppose to learn how to code? I want to actually be a programmer, it’s really discouraging. 

→ More replies (10)