LeadDev New York 2022
2022-04-05..2022-04-07
New York, NY, United States
[LeadDev New York 2022, LeadDev New York 2024, LeadDev New York 2025]
who it's for
engineering managers, tech leads, platform engineers, site reliability engineers, people managers, senior engineers
topics
technical debt prioritization framework; blameless postmortem process; on-call rotation and ownership; strangler fig legacy migration; migration maps and Backstage; observability in microservices; interview rubrics and scoring; improving code review practices; psychological safety practices; developer onboarding and training; software estimation techniques
| title | author | length |
|---|---|---|
| Refactoring: Managing technical debt before it blows up in your face | Amanda Sopkin | 11m |
Provides a concrete prioritization framework: score technical debt by developer and customer impact, how fast it’s spreading and surface area plus confidence… | ||
| Technologists: how to make decisions for your organization and our society | Nimisha Asthagiri | 32m |
Sees concrete claims, tools, numbers and outcomes: a plug-in framework is built to extend a monolith (it prolongs the monolith instead of moving to… | ||
| Fostering psychological safety in distributed teams | Taylor Poindexter | 27m |
Claims that psychological safety cuts process inefficiency and raises engagement and innovation, backed by concrete practices: recurring one on ones and asking… | ||
| What Capuchin monkeys know that engineering leaders don't | Jared Silver | 12m |
Claim: perceived fairness drives contribution and retention, illustrated by Brosnan and de Waal’s capuchin experiment where the cucumber recipient refuses… | ||
| Corpse party bugs | Danielle Leong | 08m |
Forensic entomology estimates postmortem interval by identifying species and life stages, counting instars and pupae, and using body farms to calibrate growth… | ||
| Simplify your postmortems and focus on scaling | Ricardo Aravena | 10m |
Advocates a concrete process: templatize and bookmark the page so every postmortem uses the same sections, schedule within three to five days after incidents… | ||
| Don't squander your inheritance: Expert advice for taking over existing teams | Camille Acey, Stacy Justino | 34m |
Three concrete moves decide whether taking over a team works: assess aim achieve as a 30‑60‑90 roadmap, shadowing team members to map real processes, and… | ||
| Sunsetting legacy systems: a story by Netflix | Marek Kiszkis | 29m |
Netflix narrates a two-year deprecation of a legacy system for signup and account management and gives concrete outcomes: the team builds a new service behind… | ||
| Calling out a terrible on call system | Molly Struve | 29m |
A company with ~15 developers and an SRE team of three breaks a single giant rotation into three rotations, assigns ownership of workers, alerts and monolith… | ||
| Blame, shame and panic - how not to respond when things go wrong | Jemma Bolland | 22m |
A concrete claim: build blameless teams by pairing technical safeguards (access controls used at an AWS consultancy) with specific behavioral tools — take a… | ||
| Why most technology migrations fail (and what we've learned along the way) | Jai Chakrabarti | 30m |
Argues migrations scale with accumulated tech debt and gives concrete fixes: inventory and quality standards for 600 engineering teams, a single-source… | ||
| Paying down management debt without burning out | Frankie Nicoletti | 10m |
A concrete playbook: a million dollar deal forces a language switch from Clojure to Python, the team adopts stand-up meetings to surface real‑time work, a… | ||
| Equipping your team to support junior developers | Aisha Blake | 30m |
Clear, practical checklist of what to build and what actually changes: write onboarding and friction logs, create a documented career ladder anchored to senior… | ||
| Navigating engineering leadership through the pandemic and beyond | Vaidehi Joshi, Denise Yu, Nimisha Asthagiri, David Yee | 38m |
Argues that Jane Jacobs' urban rules map directly onto codebases: shorter “blocks” (more touchpoints) increase collaboration, mixed-use surroundings… | ||
| Effective observability in microservice architectures | Lesley Cordero | 33m |
Describes building a standardized observability platform that actually enforces standard communication protocol (HTTP headers for trace context, concrete data… | ||
| The Map Book: Visual Storytelling With Roadmaps | Tadeh Hakopian | 11m |
Shows a concrete recipe: start with mission, vision and OKRs, then map a year of work as a gantt chart that anyone across LA, Switzerland and remote offices… | ||
| Harassers are nice to me | Sarah Milstein | 10m |
Claim: senior leaders usually don't see harassment because bad actors target people with less power and cultivate friendly cover relationships. Concrete… | ||
| My Monolith is Melting: Lessons from Legacy | Meri Williams | 28m |
Claim: moved an SAP-led monolith from three releases a year that forced manufacturing stops to fortnightly releases with no downtime, cutting major/critical… | ||
| Software estimation – embracing nuance and controlled chaos | Karl Sanford | 29m |
Estimation starts from the admission that everyone is bad at predicting the future and improves by naming uncertainty: use cone of uncertainty ranges not… | ||
| Bottom up org change and evolution | Sebastian Duque | 24m |
Engineers form representative working groups, run a six-week trial, and ship a focused tool: Stack Overflow for Teams, integrated with Slack and seeded with… | ||
| Rubrics cubed: Attempting to quantify the qualitative in the interview process | Shawna Martell, Dan Fike | 09m |
Claims a structured rubric system replaces a useless five‑point yes/no scale with a zero-to-four scale tied to concrete attributes, breaks interviews into… | ||
| Level up your code reviews | Denise Yu | 10m |
Four concrete lenses guide code review: readability lens (look for intention-revealing names, PR descriptions, tests-as-docs), perf/scale lens (ask about… | ||
| The clean code protocol | Usha Kuchibhotla | 10m |
A concrete protocol that runs a continuous learning cycle with four parts: take small steps, document them, enforce them, and rotate a champion; start by… | ||
| Building Culture through Communication | Neha Batra | 28m |
Shows actual practices: drafting with an imaginary panel of four reader types (new joiner designer PM leadership blunt-questioner), using emoji cues… | ||
| Instilling the built-in quality mindset into a dev team | Larissa Rosochansky, Rafael Navarro Cintra | 28m |
Content lays out five concrete dimensions—flow, code, release, system and architecture quality—and names specific practices to make them real: test pyramid… | ||
| nothing matches | ||