- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or register to comment.
After you’re in the field for long enough, you start to realise that the structure and flaws in the application mimic the structure and flaws of the reporting structure of the organisation
Yeh. Matrix structure where anyone can message anyone, and lots of people depend on each other, seems to work pretty well. But silos will develop anywhere you’ve got hundreds of people, at least as far as I’ve seen.
I’ve also witnessed matrix structure break down when too many methods of communication are used. It’s all very brittle.
I’ve seen matrixed organizations (re)build themselves to Agile (multi-disciplinary) ad-hoc teams, where there are clearly some such teams that wildly outperform the others. Basically you just hope and pray you’re plugged into one of the good ones. Meanwhile none of the lower-tier managers have any real control over workflow, workload, or what anyone is actually doing.
Every system has limitations and flaws. The trick is tailoring your system elements to serve your use case.
That tech debt graph in the background is the best thing I have ever seen.
I’m going to pronounce it “agilé” at the next stand up and see who corrects me.
With a hard g?
That’s how I hear it, anyway.
I see a fellow GIF person.
I don’t see how it is a joke tbh. Thought that was one common interpretation of said law.
I feel like it’s missing the setup of the dev complaining about why their architecture is a mess. Seems like a “management is ruining software” joke.