Operations | Monitoring | ITSM | DevOps | Cloud

Broadly speaking, the Linux community can be divided into two camps – those who upgrade their operating systems in-vivo, whenever there is an option to do so in their distro of choice, and those who install from scratch. As it happens, the former group also tends to rarely reinstall their system when problems occur, while the latter more gladly jump at the opportunity to wipe the slate clean and start fresh. So if asked, who should you listen to?

As we look to continue to provide value to our Remediate customers, we focused on how we create simple and effective workflows in the product. Our customers have told us there are some really important quality of life features that would go a long way in helping reduce the pain and frustration of remediating vulnerabilities and enable them to better communicate with their security partners.

SREs may have better long-term job prospects, but DevOps might be an easier career to pursue.

‍In Sleuth’s continuing efforts to help our customers to deliver faster and safer, we have always put security as a top-level business priority. Security and privacy of our customers’ data is always in the forefront of our design, development, and deployment concerns. We understand the level of trust our customers put in us when they connect key systems together with Sleuth.

Massive tomes have been written on engineering management, but I thought it might be helpful to take a brief minute to discuss setting up your Founding Engineers (FE) for success. For this post I define FEs as the first wave of engineers hired after the founding team. This round of hiring usually takes place after seed funding has been secured and some semblance of initial product/market fit has been achieved.