←back to thread

Splitting engineering teams into defense and offense

(www.greptile.com)
210 points dakshgupta | 3 comments | 14 Oct 24 20:07 UTC | HN request time: 1.653s | source
Show context
Towaway69 ◴[15 Oct 24 08:07 UTC] No.41846120[source]▶
What's wrong with collaboratively working together? Why is there a need to create an atificial competition between a "offence" and a "defence" team?

And why should team members be collaborative amongst their team? E.g. why should the "offence" team members suddenly help each other if it's not happening generally?

This sounds a lot like JDD - Jock Driven Development.

Perhaps the underlying problems of "don't touch it because we don't understand it" should be solved before engaging in fake competition to increase the stress levels.

replies(1): >>41846367 #
1. megunderstood ◴[15 Oct 24 08:38 UTC] No.41846367[source]▶
Sounds like you didn't read the article.

The idea has nothing to do with creating artificial competition and it is actually designed as a form of collaboration.

Some work requires concentration and the defensive team is there to maintain the conditions for this concentration, i.e. prevent the offensive team from getting interrupted.

replies(1): >>41846456 #
2. Towaway69 ◴[15 Oct 24 08:53 UTC] No.41846456[source]▶
Ok, that might well be the case! Many apologies for my mistaken assumptions.

Then perhaps the terminology - for me - has a different meaning.

replies(1): >>41847958 #
3. Kinrany ◴[15 Oct 24 12:41 UTC] No.41847958[source]▶
It's a common and pervasive mistake to assume the meaning of a term by association with the words used in the term. Names of terms are at best mnemonics.