31–40 of 110 posts
The fact that most new programming services and products are oriented towards C-suite types, and not to the people who actually use them. Most websites looks like [1] or [2] which are full of corporate-friendly buzzwords but don't help me understand what they actually do or how they work. To get a concrete understanding I need to go to github and find repos that actually use the product to even understand what it's f…
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…
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…
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…
PEPs are often great documentation. They definitely don't cover everything, but they can be helpful
The fact that most new programming services and products are oriented towards C-suite types, and not to the people who actually use them. Most websites looks like [1] or [2] which are full of corporate-friendly buzzwords but don't help me understand what they actually do or how they work. To get a concrete understanding I need to go to github and find repos that actually use the product to even understand what it's f…
Stuff I wrote in Javascript/jQuery twenty years ago still works fine in the browser. Now I’ve got some Gatsby projects I built around 2019 and I can't deploy them due to various degrees of incompatibility with minimum versions of Node.
I get why, as a server platform, Node has to be improved to eliminate security holes. But for static site deployment, there ought to be some kind of stable foundation that will work forever; or, at least, build tools should be designed around the idea of stable Node features that won't deprecate or dissolve as the future marches on.
The amount of modern languages that think they can solve everything in the type system boggles my mind.
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…
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.
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…
The fact that most new programming services and products are oriented towards C-suite types, and not to the people who actually use them. Most websites looks like [1] or [2] which are full of corporate-friendly buzzwords but don't help me understand what they actually do or how they work. To get a concrete understanding I need to go to github and find repos that actually use the product to even understand what it's f…
I actually think it's the right approach for a tech business - your main landing pages should market towards the buyers and then you can have more technical documentation pages for the users. As an example from your comment: https://tailscale.com/kb/1151/what-is-tailscale