Design for additional requirements, or not?
Do you need architecture when doing agile development? The philosophy of Agile is to do the least amount of something and no more for a given situation, but is this always a good approach?
Do you need architecture when doing agile development? The philosophy of Agile is to do the least amount of something and no more for a given situation, but is this always a good approach?
Joakim Lindbom and Greger Wistrand both talked about the pro’s and con’s with bi-modal or pace layered IT. Joakim sees the benefits and Greger explains why it doesn’t work.
When reviewing programs, projects and solution designs from an architecture perspective, I often see people doing the same mistakes as others have done before. I did some of them 25-30 years ago and I see people doing the same mistakes today.
I have a seven year old car and we drive 30 000 km per year. We follow the service instructions, change parts when needed and we will even get a free software update to our engine from the manufacturer.
For how long time can I use this thing, is becoming a more and more relevant question. Ask Arlo Gilbert, who recently bought a home automation hub from Resolve, and found out the Google will turn off the device on May 15th 2016. Gene Hugson wrote about Stirring up a Hornets Nest. and asked some questions about long term commitment from vendors.