re-fuse-nik (noun) a person who refuses to cooperate with a system or comply with a law because of a moral conviction
Some IT architecture refusenik types who may or may not have moral convictions about this sort of thing:
- It’s all in the code – Just wants to get on with cranking out what really matters (to them) the code. Thinks that anything to do with architecture is poncey nonsense and that all architects need to “get real” and realise that code is king.
- It’s all in the process – Can create the worlds most complex process that will deliver, er well nothing actually because no one will ever take any notice of it and just get on with the real work anyway.
- It’s all in the clouds – Will pontificate endlessly on things like ‘governance’, ‘process’, ‘reviews’ but will never actually deliver anything.
- It’s all in the model – Opposite of the coder. Thinks the system is completely describable by models and says their work is done, and the system is ‘complete’ once 35 (or more) UML models have been created.
- It’s all in the plan – As long as we have a plan that is at least 8 levels deep and has every minute of every day accounted for it’ll all just work at the end of it.
One thought on “Architecture Refuseniks”
Just to let you know – this post was featured in a link roundup on the SATURN Network blog at http://saturnnetwork.wordpress.com/2010/03/15/link-roundup-march-15-2010/