How To Do Kick-Ass Software Development
summary
Practical tips and outcomes: use cheap paper prototypes and “fake it till you make it” experiments; putting an in‑app feedback button yields 4x more feedback; require every developer to spend a week on first‑level support and run a developer‑on‑test program that drops bug incidence from 36%→9%. Use git with branch‑per‑task, ~2‑day life and pull requests needing two approvals. Tame slow CI by artifact caching, parallel tests and layered pipelines; add flaky‑test detectors, a static analysis “fraudbot” and even a Raspberry Pi release button.
AI-written summary · about
related talks
31mThe Effective Developer - Work Smarter, Not Harder
50mThe Effective Developer - Work Smarter, Not Harder
31mThings I Wish I Knew When I Started Playing 'Developer'
48mThe Effective Software Architect - Work Smarter, not Harder
48mEnding Keynote: 7 Principles of Productive Software Developers
45mHelping Developers to Help Each Other
26mUpdate your team to be more extreme
30mReal-Life Tips on How to Boost Your Development Team's Productivity from Within