Thanks to advancements in JavaScript engines, the performance of websites has considerably improved in recent years. However, there are aspects of websites that are out of the control of engines and yet to be adequately optimized by browsers. One of these aspects is the number of HTTP requests that your webpage makes.
As you’re juggling deployments, writing code, and attending meetings there’s not a great deal of time left for staying up to date with the latest trends in tech. The culture around performance is getting stronger — performance is absolutely a feature, yet the pressure is on to deliver more without sacrificing quality. The good news is that there are companies who have achieved their performance goals — and more.
Every software professional in a leadership role is concerned about the caliber of software that gets into the hands of customers. Questions like, is the new app slow to load? Is it working as it should? Why has churn increased? Are natural consequences of building software, yet we don’t always get the answers we need.
Debugging. It’s one of the most time-consuming ways of finding a bug. As a senior .NET developer, I can tell you that it’s best to avoid the necessity for debugging altogether by writing clean code that’s covered by automated tests. If you’re a senior developer yourself, you probably already know this. And if you’re a junior developer, now you know it too! However, the world isn’t binary.
“It’s very much clear that .NET Core is the way going forward. Certainly new features and very much performance rated features seem to be only going in one direction. So, there’s this added incentive to move over.” - Matt Warren, performance expert at Raygun. Today, our host Andre talks to Matt Warren, .NET (C#) Developer at Raygun and Microsoft MVP.
This is a guest article by Dan Holloran from VictorOps – an on-call alerting and incident response tool recently acquired by Splunk. They are experts in incident management. In software development and IT operations, we tend to focus a lot of our time on the delivery and deployment pipeline. But, what happens after you deploy new services? How are you responding to incidents in production and identifying reliability concerns?
When you build and deploy an application, chances are that you need to store some form of secrets. These are typically things like credentials for 3rd party systems and database credentials. As an ASP.NET Core developer, Microsoft provides you with an easy way to store secrets like these in your development environment, namely the Secret Manager.
