Adastral Park code retreat introduction
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Adastral Park code retreat introduction

  • 7,278 views
Uploaded on

Introductory slides for the Adastral Park code retreat on 28 October 2011

Introductory slides for the Adastral Park code retreat on 28 October 2011

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
7,278
On Slideshare
3,037
From Embeds
4,241
Number of Embeds
18

Actions

Shares
Downloads
21
Comments
0
Likes
2

Embeds 4,241

http://www.kerrybuckley.org 3,998
http://www.kerryb.org 200
http://abtasty.com 23
http://www.365dailyjournal.com 3
http://us-w1.rockmelt.com 2
http://webcache.googleusercontent.com 2
http://www.onlydoo.com 2
http://prlog.ru 1
http://www.200please.com 1
http://www.wonder-tonic.com 1
http://feedly.com 1
https://www.google.co.uk 1
http://flashattackcrew.blogspot.com 1
http://www.slideshare.net 1
http://comtel.in 1
http://prodtest.sophiaapp.com 1
http://kerryb.org 1
https://twitter.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • \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

Transcript

  • 1. ADASTRAL PARKCODERETREAT
  • 2. The boring stuff
  • 3. Perfection
  • 4. Pressure
  • 5. “Real artists ship.”
  • 6. Perfectionhttp://www.flickr.com/photos/anguskirk/2814337725
  • 7. Perfection Your normal levelhttp://www.flickr.com/photos/anguskirk/2814337725
  • 8. Perfection How much you suck Your normal levelhttp://www.flickr.com/photos/anguskirk/2814337725
  • 9. Perfection How much you suck Your normal levelhttp://www.flickr.com/photos/anguskirk/2814337725
  • 10. Simple code:1. Passes all its tests2. Clearly expresses intent3. Contains no duplication4. Has no superfluous parts
  • 11. Simple code:1. Passes all its tests2. Clearly expresses intent3. Contains no duplication4. Has no superfluous parts
  • 12. Simple code:1. Passes all its tests2. Clearly expresses intent3. Contains no duplication4. Has no superfluous parts
  • 13. Simple code:1. Passes all its tests2. Clearly expresses intent3. Contains no duplication4. Has no superfluous parts
  • 14. Simple code:1. Passes all its tests1. Fix bad expresses intent2. Clearly names2. Remove duplication3. Contains no duplication4. Has no superfluous parts
  • 15. Format of the day45 min coding 10 min retrospective 5 min break
  • 16. Format of the day45 min coding 10 min retrospective 5 min break
  • 17. After each session…
  • 18. After each session… Deleteyour code!
  • 19. Conway’s game of life
  • 20. Infinite 2-d grid
  • 21. Cells are alive or dead
  • 22. Each cell has eight neighbours 1 2 3 4 5 6 7 8
  • 23. At each clock tick…
  • 24. Cells with fewer than two neighbours die
  • 25. Cells with fewer than two neighbours die
  • 26. Cells with two or three neighbours live on
  • 27. Cells with more thanthree neighbours die
  • 28. Cells with more thanthree neighbours die
  • 29. Dead cells with exactly three live neighbours come alive
  • 30. Dead cells with exactly three live neighbours come alive
  • 31. http://www.youtube.com/watch?v=XcuBvj0pw-E
  • 32. Languages
  • 33. Ready?