Posts Tagged ‘architecture’
Marginal cost of making mistakes
In a note to my last post ‘Safety first‘ I promised more on this topic, so here goes… TL;DR As software learns from manufacturing by adopting the practices we’ve called DevOps we’ve got better at catching mistakes earlier and more often in our ‘production lines’ to reduce their cost; but what if the whole point […]
Filed under: code, culture, software | Leave a Comment
Tags: architecture, cost, design, DevOps, economics, mistakes, risk
Filed under: presentation, technology | Leave a Comment
Tags: architecture, consumerisation, consumerization, container, framework, html5, mobile, native, strategy, web
Styles of IT Governance
I had the pleasure of being invited along to one of Simon Wardley’s Leading Edge Forum dinners last week. Kate Craig-Wood did a great job of summing it up so I don’t have to: I hope to return to the questions of corporate irrationality in another post. The dinner was under Chatham House Rules, […]
Filed under: architecture | 1 Comment
Tags: architecture, comparative, enterprise, governance, IT, law, principles, regulation, rules, strategy
BYOD
I’ve spent a good part of the last year working on mobile strategy, so I get asked a lot about Bring Your Own Device (BYOD[1]). This is going to be one of those roll up posts, so that I can stop repeating myself (so much). It’s not about cost (of the device) A friend last […]
Filed under: technology | Leave a Comment
Tags: android, architecture, BYO, BYOC, BYOD, iOS, iPad, iphone, mobile, smartphone, strategy, tablet
I first drew this chart back around 2004 for my friend Alexis Richardson. At the time I referred to it in the context of a proprietary research methodology, but I don’t want trademark lawyers chasing me – hence the thesaurised title for this post. The point was very simple – we had standards based protocols […]
Filed under: architecture, software, technology | 6 Comments
Tags: AMQP, architecture, middleware, MOM, protocol, RabbitMQ, saas, SOA, web services
James McGovern came up with a good starter for 10, but since he called me out to add some more here goes: Ignoring Pareto – many enterprise architects end up becoming the creators of internal ‘standards’, and then become the standards cops. All too often the 80:20 rule is ignored (and in fact this tends to […]
Filed under: software | 4 Comments
Tags: antipatterns, architecture, pareto, patterns, scalability, software
Chris Swan's Weblog 