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 😡
I’m sure they TALKED WITH THEIR USERS ☠️ fuck that monolith behavior.
And I sound smart and deep because AND THIS IS AN ACTUAL LITERAL QUOTE: “a stream should flow unimpeded”
I am deceased 💀
@[email protected] not sure what's worse, but it's useful to have a look so you know when someone have been too inspired https://teamtopologies.com/talks
@Patricia Echoes of “How can I grow if you won’t let me blow” 🙂
@Patricia thank you for this thread.
Yeah. Everyone has been reinventing Gilbreth for a century.
@Patricia My take on people with "education" in "Agile": they have no clue what Agile really means, lest having done something Agile-ly themselves.
Talks instead of deeds.
I really want "Patricia reviews tech books". I would so hit that subscribe and like button.
As a former dev for decades, turned security nerd, this kind of babble infuriates me.
One can develop and ship code. One can work on a team. Teams can deliver.
The book's hodge-podge of quotes sounds like #AI generated "slop". Individual nuggets of sanity, pasted together with insufficient context.
They needed a bigger token window, and to add "keep the result logically consistent"
@Patricia The idea that google works that way is a fantasy and whoever says it does, I want to talk to them right now.
Google *looooooves* meetings. YAQS is dying. Everyone is encouraged to run office hours. Documentation is often dramatically out of date.
@Patricia I still want to meet them so I can deride them. I am a google sre. I'm on one of the top 10 highest incident load teams, one of the few tier 1 rotations.
I know how this works. I know how SRE does and does not scale. This process you're describing sounds a lot like "if you have a bunch of SRE you can dump all your problems on them and becuase they're a distinct org it'll all get hashed out at the VP level and you can collect promo and leave before it's done."
@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
Mark vW
Arne Mertz
Mrs Beanbag
Zirition
Owlet of Minerva
(moved)Galbinus Caeli 🌯
Kensan
D2
Alex Gantman
Dani (
Antifascista)
Alun Jones
Pseudo Nym
Pär Björklund
Chip Collier
⛈️ Information ⛈️
Steven Willems
Matúš Chochlík
Ólafur Waage
demofox
caitp