Weitere Kapitel dieses Buchs durch Wischen aufrufen
The compulsive nature of programming has long been recognized. It is not, however, the addicts that are the problem; it is the less extreme manifestations in virtually all programmers that undermine proper IT system design and development. The majority of these afflicted persons are not building IT systems from scratch; they are maintaining existent systems – a distinction that severely aggravates all the existing difficulties. Effective maintenance is based on program understanding and this is facilitated by well-structured systems, and support from software tools, such as editors. One of the reasons for the prevalence of maintenance is that IT systems represent too big a commitment to organizational infrastructure to abandon, so they are maintained well beyond their proper life span. These long-used IT systems, termed legacy systems, introduce further difficulties, such as (apparently) dead code. Even with a large IT system to be constructed from scratch, the model programmer will eventually be drawn into grappling with an unmanageable system. The essential difference between the happy hacker and the sober and well-disciplined programmer is the speed with which an IT system becomes unmanageable, and the extent of the chaos generated (which is often manifest in an excessive need for testing and debugging).
Bitte loggen Sie sich ein, um Zugang zu diesem Inhalt zu erhalten
Sie möchten Zugang zu diesem Inhalt erhalten? Dann informieren Sie sich jetzt über unsere Produkte:
- Programming with Flair
- Springer London
- Chapter 13
Neuer Inhalt/© ITandMEDIA, Best Practices für die Mitarbeiter-Partizipation in der Produktentwicklung/© astrosystem | stock.adobe.com