5 ms·
A corollary for this could be: The value of minimizing external complexities [0] For instance, if you design an application as HTML+PWA instead of native mobi
by bob1029 5y ago
A corollary for this could be:
The value of minimizing external complexities [0]
For instance, if you design an application as HTML+PWA instead of native mobile apps, you just need a web developer who understands responsive CSS techniques and maybe someone with time to test a bunch of different devices all day. With native, you usually need 1 fairly-specialized developer per native target unless you have a lot of time to go to market (or a very simple app).
Another example could be designing your product to run on a single, bare-ass VM so you don't need to hire legions of level 30 kubernetes wizards to sort our your go-to-market strategy or accountants to manage the byzantine nightmare that is AWS/Azure/Et. al. billing.
The fewer things you have to worry about, the less expertise you need to maintain.
[0] What I mean by "external complexities" - Anything that is external to the problem domain for which the solution is originally being built. If you have a banking product, an internal complexity would be state management around account or customer activities. An external complexity would be a 3rd party vendor, reporting system, database, file, network, hardware, operating system, or any other non-domain types residing within the software product itself.
- km3r 5y agoOne fairly specialized developer is a lot harder to replace then a generic level 30 kubernetes wizard. You lose that developer as a company and the ramp up time for a replacement could be >year. In addition, more standardized approaches have better defined practices, tooling, and security.