If yours uses a thermal sensing element (not just mixing blind),I’ve found running it through its full temperature range helps a lot. I suspect limescale and other crap build up on the thermal element. It adds several years on to the life of the mixer. Descaling it would likely also work, but involves removing it from the pipes, to get the cleaner in.
Then someone refactors the stop sign into a speed limit sign, leaves the comment unchanged, and years later someone else gets the fun job of figuring out which comments are lies
Also someone applied an auto code formatter to the entire codebase in the meantime, and the original file got moved a couple times, maybe just the path or into an entirely new repo
Let’s face it, such comments usually cause more problems than do good. If someone changes the code and forgets to modify the comment, the reader might favor one or another at random. “Stop sign” example isn’t the best but you get my point.
Comments at best should explain some non-obvious logic, or some sort of reasons for implementing one way or another. For SDKs and packages overall, public APIs should also be commented. The rest imo should be readable from code.
A form of “self documentation” I like to do is create variables for conditions before using it in an if statement. If you break down a funky conditional into easy to read variables it becomes a lot more clear what it’s trying to do.
If someone changes the code and forgets to modify the comment, the reader might favor one or another at random.
Hence why you should comment why, not how/what.
// slow down traffic before crossing busy main road
Now you can change the stop sign to a yield without touching the comment. Or judge that the comment can be removed if it’s clear the main road does no longer exist.
I would hope it modifies the original. It’s implied in the name. A function that returns all but the first item should be named something like tail or without_first_item.
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.