Engineering delivery

In this article, we introduce a framework for balancing engineering investments across four categories and explain how to get started.

In this article, we introduce a framework for balancing engineering investments across four categories and explain how to get started.

null

How the top 10% of engineering teams think about metrics.

null

[RFC Template] Title Authors: @nickname @nickname 1 Executive Summary A short paragraph or bullet list that quickly explains what you're trying to do. 2 Motivation What motivates this proposal and why is it important? Here we aim to get comfortable articulating the value of our actions. 3 Prop...

A reference guide to implement RFCs as a technical decision framework for engineering teams.

Monitoring systems to inform business decisions Improve monitoring across infrastructure platforms, ...

At the Agile Eastern Europe 2015 conference Claudio Perrone gave a keynote titled "Evolve and Disrup...

Introduction & Summary Most change efforts fail, even when experienced people are involved, and even...

If you are looking for a tool to start managing technical debt this article will help you make the r...

The negative impact of technical debt on businesses is massive. Here are the best ways to prevent an...

Tech debt is a metaphor, but it costs you real money. In this post, learn how to reduce technical de...

Here are some questions you might find useful when running a self-assessment with your team against ...

How an enduring framework for knowledge-sharing and decision-making helped one team make more informed, egalitarian decisions—and how you can too.

RFCs for changes to Rust. Contribute to rust-lang/rfcs development by creating an account on GitHub.

by Angela Zhang How to write a good software design doc Photo by Estée Janssens [https://unsplash.com/photos/A65Gqv38pYo?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText] on Unsplash [https://unsplash.com/search/photos/planning?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText] As a software engineer, I spend a lot of time reading and writing design documents. After having gone through hundreds of these docs, I’ve seen first hand a strong correlation

I have recently been talking at small and mid-size companies, sharing engineering best practices I see us use at Uber, which I would recommend any tech company adopt as they are growing. The one topic that gets both the most raised eyebrows, as well the most "aha!" moments is the

RFC: A Structured RFC Process Authors: Phil Calçado To be reviewed by: 10/5/2018 Revisit Date: 04/17/2019 State: Feedback Requested Need A healthy engineering organization demands a culture of asking for and welcoming feedback on our work. In smaller organizations, sharing plans,...

As an engineering leader, I value trust and believe that individual contributors should be involved in architectural and high level…

Usually we know RFCs from IETF. It’s that document that for example starts to present the HTML spec. But on this article I’m talking about RFCs (request for comments) in a broader sense. Like a tool that can be used by product/engineering teams to better plan and be productive.

What Engineers Think about Technical Debt and Its Impact on Team Morale, Velocity, and Customer Expe...

In this article, three experts discuss some of the key findings of the “State of Technical Debt 2021...

A couple of people have asked me to share how I structure my OOPS write-ups. Here’s what they look l...

DORA’s 2021 Accelerate State of DevOps report measures software delivery and operational performance...

Some time ago we announced that Allegro passes Core Web Vitals assessment and thanks to that we were...