Social Games and their Clean Code
•
0 gostou•694 visualizações
How Clean Code is used for social games in a big company.
Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Social Games and their Clean Code
Semelhante a Social Games and their Clean Code (20)
Último
Último (20)
Social Games and their Clean Code
- 1. Social Games and their Clean Code
- 3. 30.11 Mio. http://www.vgchartz.com/gamedb/?name=Call+of+Duty%3A+Modern+Warfare+3 || http://www.alextv.de/2011/11/10/call-of-duty-modern-warfare-3-review
- 4. Video Games = special interests
- 5. 159.79 Mio.
- 6. Social Games = Games for everybody
- 7. Berlin
- 8. 2009 — 20 employees
- 9. Today — 250 employees
- 10. 20 Game-Teams
- 13. Consistency
- 14. Way of working
- 15. No fixed roles
- 17. Configurability
- 18. Maintainability
- 19. Weekly releases
- 21. Agile way of working
- 22. Agility
- 24. Bubble Island
- 28. Refactoring!
- 29. 1 Consistency
- 30. Consistency
- 31. Consistency
- 32. Consistency
- 36. Naming •Speaking names •No Abbreviations •1 word per concept Consistency
- 37. Consistency
- 38. Consistency
- 39. Consistency
- 40. Consistency
- 41. Consistency
- 42. Consistency
- 43. Consistency
- 44. Consistency
- 49. Formatting •Indentation •Wrapping braces •Variables first •Public in front of non-public methods Consistency
- 50. Consistency
- 51. Consistency
- 53. Comments •Avoid them if possible Consistency
- 54. Comments •Avoid them if possible •Usage scenarios Consistency
- 55. Comments •Avoid them if possible •Usage scenarios ‣ Warnings Consistency
- 56. Comments •Avoid them if possible •Usage scenarios ‣ Warnings ‣ Simplified explanations Consistency
- 62. Maintainability
- 63. Maintainability
- 64. Maintainability
- 65. Maintainability
- 66. Maintainability
- 68. Methods •As small as possible Maintainability
- 69. Methods •As small as possible •1 level of abstraction Maintainability
- 70. Methods •As small as possible •1 level of abstraction •1 functionality Maintainability
- 71. Maintainability
- 72. Maintainability
- 73. Maintainability
- 74. Maintainability
- 76. Classes •1 reason to change (SRP) Maintainability
- 77. Classes •1 reason to change (SRP) •Only a few instance variables Maintainability
- 78. Classes •1 reason to change (SRP) •Only a few instance variables •High kohesion Maintainability
- 79. Maintainability
- 80. Maintainability
- 81. Maintainability
- 82. Maintainability
- 83. Maintainability
- 84. Maintainability
- 86. •Avoid train wrecks Data structures Maintainability
- 87. •Avoid train wrecks •Use data transfer objects Data structures Maintainability
- 88. •Avoid train wrecks •Use data transfer objects •Separate production and use of systems Data structures Maintainability
- 93. 3 Agility
- 96. •Avoid islands of knowledge Pair Programming Agility
- 97. •Avoid islands of knowledge •Integration of new team members Pair Programming Agility
- 98. •Avoid islands of knowledge •Integration of new team members •Collective responsibility Pair Programming Agility
- 99. Difficult to read & unstructured Agility
- 102. •Continuous improvements •The Boy Scout Rule (Robert C. Martin) Regular refactorings Agility
- 104. Unit tests Agility
- 106. •Safety net •Facilitated training Unit tests Agility
- 107. •Safety net •Facilitated training •Playground Unit tests Agility
- 110. •Early available software artifacts Continuous integration Agility
- 111. •Early available software artifacts •Verifiable expectations Continuous integration Agility
- 112. •Early available software artifacts •Verifiable expectations •Foreseeable problems Continuous integration Agility
- 113. Agility Agility
- 116. •Pair Programming •Regular refactorings •Unit tests Agility Agility
- 117. •Pair Programming •Regular refactorings •Unit tests •Continuous integration Agility Agility
- 118. 4 Tools
- 122. Tools CPD & PMD
- 123. Benefit for Wooga
- 125. High productivity over long period of time http://www.flickr.com/photos/stephenbegin
- 127. Clean Code as a common language
- 128. Less wtf/minute