Enterprise software lifecycle

I have seen this cycle enough times to grant a blog entry.

The enterprise application software cycle can be summarised as:-

• good abstraction
• lack of understanding and respect
• force programming

This is how it goes;

A new team arrives to the scene. Takes a look at the application and decides that it is totally not good (lack of understanding and respect).

They start force programming it for a while, making the issue even worst.

They may understanding what is going on in about a year or so, re-do some of the work and may arrive to good abstraction stage.

The team mostly leaves, a new team arrives and we are back to the future.

What can be done about it? Well, it is hard to skip the lack of understanding but we can skip the lack of respect and force programming bit.

The trick is to live with the system a bit and investing enough time to understand, lay on you hammock a bit, do a bit of in the shower programming.

Don't rush to conclusions.