DiscoverTalking Tech while Poking Smot🧐 Root Cause Analysis
🧐 Root Cause Analysis

🧐 Root Cause Analysis

Update: 2022-09-22
Share

Description

Why did I get absolutely blitzed last week? Find out now by using a tactic used by software engineers! We talk about Root Cause Analysis (RCA) and what that means to an incident. If only I could describe the abject terror one feels when receiving a PagerDuty notification. We go over that for quite some time before I finally move my ass on to half-answering a half-question from last week about software as a passion, a.k.a. (SaaP). Logistics brother. Figma is dead. Long live Figma. We then move onto a question about what to learn for being a front-end dev and cap it all off with a question about passion again wow, would you look at that. Two SaaP's in one episode. Perhaps I will elaborate on the things that absolutely KILL my passion next episode...



Happy Listening




Email me questions on software engineering:Β query@ttpspodcast.com


If you know your stuff and want to come on the show and chatΒ guest@ttpspodcast.com


If you want to collab or sponsor:Β business@ttpspodcast.com

CommentsΒ 
00:00
00:00
x

0.5x

0.8x

1.0x

1.25x

1.5x

2.0x

3.0x

Sleep Timer

Off

End of Episode

5 Minutes

10 Minutes

15 Minutes

30 Minutes

45 Minutes

60 Minutes

120 Minutes

🧐 Root Cause Analysis

🧐 Root Cause Analysis

Chad $yntax