As a small startup, and a fully remote one to boot (thanks COVID), having only the “right” amount of meetings is crucial. Over-index on meetings and your team will get nothing done. Go too far the other way and your team won’t understand the vision, why you are doing what you are doing, and won’t be able to form the personal bonds that are required for a small team to succeed. We set aside 45 minutes every morning to discuss pretty much anything and everything.

Here at Sleuth, we live in Zoom, and have accumulated a list of tips to make video meetings better. I'm going to talk about three quick tips to go from a muddled dungeon dweller to a clear, engaging talking head, all without spending a dime. If you want even more, the above video shows you 9 more tips, including one advanced (but still completely free) tip to turn a video call into a real-time broadcast experience.

Developer teams shipping software frequently are in a constant state of change. Understanding the state of their code at a given point of time is sometimes clear as mud. The Sentry | Sleuth integration is focused on helping developers automate the annoyances of deploying software, tracking the health of a release, and providing clarity on how to resolve critical code issues.

Nowadays, software development teams utilize continuous delivery or some variation, to create better, faster, more accurate software releases. Continuous delivery is a DevOps practice that empowers software teams to continuously ship code directly to an environment once automated tests pass. Continuous delivery is facilitated through the deployment pipeline. You can read more about it in a previous post.

All deployments are not created equal, but you'd never know it from your Slack channel notifications. In reality, some deployments you really care about, as they contain things like API changes or database migrations, and you want that information to surface. We created tags in Sleuth for this very reason. Out of the box, Sleuth matches files in your deployment with known patterns, and if any are found, tags your deployments automatically.

Being in the DevOps space, we're often asked questions about software deployment like, "What's the difference between continuous deployment and continuous delivery?", "What is continuous deployment?", and "Are continuous deployment and continuous delivery the same thing?" So first, let's start by clearly defining these terms.

Being in the DevOps space, we're often asked questions about software deployment like, "What's the difference between continuous deployment and continuous delivery?", "What is continuous deployment?", and "Are continuous deployment and continuous delivery the same thing?" So first, let's start by clearly defining these terms.

Quick, do you know what code is currently deployed to production? How about staging? How far apart are these environments? Sleuth tracks your deployments, and today, Sleuth is launching first-class environments support. I'm going to show you how it works, steps to take to migrate your existing projects, and where we plan to take it in the future.

Quick, do you know what code is currently deployed to production? How about staging? How far apart are these environments? Sleuth tracks your deployments, and today, Sleuth is launching first-class environments support. I'm going to show you how it works, steps to take to migrate your existing projects, and where we plan to take it in the future.

In order to have the most successful deployment, there are a few best practices that software development teams should be mindful of. First, following a continuous delivery approach allows software development teams to release in shorter cycles, so that building, testing, and releasing can be done with greater speed and reduced error rates. As stated in an earlier post of ours, you’re doing continuous delivery when: Your software is deployable throughout its lifecycle.