Jessica Deen, Cloud Developer Advocate at Microsoft, helps put to rest once and for all (in my mind, at least) the myths around what constitutes being a "real" developer and the perceptions that we often have of ourselves as "infrastructure type folks" in this regard.
Post-incident reviews, regardless of the term you use for them, traditionally offer an opportunity to "learn from failure". John Allspaw posits that it's quite difficult to avoid this, but there are better, more specific questions to ask about what exactly we are learning. We can all get better at post-incident assessment and analysis, and this post digs into areas that we need to make some mental shifts.
"Our portable computers are thousands of times more powerful than the ones that brought a man to the moon. Yet every other webpage struggles to maintain a smooth 60fps scroll on the latest top-of-the-line MacBook Pro."
We are living in an amazing age of computing, but the craftsmanship of software creation leaves much to be desired. Nikita Prokopov digs into software bloat, code rot, and various other annoyances and irritations with modern software.
CloudBees sponsored this podcast. Dr. Nicole Forsgren is the CEO and Chief Scientist of DevOps Research and Assessment (DORA), and the principal author of the annual State of DevOps Report.
I'm a big believer in the concept of "if it makes you money, build it. If it doesn't, buy it" (note - "buy it" doesn't mean forking over cash; it can be free/open source software).
Sabice Arkenvirr talks about the pitfalls of "not invented here" (NIH) syndrome, as well as some tips for when you do actually need to roll your own solutions, and how to do that better.