Confronting Common Productivity Hurdles in Modern Software Development
summary
Claims that common defaults—GitHub pull requests, microservices by default, heavy Jira usage, and Kubernetes complexity—actually slow teams and lower satisfaction; Git works great for branching in low-trust open source but in high-trust teams avoid pull requests in high-trust teams and do daily collective commit reviews, pair programming, CI/CD and feature flags instead. Reuse a single repo for code that changes together, share types (generate TypeScript from Java/Kotlin), keep teams to ~2–6 (avoid >10), fix 30‑minute builds and flaky tests (one bank had to fix at midnight). keep things that change together in one repo
AI-written summary · about
chapters (10)
- 0:00Introduction to productivity hurdles
- 1:12Background and speaker introduction
- 9:01Pull requests as anti-pattern
- 24:05Code structure and monorepos
- 29:24Continuous deployment importance
- 37:13Microservices pitfalls
- 41:25Technical debt and refactoring
- 45:37Slow builds and team size
- 50:37Simplifying tech stack
- 51:19Conclusion and Q&A
related talks
28mPull Requests: Merging good practices into your project
47mDevelopment Best Practices: An Overview of Working in the Software World
45mAn Open Source Approach to Driving Developer Efficiency
21mGetting the Most Out of Git
15mStories from the Trenches
34mBuilding a Culture For Developer Productivity
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal
24mRemote development can improve your developers remote work experience