Developers kryptonite
summary
Claims that three concrete developer failure modes cause most pain: chasing shiny new frameworks without understanding internals, accumulating technological and conceptual inconsistencies in legacy code, and ritualizing Scrum into measurement-first bureaucracy. Recommends practical fixes: learn tool internals before adopting, record important choices in architectural decision records, keep a shared glossary, run blameless postmortems with action items, and prefer clear interfaces like ports and adapters rather than renaming patterns. Argues these reduce surprises and make legacy systems gracefully maintainable.
AI-written summary · about
chapters (5)
- 0:00Start
- 7:34Technology path on conferences
- 21:26Agile Manifesto
- 22:01Corpo-Scrum Manifesto
- 30:30More accurate Dunning-Kruger effect
related talks
56mKicking the Complexity Habit
08mLightning talks – 101 Things Software Never Learnt
52mThe Developer Rhapsody
44mCruft and Technical Debt: A Long View
56mThe Diabolical Developer
44mDependencies; Devil or Darling?
45mFallacies of Software Development
01h 01mGuide to Destroying Codebases the Demise of Clever Code
