2021-02-03, 07:37, Wednesday
So I happen to be a morning person. Which means I usually habe to grind my coffee the day before, because the grinder is loud and wakes up the entire family. This is why I have to resort to tea for today, sadly.
It is very important to differentiate solving a problem from creating a product, or a framework, if you will. When there is a single problem (or a set of similar problems) that require a one-time solution, one can get by using spaghetty code and non-optinal solutions without getting into much trouble.
If the code is to be maintained and expanded, then you are writing a product. Now you shouldn't do spaghetti code or omit documenting. This is not about just you anymore, so minimize your succesors' suffering by putting extra effort into cleaning your code.
This seems obvious but is important to keep in mind. I found myself overoptimizing a peice of code required for one-time use.

Follow

@academicalnerd keep in mind that bad code quality increases the probability for bugs which may lead to invalid results due to opaque logic errors.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.