- cross-posted to:
- lobsters
- cross-posted to:
- lobsters
Matches my own experience when working on software where quality matters, like large and long-running scientific projects: Even if there are tight time constraints, you won’t sacrifice quality, because that would make you slower.


That’s pretty much in line with what John Ousterhout writes. I think if you deal with multi-threading / locking / diszributed systems stuff, that time span is likely to be lower.