When We Need Systems, Processes, and Conventions

Published on Dec 11, 2024, filed under development, management (feed). (Share this on Mastodon or Bluesky?)

When do we need systems, processes, and conventions? ^*

When we work with someone else.

Yet even if we’re working alone, we often benefit from structure and consistency. ^†

A brief comment, as this is something that’s usually taught late (and wants to be taught earlier). Not to you—you’re aware. But to peers who struggle getting behind systems, processes, or conventions.

What’s underpinning systems, processes, and conventions is the desire and need for collaboration. It’s okay to be skeptical about the specifics of systems, processes, and conventions, because it helps improve them—but it makes our work unnecessarily difficult when we don’t channel skepticism about systems, processes, and conventions in general.

^* Documentation systems, issue management systems, planning processes, review processes, code conventions, design conventions, all of it.

^† E.g., check my old CSS-Tricks article, How to Write Better Code: The 3 Levels of Code Consistency, for thoughts on individual consistency.