Here we go again
For me, JAOO is the event of the year in the danish software development community.
Last year the buzz was all about functional programming. This years buzz?
Somewhere between cloud computing and self-improvement, combined with pessimistic note
The best talk was Keith Braithwaters “Techniques That Still Work no Matter How Hard We Try to Forget Them”. He calls himself Old School – old enough to have seen 2 of the 7-year cycles in software development.
Much to peoples amusement, Keith started by announcing, that if IT was a person, It would be diagnosed with
• Retrograde amnesia
Things we got right? Nobody has never been as productive as in Smaltalk. 21 years ago. And still is.
There was once a thing called System Analysis … Anyway, somethings wrong with the UML diagrams.
Instead, we should look into how Engineers model:
- Models are useful for what they leave out
- Faster, cheaper than building a prototype
- Models Answer Questions – more quickly and easily than the real thing would
UML diagrams dont adhere to any of these principles …
Michele Lanza , from University of Lugano, Switzerland had a fantastic talk about architecture visualization. Code is text – but we are visual beings. The proper visualization tool should enable us to tell the stories behind the software.
We all know that we should build habitable systems, and that the patterns movement comes from (urban) architecture. CodeCity is the “Habitable” metaphor on stereoids – software packages are converted into cities, classes into buildings, with one floor pr method.
This was my moment of enlightenment. I attended the tutorial by Gertrud&Cope about “Fine tuning Scrum”. As well as we have software architecture patterns, deployment patterns, concurrency patterns and … dating patterns, organizations have patterns as well.
Pick a set of them – organize them into a pattern language – and you have Scrum.
Pick another set – and you have XP.
Pick another …
This explains why the thing works – there are patterns underneath.
This made me thinking how this connects to the goals of Enterprise Architecture …
Mary Popkins had a fantastic lecture about how we can transform principles of deliberate practice, into the context of software development.
Malcolm Gladwell quotes the 10.000 rule in his book “Success Factors”, and Mary quotes the same research.
10000 hour rule
Any talent which follows deliberate practice for 10.000 hours becomes a Master.
Therefore, we should strive to nurture environments, that let our talents develop under deliberate practice. This requires:
- Find a teacher / mentor
- Practice repeatedly
- Obtain immediate feedback
- Focus on pushing the limits
- Practice regularly & intensely