Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Search posts
Search posts
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.
December 1, 2022
•
5 Min
reads
Railtown is happy to announce that root cause discovery is now available for teams that run on NodeJS.
September 6, 2022
•
3 Min
reads
.png)
While .NET is one of the most loved frameworks according to Stack Overflow Developer Survey for 2021, that popularity can bring issues for .NET error logging. There are “hundreds of thousands” of .NET packages available on NuGet, so developers can end up with an overwhelming tech stack to simply analyze .NET performance and monitor errors. How can you efficiently debug your code even as it scales up with all the third-party libraries you might use and their associated configurations? One simple but commonly overlooked answer: logging.
August 22, 2022
•
8 Min
reads
© Railtown AI Technologies Inc. 2021 All rights reserved. Website Design by Sixty Two.
