|
|
|
|
|
by aequitas
3140 days ago
|
|
"Being a senior engineer means realising not everything should be done the way you want it to be." I think it's funny how these opinions can completely flip over or oscillate over time. In this case: As junior you known nothing so not everything can be done the way you want, then later you think you know a lot more and everything should be done your way, after that you really know a lot more and realise not everything should be done the way you want it to be. Same like Friday deployments. First time you always deploy on Friday until you deploy that bug and you weekend gets destroyed. You never deploy on a Friday again. Until you discover testing and CI which makes Friday deploys trivial again. (maybe until the next time it breaks?). |
|
For example, “Gotta release code quickly” to “quick is good, but all code must have unit tests and rigorous code reviews” to “gotta be quicker, can’t always be holding things up because of a rejected code review!”
I’ve also worked places where that didn’t happen because management, and the engineering culture, were strong.