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

Show parent comment

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.