3 ms·
Another thing those juniors are seldom good at, is knowing how to refactor an existing old code base. Which is not surprising, as everything they worked on duri
by yxhuvud 6y ago
Another thing those juniors are seldom good at, is knowing how to refactor an existing old code base. Which is not surprising, as everything they worked on during education is new code. Knowing how to change a code base from one abstraction to another is a skill that often take many years and lots of mistakes to learn.
- sushshshsh 6y agoYet another boomer generalization designed to sow biases against hiring younger people. At what age am I allowed to become a senior, oh wise one?
- abraae 6y ago"Junior" is about experience, not age. You can be a junior developer at age 30, or a sage by that same age.
- bombela 6y agoWe really gain skill for this over time. As I gain experience, I find that I understand in more details existing codebases. This increased my chance of a successful refactoring. Especially when replacing a core abstraction without a full rewrite.
- mech422 6y agoUsually senior is 5+ years experience... At what age did you start working, oh snarky one ?
- eggsmediumrare 6y agoThe tech industry has a lot of problems, but bias against hiring younger people is not one of them.
- yxhuvud 6y agoWhich part of my answer gave the idea that this is about age? FWIW, academia have never been good at teaching these skills, so the answer to your question is "You'll stop being junior with regards to refactoring complex code bases whenever you have enough experience of refactoring in big old code bases". Mentors pushing you in the right direction can also help. But this is very much a skill acquired by actually doing.