> You don't need to be a good engineer – these places are messes of legacy code created in fiefdoms ... For juniors coming in, "messes of legacy code" probably

> You don't need to be a good engineer – these places are messes of legacy code created in fiefdoms ... For juniors coming in, "messes of legacy code" probably isn't the best learning environment from a tech skills standpoint. For more sr folks coming in to "message of legacy code", you do need to be a good engineer, because you may have to be working around a lot of stuff that can't be changed. You may not have version control. You likely won't have any sort of fancy CI/CD/pipeline process. You may not have tests (as the code is likely untestable in its current state).