found this interesting take on how contributing to projects helps engineers bridge the gap between just writing code and actually leading architecture decisions. its basically abt using
git commit
workflows to practice the
high-stakes decision making needed for bigger roles.
it turns out side projects are more than just a hobby because they force you to review complex systems without
breaking everything at work. anyone else finding that maintaining legacy repos is the best way to learn lmao?
article:
https://dzone.com/articles/open-source-technical-leadership