tl;dr:"More than 100 people would need to be hired across engineering, product and design, to staff these teams. The new teams were stack ranked by importance e.g. teams responsible for growing the supply of drivers were ranked much higher than those generating rider demand." Gergely discusses Uber's biggest engineering organizational change: creating cross-functional program teams and introducing platform teams.
tl;dr:"This article collects some openly available RFC templates and examples, and a list of companies that use such a process. I’d encourage to use these examples for inspiration. Take parts that resonate with you, experiment with them and modify them to your needs."
tl;dr:"In this issue we cover: (1) The extremes of shipping to production. (2) Typical processes at different types of companies. (3) Principles and tools for shipping to production responsibly. (4) Additional verification layers and advanced tools. (5) Taking pragmatic risks to move faster. (6) Deciding which approach to take. (7) Other things to incorporate into the deployment process.
tl;dr:Gergely covers a timeline of events, cause of the outage, what customers are saying, the impact of the outage on Atlassian’s business, learnings from this outage, and more.
tl;dr:"I am covering details from the vantage point of software engineers and engineering managers." Gergely covers how Fast able to hire engineers competing with the big tech companies, warning signs within the company as seen from an engineering perspective, the current situation within the company, and more.
tl;dr:"If you do some groundwork before starting the migration, you’ll reduce risk, gain confidence and understand the scope of the migration better." Gergely breaks the migration process into the following steps: (1) Preparation for migrations. (2) Pre-migration steps, such as monitoring and validation. (3) The migration itself, covering downtime, strategies & toolset. (4) After the migration. (5) The migration long-tail.
tl;dr:"A deep dive with five Technical Program Managers (TPM) on what the role is, how it evolved, and how engineers and managers can benefit from working with TPMs." Gergely concludes that senior engineer already do lots of the things that TPMs do full-time. (2) Fast-growing tech companies rely heavily on TPMs to scale engineering efficiency. (3) The TPM role is spreading steadily across the industry.
tl;dr:This post covers: (1) The importance of writing for software engineers, engineering managers, and executives. (2) The process of writing well. Editing approaches to make your writing crisper and getting feedback on your writing. (3) Improving how you write. Observing and copying great writing. Habits to build your writing muscle. Continuous learning: courses, books, and tools to boost your writing.
tl;dr:95 recommendations divided by genres such as engineering management, engineering leadership & org design, software engineering careers, leadership and business, and others.
tl;dr:"Stories from 6 engineering leaders who succeeded in building and growing diverse teams," with the following key takeaways: (1) Underrepresented leaders make a difference. (2) There are tactical wins you can start now e.g. bias training, partnering with organizations. (3) Use structure to drive diversity outcomes & create processes around those outcomes. (4) Tactics need a defined strategy and goals.