Why is object-oriented programming often so nerve-racking?
Who knows already programming with OOP systems (object orientated programming) e.g. JAVA, C++, Flash, Object-Pascal or Visual BASIC, will also know that even smaller errors or deviations from the standard in the program structure of “OOP” (object declaration, transmission, encapsulation) can cause side effects, which are usually hard to understand for the non-computer-scientist because of their extreme complexity under the surface. Error-handlings can turn out to nerve-thrilling struggles, which many hobbyists and semi-professional developers (and even some professionals, too) often give up resigned.