Operations | Monitoring | ITSM | DevOps | Cloud

Recently in our Better Incidents Slack channel, there’s been some chatter around how people structure dedicated incident commanders at their company: distributed or centralized. The way I see it, there are two types of commanders: the temporary, distributed role — a hat that an on-call engineer or an engineering manager puts on during an incident. Then there’s the centralized, full-time role, where someone is the designated incident commander (or one of a few) for all incidents.

Docker: it’s one of those technologies that seems to be everywhere. Whether you’re a junior developer just starting out or a seasoned.NET developer, at some point in your career, you’ll most likely come across Docker for.NET. So, what is Docker?

Have you ever needed to provide proof that a critical business process actually took place? It’s a painful process involving all kinds of paperwork, but it’s the reality for many organizations working in highly regulated industries. For these companies, records need to be kept for actions like the provisioning of user accounts and access to sensitive records. It’s necessary, but it’s manual and time-consuming work.

If you’re a software developer in the public sector, you’re familiar with the unique challenges public sector professionals face. From grappling with tight deadlines and limited resources to working with complex legacy systems, the journey of a public sector software dev seems to be filled with obstacles at nearly every turn.