the internal software quality of a code base correlates to the level of emotional intelligence shared among stakeholders. EQ leads to ISQ
it's like the the code is a reflection of the conversations being had across the team
and the quality of the communication (where we need the EQ) shows in the Internal Software Quality (ISQ)
2/
and the quality of the communication (where we need the EQ) shows in the Internal Software Quality (ISQ)
2/
every piece of code you look at, is a series of conversations between one or more developers and their manager. or to unpack it a lil more ...
3/
3/
id bet that every class you look at that is easily understood, easily refactored, is a series of collaborative, respectful, clear, healthy conversations between one or more developers and their manager, and their manager's manager, the customer, and the end user
4/
4/
on the flip, id bet that every class you look at that is confusing, hard to read, test, refactor, is a series of
confusing or contentions or guarded conversations between one or more developers and their manager, and their manager's manager, the customer, and the end user
5/
confusing or contentions or guarded conversations between one or more developers and their manager, and their manager's manager, the customer, and the end user
5/
relates to day to day convos we have as devs
and what we know about #conwaysLaw to paraphrase:
"systems are copies of the communication structures of organizations"
6/
and what we know about #conwaysLaw to paraphrase:
"systems are copies of the communication structures of organizations"
6/
and since - higher EQ = better communication
we might extend conway's law to:
"systems are copies of the communication style, quality, and shared EQ between teams"
/7
we might extend conway's law to:
"systems are copies of the communication style, quality, and shared EQ between teams"
/7
• • •
Missing some Tweet in this thread? You can try to
force a refresh
