You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: "The Gitflow of Version Controlled Knowledgeware"
4
+
subtitle: "Teams, Code Review, And The Elevation of Communication Discipline"
5
+
date: 2023年07月09日 3:30:00
6
+
categories: LEAN
7
+
---
8
+
9
+
10
+
# How does Git FLOW?
11
+
12
+
And how doesn't it?
13
+
14
+
# COMMIT to improving communication technology.
15
+
16
+
Understand what communication is ... you do NOT just know because you graduated kindergarten ... most of what you have been taught and most of the bad habits that you have reinforced need to be broken and thrown away.
17
+
18
+
Asynchronous communication of knowledgeware development has to flow in a Git info stream ... understand the hydrology of Git.
Copy file name to clipboardExpand all lines: _posts/2023-08-09-toward-a-theory-of-quantum-communication.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,11 +9,15 @@ categories: LEAN
9
9
10
10
# Knowledge work is ASYNCHRONOUS communication
11
11
12
-
Organizations are still organized around face-to-face boss-man-to-slaves plantation-style communication, but knowledge work is predominantly ASYNCHRONOUS -- it IS easier for a group to lift a large object together, but in the realm of knowledge work it is NOT easier to have a meeting room full of a-hole yesmen leaning in to seek facetime with the boss to *lift* a big idea ... in fact, it's more likely that the room is packed with the wrong people OR that the right people are scattered around the globe, not just in different time zones but with different priorities and very different sleep/work/family/play schedules.
12
+
PRODUCTIVE work, ie where hard stuff actually gets done, or the bulk of progress in knowledge work is predominantly ASYNCHRONOUS -- but it is also necessary to synch up, to maintain focus, to occasionally have meaningful synchronous meetings. The problem with synchronous meetings is that schedules are cleared and left open while people wait for their part of meeting to happen -- a lot of time is wasted and effort expended to synch up, to actually get people together at a particular time.
13
13
14
-
The PROBLEM is that bossman slaveowner types still love being stroked ... and cocksucker yesmen still are proud of their lean in skills and being selected to getting on their knees and pleasure the bossman ... so the SYNCRONOUS on-site work schedule persists even there is no physical justification for it.
14
+
In physical work, synch matters more. It IS easier for a group to lift a large object together and Henry Ford's Model T line needed to have bodies on the line to build cars, but in the realm of knowledge work it is NOT easier to have a meeting room full of yesmen leaning in to seek facetime with the boss to *lift* a big idea ... the bossman's idea gets *lifted* but other ideas stay put. The fact of meetings is that it's too likely that the room is packed with not exactly the right people ... the truly *right* people are scattered around the globe, not just in different time zones but with different priorities and very different sleep/work/family/play schedules. When the *right* people are not allowed to have lives, they can be ridiculously productive for a while, but they cheat themselves and tend to burn out.
15
15
16
-
The FACT of the matter is that although physical *lifting stuff together* work is best accomplished in a SYNCHRONOUS fashion ... knowledge work is primarily about ASYNCHRONOUS communication. Choosing and extending the [right OPEN SOURCE tools for efficient asynchronous communication](https://zulip.com/why-zulip/) WILL provide a massive productivity boost ... it's all about extensibility because the barriers to productivity will be removed when people stop assembling knowledge the way Henry Ford built Model Ts and start becoming aware of lean thinking, lean knowledge, lean ideas, lean communication and taking out the non-value-added waste that is an impediment to higher productivity in that realm ... the magic of open source happens when knowledge workers begin to tailor and extend their own asynchronous assemblyline in the virtual realm.
16
+
Synch stills matters -- but it should not predominate ... synch should be reserved for the times when getting together is a necessity for focus, ie when togetherness is treated as a constant, everyday ordinary necessity, it ceases to be ... and people quiet quit, even without intentionally doing so, ie like narcolepsy in sleep-deprived truckers. Predominantly synch workflow is not human -- it can work for awhile, but it becomes like Henry Ford's Model T assembly line ... because productive knowledge workers have other choices ... even though corporate drone yesmen may not.
17
+
18
+
Organizations are still organized around face-to-face boss-man-to-the-slaves plantation-style communication. The PROBLEM is that bossman slaveowner types still love being stroked ... and they sign the paychecks or do performance reviews in larger orgs ... and, of course, corporate drone yesmen still are proud of their lean-in skillsets ... so the SYNCRONOUS on-site work schedule persists even when there is no productivity justification for it. The FACT of the matter is that although physical *lifting stuff together* work is best accomplished in a SYNCHRONOUS fashion ... knowledge work is primarily going to be about ASYNCHRONOUS communication ... so we should manage accordingly.
19
+
20
+
Choosing and extending the [right OPEN SOURCE tools for efficient asynchronous communication](https://zulip.com/why-zulip/) WILL provide a massive productivity boost ... it's all about extensibility because the barriers to productivity will be removed when people stop assembling knowledge the way Henry Ford built Model Ts and start becoming aware of lean thinking, lean knowledge, lean ideas, lean communication and taking out the non-value-added waste that is an impediment to higher productivity in that realm ... the magic of open source happens when knowledge workers begin to tailor and extend their own asynchronous assemblyline in the virtual realm.
17
21
18
22
# Use D.O.W.N.T.I.M.E. to see waste and eliminate it
0 commit comments