Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
asgs810964dIf new code doesn't have to depend on the existing code, then it is interesting.
Otherwise, adding a few lines here and there is less interesting and more risky and dangerous
SomeNone86664dSounds like transcribing hand-written code from a special code sheet onto punch cards. So 60s…
Back then I guess they all wore formal dress (suit and tie) with a lab coat on top.
vomitmachine34964dI'm currently doing that over multiple systems actually. Unit tests are one of the best tools. Break your program down into single role responsibility classes and functions and test those as well. Run those every time you make a change. It ultra sucks when the previous guys didn't write any unit tests though. It's a lot of work but it helps prevent breaking the system and your code will be tested in the future.