DevCorp: Choose Your Own Adventure
summary
Interactive scenario shows concrete tradeoffs: pressing the team fixes the CI pipeline: 30 minutes, 90% failure so deployments become fast and reliable; building an internal reporting tool removes ad‑hoc requests; choosing pair programming mentorship teaches a junior to swap a pricey loyalty vendor and enables a quick replacement; allowing a developer to edit production once creates a precedent that later contributes to a user‑facing outage and a junior resignation. Outcome: throughput and cost efficiency increase, but one junior is lost and hiring policy shifts away from juniors.
AI-written summary · about
chapters (4)
- 0:00Start
- 12:11prioritize the pipeline
- 13:15prioritize the pipeline over your other tasks
- 17:44joined a refinement session
related talks
01h 03mBeyond the innovator’s dilemma
32mCode First, Ask Questions Later
29mDevOps Anecdotes
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal
59mThe Tech Lead Elevator: Real Stories and Hard Lessons
49mHard Choices, Tight Timelines: A Closer Look at Skip-level Tradeoff Decisions...
38mOur adventure in building an internal developer platform
05mAdventures In Enterprise: Lessons Learned Promoting DevOps In A Legacy Organization