this post was submitted on 25 Jul 2023
34 points (97.2% liked)

Programming

17406 readers
175 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
top 8 comments
sorted by: hot top controversial new old
[–] Wats0ns 8 points 1 year ago (1 children)

"Each team is full-stack and full-lifecycle: responsible for front-end, back-end, database, business analysis, feature prioritization, UX, testing, deployment, monitoring"

"But they also shouldn't be too large, ideally each one is a Two Pizza Team"

Either that's a team with some hugely diversified skills, or that's two car-sized pizzas

[–] canpolat 4 points 1 year ago (1 children)

I agree that this is a challenge. One needs to slice the domain such that it can be covered this way. But this also means more people. In my experience, moving from "activity oriented" teams to "business centric" teams require an increase of the headcount.

[–] Wats0ns 1 points 1 year ago

Same, that's why I don't understand how this is supposed to stay a two-pizza team system

[–] [email protected] 5 points 1 year ago (1 children)

I'm a simple man, I see Fowler and I upvote

But then I read this article and it is very thin puff piece for the book. Very little insight

Obey conways law, you can't break it

[–] [email protected] 3 points 1 year ago

Like every other Fowler article?

[–] [email protected] 3 points 1 year ago

I like the concept of reducing cognitive load for the stream-aligned teams. This means all efforts go towards enabling them as much as possible in supporting the business. It also makes it relatively easy to judge if a platform team is doing the right things.

[–] Corbin 1 points 1 year ago (1 children)

Conway's Law is a category-theoretic statement; it asserts the existence of a homomorphism on graphs, mapping from modules to code authors. Quoting Conway's original paper:

Speaking as a mathematician might, we would say that there is a homomorphism from the linear graph of a system to the linear graph of its design organization.

The author does not really show an understanding or respect for the underlying maths.

[–] kogasa 2 points 1 year ago

Nothing to do with category theory. A homomorphism of linear graphs is a fairly concrete object, and Conway only uses graph theoretic terminology to clarify his semi-formal exposition. Dunno if I'd say there's much math not being respected.