At my current place of employment, we had someone come in to talk about some Agile development processes.\u00a0 One of them was Test Driven Development.\u00a0 As an example, the presenter explained how scoring works in bowling and then asked the audience to create the code used to implement the scoring.<\/p>\n
To make a long story short, both he and the audience started with a brief design phase(!) to design something to do something as simple as keeping score.\u00a0 I thought this was very interesting, even when hearing some of the other developers as they started to design a multi-level hierarchical design for KEEPING SCORE!<\/p>\n
I was reminded of an older idea\/post that I had regarding the problems when you combine too much formal education with too little practical experience and throw the resulting\u00a0person\u00a0into a production-level software project.\u00a0 Just like when you give a\u00c2\u00a0small child a hammer, everything looks like a nail.\u00a0 When you give a lesser-experienced developer the task of designing something, you are more likely to get an over-design<\/em> of something that does not reflect reality and tries to attain perfection instead of practicality.<\/p>\n