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.

897 Upvotes

310 comments sorted by

View all comments

Show parent comments

0

u/[deleted] Oct 04 '26

[deleted]

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]

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)