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.
Logging is the practice of recording the alerts and messages that you get about the state of your code. As your application may run into inefficiencies, errors, or even crash, you can save the associated messages together with all the relevant context. In this guide, we will go through JavaScript error logging across the multiple categories.
Since .NET is so versatile, this suite of products can be used for both front-end and back-end software development. People who work on both sides are referred to as full stack developers since they work with the entire tech stack for their applications. Given that full stack development encompasses a large variety of tools and techniques, full stack developers are not usually specialists in one area or another.