1: On call duty? We can't ask our devs! They work 9-6, M-F. That's it. (Remember when it was 9-5, hmm?)
2: Our servers run 24x7x365
1: The devs are our most precious resource. We can't piss them off.
2: You seem to misunderstand the role of a sr developer and yours as manager.
A feature (or any other chunk of code) is never really "done" until the code is erased from production. We all must support it, somehow. Bugs happen. Customers call. We are paid for working systems. Clicking "Deliver" and "Accept" is not the end of our responsibility.
As a manager, it is your job to express the importance of production code to your staff. They are not royalty, or privileged spoiled generation whatever. In fact, most have been remarkably pragmatic and supportive when they are informed about the importance of on-call.
So, if y'all listening, I'm going to try an experiment with my stalled writing process. I want feedback. I welcome feedback. I will exchange 🍺🍷🥃🍕 for feedback. I'm writing a blog post (y'know, long form tweeting) about annual performance reviews.
"Yay! It's time for my annual performance review!" -- No one. Ever.
Here's a more interesting statistic: "only 4 percent of HR managers think their system of assessing employees is effective at measuring performance — and 83 percent say their systems need an overhaul."