Clean code
summary
Workshop shows that small, specific changes beat big rewrites: renaming proit to productId, data to attributes and B/I/U to bold italic underline turns unreadable code into intent within minutes; developers claim 30–50% typing but most projects spend ~10% actually writing code and far more time reading. A pragmatic boy scout rule and the “add refactor!!!” marker guide priorities. Encapsulate side effects (sessions, echo, exit), drop closing PHP tags, follow PSR2, and enable safe refactors with functional tests with PHPUnit + Mink + Sahi.
AI-written summary · about
chapters (15)
- 0:00Workshop introduction
- 1:29About the speaker
- 6:24Clean code Twitter discussion
- 13:29Why clean code matters
- 16:39Naming things properly
- 27:20Practice naming improvements
- 39:24Coding structure rules
- 57:45Handling side effects
- 1:03:31Practice side effect cleanup
- 1:12:58Error handling best practices
- 1:25:41Comments in code
- 1:32:32Coding style importance
- 1:39:50Clean code vs new trends
- 1:42:18Boy scout rule in teams
- 1:46:12Q&A and closing
related talks
45m'Writing code that lasts'...or writing code you won't hate tomorrow
43mClean Code: Be The Hero
40mMore Code More Problems
40mGood Code: What, Why, and How to Get There
44mNaming Things
53mIntentional Code - Minimalism in a World of Dogmatic Design
57mThe Art Of Clean Code
39mClean, Concise, Collaborative Code