Software architecture is in crisis, and the way to fix it is a hefty dose of anarchy.
Some lay the blame for this on @boicy with the whole microservices thing.
(Admittedly, @nicolefv, @jezhumble and @realgenekim didn’t help when they statistically proved that he might have been onto something with all that de-coupling and team-alignment…)
However I don’t blame him at all.
I think he saved us; bringing us back to the path of value-delivery and independent services, but now with added independent teams.
“Patterns of Anarchy” is a collection of writings published in 1966. I came to it because a) Christopher Alexander quotes from it in “A Pattern Language” and b) because as a consultant and developer I’m interested in different patterns of organising. goodreads.com/book/show/1663…
Edited by L. Krimerman and L. Perry, the book brings together thinkers from across the anarchist spectrum and considers definitions of anarchism, anarchist critiques of socialism, it's philosophical foundations, and more.
There’s a lot in it, especially if like me, you don’t know much about anarchism beyond “A Homage to Catalonia”.
I was talking to a colleague & fellow Domain-Driven Design obsessive @thoughtworks the day before yesterday.
Their gig wasn't using #DDD, and while they knew it would bring benefits, they had no remit to start a full-on adoption effort.
And so the conversation turned instead to how they can make their little part of the codebase a #DDD haven, and keep themselves sane in the process.
Now, the typical mindset of a grafting Dev shipping quality code these days is SOLIDSOLIDSOLID, and while that's generally no bad thing, is there a similar place for #DDD in that scene?
In my life as a consultant I've seen many peeps adopting Domain Driven Design.
Things go wrong a lot; and frequently the problems start in the initial stages.
So I made a thread to share my thoughts and tips on the subject of starting out.
(Please comment. I love feedback.)
When I say "Domain Driven Design" I'm talking about the design process introduced by Eric Evans (@ericevans0) in his 2003 book "Domain-Driven Design: Tackling Complexity in the Heart of Software". amazon.com/Domain-Driven-…
This book, while incredibly readable (one of my top three books for devs) also puts people off with its heft. (Understandable.) There are related works too (Implementing Domain Driven Design by Vaughn Vernon (@VaughnVernon) being the most well known.) amazon.com/Implementing-D…
Arrived for the @sainsburys Agile Community Autism Awareness Workshop at @MSFTReactor. I'm excited to see what they have in store for us...
Catherine Leggett from the @nationalautisticsoc kicks us off. Focusing first on workplace adjustments.
Catherine Leggett: "We're not diagnosed on our strengths, these (from the diagnostic criteria) are "difficulties". But these are strengths in different circumstances.