Keep Software Weird
summary
Argues that measurable rituals and certifications often replace judgment and kill creativity, citing a waterfall-at-LexisNexis workflow, the agile Manifesto’s origin as a philosophy, and teams that end up doing waterfall with cards instead of real agility. Points to a 69% quip about made-up stats, a 1970s paper on LSD aiding system design, time spent on net and iOS work before finding Ruby at GitHub, and insists experiments that change how code is built and shared matter more than prescribed process.
AI-written summary · about
chapters (4)
related talks
27m'The Art of Software Development'
39mSoftware Craftsmanship
30mThe End of Fun
23mCode and Fear: Talent, Art, and Software Development
51mThe Art of Software Development
01h 00mThe Influential Software Engineer
48mThe Effective Software Architect - Work Smarter, not Harder
49mExtreme Professionalism - Software Craftsmanship.
