Advice I Wish I Knew as a Junior Developer(raheeljunaid.com) |
Advice I Wish I Knew as a Junior Developer(raheeljunaid.com) |
Although, on the other end is people that spend way too much time attacking the problem with limited context, and then asking for help after the day is almost done.
If a junior developer complains about legacy code, or just gives up, it shows they’re resilient enough just won’t put the work in when things get hard
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?
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.