Posts Tagged ‘architecture’
Last week my former colleague Doug Todd asked a question about recording decisions on BlueSky: Of course I replied suggesting Architecture Decision Records (ADRs), with a pointer to the at_protocol GitHub repo where we use them. A few days back Doug demoed how he’s using ADRs with his coding assistant (Claude and Claude Code), and […]
Filed under: architecture, code, software, technology | 1 Comment
Tags: ADR, ADRs, AI, architecture, Claude, coding assistant, decision, LLM
Dealing with Policy Debt
TL;DR Start writing down why decisions are made. Future you may thank you. Future other person who’s wondering what you were thinking may also thank you. Then keep a dependency graph of the things impacted by the decision. It will help unravel what gets woven around it. Background I was at an excellent AFCEA event […]
Filed under: security, strategy, technology | 1 Comment
Tags: ADRs, AFCEA, Agile, architecture, change, compliance, culture, debt, decisions, innovation, policy
One of my favourite features of Dart is its ability to create executables (aka ahead of time [AOT] binaries)[1]. Creating binaries for the platform you’re running on is very straightforward, just dart compile exe but Dart doesn’t presently support cross compilation for command line binaries, unlike Rust and Go, which have also surged in popularity. […]
Filed under: Dart | Leave a Comment
Tags: Actions, architecture, ARM, Arm64, Armv7, binary, Buildx, Dart, Docker, github, Linux, MacOS, matrix, multi, platform, RISC-V, riscv64, tar, tarball, x64
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 