from Hacker News

Recently hired as team lead/manager, team seems somewhat dysfunctional.

by tmoaad on 7/16/20, 6:53 PM with 5 comments

• by tmoaad on 7/16/20, 7:03 PM

  I've shortened the title just a bit due to the character limit.

  72 hours of production downtime is /insane/ to think about and with such a brass attitude coming from the team as well.... I'd be inclined to go to the board and ask for additional funding to start a new team/begin knowledge transfer ASAP and start winding down the old team. I'd be curious to know why the CTO's isn't being grilled about the downtime and if they even have a CAPA process to prevent this from happening again?

  Additionally, one of the commenters in the thread also points out just how important devops as a /culture/ is compared to just treating it as something to be bolted on at a later point in the organization life. I've worked with too many devs that seem to think their involvement ends when they throw the code over the proverbial "devops fence".

• by CodeWriter23 on 7/16/20, 10:10 PM

  Start by firing the guy who pushed the code on Friday Night. Then email the rest of the team and say anyone who wants a job to just show up 9AM Monday.

• by 908B64B197 on 7/16/20, 7:35 PM

  I'm curious how the compensation is structured. For someone with equity in the business a 72 hours downtime is horrible.

  But if the devs are making below market rate, and their compensation is unrelated to the business' performance, it's a little unrealistic to expect them to be going above and beyond for on-call duties.

• by beckingz on 7/16/20, 8:45 PM

  Pushing code to production at 11pm on a friday???

  Yikes.