🧐 Root Cause Analysis
カートのアイテムが多すぎます
カートに追加できませんでした。
ウィッシュリストに追加できませんでした。
ほしい物リストの削除に失敗しました。
ポッドキャストのフォローに失敗しました
ポッドキャストのフォロー解除に失敗しました
🧐 Root Cause Analysis
-
ナレーター：
-
著者：
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