What if Clean Code is a scam?

Here you can find all links from this presentation: https://gist.github.com/mehowte/b28b04f187fe35638769

WHAT IF CLEAN CODE IS A SCAM? It seems that we are keen to follow charismatic leaders who tell us how to do stuff. There are already a lot of rules and principles that we take for granted instead of asking questions: Will this really improve my code? Will it help me deliver faster/more reliably in the long run? It seems that sometimes we fail to challenge their ideas. Maybe you can have too many classes? What if your methods don't need to fit in a tweet? Maybe Object Oriented design as a whole is a case of premature optimisation? What if we just waste time writing tests for everything? Maybe cucumber is a massive overkill? What if... DHH was right? Then again, he is also a charismatic leader...

Transcript

1. What if… ?
2. What if…? WHAT IF CLEAN CODE IS A SCAM? It seems that we are keen to follow charismatic leaders who tell us how to do stuff. There are already a lot of rules and principles that we take for granted instead of asking questions: Will this really improve my code? Will it help me deliver faster/more reliably in the long run? It seems that sometimes we fail to challenge their ideas. Maybe you can have too many classes? What if your methods don't need to fit in a tweet? Maybe Object Oriented design as a whole is a case of premature optimisation? What if we just waste time writing tests for everything? Maybe cucumber is a massive overkill? What if... DHH was right? Then again, he is also a charismatic leader...
3. What if…? WHAT IF CLEAN CODE IS A SCAM? It seems that we are keen to follow charismatic leaders who tell us how to do stuff. There are already a lot of rules and principles that we take for granted instead of asking questions: Will this really improve my code? Will it help me deliver faster/more reliably in the long run? It seems that sometimes we fail to challenge their ideas. Maybe you can have too many classes? What if your methods don't need to fit in a tweet? Maybe Object Oriented design as a whole is a case of premature optimisation? What if we just waste time writing tests for everything? Maybe cucumber is a massive overkill? What if... DHH was right? Then again, he is also a charismatic leader...
4. What if…?
5. What if…?
6. What if…?
7. What if…?
8. What if…?
9. What if…?
10. Opinionated
11. Opinionated
12. Opinionated
13. Opinionated
14. Doubtful
15. Doubtful • Michał Taszycki - @mehowte • Neutral - Good / Chaotic - Good • former AAA Game Developer • Develops Clean Code Remotely at GunpowderLabs • Launches Commodore 64 Screencasts soon.
16. Doubtful
17. Doubtful
18. Wise
19. Wise
20. Coding Style
21. Coding Style
22. Coding Style
23. Coding Style
24. Coding Style
25. Coding Style
26. Coding Style
27. Coding Style
28. Coding Style
29. Coding Style • John Carmack on Inlined Code • Jonathan Blow on Coding Style in Braid • John Carmack on Functional Programming • Handmade Hero by Casey Muratori • Casey Muratori on API Design
30. Refactoring
31. Refactoring
32. Refactoring
33. Refactoring
34. Refactoring
35. Refactoring
36. Refactoring
37. Refactoring I also must confess to a strong bias against the fashion for reusable code. To me, "re-editable code" is much, much better than an untouchable black box or toolkit. I could go on and on about this. If you’re totally convinced that reusable code is wonderful, I probably won’t be able to sway you anyway, but you’ll never convince me that reusable code isn’t mostly a menace. — Donald Knuth
38. Refactoring I also must confess to a strong bias against the fashion for reusable code. To me, "re-editable code" is much, much better than an untouchable black box or toolkit. I could go on and on about this. If you’re totally convinced that reusable code is wonderful, I probably won’t be able to sway you anyway, but you’ll never convince me that reusable code isn’t mostly a menace. — Donald Knuth
39. Refactoring • Things You Should Never Do by Joel Spolsky • The Big Rewrite, Revisited by DHH • Jonathan Blow - designing new Programming Language For games part 2 • Literate Programming by Donald Knuth
40. OOP
41. OOP
42. OOP
43. OOP
44. OOP
45. OOP
46. OOP
47. OOP
48. OOP • Search “garybernhardt oop” on twitter • OOP is an expensive disaster which must end • Compression Oriented Programming by C. Muratori • Data Oriented Design by Noel Loppis • Mike Acton on Data Oriented Design • Immediate Mode GUI by Casey Muratori
49. TDD
50. TDD
51. TDD
52. TDD
53. TDD
54. TDD • TDD is dead. Long live testing. by DHH • TDD, Straw Men, and Rhetoric by Gary Bernhardt • Monogamous TDD by Robert Martin • Search for “@dhh tdd is dead” on twitter • http://martinfowler.com/articles/is-tdd-dead/
55. Version Control
56. Version Control
57. Version Control
58. Git
59. Git
60. Git
61. Git
62. Git
63. Git
64. Git
65. Git • Search twitter for “Jonathan Blow git” • Jonathan Blow on using SVN in Witness • Unorthodocs: Abandon your DVCS and Return to Sanity
66. Diversity
67. Diversity WARNING! SIMPLIFICATION AHEAD
68. Diversity 1. accessibility, regardless of culture, gender, skin colour 2. freedom to express extreme/contrarian ideas Different Focus
69. Diversity 1. Some believe those aspects are opposite 2. Some believe one cannot be achieved without other 3. Some believe they can coexist 4. Some focus on one and neglect the other 5. Some focus on one and fight the other Different World-views
70. Diversity • Feminism 101 on Geek Feminism Wiki • Code of Conduct 101 by Ashe Dryden • Talk with Wroc_love.rb organizers • Talk with those who oppose Wroc_love.rb • Don’t be afraid to state your opinion • Don’t be afraid to change your opinion
71. One more thing
72. Listen to this Łona & Webber - Have a doubt (polish hip-hop song with english subtitles).
73. Have a doubt!