At times, directing projects in multiple locales from a desktop or laptop feels like conducting an orchestra in the dark. Coordinating with diverse, remote teams of developers producing software on an agile schedule of continual updates and releases can be especially nerve-wracking. At Sleuth, we’re crushing the remote-work challenge because, in 20 years of managing from afar, we’ve learned a thing or two — actually three — about how to do it right.
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.
