Conversation

Notices

1. Embed this notice
   Evan Prodromou (evan@cosocial.ca)'s status on Saturday, 26-Apr-2025 11:27:00 JST Evan Prodromou

   I have to admit that I'm not great about this. More often than not, I will get leads and seniors and myself together to fix the problem, and not even identify the responsible party. When they come in on Monday, they will get a talk with me or a lead, and we'll go over the problem with their code and how to avoid it in the future, and maybe the link with the outage will never be made explicit.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Saturday, 26-Apr-2025 11:28:59 JST Evan Prodromou

     in reply to

     I would like to shift to having more participatory fixes, so people understand that it's part of the job. So, I'm no, but I want to improve my process.

   • Embed this notice
     genehack (genehack@dementedandsadbut.social)'s status on Saturday, 26-Apr-2025 22:54:15 JST genehack

     in reply to

     @evan all of that but also, if you don’t get to help clean up, you never learn HOW to clean up. It’s a critical part of career progression.

     clacke likes this.
   • Embed this notice
     clacke (clacke@libranet.de)'s status on Saturday, 26-Apr-2025 22:54:16 JST clacke

     in reply to

     @evan In most cases, isn't the immediate fix a rollback? After that, the junior can take their time pairing with a senior to figure out why it went wrong and implement it correctly.

     For minor errors I will just write a fix, but for me it feels straight up rude to fix someone else's grave error without giving them a chance to do it themselves.