3 ms·
I recommend that you write notes on which aspects of the code are poorly put together, for your own benefit now, and also so you can remember it in the future.
by itronitron 6y ago
I recommend that you write notes on which aspects of the code are poorly put together, for your own benefit now, and also so you can remember it in the future.
I did this at a previous job, where the application code base had some very unique (I hope) characteristics. I haven't read my notes recently but it's comforting to know that I have a record of it.
- potta_coffee 6y agoThat's an excellent idea.
- jjice 6y agoI personally note all the code I use in multiple ways, even if I'm the only owner. General design and architecture especially helps in over-modularized environments. I think I had a similar modularized nightmare at my last job where each file was split into 3 files too many. Taking notes on how they connect and even drawing our the graphs can help a lot. Depending on how it would be received by your coworkers (sounds like not very well), you could make a main design doc in each repo and maybe sub documents in separate namespaces.