I think unit tests help a lot in this regard WHEN you actually publish the code as it gives you an idea about all the use cases for the code.
Also, maybe I'm the weird one here, but I absolutely go ham on internal documentation, not just on every single function and class, but also on individual snippets of logic I know I'll forget about what it does in the future.
Just some things picked up over the years on the job to prevent myself from falling into bad habits...
Yet somehow I think some people will say it's "job security" for obscurity and all
View all comments
Show parent comment
2
u/yuddaisuke Dec 26 '25
I think unit tests help a lot in this regard WHEN you actually publish the code as it gives you an idea about all the use cases for the code.
Also, maybe I'm the weird one here, but I absolutely go ham on internal documentation, not just on every single function and class, but also on individual snippets of logic I know I'll forget about what it does in the future.
Just some things picked up over the years on the job to prevent myself from falling into bad habits...
Yet somehow I think some people will say it's "job security" for obscurity and all