Simple code: 1. Passes all
its tests 2. Clearly expresses intent 3. Contains no duplication 4. Has no superfluous parts
Simple code: 1. Passes all
its tests 2. Clearly expresses intent 3. Contains no duplication 4. Has no superfluous parts
Simple code: 1. Passes all
its tests 2. Clearly expresses intent 3. Contains no duplication 4. Has no superfluous parts
Simple code: 1. Passes all
its tests 2. Clearly expresses intent 3. Contains no duplication 4. Has no superfluous parts
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
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