Bad software kills

people-2561631_1280.jpg

Bad software development habits are like smoking cigarettes. 

The biggest challange for the organisation is to understand that those habits are as leathal to IT as smoking is to your lungs.

Your companys IT-systems will get a massive technical dept, and it will be to late to save them, if you don’t take action now.

Lack of disease insight make ad-hoc programming without design comparable to smoking a parties. You feel good and having a joyful evening. Eventually you cough a little in the morning the day after, but nothing serious.

Today, in many organisations, the health awerness for IT systems, are like the public knowledge of dangers of smoking in the fifthties. A time when smoking was glamourous.

 In order to avoid technical debt building up like tar in your lungs, you have to be aware and understand that bad software kills IT-systems. Not today, but slowly over time.

For an architect, in a organisation with lack of disease insight, the first step is to build up an awareness of the problem together with the major stakeholders.

 

 

 

The naked architect

I’m not thinking of Jamie Oliver and the naked chef, but instead H.C. Andersens classic story.

Today, lots of people in the industry put up the title Architect on their business card or profile. The problem with this approach from some architects, is my opinon threefold.

  1. They can’t define what they mean with Architecture and the benefits with it.
  2. They don’t have a described method of how to do Architecture, instead it is ad-hoc work and random activities.
  3. They only know architecture theory, but not how to apply it in the in the real world by using prior art and examples.

So when recruiting or hiring an Enterprise Architect, make sure his not naked, but have the right outfit for the job. 

If you are an Enterprise architect you should be able to:

  • Define what architecture is for you and the benefits you get from it
  • Describe the method you to make architecture work, according to above description of architecture and benefits
  • Be able to show how to apply this in real world examples

The below image is from an interview for a client in Sweden where I showed how to make a high level enterprise architecture (organisation, process, information, IT) in their type of business in 45 minutes.