The 20th century was prime-time for the assembly line. There are countless famous examples including:
- Henry Ford cutting the time it took to produce a vehicle by 10x with his Highland Park assembly line
- McDonalds and Starbucks experimenting with thousands of layout variations in their stores to find the one optimal "path" for efficient production
- Toyota's lean production system and values of "constant improvement"
- Airlines all over the world focusing on minimizing turnaround time to boost profit
It's probably not a stretch to say there are trillions of dollars at stake in the race to be more efficient in the physical world, and everyone is working off a similar "best practices" playbook to limit waste, improve speed, and trim unnecessary steps from a system to earn more.
That's fine, but what about the digital world? What does a digital assembly line look like? What are the digital "best practices" for getting more work done, with fewer distractions or dead ends?
When I work (and I assume most people have similar work habits), I bounce around between all sorts of tabs on multiple devices all day long, and anyone observing me would have to conclude that I'm basically the exact opposite of efficient.
For all the value locked up in the digital world today, you'd think there would be some sort of "assembly line" or "efficiency" blueprint that was widely adopted, but I can't think of one off the top of my head.
Maybe this is a function of the way the digital world is structured, maybe it's just me, but maybe there are underappreciated rules, systems, or strategies that we could all be using to be more productive with our digital time.
gem
maven
npm
cargo
pip
, thendocker
that came to mind for meDockerfile
- yes, good one! Despite it not always being useful to me (in those cases I write packer/terraformhcl
forlxc
), it really is the nicest container building format out there.pip
- especially since withuv
you get a nice lockfile too nowadays.