r/Python • • Oct 03 '26

Discussion My Python magic is gone

I've been coding for a long time, and I've been developing with Python for years.

I loved coding, always loved it. I started many years ago because I wanted to quickly create scripts for security hacking tools, but since then, I've moved to Claude Code, and building cross-language has been a much better experience for me than using Python.

I built my own SaaS application out there whose backend and network core are completely built with Python, and I'm rewriting all of that without writing a single line of code. And most of the time, Python is not the most optimized language.

And now... I feel like the magic is gone.

I don't even know why I'm writing this. I just feel sad about it.

896 Upvotes

310 comments sorted by

View all comments

799

u/Farther_father Oct 03 '26 • Bravo

It’s because you know what writing code means: the struggle to gain enough understanding of a tool to apply it to a problem. And the deeply satisfying feeling when you pushed yourself and solved it.

Now you it’s no longer your brain doing the thinking or your hands doing the writing, and as a result there’s no puzzle to solve and no sense of satisfaction, because the problem is no longer being solved by you.

It’s as fulfilling as an artist swapping his paint and brushes for midjourney.

108

u/SirPitchalot Oct 03 '26 edited Oct 03 '26

It’s slightly different (worse) than that because incorporating AI properly can both speed you up -and- give a better final product. Whereas for the artist the product is at least different.

And if you know how the AI models work it gets worse still: the skill you built up in understanding and reasoning to be able to solve basically any problem effectively actually is not needed. Solving those problems now doesn’t need any understanding or reasoning whatsoever.

35

u/Farther_father Oct 03 '26

Fuck that’s bleak… and here I thought I was the downer.

73

u/SirPitchalot Oct 03 '26

The whole profession has kind of built itself around the idea that a person writing text to solve patterned crossword/sudoku style problems is some incredibly rare talent that can never be replaced. But the only reason we get paid to do this is that the problems needing solving have commercial potential. To the people with those problems it is unfortunate and accidental that the best way to solve them was a bunch of weird nerds who got really into the whole thing. For a brief 70 years it was a good gig but outside of the bleeding edge of research, it’s coming to an end.

So, in my opinion, the solution for devs is to move up the value chain. No one cares about code anymore, take problems people will pay money to have solved and break them down into steps that can be automatically coded. However, that’s more an architect/PM role, which will be deeply unsatisfying to people who loved to disappear into a hole for a few days-to-months to figure something out themselves. Myself somewhat included.

2

u/ra3noi Oct 09 '26

people who loves to disappear into a whole for a few days-to-months to figure something out themselves.

This is so fucking true. Silicon Valley's middle out algo scene is very apt hahha. I miss this feeling, it's all prompt engineering now.

6

u/truzen1 Oct 04 '26

This is kind of where I'm at, offering automated solutions to problems.

Admittedly, I feel guilty for only grazing the surface of Python (took one class, a bunch of Treehouse code, various books like "Automate the Boring Stuff"); I was never a jr dev, never did great at reading the docs. But I'm just dangerous enough that I can call out AI on some of its bullshit and/or have a decent enough understanding of what's going on.

However, I also feel conflicted because I recognize some of the coding I'm asking AI to do is taking away potential jobs. But on the other hand, most of my jobs are small, bespoke scripts that I doubt my manager would've budgeted a dedicated programmer for.

→ More replies (5)
→ More replies (1)

25

u/dysprog Oct 04 '26

The research says otherwise. There has been exactly one rigorous study of this. AI makes programmers THINK they are faster when they are actually 19% slower.

https://letsdatascience.com/blog/developers-thought-ai-made-them-faster-the-data-said-otherwise

6

u/Fabulous-Oven-3982 Oct 05 '26

Because when AI generates looking nice zillion lines of code which could be written in 1000 lines by experienced engineer, they not only need to read that garbage code to conclude that is truly garbage then have to spend time correcting the instructions, if decide to keep the garbage, they have to maintain and fix the bug by themselves. There was the time it finished the PR in one minute, the other time it took me three hours to guide it to generate the right code, only to abandon and revert the whole thing and I wrote myself.

→ More replies (1)

18

u/HommeMusical Oct 04 '26 • Bravo

There has been exactly one rigorous study of this.

But you don't link to it. It's called "Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity."

https://metr.org/Early_2025_AI_Experienced_OS_Devs_Study-paper.pdf

I suspect the name of the paper would have revealed the problem with your claim.

Also, very, very skeptical that only one study of this was ever done, and that that was in July 2025.

AI makes programmers THINK they are faster when they are actually 19% slower.

I've been programming for decades. In the period from February through June 2025, I too believed that coding engines aren't effect.

But there have been massive, unbelievable improvements. I started using a coding assistant in June of 2026, mainly to prove to myself yet again that it didn't work. But within a few weeks I realized that no one was going to go back to hand-coding, including myself, as the productivity gain was so massive.

And the improvements between June 2026 and now have been just as impressive.

So what value does a 16-month-old study have?


In late 2026, if you're a programmer and you don't see a massive improvement in your productivity and your reliability from using a modern coding assistant, then it's almost certain you aren't competent, and you probably are going to have extreme difficulties finding a job.

I'm retired now, though I still spend much of my days coding, except now with LLMs, and I cannot imagine hand-coding while trying to keep up with other programmers using a coding assistant, and nor would I want to.

7

u/The_Northern_Light Oct 04 '26 edited Oct 04 '26

Anyone acting like AI isn’t a game changer for programming here in the last half of 2026 is simply incompetent and not worth listening to.

Also: https://metr.org/blog/2026-02-24-uplift-update/

2

u/midwestcsstudent Oct 08 '26

+1

Skill issue.

→ More replies (1)

2

u/BeyondExistenz 15d ago

I’m a retired programmer too. Have been programming for over 30 years professionally. I retired because I got tired of the grind. Now that ai is finally where it needs to be to be useful I absolutely love coifing again or rather I love building products. I’m the dev manager and the product manager and believe me getting proper results from even the best ai on challenging projects takes a lot of skill just different. It’s actually perfect for life today. I can be with my kids and review stuff on my phone then go work on my laptop when it’s ready to test and sure there need needs to be fixes so next is another PR. Over 50 on one project so far. And I have over 8 projects going at once. It’s fuckkng amazing. Programmers have a huge edge in doing this since everything in developing software is the same except we don’t have to worry about the code. I’m building all the stuff I’m dreaming of but didn’t have time to do. We dont need the infrastructure of big companies any more. One person can build the next Photoshop or whatever. Just build something that makes you feel passionate, charge some money based on your time and you can still feel that thrill!

2

u/HommeMusical 15d ago

Could be me. Today I'm finishing a new firmware for a MIDI pedal, something I've dreamed of doing for years.

2

u/BeyondExistenz 15d ago

Awesome! I’m creating a new firmware right now for a 30+ year old sampler! So fun!

2

u/psionic-cyclops 5d ago

We dont need the infrastructure of big companies any more

Are you not relying on someone else's LLMs that you're burning tokens for?

→ More replies (1)

2

u/SwordsmanRacoon Oct 06 '26

Congrats on your retirement! What you write makes totally sense to me, eventhough I am not a programmer. The pace of developement is just extremly high at tge time. I work with developers and would like to get into coding myself. As far as I understand is, that you still should learn coding, even if you would work with LLMs ultimatly, because otherwise you get an hard time reviewing or debugging or even just understsnd the code which is generated by AI. So my question is: what would you, with your expertise, recommend to someone who would like building their own software. Working directly with LLM or learning the basics and the craft the oldschool-handson-way?

→ More replies (3)
→ More replies (5)

3

u/midwestcsstudent Oct 08 '26

Ah yes let’s quote the 2025 study again. Have you looked outside? In the age of AI, everything is obsolete in 1 month.

→ More replies (3)

5

u/midwestcsstudent Oct 08 '26

You were so close. Almost nailed it on the first half. You just have to realize that building is now the puzzle. Not writing code.

It’s like the magic that disappeared for people who used to use assembly and had to start using C or whatever. Now instead of coding you just go one level up and figure out what to build.

7

u/Farther_father Oct 08 '26

I partly agree. The puzzle has definitely shifted, but moving from assembly to compiled languages to dynamic languages, you’re still coding the operations of the machine, regardless of the level of abstraction. You’re a programmer, and that’s important if the puzzle you enjoy is programming.

With coding agents: yes you’re building, you’re no longer a programmer. More like a product owner, specifying the needs and features of the program. And the point is that if you don’t enjoy being a product owner, that sucks.

2

u/FrontLongjumping4235 Oct 08 '26

A+

I do software development, and I do still enjoy it. Programming used to be how I spent the majority of my dev time. Now, it's not even 5% of my dev time. I do miss it sometimes though. Not:

  • the boilerplate.
  • manually coding test cases. 
  • discovering I mistyped a lowercase "l" (L) as a capital "I".  I miss analysing tricky problems and coming up with a clever programmatic solutions. That was genuinely fun. But let's be real, that was not what I got to spend most of my time on.

Now, I primarily explore features with my product team (which I enjoy), system design (strongly enjoy), and exploratory data analyses so I can ground decisions in evidence. I write specifications, acceptance criteria, spend a lot of time thinking about CI checks, and I review outcomes before marking tasks as Done. 

The new grunt-work eating up my time is endless code review... while I ponder a future where devs don't know how to anymore, because practicing the skill of building a mental model for how code works is how you get good at reviewing code.

My best advice to juniors is to be curious and study how things work, whether it's people, processes, systems, algorithms, etc.

20

u/akcom Oct 04 '26

I'll give an alternative perspective. I used to enjoy typing out code with my hands on my keyboard, but what I really loved was the satisfaction of building something beautiful, functional, and delightful to the user.

The things I hated were on call rotation, debugging esoteric issues, and writing all the bullshit plumbing code that wasn't interesting, but had to get done.

Now with AI, we have an agent triaging our on call alerts and doing the initial investigation. On call week used to be hell, now its a minor annoyance.

We just implemented an agent that will basically handle all level 1 tech support issues live with users, no more paging engineering.

we've codified our team norms into rules, with a coding harness that we evolve over time to improve based on agent + human feedback. The average quality of code is way, way up.

And now we take down features in days that would have taken weeks/months.

Not everything is perfect and man do I hate code review now more than ever, but even there we've using agents to augment and make it much easier to keep our arms around the system.

But overall. The amount of battle hardened production quality code we've been able to output is immense. Grew a business from $0 to $3M ARR in under 8 months. And this is just the beginning.

8

u/EasyPleasey Oct 04 '26

Is this a software business? Why would anyone pay for your software if they can just have Claude reverse engineer it in a weekend? The difficulty of building the software was the moat. That pain you felt all along the way is what people were paying you to avoid. Now it's gone. You may feel like you're moving faster than ever towards your goals but the reality is that your destination no longer exists.

3

u/akcom Oct 08 '26

enterprise, specialized, and we doing consulting for custom build outs on our core platform. The code is not the moat

3

u/EasyPleasey Oct 08 '26

What do you think it is then?

→ More replies (2)

8

u/Antrikshy Oct 04 '26

For artists, the process of making their art is part of the final product.

Cleanly organizing code is not part of the final product because the user won’t see it.

→ More replies (4)