4 ms·
Take notes. Draw up an overview architectural diagram. Divide your notes into major sections for each area of the project and use it to jot down weird and inte
by kstenerud 3y ago
Take notes. Draw up an overview architectural diagram.
Divide your notes into major sections for each area of the project and use it to jot down weird and interesting bits as you encounter them.
This not only gives you a handy reference so that you're not relearning the same stuff all the time, but writing things down gives your memories more resilience, so you'll remember more on the spot.
- pillefitz 3y agoThis. Also, quiz yourself about the system, maybe allocate 15mins just for that a day. Why do we need X? How are these parts connected? Are there connections that are different? Why? Additionally, try to deeply understand the business logic. As a former dev who currently works on product, I'm often surprised how long it takes for developers to come up with solutions, which I can generate on the spot. I tend to believe there's no difference in technical skill, I just have a lot more context knowledge about what the system is supposed to do, making me more confident and thus faster in making technical decisions, despite having spent only a comparatively tiny fraction of time in the code base.
- cameron_b 3y agoYes, the exercise of “teaching” it helps retention even if you’re teaching yourself or a rubber duck. Model it, draw it, make a dashboard with servos that measure important metrics, any way to abstract it or reshape the information. Take on the onboarding presentations to help other people understand it and talk about it. It will help you to dig deeper and know it more by putting the information into a different context. Or in other words, that guy knows it because everyone asks him.