Topic:
Culture
Too many software development teams treat error logging as a burden rather than a chance to grow.That’s why Jeli’s “Howie: Post-Incident Guide” felt like a breath of fresh air. In the guide, Jeli’s team notes that negative treatment of bugs is everywhere, including the language we use to describe software development. Terms like “post-mortem” and “root-cause analysis” speak for themselves.We’d like to build on the suggestions put forward in Howie and share our perspective on error logging as well. So let’s take a look at how a small mindset shift around debugging could encourage more positive moments in your team.
Are you sick of switching between tools when trying to keep track of customer support tickets? With Railtown.ai, you can integrate your Azure DevOps records together with your customer support tickets.
Most of the articles discussing common causes of JavaScript errors online are surprisingly outdated. Why does this matter? Since 2011, JavaScript has changed a lot. Maintaining an accurate understanding of common issues with the language is important for developers of all skill levels. After all, JavaScript is notoriously prone to errors and looking through developer forums confirms that reputation as Stack Overflow returns 2,346 separate questions tagged as “JavaScript” and “Error-Handling”.
Railtown is happy to announce that root cause discovery is now available for teams that run on NodeJS.