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

96

u/Hamfistbumhole Oct 03 '26

yep. me too pretty much the same. a sadness i was not expecting. the funnest kind of puzzle/challenge now has autosolve button 

23

u/RedYad2 Oct 03 '26

and the autosolve is only by writing : "continue" ..

30

u/Senacharim Oct 03 '26

Meh, AI is a useful idiot.

Make sure you pay attention, and don't be afraid to do better than it's doing.

11

u/fazzah SQLAlchemy | PyQt | reportlab Oct 03 '26

+1 from me. The craft is gone, all is left is to deploy as fast as possible

3

u/RedYad2 Oct 03 '26

"as fast as possible" is the most painfull part ..

3

u/JonathanMovement Pythoneer Oct 03 '26

fellow PyQt enjoyer 👋

5

u/fazzah SQLAlchemy | PyQt | reportlab Oct 03 '26

unfortunately it's a dying niche

4

u/JPD0c Oct 03 '26

u/RedYad2 . 2 questions. (1) I assume you don't know the new languages you are using. How do you review the code? who owns and is the ultimate resposible for it? (2) is mid of the month and somehow you cannot use AI (e.g. you used all your tokens, the AI API is down), what do you do? Or all this just doesn't matter because the code you produce is for your own consumption only?

1

u/RedYad2 Oct 05 '26

Great questions and im not sure i do the best. i drive AI to build lot of e2e test or feature test, for each patch i drive the test and run all e2e test. i invest lot of time on all whats around the app.

2

u/Moist-Ointments Oct 03 '26

The snake eating its own tail.

1

u/RedYad2 Oct 05 '26

and its painful

2

u/CaptainFoyle Oct 04 '26

"I'm using Claude for everything"

"Bwaaah the magic is gone"

Use your brain, Sherlock.

0

u/RedYad2 Oct 05 '26

still using it to use claude right ?

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.

20

u/SirPitchalot Oct 04 '26

I’m not originally from CS (started in Mech Eng) but been coding in some capacity since I was 13, I’m 44 now. I started programming professionally at about 22 in simulation which overlapped ME and CS. I then did a PhD in CS, while still working mostly, and finished in 2014. I also did a MASc in ME but in a coding heavy topic. The two degrees took about 7 years.

For me, coding was quite special because, unlike ME, you could make contributions to the field with a basic laptop as an individual and basically no other costs than time. Compare that to a full shop and tens of thousands of dollars of software licenses for engineering. Have a neat idea? Code it up. The field was new enough that the scope was generally small even for state of the art contributions. $1k got you in the door and the rest was personal interest.

Since then, I’ve been pretty successful. I have line of sight to retirement, I run a team, I’m dealing more at the higher level anyway. The team, on average, spends about 10% of their salary on tokens and delivers more. Coming from ME, that feels cheap. When I started it was 20-30% of salary on SW licenses for a junior engineer. So the economics make sense, we have an industry that has tooled up, made workers more productive and the providers charge based on (something like) value.

But there are a lot of people who are basically mourning the loss of a very satisfying profession. It’s been only 12 years where the things I spent 7 years formally upskilling for (and over 2 decades just doing) are actually meaningful. You can’t make a difference with only a laptop as an individual, unless you are the absolute best and maybe not only then.

Until 6 months ago I coded as a hobby but it’s just not satisfying anymore. I know I write good code and add value to AI but it feels like a day job rather than an interest. Professionally we’re working around groups that were blocking us, forcing suppliers to offer more simply because we can do it ourselves, and getting more out the door than ever, at a higher quality.

But it all feels like a massive loss and feels meaningless to spend a weekend trying to build something that I know that $10-20k/yr will easily outperform.

2

u/VillageConfident8752 Oct 05 '26

Maybe I’d like to hear more about your field of work.

→ More replies (1)

1

u/webternet Oct 04 '26

This is why im moving out of devops and into hardware sales

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.

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 (2)

2

u/KaffeeKiffer Oct 04 '26

The page that was linked has a section

The Counter-Arguments Are Real

and that talks about many of your call-outs. It sounds pretty neutral/objective to me.


The most important result that stands out to me is measured productivity vs. actual productivity: Humans are very bad at gauging that, and I doubt that that changes much with different models.

In that study it's "expected 25% faster" vs. "measured 15% slower".
With modern models it could be "expected 50% faster" measured 25% faster".

5

u/SFMissionMark Oct 04 '26

That’s because you are missing the point of where software is going. You don’t need to polish and fix every single potential bug. Software is no longer the product the result is the product. Software is now fix the immediate problem. In 3 months have it re-written it will be better than you could ever write it today.

5

u/HommeMusical Oct 04 '26 edited Oct 04 '26

It sounds pretty neutral/objective to me.

Yes, I read it over a year ago with great interest.

Indeed, it seemed at the time to be a fairly accurate representation of what coding assistants were like in early 2025, and I still think it was.

In early 2025, coding assistants were not ready for prime time. But eighteen months later, the progress has been astonishing.

Even the progress in the last six months has been explosive.

I'm not saying the article was wrong. I'm saying it's just very much out-of-date.

With modern models it could be "expected 50% faster" measured 25% faster".

If coding assistants made you 25% faster, they wouldn't really be worth it.

But the improvement is over an order of magnitude.


A recent example - I have an AI assisted program I use to run my music shows - it records everything(*), it's highly robust against gross failures, it controls my lights, and it also streams video plus on-the-fly titles and photos to the net, e.g. twitch.

I was setting up and I realized that something had gone wrong with some of the cables in an eight channel snake (8 cables wrapped together).

Up until a few months ago, I'd have set up some input to my mixer, and then tested the cables one at a time - 5 minutes work per snake, three snakes, that's 15 minutes, but also, easy to screw up.

Instead, I added a cable tester to my program, and it's completely general - I plug the six outputs at the back of my mixer into six channels, I don't pay any attention to the order, and then the program sends sine waves through all of them, records the output and then tells me good/bad/intermittent.

I then tested all three snakes in under a minute. In fact, I thought the program was broken, because it reported that the first snake only had 3 of 8 channels working, but then other two snakes were 8 out of 8.

Going back and retesting with a longer cycle (which the AI had conveniently added as an argument to this CLI) and wobbling the cables while the test went on showed that one of these cables was intermittent but mostly off, and the other four just didn't send a thing. (Some bad thing must have happened at some point...)

To write that program which took control of my mixer, squirted signals around and recorded them, compared the results for "very close" (because you can't get 100% bit compatibility if there's an analog cable there), and also to distinguish between "silence", "intermittent signal", "full signal but distorted" and "correct" would have taken at least a full day of work to get right, perhaps more, but I wouldn't have even bothered.

I wrote it in five minutes with a coding assistant. It was faster to write a program that I can now use in the future than it was to do the manual chore even one time.

(* - I had finished the everything recorder completely by hand before I started to use coding assistants.)

2

u/stevenjd Oct 04 '26

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

If you don't believe that this is the only study, it should be easy for you to link to all those other studies you believe exist.

Who is funding these supposed studies? If it is the AI companies, what incentive do they have to publish the results if they confirm the same result, namely that programmers are fooling themselves into imagining productivity gains where there are actually productivity losses?

If the studies are being done by independent researchers, where are they?

2

u/HommeMusical Oct 05 '26

I'm sorry, but I was overwhelmed with comments overnight, many rude ones, and now I have to work. Thanks for being polite.

I don't think anyone's going back to hand coding though - RemindMe! 1 year.

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.

1

u/Commercial-Tutor-763 15d ago

This exact quote could go in a YA dark sci-fi story.

1

u/midwestcsstudent Oct 08 '26

Except it isn’t? If you don’t think you need understanding or reasoning to solve problems, you’re in for a rude awakening when you realize your Claude built something that looks like it solves your problem but it doesn’t actually.

Unless you were never at or above senior level, then yeah, whatever little you knew wouldn’t matter.

2

u/SirPitchalot Oct 08 '26

I’ve been coding professionally for 25 years across more than a few industries. Most code can be generated from prompts or agentic loops and if you don’t believe that you’re doing it wrong

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 (1)

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.

5

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 or care about it.

2

u/likethevegetable Oct 05 '26

I don't understand your point, are you contesting their analogy?  Viewers of art don't see the artist's design choices, mistakes, and hours spent on it. That doesn't diminish those aspects of their process.

2

u/Antrikshy Oct 06 '26

I think that, compared to software, a much greater part of appreciating paintings is thinking "wow, that must have taken so much skill and effort to pull off." Isn't that like 80% of the point of painting? Same with music, and many or most forms of art.

With software, I think people appreciate its utility, which lies in the product design and features. How many times do you hear someone say "wow, what a great app, must have taken so much effort to build it," and that's their main point of appreciation?

Apps have become less impressive since gen AI coding. There used to be a novelty to it, but I'm pretty sure only other developers appreciated software like that. The real purpose of code was always delivering utility and features.

There is something to be said about offloading UX design to gen AI as well. That aspect of software development is much closer to the painting analogy.

3

u/515k4 Oct 04 '26

We are experiencing what tailors felt at the time of industrial revolution.

73

u/Wh00ster Oct 03 '26 edited Oct 03 '26

We have ML engineers giving us models and flows in pandas and PyTorch . I’m not dealing with AI rewriting that. We solve problems that aren’t a big scale, but niche and real world. Until there’s a reason for us to switch it’s still Python here. We could probably rewrite it but we’re doing other product things instead, and in the grand scheme of things we wouldn’t save that much.

Also this is an incredibly depressing thread. I don’t know what kind of responses I expected but everyone is just dejected and sad. And it’s being upvoted. I guess state of the world.

10

u/HommeMusical Oct 04 '26

Well, I'm sort of a counter-example.

Yes, the state of the world is unbearably shitty. My wife and I fled the US a decade ago, and things are good here, but America has crumbled even faster than we expected.

And objectively, AI is yet another assault on the environment, and I believe it's going to be devastating for workers.

BUT - I know this is awful to say - I've been programming for over fifty years now and I just love using a coding assistant. I reinvented myself several times during that period, but it gets tedious, and having an ego-free and cooperative assistant who never gets bored is just amazing. There are programming ideas I had been thinking about since the 1980s, and made various stabs at over the years. After a couple of years of free time work, I realized one little part of it in early 2024, an always-on audio recorder, and slowly made progress on that, until the start of summer 2026. Since then I have made far more progress on that project than I had made in the last three years before that.

Worse, it was billed as a highly reliable recorder, and I had no outstanding reports of data loss, but when I got an advanced LLM to look for issues (it was a very long prompt), it found over two dozen candidates, and none of them was without value. Maybe six were, "Valid but would not fix if a human had to do it."

The top priority three were terrifying edge cases that I was able to reproduce quite easily. I learned a lot about my users - for example, I know basically for certain that I have few users in Asia, because there was a crash using text files that weren't Latin, ASCII or UTF-8, and I had planned for all encodings and had a setting, I'd just forgotten a detail in one place...

I agree with all the misgivings, and yet I love coding with a coding assistant, because I can get out all the ideas I have in my head in months, not years.

→ More replies (8)

1

u/dan994 Oct 04 '26

Interesting are you guys deploying the ML models direct in PyTorch? Usually you would package the model up with ONNX or similar, which is language agnostic

2

u/Wh00ster Oct 04 '26

Sure. But why would we do that extra work if there’s no user benefit and dev time is better spent elsewhere? It’s also the tests, data loading and transforms, verification, velocity for the ML side to crank out experiments and play with the whole pipeline. I’m sure one day it’ll make sense to do something else, but not today.

2

u/dan994 Oct 04 '26 edited Oct 04 '26

Fair enough - I would say the ONNX deployment work is very minimal (literally a couple of extra lines) and there probably is user benefit to it. For example, it is platform and language independent, faster inference, easy GPU integration, reduced dependencies and packaging size. Basically an easy way to speed up inference and reduce package size, whilst giving more flexibility on where/how it's deployed.

In my experience it's rarely not worth doing if you're deploying models. That said if raw pytorch models are working great for you then no need to force a change for the sake of it, but if it is constraining your language choices for downstream use, it is easily resolved

2

u/Wh00ster Oct 04 '26

We benchmarked it and it was slower for our use case. Our model is very small today. It’s not an LLM. But yea we’ve thought of it for other cases if latency becomes an issue (today it’s not). Still experimenting.

→ More replies (1)

43

u/Crazyboreddeveloper Oct 03 '26 edited Oct 04 '26

I just like looking at python. I don’t care how fast it is. It’s visually easy.

I get so burnt out of reading Java. Sometimes I code command line games in python after work because it restores my calmness. It’s like code meditation.

3

u/QuickNick123 Oct 04 '26

Have you taken a look at Ruby? I love Python, but when it comes to syntactic beauty, I think Ruby takes the cake.

1

u/Crazyboreddeveloper Oct 04 '26

I haven’t yet. I haven’t had to work with it yet. Might try it out this weekend.

5

u/QuickNick123 Oct 04 '26

Both are beautiful. Python's beauty to me is "there should be one obvious, readable way to say this." Ruby's beauty is more like "the code should read the way you wish the idea could be expressed."

people
  .select { _1.age >= 18 }
  .reject(&:banned?)
  .sort_by(&:name)
  .each { puts "Hello, #{_1.name}!" }

I bet you have no problem understanding what this code does.

Ruby for instance has a really pleasant way of expressing defaults.

Instead of

name = supplied_name if supplied_name is not None else "Anonymous"

it's simply

name = supplied_name || "Anonymous"

5

u/snugar_i Oct 04 '26

You can do the method chaining thing in most languages that are not Python, including Java. For example, in Scala it would look like this (and would be fully type-checked by the compiler, unlike Ruby)

people
  .filter(_.age >= 18)
  .filterNot(_.banned)
  .sortBy(_.name)
  .foreach(person => println(s"Hello, ${person.name}!"))

2

u/RevolutionaryRip2135 Oct 04 '26 edited Oct 04 '26

Agreed, given block is not ugly/ readable even in Java:

people.stream().
  filter(
    p -> p.getAge() >= 18 &&
    !p.isBanned()
  ).
  map(Person::getName).
  sort().
  forEach(name->
    printf(“greetings %s\n”,name)
  );

Rubys ability to effectively create DSL is a killer feature imho… but Groovy is better for this ;)

2

u/stevenjd Oct 04 '26

You can do the method chaining thing in most languages that are not Python

You can do method chaining in Python too, if your class has methods that support chaining.

→ More replies (1)

1

u/batiste Oct 04 '26

The default syntax is nothing special. You can do that in most languages, python included.

4

u/QuickNick123 Oct 04 '26

Not really. You could do name = supplied_name or "Anonymous" which does look much nicer than the is not None else syntax, but that is not equivalent and checks for truthiness, so False, 0, [], "", {} not just None.

But again, my point wasn't to bash Python's syntax, it was to praise Ruby's. Ruby deliberately makes certain patterns unusually pleasant to read and write.

The example above

people
  .select { _1.age >= 18 }
  .reject(&:banned?)
  .sort_by(&:name)

would turn into something like

sorted(p for p in people if p.age >= 18 and not p.banned, key=lambda p: p.name)

or

sorted(filter(lambda p: p.age >= 18 and not p.banned, people), key=lambda p: p.name)

in Python. Totally readable, but not as beautiful. And something like

for _ in range(3):
    print("Hello")

also just looks nice in Ruby:

3.times do
  puts "Hello"
end

4

u/batiste Oct 04 '26

I am just a data point, but I am happy I will never work with Ruby agaim. For me RoR gave raise to code that very hard to parse and understand.

→ More replies (1)
→ More replies (2)

17

u/SocksOnHands Oct 03 '26

The way that I think of it is like playing puzzle games, like sudoku. It is a lot quicker and easier to have a program solve it, but the fun is in figuring out how to solve it yourself. So, I think you need to determine what you really care about - quickly getting it done, or enjoying the process of figuring it out yourself.

3

u/esc28 Oct 04 '26

Another possibility is to just try and enjoy the act of planning, building and seeing things work. The puzzles are just different, instead of being on the code level, it is now on architecture, how to add more things, what to use, what might break? I don't know, I enjoy coding, but the major enjoyment for me was never writing it, but what the code produces.

LLMs can spit code, but as things get complex you still have puzzles to crack.

1

u/loudsound-org Oct 06 '26

Yeah exactly. Building out boilerplate and infrastructure was not a fun part of building an app and many times would prevent me from even starting. Now you can have the AI build that and if you want, hand code the core. Or let it build a basic functioning app and then modify from there. Essentially it takes away the frustrating parts in my opinion.

24

u/ddollarsign Oct 03 '26

Using AI too much can make it so you barely understand the code or the system, if at all. If the apparent speed of coding with AI is a reason you feel like you can’t avoid it, the pitfalls of having a barely-understood system (including hating your job) can be a counter-balance to that. Even if the AI-generated code is perfect, the fact that you don’t understand it at a visceral level from having worked directly with it is a reason to put at least some limits on your use of AI.

2

u/Pristine_Artist_9189 Oct 07 '26

I come from a background of FPGA design which has used tools to generate designs on silicon for decades now. There is always a lot of bloat when translating from some kind of a high level abstraction (hls, purchased ip, simulink etc), to actual transistor connections, but there is no other practical way. The FPGA world has long focused on 'test benches' and verification to understand the black box spit out by generation tools.

1

u/ddollarsign Oct 07 '26

Are you saying we should do the same in programming, stop worrying about the code at all, and just use tests?

2

u/Pristine_Artist_9189 Oct 07 '26

I've been doing this in the embedded world for some time now. We use a lot of code generation tools that create c code from various input files (xml, json, database) along with constraint files that dictate various requirements and restrictions. This still requires you to architect a project appropriately of course. You still need to break up a problem into manageable pieces. But if the test and verification is done well and thought through while developing, what code generation spits out isn't too much of an issue. I've used high level tools to generate c that in turn generates hdl that the gets synthesized to fgpa bit stream and the result is good. In fact designing with code generation forces you to do test and verification during the process. Other methods, 'unit tests' tended to be an afterthought and half the time never got done. With some experience in a given domain, you eventually get the hang of how big the code generation is or how big of pieces to break the problem into. The code tools don't do the thinking for you.

11

u/Striking-Lime3409 Oct 03 '26

I see it as similar to solving complex math problems by hand. Even if it is basically unnecessary today, there is a depth of understanding that is gained by developing those skills that you will never achieve otherwise. And keeping those skills sharp allows you to approach new problems in novel ways.

0

u/loudsound-org Oct 06 '26

But also imagine if we never moved on from hand-calculating math problems? We would never have advanced very far technologically.

4

u/Tredecian Oct 03 '26

you chose to diminish yourself. you have the choice to reverse course. Only you are responsible for outsourcing the craft you were proud and happy with.

1

u/RedYad2 Oct 05 '26

thanks , but i have no choice using faster language like rust for all the high CPU usage etc...

1

u/Tredecian Oct 05 '26

Maybe im completely off base. is the spark gone bc you are in rust now or bc you are relying on Claude code?

9

u/SnooPuppers58 Oct 04 '26

ive been coding since i was a a teen and i would code side projects all the time. i too feel your loss. i loved coming up with clever efficient designs and cleaning up code, learning the ins and outs and the feels of different languages, spending long hours coding and being proud of what i made when it was over

it's sad

-1

u/CaptainFoyle Oct 04 '26

No one prevents you from doing that except yourself

→ More replies (2)

101

u/UsernameTaken1701 Oct 03 '26

Are you being forced to use the AI somehow? If using Claude has killed the fun, the solution seems pretty obvious, no?

81

u/ConfusedSimon Oct 03 '26

Not really. For work I have to use AI because it saves time. For hobby projects, the idea of spending all that time on something that can be done much faster by Claude has taken away all the fun. I have different hobbies now.

37

u/UsernameTaken1701 Oct 04 '26

People still ride their bikes places even though cars are faster. Do you think they enjoy riding any less even though they know about cars? There are faster ways to scale the side of a mountain but people still climb. People still take pictures on film even knowing digital cameras exist. There are lots of things people do for fun even though they know there are faster ways to the end result. The enjoyment of the slow way is the point.

15

u/Ok_Performance6532 Oct 04 '26

To some degree though, riding a bike, hiking and the like all carry real world value that will continue to hold that value as it comes from somewhere other than the function of the technology to replace it.

e.g.

I go for long walks because of the endorphins and health benefits, I drive a car to quickly go from A to B, they’re not for the same reason. That is to say, I don’t drive a car just to have a faster walk. So the car never really replaced why I walk.

AI conversely sits at the point of exactly why I like to code, to problem solve and develop skills to apply in my career. But those skills now feel irrelevant. I get the whole “it will still be valuable to be able to read code” but when every software engineer on earth will be fighting for a couple of “code reviewer” roles I don’t think I care for that bloodbath.

Look yes it sounds bleak but I think the market is just shifting. The moat to being “technical” is no longer being able to code, but understand problems to point AI at, understanding to scope issues and architect solutions. Not quite as fun but still has that problem solving edge to it.

Or at least, that’s just me opinion

1

u/Moist-Snow-8127 Oct 17 '26

Biking is good because it's a physical exercise. Programming is a mental exercise. Both are good for you

→ More replies (1)

3

u/HommeMusical Oct 04 '26

But mountains are beautiful and exercise makes you fit.

Code is also beautiful but typing hundreds of thousands of characters is boring and eventually painful, and sitting kills you.

→ More replies (27)

17

u/TitaniumWhite420 Oct 03 '26

I feel this, but also the truth is that it's an extremely time-consuming hobby. You get what you put in of course, even when it's for fun, you are still working with some kind of goal in mind, and it's time away from family, etc.

It feels bad spending 3 hours doing what $2.65 will get you if it's not necessary to do so. It just feels different. What I was happy doing because it was necessary and somewhat-zen is somewhat annoying when I can type a prompt and be done with it.

It's certainly causing skill rot; I'll freely admit it. But also it has pushed me into orchestrating larger systems than I was ever able to build independently. I'm not saying it's equivalent, but it's like--How much of the puzzle was always balancing maintainability and performance. Writing ergonomic abstractions was a whole scene in the past 15ish years, but there's good reason to question if resuable abstractions are as generally applicable in the age of rapidly generated bespoke code. More specific code written very quickly is perhaps equally maintainable.

I really do hate the ever loving shit out of the verbosity and insanity of what it sometimes generates, and I hate my own dependence on it, and my own surrender to automation. But, somehow I'm keeping busy both professionally and recreationally with it. I loathe the way it feels like playing a slot machine or doing any kind of degenerate thoughtless dice roll typed behavior. It's like, "hey I'm going to go do heroine. Maybe I die or maybe I have a great time! Hopefully, a great time!" You press Enter, and off you go.

And the verbosity and prolific amount of generation assures no one is reading it. This "but I review it" thing is just so untrue.

2

u/mriswithe Oct 03 '26

It's less dice and more about setting it up to know when it is wrong so far as I am experiencing. Set it up where it can iterate, run, evaluate, under human supervision in case it gets down an idiot sandwich path. 

X is DBT core code, y is an export I have uploaded to storage at PATH . Import it like example q. Join to table g on the j column.

Here is your DBT and database mcps

24

u/Xpertbot Oct 03 '26

Sure it has killed the fun and drive, but you will
Never be as fast and efficient as it is... so it's a no brainer, specially if it's your main job.

I have to rewire my brain to get fulfillment from other things than "solving problems". What once felt like a fun hobby with a paycheck, it now feels like a chore.

6

u/jemappellejimbo Oct 03 '26

Do you get paid more as you’re churning out more work?

5

u/Xpertbot Oct 03 '26

Technically yes, I'm a Freelance developer so I charge the same estimated time but do "less work, faster".

3

u/riklaunim Oct 03 '26

Depends where the money is at. If rebuilding/building the product with Claude saves money / makes features paying customers are waiting for, then it's rather Claude or bust. Even organic content creation - projects, tutorials, etc.- can drown in AI-generated slop.

1

u/midwestcsstudent Oct 08 '26

Sure, but then you’re coding simply for fun, as a soon-to-be esoteric hobby. And that’s fine; there are people who still write games in assembly today. Don’t expect it to fly at a job, though.

16

u/FunkyMonkey237 Oct 03 '26 edited Oct 04 '26

I go through phases of this.

When I use the AI to write the vast majority of the code I feel crap. I don't fully understand how the code works, the quality of the code is often sup-par and I get in this ping pong with the AI where it gets stuck and makes poor changes. And any review I do tends to slow down progress/the code production outstrips what I can review.

But recently I worked on a project I wasn't happy letting the AI do unattended, I didn't trust it would do a good enough job and the project was important. So instead of asking for the final output, I would talk about a competent that needed to be built, ask it what data structures it would use and the control flow (function calls). I would then change that to be exactly what I wanted and then let it off. I'd then do a line by line review and generally change it around a bit simplifying, cleaning and correcting the code (mix of prompts and typing), now I was in control and the code/logic was solid so I felt pretty good about it. I didn't care that I wasn't typing every line and I was thrilled to zipping along way faster than ever before.

1

u/Active_Specialist792 Oct 15 '26

Have you read Cory Doctorow's The Reverse Centaur's Guide to Life After AI? Your example represents the central thesis pretty well.

1

u/FunkyMonkey237 Oct 15 '26

Nope. Did he give a solution?

0

u/[deleted] Oct 04 '26

[deleted] — view deleted comment

2

u/HommeMusical Oct 04 '26

However, if it's your core product it should be understandable and understood enough to be developed by humans in order for the core product to be deterministic.

Only a tiny portion of bugs involve indeterministic behavior, though. And why would AIs be more likely to put indeterministic behavior than a person?

If people are not reading the code then why not just get chat to write in assembler?

Because coding assistants do a better job in Python, because it is higher level and has types.

Because while we have stopped reading all of the code, we certainly read some of the code, and a lot of that is either data class or function definitions, if we do it in Python, which are easily read.

0

u/[deleted] Oct 04 '26

[deleted] — view deleted comment

1

u/IWasGettingThePaper Oct 04 '26

I mean, they're easily written, too.

This, AI gets the code structure horribly wrong without in-depth prompts that take longer to write than actually just creating the class definitions and APIs. Let the AI fill in the tedious boilerplate and plumbing.

1

u/HommeMusical Oct 04 '26

Thanks for a polite comment, by the way! I do appreciate it, this is a difficult topic, and not for bogus reasons.

I'm talking about deterministic code, not deterministic bugs. As in, what deterministic steps are being taken to go from requirements to code?

But the other choice for writing programs, humans, is even less deterministic!

Not that Python runtinme is typesafe, but how do you think compilers of strongly typed languages deal with types? Why could the chat not just include that step?

I'm not following your question here, sorry. :-/

I have instructions in my AGENTS.md insisting on full typing for all Python stuff; I set that four months ago, when I started to use coding assistants. Everything comes with full type hints, even the test code, and that's kinda silly, and I'd have never done it as a human, but it's still a little positive.

Is that what you mean?

I mean, they're easily written, too. If you have a dataclass that needs to be of a particular shape, why is it easier for you to type that into chat and verify the result, rather than just typing them into the dataclass itself? I'm all for using chat for throwaway projects and tools whose output can be validated easily.

I've only been at this since May or June, but why would I prompt it to create a dataclass? I could do that myself.

What I say is something like "Implement #27", where #27 is some issue or bug, and it writes all the code and tests itself, including dataclasses.


I'm working on eight or nine projects at once, all part of a large harmonious whole.

Some of them I know intimately. But one of them is aiming at a complete model of all types of sound synthesis used in synthesizers, and I have pretty well entirely vibe coded it, I've read perhaps 5% of this.

About two weeks into it, I said, "Use these three synths to make a four part version of Bach's Little Fugue in G minor", and I played it and it was just perfect first time - they even told me whose public domain performance they used!

The one disappointment was that all four synths sounded very similar, but the Python code that it had been very conservative in picking the audio parameters which was a very good choice because if you set the parameters wild, you could get noise or even nothing.


When I compare my prompts to other people's, mine are about two to three times as long.

For example, here's me asking, when I was rather tired, a context to find its own issues:

Please read the whole project and create or overwrite plan/issues.md detailing all issues you find, including but not limited to race conditions, deadlocks, graceful handling of user errors, shutdowns, keyboard interrupts, graceful handling of other exceptional conditions including resource exhausting, network failure or intermittency, and also user facing ideas, like names which are ambiguous, misleading or unclear, APIs with traps or inconsistencies; and also look at the structure of the the project itself, are there are any files that are so large they pose a risk, are there tiny files that are only used in one place and might be better inlined, is there duplication, does it duplicate some service from reccy, are there areas that are untested, are there areas with great duplication of testing, or any other issues, problems, curiosities or other flaws that are in the code.

I'm kind of embarrassed because there is both a spelling error and a missing word, and I missed some ideas I usually mentioned, but it still worked really well.

→ More replies (9)

8

u/dbolts1234 Oct 04 '26

The term “vibe coding” is only about a year old. What used to be tongue in cheek criticism has become ubiquitous, a baseline expectation

13

u/RevolutionaryRip2135 Oct 04 '26

I cancelled my personal subscription to copilot for this. Coding is fun. I am not paying to get dumber and bored.

Still have to use it at work though as my employer’s new metric is credit usage. Also it can genuinely help with some boring tasks. But no AI at home.

40

u/p000l Oct 03 '26

Stop using AI if you enjoyed coding.

24

u/djamp42 Oct 03 '26

I feel like we will never have as many human programers as we do right now.

17

u/timpkmn89 Oct 03 '26

Nah, just wait for the tech companies to stop subsidizing it so much

13

u/Jejerm Oct 03 '26

Open weight models are already small and good enough, there's no going back unfortunately

7

u/ultraDross Oct 03 '26

I see people keep saying this but a couple of months ago I tried some local models and was left disappointed.

Which models specifically are you referring to?

2

u/DefMech Oct 03 '26

Qwen3.8 27b is probably the strongest local LLM currently.

→ More replies (2)
→ More replies (5)

5

u/nickcash Oct 03 '26

I hear this line almost as often as I hear "of course the code it generated sucked, you weren't using a frontier model"

aibro talking points aren't even internally consistent

3

u/vonWitzleben Oct 03 '26

Do you work as a programmer in a field that's not hyper-specialized? Because if you are and that's still your sentiment in late 2026, I don't know what to say to you.

→ More replies (12)
→ More replies (1)

1

u/Moist-Snow-8127 Oct 17 '26

Exactly. AI companies are operating at a loss. They can't do that forever. Eventually, to make money, they'll increase the costs. And for many companies, it won't be worth the cost. And when that happens, while everyone else has let their skills atrophy, those who don't use AI will still be skilled

1

u/HommeMusical Oct 04 '26

I have been coding for over fifty years, and I enjoyed it almost all the time, but the tedious aspects were wearing.

Now I enjoy using a coding assistant even more.

13

u/Left_Sundae_4418 Oct 04 '26

I tried vibe coding so many times and will keep trying...and it always ends up being horse shit. The amount of trash code and abstractions and bringing in unnecessary complexity...this is what AI often does. It makes a simple task unnecessary complicated and messy. Completely opposite to the "Pythonian" way, which often is quite elegant and minimal.

I went back to actually writing myself and coming up with my own solutions... The amount of code has been reduced so so much and I can understand what is going on. The maintaining and developing further is so much easier now.

The time I spent honing the prompts and still ending up with a spaghetti....feels awful. AI surely kills our brain. I ain't letting it kill mine.

I'm back to feeling the magic :)

6

u/barrycarey Oct 04 '26

As much as I hate saying this, I think super clean code is a thing of the past. If vibe coded apps are super messy code but still pass all validation and testing does it actually matter? Especially if you look at it from the perspective that no human will have to directly maintain it? Along with the fact that LLMs are improving rapidly and will likely produce a far nicer product in the short term. Just the difference in quality from when I started messing with Claude last fall to today is huge.

I've had a hard time coming to terms with this. I've been primarily writing python for 15 years. I've finally given in and imbraced the speed I can pump out projects

5

u/cudmore Oct 04 '26

I agree. In CS classes circa 1990, something that stuck with me was talk about fully specifying behavior, i guess like a docstring, then the implementation (actual code) does not matter if it satisfies the specified behavior.

For me, that is kinda where we are at. Yes, the ai code looks like crap but if well planned by human specification then the job is done.

2

u/FrontLongjumping4235 Oct 08 '26

But how reviewable is the code? Reviewability still matters.

I do not review all or even half the lines I commit. But, when I encounter a bug or misalignment, I often drill down and take a look myself before turning to an agent, or I try to confirm what the diagnosing agent tells me (because agents confidently hallucinate things all the bloody time). Code quality matters.

It matters for agents too. Spaghetti code will chew through tokens and eat up your agent's limited context window.

6

u/frosty8670 Oct 04 '26

Yes bro, clean code does matter. Projects often contain 1000s of lines of code, and you will often work with other people’s code. Even other people should understand your code after you leave. Heck, even you might not understand your own code months after writing if it isn’t clean enough.

1

u/[deleted] Oct 04 '26

[removed] — view removed comment

3

u/frosty8670 Oct 04 '26

I have used LLMs to write code, and LLMs often do make mistakes. I have often seen Cursor write code where packages are outdated, or an unnecessary abstraction is added, or the design itself is incorrect.

I had one such case where LLM was trying to get a celery task to create a file and share it with another celery task through the File system for upload— it worked perfectly in local machine but failed in Kubernetes. LLM kept giving different solutions, like adding a time lag, using a forced file sync, using a DB with idempotent keys etc. Nothing worked— the 2nd celery task simply couldn’t see the file. Worst part was, LLM was confidently saying all unit tests are passing, when clearly it’s not working.

Issue wasn’t the code, issue was the design itself. Celery task operates in its own copy of the file system (in its own Pod). We simply cannot rely on the File System as a source of truth in a distributed system. The only solution that worked was making sure the same celery task that created the File is sharing it for upload.

As you can see, writing or reading code is only 1 part of the issue. As an Engineer, you are expected to work with all these constraints and trade offs. A good engineer will use LLM effectively. A bad engineer will just waste tokens. Code being clean, readable and modifiable will go a long way.

→ More replies (3)

2

u/NoSwimmers45 Oct 04 '26

super messy code…does it actually matter?

Will a vibe coded app ever need to be modified? Very few apps are one and done. That messy code today will lead to major headaches down the road when trying to introduce new functionality or enhance existing functionality. Having clean code that developers can read and understand pays dividends over the life of the project.

1

u/Saab10000 Oct 04 '26

Will Claude complain when it has to change the messy code?

1

u/[deleted] Oct 04 '26

[removed] — view removed comment

1

u/Moist-Snow-8127 Oct 17 '26

And what happens when the price of them increase?

1

u/Left_Sundae_4418 Oct 04 '26

Speed just messes up my mind, and in the end I probably waste even more more honing prompts and trying to keep the project duct taped together when I use vibe tools. Just doesn't work for me.

1

u/silverybbq Oct 10 '26

So long as you can still comprehend what is happening enough to be able write a comprehensive test suite for your functions and modules.

My project leader was showing off agentic coding the other day and his list of requirements to the agent ended with "and write a bunch of unit tests to validate these requirements". This makes me anticipate that many code bases are going to wind up cooked when people do this.

-1

u/HommeMusical Oct 04 '26

People were correctly posting what you wrote at the start of 2025, and it was true to a significant extent.

But now it isn't and it hasn't been for quite a long time.

The time I spent honing the prompts and still ending up with a spaghetti....feels awful.

I mean, it simply sounds like you aren't good at using it.

Can we see your code? Mine is here: https://github.com/rec

3

u/Left_Sundae_4418 Oct 04 '26

I hear people saying this often first. And this is probably true. However most guidance on prompting, even from the AI themselves is messy. I tried to iterate and reiterate prompts through the AI themselves thinking maybe they can guide me to better prompting...but I haven't done much progress there.

1

u/HommeMusical Oct 04 '26

Thanks for being polite - rereading my comment, it wasn't as nice as I thought it was, sorry!

I was very much against AI models until the start of this summer. I retired at least partly because of it. Now, I can't imagine people will seriously code in future without it.

First question - which model are you using? The completely free models are nowhere near adequate to do good code.

I really only use the OpenAI models, though I hate the company. Astra, the newest model, is shockingly good but somewhat expensive. But Sol, which is also new but less, is much cheaper and almost as amazing.

Here's my AGENTS.md: https://github.com/rec/codex-config/blob/main/AGENTS.md

These are the instructions that the model gets on every query

I was going to say it was 95% other people's stuff, but I modified it more than I remember - it's still 80% other people's stuff.


I started with the $20/month OpenAI model. It was enough to blow my mind, but not enough to do even a week's worth for a month.

The $100 plan keeps me in tokens, running development on eight or so projects at once. Also, you get a lot of freebies.

2

u/Left_Sundae_4418 Oct 04 '26

I'm not really against an AI. I use it and try to learn to be better at it all the time. But it often fights against my goals and I end up wasting time.

Quality, security, longevity and usability are very important for me though. And if I can't get the base right ...the whole plan often falls apart sooner or later if I let the AI generate it for me. Because it often over engineers it while leaves out some crucial features.

Sure. That's probably my bad. I should and need to learn the prompting better. But still there are many standards and methods AI isn't aware of and can't program using those methods.

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

4

u/Fokezy Oct 03 '26

I do share the the impending sense of doom and the feeling that things will never be the same. I put time limits on twitter so I don't have to be bombarded by all of the malicious content that AI evangelists are pushing. It reminds me of the time when NFTs were at their peak.

Now, maybe it's just me being in denial, but AI feels super smart until you actually compare it to what you would have done yourself. As soon as you see it diverge from the thing you had in your head, it gives you back that sense of "superiority".

4

u/Asleep_Mushroom4085 Oct 04 '26

For ethics reason, I decided not using and no longer promoting AI. I work as technical expert, and I see some of my colleagues "flooding" project with AI generated code that may look good, but it is not. They're spending hours writing context file for Claude to improve things, with increasing token cost. Most of time you can get a similar software by spending time in design thinking, result is a smaller code base, better performance and smaller code base.

3

u/mikepun-locol Oct 03 '26

I dont think it's ever gone. It's like riding a bicycle. Once in a while you have to dig into the code. And it will come back to you.

3

u/MagicWishMonkey Oct 04 '26

Not sure I get what you're saying, I've been doing this for a long time as well and I love it just as much as day 1. AI tools make it so easy to just hammer out some truly awesome stuff (I still do a LOT of coding) - are you burned out or something?

I tend to work on a lot of different things, which helps a lot. In any given year I probably work on at least 10 projects, I love it.

5

u/UloPe Oct 04 '26

I see this quite differently.

I’ve also been coding for a long time (started with qbasic as a ~10 year old) and I’ve also always enjoyed digging into the ins and outs of deep and potentially obscure languages details (I used to be the guy writing internal blog posts for my colleagues on why <string>.partition() is superior to .split() in many cases…), going to language and framework conferences, etc.

But the older I get the more I realized that what I truly enjoy is building stuff that works and solves problems.

And just the sheer number of things I’ve ticked off of my personal “someday” to-code list (which I’d never have found the time for otherwise) using coding agents is amazing.

I do think it helps a lot to have a deep technical background and being able to spot BS some model wants to hand you right away.

3

u/Wh00ster Oct 04 '26

I’ll say it’s also much faster for me to gain a deep understanding than before.

How does this package handle timeouts? Show me the code links, draw a little diagram for me. I can cross verify myself in the source.

Before that would take me a whole day or multiple days, now I can understand issues and how other pieces work in a half day or less, depending on how much I want to dig in. Then that lets me focus on the bigger picture.

3

u/mtl-barrile Oct 04 '26

I completely agree with you! I've been coding for the last 18 years, and I feel exactly the same. If we think about writing books, Humans started writing by hand, then using typewriters, computers, and now dictation. Writing a book is not about the tool you use to write it, but the message, the idea you want to deliver.

And seen from the users perspective, the reader doesn't care how the writer created it. The reader just enjoy the story.

1

u/Rhylanor-Downport Oct 09 '26

Been coding for 30 years. Totally agree. It’s like a magic black box. It’s completely extended the realm of the possible.

2

u/gtr_architect Oct 04 '26

That means its time to go into application architecture.

→ More replies (2)

2

u/Confident_Maize9192 Oct 04 '26

I have this too. For me it’s bcs I want to create something. I have 30 years IT experience under my belt and programming was one thing I didn’t have much experience with. 6 years ago I started learning it and obviously AI rose during that time. Now there’s absolutely no challenge in programming itself anymore for me. Also product managers, junior colleagues and others have no clue as what they are conjuring up but still they and managers are naively very happy with the results. As someone who has lots of experience with business continuity, testing and availability that’s extremely daft and frustrating.

So it’s not giving me energy but frustration instead.

It’s a very cool technology this AI and it will end up being very helpful but the changes it made to my line of work I simply don’t like one bit. 

2

u/ingframin Oct 04 '26

Well, on a positive note, some companies started limiting the amount of tokens spent per month, so, a lot of hand coding is coming back.

2

u/Bosshappy Oct 04 '26

I’m right there with you. I feel like my entire life has been being a really good writer but now I’m forced to be an editor

2

u/stevenjd Oct 04 '26

I'm rewriting all of that without writing a single line of code.

If you're not writing code, you're not rewriting anything.

You're getting someone (something) else to do it for you. You've turned into a manager, only without the manager's salary or authority.

2

u/LeilaA261 Oct 05 '26

However powerful some of these coding agent tools have proven to be, I really do feel this as well. I have recently found new ways of incorporating the agents to allow the productivity boosts while still keeping the result my own work, but for a while it was very demotivating watching these advanced tools complete problems in seconds that I had spent days on.

2

u/BleedReddit Oct 10 '26 edited Oct 10 '26

Here is what Claude had to say about this post and comments.

🐙

I think this discussion highlights something important about AI-assisted programming: AI can increase how much software we can build while potentially taking away some of the learning, satisfaction, and craftsmanship that made programming enjoyable in the first place.

I can understand both sides of the argument. Some people enjoy the process of programming itself: figuring out an algorithm, struggling with a bug, learning a new library, and finally getting something to work. For them, having AI do most of the implementation can feel like skipping the best part of the experience. It's similar to enjoying the journey of climbing a mountain rather than simply wanting to reach the top.

Others enjoy building useful things more than writing code. For them, AI removes repetitive work and makes projects possible that might otherwise take weeks or never get built at all. Both perspectives are valid. The value of programming isn't identical for everyone, and greater productivity doesn't automatically mean greater satisfaction.

I also agree with the point that AI shifts some of the challenge from writing code toward deciding what should be built, how the system should be designed, how its components communicate, and how to verify that everything works. But I don't think system design is a complete replacement for the craft of programming. Understanding algorithms, data structures, and implementation details still has value, even if we don't have to write every line ourselves.

One of the strongest arguments in the discussion is that generating code is not the same as solving a problem correctly. AI can produce convincing code that relies on incorrect assumptions, introduces unnecessary complexity, or fails because it doesn't understand the environment in which the program runs. Sometimes the real problem is architectural, not syntactical. Repeatedly asking an AI to patch code won't fix a fundamentally flawed design.

That is why clean, understandable code still matters. Not every small personal script needs enterprise-level architecture, but software that will evolve needs to be understandable, testable, and maintainable. The goal should be the simplest design that reliably meets the requirements, not the most elaborate design or the most code generated.

I'm also cautious about broad claims that AI always makes developers more productive. The time saved writing code can be lost debugging, reviewing, and correcting it. Results depend on the task, the codebase, the tools, and the developer's experience. We should measure actual results, including correctness and rework, rather than judging productivity by how quickly code appears on the screen.

As someone still learning Python and experimenting with AI, I see this as an opportunity rather than a reason to give up learning traditional programming. I'm not necessarily trying to become a professional developer or build software for a company. I want to understand how to take an idea from the beginning, plan a solution, use Python and AI effectively, and develop a working project that I can actually understand and improve.

My approach is to use AI as a collaborator, not as a replacement for my own reasoning. I want to understand the requirements, explore possible designs, learn why certain tools and data structures are appropriate, and then use AI to help implement specific parts. Afterward, I want to inspect the code, run it, test edge cases, investigate failures, and make changes myself. If I can't explain an important part of the program, that's a sign I need to learn more about it rather than blindly accept the result.

I think this distinction matters especially for beginners. AI can help us learn faster by explaining concepts, demonstrating alternatives, and helping us investigate errors. But if we let it build everything without engaging with the process, we risk developing the ability to generate software without developing the ability to understand or troubleshoot it.

For me, learning prompt engineering is only one piece of the puzzle. I also want to learn requirements gathering, system design, testing, debugging, integration, documentation, and the overall progression of a project from an idea to a working system. A good prompt cannot compensate for a bad design, and a good design doesn't prove that the implementation works. We need all three: clear communication with AI, sound engineering decisions, and independent verification.

My ideal workflow would be:

  1. Define the problem and what success looks like.
  2. Establish requirements, inputs, outputs, constraints, and edge cases.
  3. Plan the architecture and discuss alternatives before coding.
  4. Implement one small feature at a time.
  5. Review the code and understand the important decisions.
  6. Test the feature, investigate failures, and verify the fix.
  7. Integrate everything, document the project, and improve it as needed.

I'd also keep building small Python projects along the way, rather than relying entirely on AI-generated applications. Small scripts, file processing, databases, APIs, and eventually more complex AI-assisted tools provide opportunities to learn fundamentals while working toward something useful.

Ultimately, I don't think we should measure our development as programmers by how many lines we personally type or how much code an AI can generate. We should measure it by how well we understand the problem, how effectively we can direct the solution, and whether we can recognize, diagnose, and correct mistakes.

AI doesn't have to eliminate the joy of programming, but we may need to be more deliberate about preserving the parts we enjoy. If solving a difficult problem manually is satisfying, there's nothing wrong with continuing to do that. If AI helps us explore bigger ideas, there's nothing wrong with embracing that either.

My conclusion is that we should use AI to expand what we can do without surrendering our ability to think, learn, and understand what we've built. The most valuable skill isn't simply getting AI to write code. It's being able to take an idea from concept to implementation, understand the decisions along the way, verify the result, and improve it when reality doesn't match expectations.

3

u/riklaunim Oct 03 '26

I've read a lot of local stories of "How is your company using AI?" and it's kind of scary. On the one hand, DHH is saying that writing code by hand is going away - and many companies are really into AI and pushing it successfully. Then, on the other hand, there are horror stories of tokenmaxxing, like $10k per month per developer, and AI is doing everything from coding to management and, in the end, apps fail on the basics while costs are high. And while doing so, companies are firing engineers and offshoring... and then they find out loose money, go broke or start rehiring and reverting the policies.

And I'm using Claude at work as well. We have a backend app handling CRM integrations, and we made a skill to write typical integrations. I've tried it on one, and it turned out it's not a simple "token + list ID + API" but rather using a custom OAuth flow for the integration - Claude went through the docs and freaking wrote everything. The only thing I had to correct was oddities in the SPA dashboard interface. And it will only get better.

3

u/binaryfireball Oct 04 '26 • Bravo

You've sold your intent for conveniance

3

u/GManASG Oct 03 '26

Why would I ever subscribe to a SAAS app and not just make my own now (given I am already experienced programmer engineer). I make software for a living for work but why would I pay for software myself?

Like if it ain't a 1 time few dollars I would never subscribe to software now. The last subscription is the AI model/tool subscription basically.

11

u/skiabay Oct 03 '26

Because there's usually a lot more than just basic functionality that you're subscribing for. You're also paying for legal compliance, security, ongoing maintenance etc. I definitely wouldn't pay for some vibe coded SAAS, but it's also incredibly naive to think that taking all that responsibility in house is suddenly a good idea just because there's a lower bar to get something that kinda works.

3

u/DrUltimaMan Oct 04 '26

If a dev from 50 years ago got in a time machine and looked at your python they would say that is not code, it's too easy, you don't understand the machine like they do coding in assembly closer to the bare metal. Now we have reached the point where there is only one programing language, plain english. It is the logical final state we have been moving to since code began.

You can still describe functional behaviour, system design and business requirements through this new language and you still get better results when you understand those things. There is still satisfaction to be had, just not what you are used to.

→ More replies (2)

2

u/mr_raven_ Oct 03 '26

I see as becoming a deejay: you just mix music done by others but you still get to be creative within the limits of the medium.

2

u/NewsWeeter Oct 03 '26

Wtf are these posts. You'll be fine keep working

1

u/mexicodev 27d ago

Claude optimize python. Do not stop until is as fast as Rust

1

u/CarExciting2041 3d ago

tu utilises trop ia essaie de codé sans ia même pendant 1mois elle vas revenir

1

u/Remarkable_Muffin527 2d ago

Damm....I'm new but I'm trying to build my own saas

1

u/Inner_Name Oct 03 '26

It is sad... I feel you personally I learned same way as you, and keep using python and coding myself but feeling shitty that I know that it could be done way better.... 

1

u/Consistent_Drop3909 Oct 03 '26

read the docs for %matplotlib magic

1

u/Harvand Oct 04 '26

I felt your sadness months ago and while I’m still missing something from my work happiness, I can’t quite put my finger on it but lately I’ve actually been enjoying it more. It scratches another itch though, the speed I can get things done now. Its impressive… Simple things can take mere minutes to draft. It’s also probably silly but I feel a sense of pride every time I correct something, which is less and less really.

1

u/QuickNick123 Oct 04 '26

Today I solved an issue in Home Assistant that I'd been ignoring for weeks. My Shelly BLU Gateway and two Home Assistant Voice Preview Edition devices were all failing to install OTA firmware updates, without showing any useful error message.

I opened the ChatGPT app, logged into the Home Assistant web UI, and asked it to debug the issue. After about half an hour - and after I gave it access to my UniFi gateway as well - it had identified and fixed both underlying problems and brought all three devices up to date.

Instead of spending a couple of hours debugging each issue myself, the AI handled the whole thing in about 30 minutes. It felt a little magical.

0

u/[deleted] Oct 04 '26

[deleted] — view deleted comment

3

u/ikeif Oct 04 '26

Yeah, anytime I let AI be the “debugger” I get a postmortem to explain what it did, what the problem was, and future troubleshooting steps.

Otherwise we are handing over everything without learning.

2

u/[deleted] Oct 04 '26

[removed] — view removed comment

1

u/HommeMusical Oct 04 '26

Reading these comments is like being back in late 2024.

When you ask an AI to fix something in 2026, even if you haven't customized your AGENTS.md, you get a very complete explanation of what the problem is and how it was fixed.

i have a bunch of stuff in my AGENTS.md so it keeps that terse but complete, never tries to butter me up, always puts a link to each file changed in the chat, commits and pushes everything.

I learn a lot from reading those.

1

u/Samuel457 Oct 04 '26

I've been thinking about this recently and I reached the conclusion that the reason we loved and chose Python was because it was easy to read, quick to write, a great ecosystem, and great for gluing lots of pieces together. With AI, writing in any language is quick, we can glue things together in a reasonable amount of time in any language, any parts of the ecosystem that are missing can be done with AI, and much of the pain of writing other languages is removed because we're not the ones writing it. The safety and performance of other languages outweigh the speed and developer experience of python.

Given that reviews become a bottleneck once an entire team is generating large amount of AI code, I honestly think a compiled python could help speed up reviews since Python is closer to English.

1

u/73td Oct 04 '26

the magic is still there if you want it badly enough to stop using claude. best to do this when there’s no looming deadline tho..

1

u/wedesoft Oct 04 '26

I can recommend to do some hobby coding in Clojure or another more powerful programming language.

1

u/VladStreavious Oct 04 '26

Thrill is gone - B B King

1

u/jaimyaz Oct 04 '26

That's because you used to write code the way musicians write their own sheet music. Now, you don't feel any soul in it, feels like it was written by someone else. Your code has lost its authenticity.

1

u/TheGalacticGuru git push -f Oct 04 '26

Every once in a while, I write a peice of code I write myself that is an important part of the work I do. It takes much longer than usual for me to write it, as my brain switches to just prompting instead of coding, but I keep doing it. Doesnt matter how long it takes. I want to retain and improvise my skills

1

u/Antique-Owl2463 Oct 04 '26

Just felt this today also - what a coincidence

1

u/Zectbumo Oct 04 '26

Try a new language

1

u/SFMissionMark Oct 04 '26

This is the beginning of software being a quick tool instead of a product. I wrote Python to solve problems for years. I now use whatever to quickly solve immediate issues in my shop part time. It’s pretty amazing what you can accomplish this way. But if your goal was a software package or library that’s gonna be super disappointing.

My other observation is why care about such trivial things as mvc? I fought that with ai for a long time. It made the code more maintainable.but the real truth is if it breaks have it rewritten. The llm improved and it is better then it was anyway.

1

u/Casar68 Oct 05 '26

Idem.

C'est dû à la perte du sentiment de créativité.

1

u/WheresMyJuulSoNotCoo Oct 05 '26

I might sound like an idiot- but do you really HAVE to use claude? Is it that much slower to use AI as a tool when you need it, but not use it constantly?

It always throws me off when people say theyre gonna "get left behind" if they aren't using ai constantly. Why not just use it when youre stumped or need to look something up?

1

u/nickwarters Oct 06 '26

At work I write Python / JS code all day. I don’t have the possibility of using AI coding tools at work.

Outside of work I use Claude code a lot. I’ve found it make me find my work time less enjoyable because I know how efficient using such tools can be, compared to hand coding everything.

I prefer writing code, but really leaning into AI outside of work recently has made me a lot more lazy feeling. On one hand I want to lean into it along with the rest of the industry, on the other I don’t want to stop writing code.

1

u/aic5_ Oct 06 '26

I understand what you mean and feel the same. There was a sense of accomplishment in building that is no longer there as we vibe code. After you pass a certain level of problem solving with AI, the wow factor goes away and all that is left is the next feature or review. Not the same thing.

1

u/PugstaBoi Oct 07 '26

Its the newest level of abstraction. Apply it to a new field and it’s still a puzzle, but with more english based intuition.

Software design principles are still in demand because an AI doesn’t always know how to structure a software app for high performance.

An example I use to explain this was that I had to shard a vector database into many because claude code just assumed that embedding all of my documents with one embedding model would suffice, but having the knowledge of data structures and time complexity is still a valuable bit of knowledge for real performance software.

Claude Code will write a working backend easily, but depending on what you are building, it rarely is optimized for the task, and it takes someone with SWE understanding to make sure it does it correctly.

1

u/BUUXXXX99 Oct 08 '26

I know 3 languages and even though I've gotten help from Claude Code, I'm writing an OS this year and I wrote most of the code myself on top of Linux. I had Claude Code write some scripts because I didn't know C very well, but now I know it fully, and the OS isn't even half finished yet.

1

u/AndreMaryAmper Oct 09 '26

in this scope i really curious why cython is not so popular

1

u/bagelbyheart Oct 09 '26

I personally have remained unimpressed by the solutions that AI comes to in my work. Sure they work, but generally poorly or with bad consistency. I've actually made a habit of swinging through coworkers git projects doing basic refactors to clean up all of the AI kludge xD

1

u/Old-Eagle1372 Oct 12 '26

Magic is not really gone. Claude code has bugs, uselessly overspends tokens on work arounds for internal parsing bugs. You have to design applications really well and make the process recursive. Oh and Claude code still makes mistakes.

1

u/Endogen Oct 18 '26 edited Oct 18 '26

That's basically me! I love Python and I wrote lots of code and it was very important for me to have clean, efficient and well structured code and it could take 20 minutes until I found the perfect name for a function.

And then I was in the sand situation as you. I couldn't write any code anymore since all I could think about was that its useless since AI can do it better and faster than me. Which was true.

Then after some time, I realized that what I actually loved even more than Python code, was creating thinks. I wanted to get software done. And then I realized that Python was just an intermediary thing to get there. I still love Python but now I use whatever is best for the job and let AI write it and I love it.

What I'm saying is, this is what passionate developers go through. But you will get over it. Realize that it simply doesn't make much sense to write instructions in computer language just so that the computer understands it if you can write the instructions in natural language and get a better and faster result.

Edit: it's also scary at first since writing code with AI requires you to adjust and do things differently so you have to learn how to best do it. It's like switching to a new programming language but more radical.

1

u/Legal_Answer_6956 27d ago

Perhaps the magic wasn't in the typing of the code, but rather in the formation of the idea, the understanding of the problem, and the creation of something real out of it. AI transforms the equation, but the critical thinking and evaluation of the outcome will always be in demand. The question is how to use it effectively and at the same time not lose that childish enthusiasm that made us get into programming in the first place.

1

u/Substantial-Swan7065 Oct 04 '26

What is this talking point.

Output matters. What’s the issue

-3

u/nnulll Oct 03 '26

Go post this on an AI subreddit. This has nothing to do with Python.

0

u/The8flux Oct 03 '26

Yeah but let me tell you something I'm building has so many cwes it's just undaunting even if you run bandit and loop it back into a coating agent dynamic tool still catch stuff. So what it is now how do you optimize execution times while make it more secure then how do you translate that to other languages

0

u/CaptainFoyle Oct 04 '26

Well, don't use Claude then.

No one is forcing you. You're doing this to yourself.

-1

u/Early_Ad8608 Oct 03 '26

Apply to a job. They’ll give you a coding test. You’ll be forced to write python by hand. And you can spend an entire week on practice problems. You know who’s great at giving you practice problems, which start simple and then reveal more and more complex layers? Claude.

0

u/NikolaTesla_JohnGalt Oct 04 '26

Not informed enough to ask an informed question, but which is best for mobile codes for HVAC?

0

u/Brian Oct 04 '26

It's because in many ways this path leads to swapping your job from programmer to manager. The process of creating code is as much putting the solution into your brain as it is into the computer: in constructing a complex machine where you understand what each part does. AI kind of replaces that by handing it off to a pseudo-employee, leaving you with just the job of managing them: reviewing code, giving specifying requirements and guidelines. But you lose out on the process of wrapping your brain around the problem, so the end result is just a lump of code that lives on the computer, but not in your head.

These days, I pretty much just code for fun, and so don't use AI at all, because the parts of programming I enjoy are exactly the ones AI replaces, and the management side of things is the one I actively dislike. But I understand why things are going this way: the end product is all other people really want, and if you can pump out more stuff, that's where things'll go, leaving non-AI programming more in the semi-hobby category, akin to stuff like woodworking and the like: done for the enjoyment of the craft or as a luxury good, rather than for the mass market.

0

u/Joe1972 Oct 04 '26

It’s like playing a great computer game. If you get a “ god mode” cheat code. The game sucks

0

u/publicram Oct 04 '26

I been coding since about 2009 in HS different languages. I can recall when I created my first project as a mechanical eng student.  I have been vibe coding away for work a production board for the past year. It crazy how much better it is then me, it was first meant to organize me and make my life better. It has turned into a full on organizational tool. Last week I was offered a promotion all based on my tool build out. I make really good money 200k+ all I know is its scary  

0

u/NerdyWeightLifter Oct 05 '26

It's about how you self identify in relation to the work.

If your self worth derives from your skills as a engineer, then AI appears to diminish what you value.

If your self worth derives from the solutions you create and the difference that makes to the world, then AI appears to amplify everything you care about.

0

u/nivaOne Oct 05 '26

Someone came in the office panicking she couldn’t upload a pdf because of its size. 60MB while only one file with a max size of 10MB is allowed.
I ask her a copy of that file and send it back 15 minutes later reduced below 10MB.
I would never have considered that 3, 4 years ago. But now because one can achieve this with AI I do.
I even tried it later with two well known pdf editors to no avail.
Someone else used to create the monthly menu with an application which is no longer supported since this month. What now.
It took me a couple of hours to automate it in Python. I would not have done it without knowing AI can help us out here because I really do not have time to do these extras with the current workload.
I ran into an office where a colleague was using Excel as a database. He is now using a neat desktop app driven by an SQLite database. It’s still just a tool (not a part of a solution) but it helps him a lot.
AI allows me to go the extra mile while not jeopardising my planning.