Ask HN: Do startups follow Unix philosophy,or is 'one thing well' resource ltd.?
A lot of the development trends in utilizing app integrations, where one app does one thing very well and exchanges data with other apps, seems similar to the UNIX pipe philosophy - "make each program do one thing well" and you're able to then pipe them for an output.
macbook > bitbucket > drone.io> dploy > digital ocean etc.
I don’t know if this is a function of small startups not having the resources to go big, or a conscious effort / recoil from bloatware like Lotus Notes (no offense to IBM.) Dropbox seems to keep their functionality very concise, for example. Wanted to ask what the inside talk may be regarding this, if at all. TY.
This is one of many concepts that supports working from a MVP (minimum viable product) and doing one thing (or a few things) really well and to build based on real user metrics. This makes the whole thing a learning process with fast iteration rather than a strict plan to market that is followed from beginning to end.