LeadDev Austin 2019
2019-11-15
Austin, United States
who it's for
engineering managers, tech leads, engineering architects, people managers, senior engineers, product managers
topics
scaling engineering teams; architecture north star; architecture groups; splitting the monolith; hiring junior developers remotely; crafting effective 1:1s for distributed teams; observability that matters; inclusive project management; returning from parental leave; introduction to functional programming; delivering imperfect software; managing business risks together
| title | author | length |
|---|---|---|
| How to scale yourself as a first-time leader | Poornima Vijayashanker | 22m |
Claim: first-time leaders can stop being the bottleneck by teaching people to own work and decisions. Practical moves: build test infrastructure to enable a… | ||
| Bridging the gap between engineering and customer success | Annie Cook | 11m |
A lightweight, repeatable program called Bug Dives documents and walks through specific customer bugs with a document with links and a live context →… | ||
| Scaling engineering teams with an architecture North Star | Hanjie Ji | 23m |
Claims that an architecture North Star lets dozens of autonomous agile teams align without adding heavy coordination, based on a real WeWork scaling story… | ||
| On motherhood and leading engineering teams | Tara Feener | 21m |
An engineering lead manages an acquisition while nine months pregnant and has the acquisition finalized the day the baby is born so planning is urgent and… | ||
| Returning from long parental leave | Matt Newkirk | 10m |
Takes six months of parental leave, returns to a reorganized team where half the team is new and there are now two direct reports, and tests a personal… | ||
| Using architecture groups to scale people and technology | Iccha Sethi, Jony Jeyaratnam | 29m |
InVision grows from tens to hundreds of engineers and creates an architecture group of ~15 rotating reps to push standards, run weekly Kanban-tracked rituals… | ||
| Hiring junior developers remotely | Romina Suarez | 28m |
Argues that remote teams can hire juniors if they meet concrete conditions and then lists them: two senior mentors for 3–6 months, clear onboarding that gets a… | ||
| Crafting effective 1:1s for distributed teams | Spencer Norman | 11m |
Team size is 15 and meetings hit a 10 hour gap so one-on-ones run weekly and serve as the primary health check for people projects and teams. Concrete rules… | ||
| Splitting the monolith | Jimmy Bogard | 32m |
Case study of a 43-year-old mainframe migrating to microservices with a four-step approach: gain perspective (three months max of analysis), plan, pilot, and… | ||
| Solutions for managing an inclusive project | Yvette Pegues Ed.D.(c) | 26m |
Claims that strategic advocacy pivots the solution so architecture, tech and policy deliver inclusive access to systems, SLAs and SOPs with minimal disruption… | ||
| Managing business risks together | Jonathan Graham | 11m |
Five concrete moves: identify communicate prioritize mitigate roll up using the Cynefin frame to find obvious, complicated, complex and chaotic risks… | ||
| Lessons from flying for engineering leadership | Rebecca Murphey | 25m |
Sixty hours of training leads to one concrete claim: practicing rare failures makes decisions reliable under pressure — including repeated engine‑out drills… | ||
| Introduction to functional programming | Manju Vijayakumar | 11m |
Fast, concrete demo of replacing imperative loops with JavaScript higher‑order functions: live code shows a pantry→breakfast taco example refactored from… | ||
| Observability that matters | Tom Oketch | 13m |
Argues that observability pays only when tied to concrete goals: define SLIs/SLOs, use instrumentation to answer specific questions, and measure whether fixes… | ||
| The four components of high performing teams | Lisa van Gelder | 29m |
Names four concrete levers: mastery, autonomy, purpose and safety, and shows how measurement and process changes move delivery. Uses cycle time from tooling to… | ||
| Delivering imperfect software | Stevi Deter | 11m |
Claim: shipping good‑enough software is deliberate and measurable not sloppy. Example: a same‑day care platform at Providence St. Joseph Health trades an… | ||
| The race to Mach 2.0 at scale | Nickolas Means | 42m |
Anglo‑French Concorde reaches Mach 2 supercruise and crosses London–New York in about 3h15m by using slender delta vortex lift, a droop nose for landing… | ||
| nothing matches | ||