Ok, I’m sorry, I’m going to ruffle feathers here but… I’m trying to read some newer development process books and… oh my… even super popular ones are so immensely long winded and unconvincing in their dogmatic argumentation: this is bad, this is good, because I said so that’s why.
Recent examples that I’m struggling to finish: “Team Topologies” and “Data Mesh” - I mean they might be great but I’m getting strong “this should’ve been a blogpost” feels.
I can’t. “This is how you simplify things for these silly dev folks who struggle to understand even basic stuff.”
“How to break down large domains”
If you think that there is a Perfect Org Breakdown for all the things I believe you don’t know anything about anything.
“Here is example number four of a team who struggled to keep up with requests after a lot of people started to use, love and depend on the thing the team had built”
“They are struggling because… actually… they are extremely dysfunctional and not actually… extremely successful”
Grrrrr 😡
@Patricia I'm pretty sure if you say outlandish opinionated stuff about something a lot of people have a lot of money riding on, that affects a lot of people, you'll get enough people talking about the book to retire early and never have to care about it again
so maybe that was the plan all along?
Patricia Aas
caitp