Code goes in the Developer folder

(I got used to that name on macOS, where it is the “canonical” name for it, because it automatically gets a special icon)

What !? Siblings hating each other seems exceedingly rare in my personal experience 😅

This towel doesn’t account for something like 90% of your body surface x)

I don’t care if human meat made for tastier, healthier hamburgers, and faster too ; I refuse to eat people for any reason whatsoever.

If you don’t see how this relates to AI, maybe you are AI yourself.

The only reason monorepos are used is because tooling for multi-repos is inadequate, or people don’t know how to use it.

Version control tooling is still at its “blackberry” stage anyway.

Write it yourself next time instead of generating it.

Evil spreads its tendrils further yet.

When I was young I thought “who needs 3 computers at once ?”

Now I get it.

The real question is : Why did you invite anyone over, before having a guest VLAN set up ? Classic beginner mistake.

I use ed too…

Except I have alias ed=$EDITOR and export EDITOR=nvim in my .zshrc x)

JavaScript is great for making websites !

Yes and no. “Real” programmers care about engineering choices ; and JS is the cardboard of programming languages.

Perfect for packaging (which in this metaphor is UI), horrible for building a bridge with. And vice-versa, I wouldn’t try and make amazon packaging out of reinforced concrete.

JavaScript really depends on the people writing it restricting themselves to a sane (ish) subset, just like C++

My personal gripe with JavaScript is how horribly slow it is. C++ at least has the merit of being fast once compiled. I wouldn’t feel great contributing to a JS project knowing fully well that a rewrite in a faster language would be 10x as effective as anything I could improve as is.

On the power user side, the nice thing about NixOS is rhat moving your config to another computer or server gets you a perfect clone, every time.

If you could go and muck around in there, this promise would be lost. Immutability makes it rock solid reliable.

The only correct kind of faucet is the kind with a thermostatic handle for temperature, and a separate handle for flow.

They are almost exclusively available for showers and that’s stupid. It’s the correct solution for the problem, with extremely few drawbacks.

The only improvement I could see is making the temperature handle short circuit to the drain until the water going through is hot enough. But I dont know if that’s really possible without electronics, and I really dont want my faucet handles to be plugged in or take AA batteries.

The perfect setup is a journey, not a destination. You will never be “done”, so enjoy the process.

Besides the privacy implications : trying to protect children from grooming by forbidding specific apps, is like trying to treat chickenpox with concealer.

The real problem is that our society is even producing people who would groom a child.

But as always, politicians will try to “prevent” crime at the latest possible point in the action chain, instead of going back to the source.

I dont want to understate the fact that going to the source is extremely hard to do in many cases ; but maybe people would be less disinterested in politics, if we were actually choosing between different treatments - instead of different brands of concealer - to treat our various collective cases of chicken pox.

No. These principles are supposedly designed to help those inexperienced programmers, but in my experience, they tend to do the opposite.

The rules are too complicated, and of dubious usefulness at best. Inexperienced programmers really need to be taught to keep things radically simple, and I don’t mean “single responsibility” or “short functions”.

I mean “stop trying to be clever”.

Getters and setters are superfluous in most cases, because you do not actually want to hide complexity from your users.

To use the usual trivial example : if you change your circle’s circumference from a property to a function, I need to know ! You just replaced a memory access with some arithmetic ; depending in my behaviour as a user this could be either great or really bad for my performance.

99% of code is too complicated for what it does because of principles like SOLID, and because of OOP.

Algorithms can be complex, but the way a system is put together should never be complicated. Computers are incredibly stupid, and will always perform better on linear code that batches similar operations together, which is not so coincidentally also what we understand best.

Our main issue in this industry is not premature optimisation anymore, but premature and excessive abstraction.