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.
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
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 unless keyword is an abomination
x = "I disagree."
y = false
puts x unless y
I miss it when writing python.
Specifically I hate it as a prefix. It's even worse when else clauses become involved!
x = "this is great"
y = "this is awful"
z = false
unless(z)
puts(y)
else
puts(x)
end
Despite this being the perfect spot for one, I'm not a fan of ternary operators but syntax isn't supposed to matter...
Since we're going for unpopular opinions or hills to die on: if syntax didn't matter we'd all be using Ada.
Linux should be forked at a pre-ai date.
I've got good news for you!
Ha! Well, by a solid group of committed lead devs I guess is my point.
Who's coming with me!?
The entire modern web tech stack should be thrown in a dumpster, ignited with gasoline, and blown up with a nuke for good measure.
100%
I want an entire separation between my view and the data. We strayed from the true path as soon as we let web sites enforce the CSS
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.
How about overrated instead of dogshit?
The overlap between those circles is not insignificant.
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.
This is the only way I would ever use one. Local, open, more ethically trained.
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?
I remember on Reddit several years ago I said that automatic bitlocker is the curse of installing W11 on a laptop.
I got down voted so hard. One comment even said you should be thankful because encrypting by default should be the norm.
But yet if I add any thunderbolt device to my windows before I boot it, it requires me to input my 25 character bitlocker key... that's hosted online within my Microsoft account.
Bitlocker enabling by default without user input is horrible. Hosting the keys online is also horrible. It could be so easy to socal engineer into your Microsoft account.
HTML/TeX/etc are real programming languages that just happen to be declarative as opposed to imperative.
Unit tests are overrated to the point of being harmful. They have their place, but that place is certainly not "the base of the testing pyramid". They are useful for a very specific type of "units" - and using them anywhere else just messes things up.
Gosh I totally aggree! The amount of discussions I had about this is staggering.
From both sides. Devs who didn't understand what a unit-test actually is and devs who thought if they have unittests that they must have perfect functionality.