3 ms·
I think the last line is quite telling: "[docker and electron] are just compromised attempts to hide accumulated complexity from developers because it became im
by ClumsyPilot 7y ago
I think the last line is quite telling: "[docker and electron] are just compromised attempts to hide accumulated complexity from developers because it became impossible to deal with"
The alternative is what, infinitely increasing complexity? Every industry has division of labour: If you are a chef baking cheesecake, you don't need to know how to make cheese. If you are a cheese-maker, you don't need to know how to milk a cow. If you are a farmer, you don't need to be a cattle vet, or be skilled in building a barn or repairing tractors, or in smelting stainless steel that it's made of.
Step into the software sphere and the abstractions we are building are leaky, and unstable. The best example of this is Kubernetes -> it has a hundred moving parts, and if you got an error it could be because of the problem in the kubelet, or in underlying Docker, or in Flannel, or in IPtables, or linux kernel settings, or in the settings of hypervisor, etc, etc.
Instead of creating productive division of labour, in IT we create UNPRODUCTIVE division of labour: Ow, this is written in .Net and that is written in Java, But I only know Golang, Javascript, C++ and Python!
The most elementary problems don't have a standard solution: how many ways are there to format a settings file? Probably a few dozen. How many of them afford the user syntax highlighting?
I believe the root cause of bad quality software is accountability: an average android phone ships with dozens of bugs. You could not ship a car with a missing wheel. But if WiFi calling doesn't work, nobody cares. Companies know that they can get away with it, and they do. If your management knows that shipping buggy software is fine, and so does the rest of the industry, actions of individual developer can only go so far.