The key principles of zero-downtime deployment applied to the main components of any web app: the backend, the frontend, and the database.
Many engineering teams use staging to test new features before pushing them to production. But is it really the best way to test?
An easy, low-cost way to start your monitoring routine that covers the most basic needs. For those who lost in application monitoring, infrastructure monitoring, uptime monitoring, etc.
In this episode, we'll cover the basic principles of zero-downtime database migrations and provide quick recipes for the most common scenarios.
As a developer, how do you start building a new feature? You may think, "It depends," and it certainly does. However, there could be frameworks that fit many situations, and I'd like to suggest one.
What does it mean to be a full-stack web developer today, and what are their pros and cons for team productivity?
How we communicate makes an enormous impact on our work. One of the best strategies for improving communication in a team is making it open.
Developers spend an enormous amount of time being stuck. I've been a developer and an engineering manager myself for many years, and I think being stuck is the default state. We, developers, spend most of our time being stuck, and just occasionally, we get unstuck and make progress.
In software engineering, communication around the manager organizes itself into two common modes – either a "router", or a "moderator".
If you've ever managed any software project, you've probably asked yourself: how could our teams move faster? How fast are we moving today? For these kinds of questions, it's tempting to turn to metrics.
Since we began developing software, we’ve looked for ways to reliably estimate our development time. Now, some 60+ years later, we've gotten no better at it.