Mine is that the useState hook is an actual plague on the entire React ecosystem. Regardless of your opinions of React, if you wanna use something then use it right.
You should definitely look at how your time related code works and not trust the libraries.
Because most of the time your assumptions about how your library works will be wrong. And the rest of the time your library will be riddled with bugs.
If you don’t prematurely optimize your code you’ll never optimize your code.
I know people are advised against premature optimization because it risks you wasting time on something that ends up unused.
But let’s be honest, once you get something into a working state will you ever be afforded the time to go back to it? Even if you are, are you really gonna choose to uproot code and do a refactor on it and potentially everything relying on it?
Rather than waiting until your hacks and workarounds run out and you absolutely have to do a refactor, I would prefer spending more time upfront to make sure it is efficient and flexible before moving on.
I’ve talked about it before, but I really hate PDFs. Specifically the things PDFs are used for. If you aren’t planning to print something and will only ever look at it on a screen, HTML is better. It’s so frustrating when you’re going to a website, you know, a thing that serves content in HTML, and then some piece of information is in a PDF.
The
unlesskeyword is an abominationLinux should be forked at a pre-ai date.
The entire modern web tech stack should be thrown in a dumpster, ignited with gasoline, and blown up with a nuke for good measure.
I just got out of an interview where they pretty much told me they will ask me to vibe coded the tool they’re working on. LLMs do not make your code faster, and you are not more productive using it. I will never change my mind. We coded for 70+ years without it. You’re gonna end up with some subtle hard to reproduce bugs that are intermittently reproducible, and code that is nearly unmaintainable, and nobody knows what it does or how it works.
Good luck with that.
Object oriented programming is dogshit.
Async/await turns the concepts from the [CSP] (https://en.wikipedia.org/wiki/Communicating_sequential_processes) that are useful into an overcomplicated mess in every language that implements it, and golang is a prime example of how clear and intuitive an implementation aligned with CSP can be without requiring arcane typing and language infrastructure that comes with async/await approaches.
I like local LLMs. I got to try one recently and it felt different using open ones than corporate ones.
My masochistic tendencies brought me back to say:
One reason python is a great language is that most LLMs are particularly good with it
Cloud computing is the biggest breach of privacy out there that we’ve adopted whole hearted.
if you’re making a user-facing program, you should always design with the possibility that it will be run on some truly dogshit hardware and you should make sure that they still have a good experience. good computer hardware is a luxury on the world scale, even before the rampocalypse
related, but the answer to the question “who still uses {x} these days?” is almost always way, wayyyy more people than you think
systemd does a lot of things very right and a mayor reason that linux is in a way better place than 15 years ago. 27 unmaintained tools are not better than one that is professionally developed.
Not a programmer, but I hate softwares that use python, why the fuck it requires 10 million dependencies to function?
