6 ms·
Legacy or not, I don't consider anyone really senior unless they have spent building and more importantly maintaining/fixing a system at least for 3-5 years at
by codegeek 2y ago
Legacy or not, I don't consider anyone really senior unless they have spent building and more importantly maintaining/fixing a system at least for 3-5 years at one single place and have done this at least 2-3 times across different companies. We all know that it is a lot easier to start a new/greenfield project with shiny tech etc. It is a lot harder to maintain especially once it is 2-3 years old and in production with tons of users.
- milesrout 2y agoNo a senior engineer is someone with at least 3 years experience, haven't you seen any job ads?!
- jessekv 2y agoIt's like credit cards. You start with senior and from there it's gold, platinum, diamond and so on.
- hnthrow90348765 2y agoThat's nothing, I don't consider anyone a real senior unless they've maintained something for 10 years! But seriously, everyone tries to move these goal posts. We still have no good idea.
- Cthulhu_ 2y agoThe challenge there is that "legacy" codebase are just so much slower; you spend more time figuring out what needs to be done and how, than just writing code like in a greenfield project. And everyone knows the latter is just so much more fun.