I always tell our new developers: If your new feature works, you aren’t done, you have to check if your code has to be refined first, before checking it in. (e.g. duplicated passages made into a common function, ugly hacks removed and “done properly”, stuff like this)
Documentation and testing are also mandatory, but that’s because of the industry we work in.
You can avoid having to do something like a total refactor that takes half the year, if you do the rough equivalent of a sanity check / clean up pass, when any new system or feature set is added, and make that habitual.
Its… kinda like how if you just do a bit of regular shopping, regular meal prep, regularly do the dishes, whatever, everything just flows easier in general.
The longer you run lean, move fast and break things… yeah it can improve output in the short term, but medium to long term, you’ll run yourself ragged, and things will break and fall apart.
Absolutely correct.
I always tell our new developers: If your new feature works, you aren’t done, you have to check if your code has to be refined first, before checking it in. (e.g. duplicated passages made into a common function, ugly hacks removed and “done properly”, stuff like this) Documentation and testing are also mandatory, but that’s because of the industry we work in.
Yep.
You can avoid having to do something like a total refactor that takes half the year, if you do the rough equivalent of a sanity check / clean up pass, when any new system or feature set is added, and make that habitual.
Its… kinda like how if you just do a bit of regular shopping, regular meal prep, regularly do the dishes, whatever, everything just flows easier in general.
The longer you run lean, move fast and break things… yeah it can improve output in the short term, but medium to long term, you’ll run yourself ragged, and things will break and fall apart.