Extending on that, I do not agree with "do not define yourself with your job". Why not? It's a big, if not biggest, part of almost everyone's life. What's bad is defining yourself with your job ALONE. Psychological safety comes from having multiple self-identities: be an engineer at work, a volunteer on weekends, amateur radio enthusiast on Thursdays nights, or whatever, and don't mix those!

Granted, this is a linter, not a formatter, but my larger point is I am glad that Python ecosystem evolved like it did recently.

Not unlike that experience, I also saw coding agents spend lots of tokens trying to fix a benign issue, as well as doing the opposite - like disabling the tests !!! when they don't pass. :facepalm:

I grew to trust AI results in terms of overall correctness, but I still have hard time trusting their *judgement* on the *code quality*.

To be clear, that's an honest question, not sarcasm of anything. I only assume I don't know about some corner case with SSH or something? Because we have those on our websites, they are supposed to be used to verify signatures, etc. How is publishing them bad?

Good luck with your new business!!! It sounds super exciting, hope everything works out, the roof, the patrons, and all.

Hm. Most users usually need 0 or 1 of those at a time. Makes me question other choices in there.

I live and work in France, and oh boy... It's just cultural. Every email is like a letter to the King. "Would you be so kind enough to consider my humble request that is described hereafter in next three paragraphs". Funny thing: I welcome AI summaries on those.

My other pet peeve: meeting invitations. Half of the meetings in my calendar are called "Point" in French (loosely translated as "Topic"), the other half has no descriptions but the headlines. I tried the "I am not going unless I know why I am invited" thing to no avail - you cannot win this against the entire org.

So, you guess from the list of invitees. Or ask the organizer at lunch. Then go with them to the meeting to discuss the Topic for 15 minutes. Which could have been easily discussed at lunch, but lunch time is reserved to discuss food, not work.

Oh well. I love our cuisine, though. And the culture, and people, everything really. Just not how we write email.

Just today I ran Claude Code with Sonnet 5 and, to compare, OpenCode with a local Qwen 3.6, and asked both to explain me a pull request, same prompt, same CLAUDE.md file. Here are some excerpts:

Sonnet title: "Teaching the program to speak JSON"

Qwen title: "JSON deserialization support for AMQP consumers"

Sonnet's description of a larger context: "Rather than one giant program doing everything, the work is split across small applications that talk to each other through RabbitMQ".

Qwen: "This is a Python library that provides shared infrastructure for AMQP data processing applications: applications extend MessageConsumer class, implement process_one_message(), and the framework handles the rest, consuming messages from RabbitMQ, calling the application logic, and publishing results."

Like, from the Sonnet's description alone I wouldn't even know what this code does for real!

And the metaphors by Claude... "From bytes to DataFrames, and back", ugh... Just call it desirialization, come on!

And then later, Claude Code spent a paragraph explaining me how a lookup table is better than an `if .. else` ladder, duh... While Qwen actually focused directly on the nature of the change.

OK, I admit it Sonnet produced a super nice HTML report, Qwen's output is more reminiscent of a man page in HTML format. But... this kind of goes the same way, the niceties just create a impression of being professional.

Did you notice anything like this? Is this new in Sonnet 5, or did I just miss it before? Do you remediate this somehow?

Comments URL: https://news.ycombinator.com/item?id=48774742

Points: 1

# Comments: 2

I am sorry to being rude, I just don't understand this publishing beyond getting the media exposure.

You need two transistors, a ferrite coil and a small set of simpler elements. And it is so simple you can actually explain what every part of the circuit does.

And then the reward... Once built you could listen to BBC regardless of where you are in Europe. My kids just LOVED IT, no Netflix K-Drama replaces this experience. My daughter was listening to BBC on her radio every night going to sleep.

Wait... same like in real life you mean?