LeadDev Berlin 2022
2022-11-02..2022-11-04
Berlin, Germany
[LeadDev Berlin 2019, LeadDev Berlin 2022, LeadDev Berlin 2023, LeadDev Berlin 2024]
who it's for
engineering managers, tech leads, senior individual contributors, director-level engineering leaders, platform engineers, site reliability engineers
topics
asynchronous collaboration practices; engineering organisation scaling strategies; developer productivity metrics and tooling; platform team evaluation and design; feature flagging for safe rollouts; refactor and rearchitecture patterns; remote onboarding and documentation sprints; lean learning and development backlogs; debugging practices and on-call workflows; large-file ingestion and decoupled pipelines; diversity and inclusive hiring practices; data-informed green software engineering
| title | author | length |
|---|---|---|
| Stop! Strategy time! | Lena Reinhard | 30m |
Claims a concrete habit: build a five‑part STAND routine (space, think, act, no, draw—broadcast) and schedule a 15‑minute daily block, a 30‑minute weekly… | ||
| Transitioning from synchronous to asynchronous (and somewhere between) | Michael Tempest | 11m |
A concrete case: a new remote team builds its backlog using a shared Meo board with instructions and a how-to video, collects input asynchronously, then meets… | ||
| Tips for part-time project managers | John Ong | 08m |
Practical rules and tools: choose a unit and translate for estimates (clarify whether estimate means cost time or commitment), force an early decision between… | ||
| Lessons learned from refactors and rearchitectures | Josh Goldberg | 31m |
A major refactor rolls back after a disastrously buggy release because unit and end-to-end tests got punted, proving manual verification fails; one module… | ||
| Explaining distributed systems like I'm five | Michele Riva | 11m |
Starts from a concrete interview problem: uploading a 10 gigabytes CSV and normalizing it, then shows a working pattern—write to S3 / Google Cloud Storage /… | ||
| Scaling engineering organizations | Sangeeta Handa | 26m |
Claims concrete: engineering and org scale together to drive growth, with teams that grew 2x–3x by focusing on four dimensions: humans, data, systems… | ||
| The making of a manager's manager | Anita Singh | 25m |
Clear, actionable advice: three tactics—fill in gaps by fixing processes, volunteer to take your manager’s work, and mentor new EMs—plus concrete rituals to… | ||
| Developer productivity 2.0 | Gergely Orosz | 32m |
A survey of engineering teams (75 detailed responses, ~100 pages of notes) finds concrete patterns not slogans: small teams with clear goals outperform… | ||
| Setting goals as a senior individual contributor | Sabrina Leandro | 26m |
Creates a personal backlog of vetted initiatives, prioritizes by company needs and risk, and matches items to explicit growth areas. Uses a spreadsheet with… | ||
| Feature flag use cases you haven't heard about yet | Joy Ebertz | 11m |
Feature flags get used here to do real work: wrap logging with a toggle and enable it briefly for a small cohort to find and safely delete dead code, mirror… | ||
| Shopify's remote working toolbox | James Stanier | 27m |
Shopify goes fully remote one month after the pandemic and claims specific, repeatable practices: organize teams so members have one to two hour time-zone… | ||
| A lean DevOps approach to learning & development | Sorrel Harriet | 30m |
Argues that applying lean and DevOps to L&D produces concrete practices rather than platitudes: a learning backlog (kanban) for small-value work-aligned… | ||
| Tackling the toppling tech talent pyramid: a radical challenge to building diverse teams | Richard Ng | 30m |
Claims that Tech's problem is a pyramid not a pipeline get backed by numbers and experiments: only 4 in 100 entry-level roles in some samples, and a program… | ||
| The database trends that are transforming your database infrastructure forever | Peter Zaitsev | 30m |
Argues open source databases move from single-node to distributed architectures and separate storage from compute so serverless querying is feasible; cites… | ||
| Technical documentation – how can I write them better and why should I care? | Hila Fish | 13m |
Claims a practical, repeatable method: anyone can write useful tech docs and doing so cuts interruptions — one example drops ~7–8 daily questions to 1–2… | ||
| Silly baboons, stubborn elephants: navigating culture differences across R&D groups | Rina Artstain | 11m |
Claim: cross‑functional conflict usually hides stable cultural gaps — speed, tech debt, security, ambiguity and customer focus — not personality. The method… | ||
| Leading software teams with systems thinking | Francisco Trindade | 11m |
Argues that systems thinking turns vague priorities into concrete actions by following a three-step routine: understand goals, inspect work as processes, then… | ||
| The role of data in green software engineering | Simon Müller | 30m |
Data already consumes about 200 terawatt hours a year — more CO2 than the entire airline industry — so the talk gives actionable rules: eliminate utilize… | ||
| Fight back against imposter syndrome | Garance Vallet | 10m |
Names imposter phenomenon as a normal, decades‑old phenomenon (not a disease), gives three diagnostic signs, and offers three concrete tactics: list past… | ||
| On call does not have to suck | Charity Majors | 30m |
Argues that owning code and redesigning alerts makes on‑call sustainable: adopt event‑level observability, feature flags and auto‑deploy to a small percentage… | ||
| Do you really need a platform team? | George Peter Hantzaras | 11m |
Argues platform engineering is one scalable path to DevOps outcomes not a replacement for DevOps or SRE, and that an internal developer platform (think managed… | ||
| Debugging debugging; why we must approach debugging differently | Elinor Swery | 13m |
Seventy five percent of developer time goes to bugs so the claim is if debugging improves feature output rises. Concrete fixes include 75% of developer time, a… | ||
| Leading as an introvert | Nelida Velazquez | 24m |
Asserts that introverts lead well by leaning into listening and observing rather than mimicking extrovert swagger, cites books like Quiet and The Confidence… | ||
| Decision making in black box scenarios | Boyan Angelov | 10m |
A bought legacy system turns into a critical black box: weird language, no external support, no backups, and a complete work stoppage with direct financial… | ||
| Leading through turbulence | Ritesh Manchanda | 11m |
Describes specific incidents and concrete tactics: lost temper and cost months of trust when unprepared, listening to a team worried about layoffs and offering… | ||
| Integrating an expert solo developer into a development team | Theresa Robinson | 31m |
An internal product called engineNetwork internal product already predicts engine health and ships analytics; integrating solo experts succeeds when specific… | ||
| Leading software teams with context (visibility) | James Samuel | 22m |
Claims four measurable pillars—process, operation, people, product—and shows how to instrument each with concrete signals: run DORA metrics and watch… | ||
| Bridging the Dev-Sec divide: Three tips for agile developers | Lusia Emme | 27m |
Three concrete steps: run threat modeling sessions to map auth flows and surface real vulnerabilities, instrument a login router logs pipeline to get baseline… | ||
| nothing matches | ||