Adastral Park code retreat introduction
•Als KEY, PDF herunterladen•
3 gefällt mir•17,475 views
Introductory slides for the Adastral Park code retreat on 28 October 2011
Empfohlen
Weitere ähnliche Inhalte
Mehr von Kerry Buckley
Mehr von Kerry Buckley (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Adastral Park code retreat introduction
- 4. Perfection
- 5. Pressure
- 8. Perfection Your normal level http://www.flickr.com/photos/anguskirk/2814337725
- 9. Perfection How much you suck Your normal level http://www.flickr.com/photos/anguskirk/2814337725
- 10. Perfection How much you suck Your normal level http://www.flickr.com/photos/anguskirk/2814337725
- 11. Simple code: 1. Passes all its tests 2. Clearly expresses intent 3. Contains no duplication 4. Has no superfluous parts
- 12. Simple code: 1. Passes all its tests 2. Clearly expresses intent 3. Contains no duplication 4. Has no superfluous parts
- 13. Simple code: 1. Passes all its tests 2. Clearly expresses intent 3. Contains no duplication 4. Has no superfluous parts
- 14. Simple code: 1. Passes all its tests 2. Clearly expresses intent 3. Contains no duplication 4. Has no superfluous parts
- 15. Simple code: 1. Passes all its tests 1. Fix bad expresses intent 2. Clearly names 2. Remove duplication 3. Contains no duplication 4. Has no superfluous parts
- 16. Format of the day 45 min coding 10 min retrospective 5 min break
- 17. Format of the day 45 min coding 10 min retrospective 5 min break
- 21. After each session… Delete your code!
- 22. Conway’s game of life
- 24. Cells are alive or dead
- 25. Each cell has eight neighbours 1 2 3 4 5 6 7 8
- 26. At each clock tick…
- 27. Cells with fewer than two neighbours die
- 28. Cells with fewer than two neighbours die
- 29. Cells with two or three neighbours live on
- 30. Cells with more than three neighbours die
- 31. Cells with more than three neighbours die
- 32. Dead cells with exactly three live neighbours come alive
- 33. Dead cells with exactly three live neighbours come alive
- 35. Languages
- 36. Ready?
Hinweis der Redaktion
- \n
- \n
- Created format as group practice exercise, concentrating on code quality and removing pressure to deliver working system.\n
- When did you last write perfect code? Never.\n
- Pressure to deliver (even self-imposed pressure, eg on hobby projects).\n
- Delivery pressure not a bad thing! No use writing perfect code that never does any useful work.\nBut, just for today, concentrate only on quality of code, not finishing the problem (it’s designed so you can’t finish it)\n
- Hopefully go back to work on Monday writing code that sucks a little bit less!\n
- Hopefully go back to work on Monday writing code that sucks a little bit less!\n
- Hopefully go back to work on Monday writing code that sucks a little bit less!\n
- Hopefully go back to work on Monday writing code that sucks a little bit less!\n
- Hopefully go back to work on Monday writing code that sucks a little bit less!\n
- Hopefully go back to work on Monday writing code that sucks a little bit less!\n
- Hopefully go back to work on Monday writing code that sucks a little bit less!\n
- Intent: each piece of the system should do one thing only, and make it clear what that is.\nDuplication: concepts as well as actual chunks of code.\nOrdered, highest priority first.\n
- Do these things and you’ll generally have good code.\nClean code is all about minimising the cost of change.\n
- Do these things and you’ll generally have good code.\nClean code is all about minimising the cost of change.\n
- Do these things and you’ll generally have good code.\nClean code is all about minimising the cost of change.\n
- First session get a feel for the problem, then start approaching from different directions, or with different constraints.\n
- First session get a feel for the problem, then start approaching from different directions, or with different constraints.\n
- First session get a feel for the problem, then start approaching from different directions, or with different constraints.\n
- First session get a feel for the problem, then start approaching from different directions, or with different constraints.\n
- First session get a feel for the problem, then start approaching from different directions, or with different constraints.\n
- First session get a feel for the problem, then start approaching from different directions, or with different constraints.\n
- First session get a feel for the problem, then start approaching from different directions, or with different constraints.\n
- First session get a feel for the problem, then start approaching from different directions, or with different constraints.\n
- Pair with someone different each session. Learn something from everyone, and also helps approaches to today’s problem spread.\nSwap driver and navigator frequently.\nTry a different language.\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n