4 ms·
You have to assume a certain amount of domain knowledge, or you end up explaining the entire universe. In this case, "set point" is a well-understood term, and
by jdlshore 5y ago
You have to assume a certain amount of domain knowledge, or you end up explaining the entire universe.
In this case, "set point" is a well-understood term, and its purpose is similarly well-understood. [1] Although the team may wish to document it, the place to do so is in the team glossary (or other overview documentation), not in every function that uses it.
[1] http://faculty.washington.edu/brengelm/neut_zone/pg3.html http://faculty.washington.edu/brengelm/neut_zone/pg3.html
- watt 5y agoThanks for info, I did not know it's a common industry term! Anyway, the point I am driving is, it's more interesting to discuss _why_ would anyone change the "set point" - common scenarios and pitfalls, than just explaining the "update_set_point changes the set point". It's nice to go into details what are the consequences and common use-cases.