Coupling of software is bad (maybe even all kind of coupling??)

By coupling, I mean designing software/system that a component is depends on another entity in order to function, or part of the functionality is located in another object that does not related (directly or indirectly) otherwise. Functionality should be clearly partition in a way that a component can be replaced without causing other part of the system to fail. There are many scenario that limitations and flaws are caused by this.

Software should be smart

There are bugs and there are scenarios that the system just failed (foreseeable or else), so we need defensive programming. The best defends is to design/write good software that not even getting into a bad case like this. But in case of problem does araise, the software should be self-healing (that's detect the error, report it, and take corrective action) if possible. If this route failed, it will rely on auto-recovery (ie reset) if unable to calm with the error. The worst is the software just failed and go into freefall and OoC (Out of Control).... ultimately unacceptable: just crashed

Global/Static data is bad, we should all know by now

I thought all 1st year students learnt it already. This shoud be imprinted into their brain: prevent global/static at all cost! Static data in the global scope is accessible by any software, someone can make a mistake, or change the data by bad design when it should not. There are also a chance of race condition if the static data is in multithreads environment. What if the data in the future needs to have multiple instances in the future? Use the singleton design pattern.

To help our civilization find the ET out there, I have updated my SETI@Home client with the new BOINC platform based client.

Cool.