eXtreme .NET

1
eXtreme .NET

• Dr. Neil Roodyn

2
Who is Dr. Neil?

• MISSION To increase the value of your Software
  Business
• Working with software for way too long to be
  healthy
• Spend half my year in Australia
• Regular contributor to Australian Developer,
  International Developer, Cutter IT Journal, CUJ,
  CODE

3
Books
http//tablet.roodyn.com/
http//smartphone.roodyn.com/
http//eXtreme.NET.Roodyn.com
4
Quick Definitions

• What is XP?
• What is .NET ?
• What is eXtreme .NET ?

5
Thinking Out of Focus?

• Technology
• Features
• Toys
• Process
• Methodologies
• Best Practices
• People

6
What is software?

• CODE!

7
CODE

• Code is what it is all about
• software product some code

8
Better Product

• better code
• Easy to install
• Has functions the user wants
• High quality
• repeatedly works
• Upgradeable
• more features the user wants easily added

9
It's not hard!

• So why do software projects fail?
• We should use language xyz
• We should use technology abc
• We should use these complex patterns
• That we dont actually need
• We should use these practices
• That are not suitable for this project

10
We make it more complex than is needed

• Makes us look smart
• Justifies our high salary
• Covers our arses
• 'It was a tough project, no wonder it failed!'

11
STOP IT NOW!

• Do the simplest thing that could possibly work.

12
How?

• Let me show you....

13
Iteration 0

• The automated build file
• The installer

14
Demo

• Simple build batch file

15
Planning game

• Customer meeting
• User stories
• Task break down

16
The Development Cycle

• Test
• Code
• Test
• Refactor
• Test
• Integrate

17
Test Driven Development

• Test First Programming
• Test Frameworks support TDD
• NUnit

18
The Why Questions

• Why do we need tests in our code at all?Isnt
  that the job of the testers?
• Why do we have to write test code?
• Why not do manual testing?
• Why write the test code before the proper code?
• Why doesnt this whole process cost the customer
  more?

19
Refactoring

• Changing the structure of code while maintaining
  the behaviour

20
The Why Questions

• Why not just get it right the first time?
• Why not just start again if you know its wrong?
• Why cant I just refactor at the end of the
  project?
• Why does this help me develop more robust code?
• Why should I do it when no one else does?
• Why do something that doesnt add any new
  features to the code?

21
Demo

• TDD and refactor

22
Testing the GUI

• Its SO HARD
• Yes so is writing good software!
• Its actually not so hard
• use reflection

23
Spiking the unknown

• When you find an area you dont fully understand
• Explore
• Experiment
• Explain

24
Ship It!

• Anytime you have a green screen
• Should be ready to ship your software everyday

25
eXtreme .NET Day

• Hands-on how to use the techniques
• Coming back in October
• 1 or 2 days?
• http//www.dotnetsolutions.com.au/

26
Resources

• http//www.Roodyn.com
• http//eXtreme.NET.Roodyn.com
• http//www.xp123.com
• http//www.extremeprogramming.org
• http//www.xprogramming.com

27
Questions?

• Thank You!