4 ms·
The difference is understanding the architecture at a higher level: how programs communicate with their dependencies, how to do resiliency and failover, how to
by twblalock 4y ago
The difference is understanding the architecture at a higher level: how programs communicate with their dependencies, how to do resiliency and failover, how to scale an entire system of such programs, how to react when something is wrong in such a complex system, and crucially how to design your programs so they can behave as expected when things fail.
- still_grokking 4y agoAnd how do you program such complex software in the first place if you don't know all those things? Not understanding the architecture means not knowing what you do at all! If you don't know what you're doing you should be strictly prohibited form doing it anyway. Or else you will very likely cause damage. Or do you think it's viable that some programmers require constant hand holding with almost every line of code they write because they otherwise don't know what and how to implement anything correctly? The model "coding monkey" just does not work; as everybody knows…