I can verify that chasing autonomy is worth it. Almost a decade ago, I ditched Java to focus on a single language and have less overhead as a full-stack engineer. It was the best bet of my life, and it paid off.
About being on call - I never did it. But I’m applying to an organization that has mandatory on-call. However, my understanding is that if you’re confident in the pieces you deploy, you might sleep well. What is your take on this? Is mandatory on-call a bad thing? What does it tell about an organization?
Very solid post. Thank you for sharing it. We also write about DevOps, you can check out one of our articles here https://www.metridev.com/metrics/code-review-guidelines-best-strategies/
Great ideas in here, Luca!
I can verify that chasing autonomy is worth it. Almost a decade ago, I ditched Java to focus on a single language and have less overhead as a full-stack engineer. It was the best bet of my life, and it paid off.
About being on call - I never did it. But I’m applying to an organization that has mandatory on-call. However, my understanding is that if you’re confident in the pieces you deploy, you might sleep well. What is your take on this? Is mandatory on-call a bad thing? What does it tell about an organization?