![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
What’s the difference?
What’s the difference?
Cause none of my choices of ISP supports it…
they tell you they want someone with 5 years Java experience.
Or 6 years of experience with that framework that’s 3 years old which is par for the course for dating apps; unrealistic standards.
Obligatory fuck DST
You can get a small high-frequency whistle you can attach on the front of the car that should scare them away. It is outside audible range and supposedly has lowered the amount of incidents from a test phase our local elder care conducted when they placed them on all their cars.
There’s also a Ship of Theseus thing going on here since your cells are constantly being replaced by new cells. At what point do you stop being you and are simply the train of thought that carried over from your old cells?
Hate it when it happens
Put down the bong while I’m in the shower? How preposterous!
The Earth’s gravity well extends far beyond the atmosphere. The moon is for example is well inside the gravity well and even the hill sphere meaning Earth’s gravity is the dominant gravity force on the moon.
Hey, no need for shower shaming. As long as it doesn’t hurt anyone they’re within their rights to do as they please in the shower.
I don’t know about you but my phone is waterproof for this exact reason.
Luckily hippos aren’t known to be good at biking.
No, it is the bad kind of puppy!
Code should always by itself document the “how” of the code, otherwise the code most likely isn’t good enough. Something the code can never do is explain the “why” of the code, something that a lot of programmers skip. If you ever find yourself explaining the “how” in the comments, maybe run through the code once more and see if something can be simplified or variables can get more descriptive names.
For me, that’s what was originally meant with self-documenting code. A shame lazy programmers hijacked the term in order to avoid writing any documentation.