155: Architectural Outages

Refactored #155: “Six Figure Flat Tires”

On this episode of Refactored…

• Hill Rejection Assist: Chris complains about Honda
• The guys decrypt the firewall to open a socket to the kernel.
• Comment Block
  • How do you not beat yourself up over causing an outage? Recently caused a SEV-1 outage that impacted a few hundred users. It was able to be corrected in a few hours but the app was not usable during the event. My manager was cool about it and is focused on the process; putting guardrails in place so that it doesn’t happen again. I find myself ruminating on it quite a bit and feeling embarassed about it, as over my 13 years as a dev this has only happened one other time. I am also somewhat newish to this company so I’m hoping this doesn’t ruin my reptuation.
  • Why do we even need architects? Question/observation: maybe it’s just me, but in my 19-year career as a software developer, I’ve worked on many different systems. In the projects where we had architects on the team the solutions have tended to be over-engineered with large complex tech stacks making them difficult maintain and challenging to find engineers familiar with the technologies. Over time I’ve started losing respect and appreciation for architects. Don’t get me wrong, I’ve also worked with some great architects, but most of them have been underwhelming. What has your experience been?
• … and much more!

Don’t be shy! Reach out at feedback@refactored.work.

Visit https://refactored.work/ for the full archive, show notes, and more. Hosted by Chris Tonkinson and Frank Koehl.

Direct link to RSS feed