My favorite footguns I observe people doing when building software systems:
Reposted from
Anton
- asume that a system is always available
- ignore potential latency
- asume that distributed system X can scale forever adding more nodes
- develop solutions assuming that exactly once semantics are the default/easy
- use interpreted language for performance critical applications
- ignore potential latency
- asume that distributed system X can scale forever adding more nodes
- develop solutions assuming that exactly once semantics are the default/easy
- use interpreted language for performance critical applications
Comments