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.
[A photograph of a road signpost in front of a metal fence with a low, long building in the distance. The post has two signs on it. At the top is an octagonal sign, filled red with a white outline, reading “STOP”. Beneath it is a rectangular sign with an arrow pointing up to the stop sign, and text reading “THIS IS A STOP SIGN”.]
I am a human who transcribes posts to improve accessibility on Lemmy. Transcriptions help people who use screen readers or other assistive technology to use the site. For more information, see here.
Thanks! Not sure if there’s been other people doing any or not, but for my part I just do them when I find the time, which unfortunately isn’t all that often.
Sounds like a good use of comments. Explain why, not how. (that should be readable from the code for the most part. Unless you’re having function calls like xmmmuldp (simd) )
This actually makes a lot of sense. A computer executing the code and a human maintaining it need to know different things. A human needs to knon what the code does on a high level (what the programmer intended), how it handles (or does not handle) edge cases, etc. A computer only needs to know how to run the code at a super low level. Without comments, it is impossible to know if code is doing the right thing, or what is expected from the caller.
Just did this last week. Had a case for special handling db column “A” and wrote combined logic for “A” and “B” and spent an embarrassing amount of time wondering why “B” was still coming out wrong.
Edit: FFS does no one realize that women experience sex differently from men? Bad sex with an oblivious partner can be downright painful for a woman. The same is typically not true for men. My point was not that women don’t have sex or that they don’t enjoy sex. My point is that they don’t experience it the same way as men.
I disagree. When comments are essentially just a rephrasing of the class/method name or arguments it is not helpful and anything that is not helpful is cluttering up the code and making it harder to quickly see what the code is doing. I’d rather have no comments than comments like that.
I reserve comments for explaining why a section of code is needed or explaining how a complex algorithm works.
i = 0; // Set i to 0 is pointless.
if (last_output_vertex[i] == bounds[i]->length - 1) contibuting_bounds[i] = NULL; // stop outputting a bound if the entire bound has been output is helpful.
Comments can also be useful for explaining what the code is intended to do when debugging.
“Hey this function says it should return the number of apples, but looks like someone, not saying who, but someone had a brain fart and typed oranges in one variable. Who wrote this code anyway?”
I think even the second comment is not that helpful.
Just use (boolean) variables that phrase what your comment would explain, often more concise and better to read IMO. Also if the logic is more complex compose multiple named (boolean) variables. I think comments seldom make any sense at all (function doc is a one of the rare cases, mostly for the user of the library in the IDE).
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.