LeadDev Berlin 2019
2019-11-04
Berlin, Germany
[LeadDev Berlin 2019, LeadDev Berlin 2022, LeadDev Berlin 2023, LeadDev Berlin 2024]
who it's for
engineering managers, tech leads, engineering leaders, senior frontend engineers, platform engineers, site reliability engineers
topics
decision records and logs; post-incident review practices; React single-page app scaling; cross-team architecture governance; performance improvements via small fixes; feature flags and experimentation platforms; writing task-focused documentation; inclusive engineering and employee resource groups; salary and compensation strategy; leadership communication and decision models
| title | author | length |
|---|---|---|
| Levelling up as a Lead Developer | Patrick Kua | 27m |
Covers concrete leadership shifts: how to move from writing code to multiplying others rather than hoarding work, how the Mirror, Switch and Moan “monsters”… | ||
| Software engineering practices to improve management | Nicky Thompson | 09m |
Sees a concrete claim: managers account for ~70% of team performance (Gallup), so reusable practices matter. Recommends decision logs and simple templates to… | ||
| Lessons for frontend development at scale | Hannes Obweger | 25m |
Jira moves to a React-based SPA with over 1M+ lines of JavaScript and ~300 total contributors ~200 monthly, and lessons focus on concrete practices: treat UI… | ||
| Learning from incidents: how things went right | Nick Stenning | 29m |
Research shows focusing on human error hides design faults: hundreds of B-17 gear-collapse accidents trace to identical switches and stop after simple… | ||
| Scaling performance at Slack's scale | Aish Raj Dahal | 21m |
Slack scales performance by building a cross-team performance channel where engineers post mini digestible fixes, use tracing, flame graphs and metrics to find… | ||
| Becoming a team, one pixel at a time | Lena Reinhard | 31m |
Distributed engineering org of 65 people spends 95% of work time reduced to pixels and scales 50% year over year, so leaders build intentional structures: a… | ||
| Cultivating architecture | Birgitta Boeckeler | 29m |
Large orgs keep team autonomy but need concrete governance: use trade-off sliders to prioritise architectural requirements, run a lighthouse/boats workshop… | ||
| Strategies for making impossible decisions | Scott Triglia | 27m |
Argues that impossible technical or product choices become manageable by planning to be wrong and iterating with cheap experiments rather than perfect upfront… | ||
| Breaking the (developer) silos | Elin Nilsson, Raul Herbster | 11m |
Spotify replaces its old ABA feature-flagging system by building a new experimentation platform centered on remote configuration that exposes reusable… | ||
| Creating an inclusive engineering culture | Yenny Cheung | 28m |
Practical playbook: run an employee resource group (a Hamburg chapter grows to 13 members and runs an annual summit), run ally-skills workshops and dry‑runs to… | ||
| Writing effective documentation | Beth Aitman | 10m |
Documentation exists to help a reader complete a specific task, so focus on the actual job to be done and keep docs as small as you can sustainably maintain… | ||
| How does salary work? | Kevin Goldsmith | 33m |
Budget planning follows a waterfall budget locked in Q4 where midyear benchmarking (Radford-style) and finance forecasts dictate hiring cadence and quarterly… | ||
| Handling Security Issues | Markus Holtermann | 10m |
The talk explains a coordinated, cross‑functional process for handling software vulnerabilities, naming roles (developers, security, support, legal &… | ||
| How to affect change without losing your job | Duretti Hirpa | 24m |
Organizational change is operational work that requires credibility, clear communication and tactical follow-through: plan an offsite for back-end ICs to… | ||
| nothing matches | ||