🧩 Composing is hard, complexity is easy

We've recently explored the idea that composing simple things is the way to scale. But this is harder than just cranking something out. Some examples:

• It is much easier to create an Excel spreadsheet than write a Python script to process a CSV file and create a chart which can be later automated in a CI process.
• It is much easier to create lots of custom structs with lots of fields than to create simple structs that can be used for multiple purposes.
• It is much easier to add additional functions to an interface than to create additional well-thought-out interfaces.
• It is quicker to hack on a Raspbian image than to set up a proper Yocto build for a Raspberry Pi single board computer that can be more easily maintained long-term.
• It is quicker to draw a schematic with generic parts and manually assign manufacturer part numbers/footprints, than set up a proper parts library that will make subsequent designs and changes easier.

If your task is a one-off project, or something only you will ever interact with, then the easy path may be fine. However, if you want to scale, the hard path is the way forward.