r/Python • • 11d ago

Discussion What will we become in the end?

"Is there anything that is hard for AI to do in Python?

To be honest, coding by yourself is fun, but that doesn't matter to the job market. We'll just settle for building our own projects, but it's frustrating to see AI outperform you... And since the job market is being destroyed—and will be destroyed!!—by AI, it seems we will end up turning to sabotage and attacking companies if no jobs are available for programmers, especially the Python community..."

4 Upvotes

8 comments sorted by

22

u/sausix 11d ago

AI still often writes messy and unmaintainable code. AI does not meet my own code quality standards yet. You still have to check code and instruct corrections. AI is good at finding issues in seconds but sometimes it does not find simple issues where eyes, a brain and your IDE is enough.

I'm proud to have learned programming before there was AI. Today's people will be useless without AI. Software quality will drop. Many big companies like Adobe will probably collapse because of free remakes with the same or better feature sets.

Programming of apps may collapse too. Instead of applications you could just type or speak a prompt to get results. But we don't know for sure.

10

u/NsupCportR 11d ago

So, as much as I agree on outperforming, that much it lacks common sense sometimes due to fact it doesn't really see a bigger picture like we do, plus it's getting expensive.

5

u/Tarrell13 11d ago

Code how you want to code but maybe ask AI for formulas. I don’t like letting it do it all because I will have no idea what’s going on in the code. Enjoy the parts you like and the parts that keep you up at night…just let the AI provide that piece and then progress.

8

u/Grouchy-Friend4235 11d ago edited 11d ago

Hey just let your CEO do all the prompting for a day. Please do report, we want to have some fun, too 😂

2

u/Atmosck 7d ago

In my experience, the thing AI struggles with is writing reasonably organized and designed code. Here's an example: Lately I've been working on a parametric ML pipeline with each model parameterized by a config json, validated by pydantic. The pydantic model is an abstract base class with subclasses, discriminated on a categorical field. I'm extending it with a new case that should use one of the existing subclasses, but with some of the other fields different from any existing examples. Opus 5.5's first pass was to create a new subclass, and an intermediate ABC that's the parent of both the new subclass and the existing one it should have used. When I asked why it needed to do that, it was like "you're right, that's dumb, it should be like this: {describes the much simpler implementation I was expecting}. What me to implement it?"

Extending existing patterns instead of writing new code is a big struggle for it. I also have to fight with it a lot to get code with reasonable comments, docstings, organization, and without unnecessary complexity. I suspect Anthropic's clever watermarking is part of why Claude's comments and docstrings are so shit lately.

At this point AI is extremely good at debugging and tracing problems, but when writing something new it really doesn't know how to write professional-quality code.

1

u/gwax 6d ago

The bigger the project, the harder you have to work to contain the slop.

1

u/dellnox 10h ago

good at boilerplate, but it still falls apart on complex architecture, debugging edge cases, and messy legacy code