Comments on: How much Architecture do you need?

By: Jeremy Ross

Jeremy Ross — Mon, 09 Nov 2009 22:55:22 +0000

Every time I work on a project in your Enterprise scenario, it feels like a death march right out of the gates. These projects tend to be full of pain, politics and atrocious project management. I avoid these like the plague. Life’s too short.

By: Steven

Steven — Mon, 09 Nov 2009 21:50:39 +0000

I agree with most of your points and I’d like to pick up the “learned the rules” comment in another blog.

But the comment “These organisations are dead” I have to disagree with. The company I referred to regularly makes Billion dollar profits and is very financially secure, indeed its core business is risk aversion (It’s Insurance). I think they will roll on just fine. But I wouldn’t necessarily want to work there

By: rainwebs

rainwebs — Mon, 09 Nov 2009 21:21:51 +0000

Creative people should leave such environments immediately. It isn’t worth to invest life time in a zero fault tolerance environment. These organizations are dead, because they lost the ability to learn: the more faults the better you learn.

If you have a look at architecture from the risk management point of view it is a system of rules that assures that the developers work with a certain farsightedness. If all developers have learned the rules you don’t have to write them down. But, experience shows that it is easier for new team members to have something written down.

I don’t think it makes sense to develop an architecture without direct contact to the development team. In times of agile teams this became pretty absurd .