thinking about this: complexity has to live somewhere
complexity has to live somewhere—the trick is putting it in the right place. modern cpus are incredibly complex: multiple tiers of caching, speculative execution, etc. none of which you ever think about when building a web app, which in turn has its own kind of complexity.
a cpu runs on top of some very complex and speculative physics that we only incompletely understand: neutrino oscillations, quark color confinement... luckily you also don’t need to understand any of that when building a web app. 😀
my 2¢ is, put as much complexity as is necessary inside of a microservice, framework or library—as long as the team that maintains it can understand it. but make its interface as simple as possible, so that the team at large can effectively make use of it.
it’s kind of the opposite of worse is better, but i think the use case is different.
", "mediaType":"text/html", "attachment":[], "tag":[ {"type":"Hashtag","name":"#software","href":"https://epiktistes.com/tags/software"}, {"type":"Hashtag","name":"#complexity","href":"https://epiktistes.com/tags/complexity"} ], "type":"Note", "id":"https://epiktistes.com/objects/IXU3-jgwCFw" }