[mooreds]

Fun article! Lots of good points, each of which could be their own article. I did something similar[0] a few years back.

Author, if you feel inspired, would love to have you expand these and share the results.

For example, what are good ways to maintain relationships? When, if ever, should you let a relationship wither? Another example: what is a good way to get familiar with legacy code? What even is legacy code?

0: https://letterstoanewdeveloper.com/

[raheelrjunaid]

Very cool, thank you for sharing and for the feedback! I purposely left it to the reader to figure out the "how" since my goal was to answer the "what" and the "why." Most people figure out the how through experience. "All it takes is a little push."

For your examples, I maintain relationships by checking in every month or so by text or LinkedIn. The only relationships withered are those I've intentionally broken, not forgotten about.

Legacy code is stuff that nobody wants. Whether because its slow, the programming language is dead, the patterns are outdated, etc. I get familiar with legacy code the same way I get familiar with regular code: reading a lot of it and filling any gaps I see.