Processes break in two ways. They break because they don't have the right checks and balances and because they don't have the right execution.
Sentiment: NEGATIVE
When something is working well, it becomes too easy to let things run themselves.
The system is that there is no system. That doesn't mean we don't have process. Apple is a very disciplined company, and we have great processes. But that's not what it's about. Process makes you more efficient.
As a rule, software systems do not work well until they have been used, and have failed repeatedly, in real applications.
Either systems are in balance or they are falling apart. If people are acting in what appears to be a twisted way, I want to know the reason for that.
Windows favors multi-threading, which means that a service is implemented by one single process.
There is a construct in computer programming called 'the infinite loop' which enables a computer to do what no other physical machine can do - to operate in perpetuity without tiring. In the same way it doesn't know exhaustion, it doesn't know when it's wrong and it can keep doing the wrong thing over and over without tiring.
Postfix keeps running even if one Postfix process dies; Windows requires that someone restarts the service.
A crash is when your competitor's program dies. When your program dies, it is an 'idiosyncrasy'.
You can't break what's broken already.
Some programming languages manage to absorb change, but withstand progress.
No opposing quotes found.