4 ms·
The Unix philosophy of small, modular processes feels right to me, as a user and a coder. However the business and product developer in me wonders how I apply
by dangravell 10y ago
The Unix philosophy of small, modular processes feels right to me, as a user and a coder.
However the business and product developer in me wonders how I apply this to building more complex systems. Normally this involves building multiple functionalities. Does the philosophy say I shouldn't build "systems" that are complex and do multiple things? Or does it talk about how these should be implemented, as co-operating processes?
- edblarney 10y agoThe 'do one small thing and do it well' philosophy is at least contentious in the general sense. Reality: no unit exists outside the context of it's ecosystem. Ergo, the API to that unit, and the degree to which it integrates with the other pieces is paramount. The 'do one thing and do it well' ideal implies almost a kind of 'unit sovereignty' that in many cases does not exist. In large, complex systems, 'units' can only view as parts of a greater whole. 'What they do' is almost less important than 'how well they fit'.