Final topic we have from this peculiar book.

We know basically everything now on how to create babies, I mean, software. How does its life looks like?

Treat them with care. Photo by Ryan & Dana on Flickr

It has the following sections according to the book

• Feature List
• Use Case Diagrams
• Break up the Problem
• Requirement
• Domain Analysis
• Preliminary design.
• Implementation
• Delivery

Going back to the baby analogy. We can compare it in such way that our software is like this:

1. Planned (No happy accidents!)
2. We had decided how it would be named
3. How it will be raised
4. Setting house rules on what it should and shouldn’t do
5. Develop a good base so when it’s a teenager, it’s not a nightmare to everyone else it communicates to.
6. If everything is done correctly, you will have a happy and productive adult ready to help everyone.

Practice makes perfect!

Thankfully, software development doesn’t take 18 years but may be as expensive or even more so!

There are lots of tools, methodologies and ways to do things. I believe that while you can learn most from a book, real life experience is the best teacher.

Iterate on each software project to be better and risk will be reduced immensely. You will also get paid a lot. Basically a win/win.

Somewhere I read something along the lines of:

Everything that can be measured can be managed. If it can be managed, it can be improved.

Which I would say relates pretty good to the contents of this book.

Hasta aqui mi reporte joaquin.