Lies, damn lies and statistics

Entries for tag "rant"

The forgotton question mark

Ya know, I love me a question mark. The elegant sickle like curve and dangling dot, those little paired words of how? and why? It's much nicer than a full stop (or period for my American colleagues). Why do architects seem to prefer the latter?

There is a Proof of Concept below the rant - I beg your indulgence dear reader. The PoC uses Kafka and python to transfer files based on the argument laid out below. The GitHub project is here: mft-kafka

PoC, PoC, PoC, Production

The hint is in the name people. Proof of Concept. Why is this so difficult to understand? The point of a PoC is to show that a thing can be done, not how a thing can be done. I.e. we don't know something but we have an idea - awesome, I'm here to help. Where I seem to part ways is when the PoC plans to deliver best practice architecture, continuous delivery and push the code & pipelines into production.

Empowerment. Bollocks.

I must be getting too old for this shit dear reader, and my deteriorating brain must not be able to appreciate the magnificence that is modern corporate IT. Despite my galloping senility, I shall attempt to marshal my outdated thinking on why we often feel like hamsters in a wheel, destined to never actually get anywhere but with ever increasing demand to go faster.

Architecture Rant

One must occasionally rant. And when that cathartic wave has crashed and some of the built up cynicism washed away, hopefully the receding waters leave a perspective for a pragmatic path forward.

Enterprise architectures should represent the very best of what we can and should strive for, encourage the business and staff to reach higher and push us to see beyond the boundaries and limitations of the current landscape. I guess what it comes down to is that there's good IT and bad IT and we have become overwhelmed by a sales machine - both internal and external, which advertises one but actually delivers the other. Its not a matter of subscribing to the latest method, programme or ethos - it's about understanding the subtle idiosyncrasies and the sympathetic treatment of people, process and technology. Leaning into the complex problems, and sometimes having the courage and integrity to defend work which doesn't have an immediate payoff.