#BVSSH, Modern Enterprise Architecture, Agile, DevOps, lean, experience design, full stack dev // contributor to @ITRevBooks Sooner Safer Happier
CPH / NYC / LDN
Joined July 2016
- Tweets779
- Following536
- Followers300
- Likes1.9K
Pinned Tweet
Coming soon
ALT A graphic describing the 5 elements of Modern Enterprise Architecture - ABCDE - A - a triangle, with text “aligning value, people and technology”; B - a loop, a stylised logo, with text “better value sooner safer happier”; C - a right pointing arrow - “continuous conversational architecture”; D - an infinity loop - “DevOps at enterprise scale”; E - a graphic representing the evolutionary concept of punctuated gradualism - “evolutionary enterprise architecture”.
2
4
327
Simon Rohrer retweeted
Jevons paradox, red queen effect for staff & costs, lack of awareness for waste and the cleaning up legacy is wishful thinking.
Simon Rohrer retweeted
Why do we talk about shadow IT and never shadow finance, shadow HR, shadow customer support, shadow marketing etc? All those functions are most definitely creeping outside their silos and no one seems to mind.
Putting in a word for Kotlin. Like Java, but a pleasure to code in and less wasteful
Why the rewrite from F# to Java:
1. F# has an unfamiliar paradigm for most developers and a smaller hiring pool
2. F# doesn't have the social capital / clout to make non-F# developers see profit in learning it
3. Non-F# developers assigned to work on this project oink and squeal about "the learning curve" - that is to say, having to learn *anything* amounts to a "learning curve"
4. Boomer engineering leadership decides to rewrite the system in something the rest of their engineering team understands, despite it being a waste of money and time. It's all in the name of making the "this is too 'hard'" complaints from engineers stop
147
Simon Rohrer retweeted
This is a paper I post every six months as it is worth rereading; the 18 reasons complex systems fail.
Complex systems fail for complex reasons, and only adaption & learning by organizations, as well as individual "actions on the sharp end" keep us safe. researchgate.net/publication…
Simon Rohrer retweeted
We need a new approval process to really nail quality, the Review Board Review Board. All decisions by the CAB or Architecture Review Board must be approved by the RBRB, whose members must come from areas as far removed from the work as possible to maintain objectivity.
Simon Rohrer retweeted
How come people dont talk about Kotlin more? It’s like a nice version of Java 🫣
Simon Rohrer retweeted
Having said that, for stuff between experimental spikes and boring (that is, everything which sits between complex and clear, including the complex / complicated liminal threshold where you know roughly what you want) agree that pairing is best, energy levels notwithstanding.
Simon Rohrer retweeted
"A building is not something you finish. A building is something you start."
@stewartbrand
Software is never "done" (until it's out of production)
Simon Rohrer retweeted
Hard to summarise in a tweet. The best I've ever seen what I'm trying to say, summarised in a succinct way is in this @KentBeck interview with @lissijean. But... I feel there's a lot of prior art required for it to really sink in.
produxlabs.com/product-think…
Simon Rohrer retweeted
Are agile and architecture old friends who had grown estranged meeting up again after years apart? Read about @sirohrer's journey for over two decades juggling the concepts of these two worlds. Join him at a conference in October for more. agile-meets-architecture.com…
Simon Rohrer retweeted
Better Value Sooner Safer Happier.
Hear more from @jonsmart & @sirohrer in episode 144.
techleadjournal.dev/episodes…
Simon Rohrer retweeted
@jonsmart and @sirohrer are the co-authors of “Sooner Safer Happier”. In this episode, Jon and Simon shared how we can deliver better outcomes in a more humane way of working, by delivering better value sooner, safer, and happier.
techleadjournal.dev/episodes…
