🔀 The division between group and personal workflow

When thinking about developer workflows, tools, and resources, dividing them into two categories proves useful: personal and group. A group resource is something that multiple people use (or should use): SDKs, libraries, linters, formatters, AI commands/context, etc. Personal tools are things that others do not use: pencil, computer, phone, editor, notes system, etc.

Why is this so important? Why not just make it simple and force everyone to use the same computer, editor, notes system, chair, desk, etc.?

Humans are users and creators of tools—naturally inclined to make, modify, and optimize tools for specific needs. Innovation happens where there is freedom. Many improvements start from a single person scratching their own itch. Over time it becomes apparent that a tool or improvement will benefit the group, so it migrates to a container or some other shared resource and is integrated into the group workflow.

As previously mentioned, any shared resource should be containerized when possible. Containers allow the personal computer to be the dividing line between personal and group workflows.

No two humans do exactly the same thing. No two humans think and work in exactly the same way. While there are many benefits to having group workflows, the personal workflows must also be nourished, as these are a primary source of innovation. The key is to have a culture where the migration from personal workflow to group workflow is encouraged, supported, and rewarded.

To scale, an organization must have:

• A clear division between personal and group workflows.
• An efficient way to reuse personal workflows as group workflows where appropriate.