LeadDev Live Summer 2020
who it's for
engineering managers, tech leads, engineering directors, senior engineers, people managers, people operations professionals, team leads
topics
attitudes toward legacy code; engineering one-on-one cadence; preparing teams for financial uncertainty; professional networking for influence; software estimation techniques; eliminating hero culture; remote inclusion practices; working without pre-production environments; simplifying codebases to save time; supporting employees through redundancies; building belonging in engineering teams
| title | author | length |
|---|---|---|
| Changing attitudes toward legacy code | Patrick Kua, Nelida Velazquez, Jack Franklin, Suman Roy | 45m |
Panelists report concrete playbooks: prioritize add tests first and map interdependencies before any rewrite, keep Objective‑C/Swift interop or Chrome DevTools… | ||
| Cracking the cadence of your software engineering 1:1s | Adrienne Lowe, Alexandra Sobhani, Kwasi Ohene-Adu, Spencer Norman | 46m |
Claims concrete practices: run weekly 45-minute personal time per direct, keep a shared one-on-one doc with agenda and a follow-ups section, and use… | ||
| Preparing your software engineering teams for times of financial uncertainty | Kevin Stewart, Michelle grover, Jossie Haines, Yvette Pasqua | 43m |
Panelists recommend small Q&As of 8–10 people, two‑way honesty, and regular all‑hands where the CFO showed charts of revenue so teams see real trajectory… | ||
| Increasing your influence through building a professional network | Alia Shafir | 20m |
Claim: influence is a learnable formula — do you know who I am, do I know what you need, what value do I offer — not charisma. Tools and tactics: five-minute… | ||
| Creating efficient, accurate, software estimations | Yenny Cheung, Daiany Palacios, Dominika Rogala, Amir Safavi | 47m |
Panel argues that reliable estimates come from specifics not slogans: teams use Monte Carlo simulation and historical throughput to give probabilistic… | ||
| Eliminating hero culture in software engineering teams | Brianna McCollough | 17m |
Claims that hero culture produces extreme technical debt, slowed promotions, lost PTO and burnout, and that replacing it requires concrete changes: enforce… | ||
| Remote inclusion in distributed engineering teams | John Fletcher | 14m |
Claim: deliberate meeting rules and cheap tech fix turn a mixed on‑site/offshore group into a single-class, high‑retention team. Concrete actions: 30-second… | ||
| Living without pre-production environments | Nicky Wrightson | 16m |
Claims production is the only environment needed and backs it with concrete tooling and lessons: uses slingshot for metric-driven CD, testcontainers to run… | ||
| How simplifying software can save your engineering teams' time | Waheed El Miladi | 13m |
A messy ETL and fleet of redshift clusters gets replaced by an event-based pipeline that writes into elasticsearch, trading custom aggregation-heavy queries… | ||
| Supporting employees through redundancies and business closures | Nebojša Miletić | 18m |
Describes firsthand outcomes: survives a company insolvency, builds a team to 40-plus people then reorganizes with careful reassignments, achieves zero… | ||
| Why we must strive for belonging in our engineering orgs | Raul Herbster, Richard Oppong | 14m |
Argues that diversity alone is insufficient and gives concrete practices that teams use: a lifeline activity to surface identities, an onboarding buddy plus… | ||
| nothing matches | ||