News for hackers. Stuff that matters.
Re:How to win the coding interview by vonmoltke on Tuesday May 31, 2016 @10:20AM (#11806646)
Meaning a lot of places have shitty processes and architecture and try to compensate by hiring people that fit their broken system. Case in point: having an architecture so fragile that a bad push is capable of taking down all your servers.
Re:How to win the coding interview by sokoloff on Tuesday May 31, 2016 @12:40PM (#11807624)
Trivial to have a breaking DB change or a software push where the only part of the app that works is the little part that tells the load balancer, "yep, I'm alive and healthy; send some traffic my way".

There are probably way more successful (100-million to couple billion dollar revenue) companies that can be brought offline with a bad push than can't.

Re:How to win the coding interview by ori_b on Tuesday May 31, 2016 @01:36PM (#11808294)
Or a load balancer push that ignores the 'yep, I'm alive and healthy' bit and sends traffic anyways.
Re:How to win the coding interview by EpicEng on Tuesday May 31, 2016 @04:10PM (#11809788)
Oh please. Even the best systems will have issues, and there will always be high pressure situations, regardless of the competency of management. It shouldn't be a way of life, but it's simply not practical to expect easy sailing at all times.