The Diabolical Developer
summary
Argues that agile, best practices and tooling often add fluff not value and claims a better way: ditch CI, tests and source control, keep code on a USB, and merge everything into one giant PHP file (14,000 lines) with one giant function for procedural clarity; favors VI, shell scripts and ad hoc logging over frameworks, reports ~8–9% cloud adoption and commits roughly 200 times a day, and says reinventing small tools (logging, frameworks) takes weeks but keeps jobs.
AI-written summary · about
chapters (15)
- 0:00Start
- 7:19Modern Software Development
- 8:19Best Practices
- 9:47Scrum Certification
- 11:00Software Craftsmanship
- 11:49Practical Tips
- 12:27You Have To Be Passionate about Your Work
- 16:15Logging Frameworks
- 33:55The Single Responsibility Principle in Java
- 35:26Multiple Responsibility Principle
- 43:27Mongodb
- 46:31Get Rid of the Project Managers
- 48:08Continuous Integration
- 50:36Commit to Github
- 54:17Conclusion
related talks
52mThe Zen of Programming
31mThe Effective Developer - Work Smarter, Not Harder
52mThe Developer Rhapsody
50mThe Effective Developer - Work Smarter, Not Harder
43mGood or bad - a key skill for developers
33mThe Creative Developer
39mSoftware Craftsmanship
01h 03mThe Effective Developer - Work Smarter, Not Harder.