From a developer's perspective, being on call effectively for team members are driven by these factors:
There has to be a Team Working Agreement. This will produce a desirable schedule approved by everyone on the team as well as provision of the necessary resources(software and hardware).
If you happen to be the nuts and bolts of the system then you need to change this. I always advise my team members to avoid this by writing readable codes with proper naming conventions, i.e codes that can tell a story, code reviews, Jira notes, meaningful Git comments and pair programming if need be so some one else can play the part.
Personally there has to be a balance between one's passion for work and having spare time to yourself. Passion for work might bring recognitions, recommendations and promotions while having my spare time allows for better lifestyle, self development thereby having insights to improvement and implementations of better and robust systems.
And finally concerning compensation, this is usually a blurred line as it can come in various forms. But it surely does encourage team members to participate in on call activities.
Passion for work might bring recognitions, recommendations and promotions while having my spare time allows for better lifestyle, self development thereby
having insights to improvement and implementations of better and robust systems.
This is such a good reminder to keep worklife balance front of mind. Thank you for such a thoughtful reply.
From a developer's perspective, being on call effectively for team members are driven by these factors:
There has to be a Team Working Agreement. This will produce a desirable schedule approved by everyone on the team as well as provision of the necessary resources(software and hardware).
If you happen to be the nuts and bolts of the system then you need to change this. I always advise my team members to avoid this by writing readable codes with proper naming conventions, i.e codes that can tell a story, code reviews, Jira notes, meaningful Git comments and pair programming if need be so some one else can play the part.
Personally there has to be a balance between one's passion for work and having spare time to yourself. Passion for work might bring recognitions, recommendations and promotions while having my spare time allows for better lifestyle, self development thereby having insights to improvement and implementations of better and robust systems.
And finally concerning compensation, this is usually a blurred line as it can come in various forms. But it surely does encourage team members to participate in on call activities.
This is such a good reminder to keep worklife balance front of mind. Thank you for such a thoughtful reply.
U r most welcome.