61–70 of 110 posts
Honestly, my biggest programming pet peeves are not really technical but social. Constantly working on moving targets, being responsible for both fleshing out and building these moving targets, having to estimate work and then being told that that takes too long, ...
I can't believe that in 2025 it is still hard to find documentation for basic functionality in languages as ubiquitous as, say, Python. If I google something simple I get 100 junk sites of garbage (GeeksForGeeks, W3Schools, etc), a bunch of AI-generated crap, a bunch of archaic out-of-date stuff, the official documentation which is a wall of dense text, some tutorials that mention the basics, a bunch of shitty bootca…
be the change you wish to see
monorepos complicate everything. documentation doesn't factor them in, deployment instructions don't factor them in. efficient deployment needs a whole additional framework on top. additionally AI also doesn't understand the combination of things, but when it does, a new major version of a framework has dropped and isn't in the training set. I'm just venting because that's the prompt and I don't need a solution or re…
Hash maps. Everyone just turns their brains off and uses hash maps for everything. The code this creates is awful for users, awful for people consuming it, awful for people maintaining it. Think for five minutes about your abstraction and create meaningful types and config languages, don't just hack it with a hashmap.
It sort of sounds like you want a ~yaml config that's unmarshaled to an object.
Earlier quoted context omitted.
What kind of Python information were you having trouble finding? I do have this problem as well, I've just started a job with Ruby and it took too many searches until I could find the official docs for some kind of syntax. For Python I feel it's easy to find stdlib docs, but can be hard to find some specific things about the language itself in the official docs - sometimes it's too technical and I wish there was a mo…
For ruby, you need a good book, and be good at reading references docs.
Having used Scala and TypeScript a lot for work over the last ~5 years, I think I'm going to say static typing. It's lunacy. Computers mostly don't work in types, my brain usually doesn't work in types, and only a small subset of the problems I work on really work in types. The amount of modern languages that think they can solve everything in the type system boggles my mind.
I’m building something in Python right now and the lack of static types is just painful.
That being said, Scala and typescript have really powerful (maybe too powerful?) type systems.
Hash maps. Everyone just turns their brains off and uses hash maps for everything. The code this creates is awful for users, awful for people consuming it, awful for people maintaining it. Think for five minutes about your abstraction and create meaningful types and config languages, don't just hack it with a hashmap.
It’s frustrating to have to find the right place to report a bug, learn the specific format the project is expecting, then have the bug closed by a “stale bot” after a few weeks. I wish there were an independent, cross-product bug tracker that focused on cataloguing and diagnosing bugs for the benefit of users rather than on tracking work for the benefit of the developer.
That is an interesting idea, like a universal bug tracker If you could report a bug on any product/project and it’s up to the users to open/verify/close it Could put pressure on companies to improve quality since the number of bugs is public