A Fool with a Tool is still a Fool

cover-java-akturll-4-2016Java aktuell Ausgabe 4 – 2016

In the last several years, the effort to increase the quality in software projects has spent more attention to testing {1}. But the repeating of continuous success stories isn’t naturalness. Stringent and effective management of all available resources was and remains essential for reproducible results.

Article Download (de): 2016-04-java-aktuell-a-fool-with-a-tool-is-still-a-fool

It isn’t a secret, many IT Projects in this time can’t finished in a successful way. Off course, with all the new methodologies and tools, who developed during the last decade, we could get the idea all the problems of developing software are solved.  But if you take a deep look inside actual projects your impression will be changed. Companies tried to fix their problems with new tools. Often, all the efforts finished in a resignation of the staff. Typically, the solution becomes to a heavy weighted time thief with a lot of self-administration. The euphoria in the beginning between the involved persons, to play with new tools, changed typical very fast to rejection of usage. The reason of this behavior is a missing benefit in the work.  It’s not wondering that experienced staff mostly skeptical for new tool. They will usage when they can see that a successful usage inside the company is possible. For all the reasons the editor choose as title the provoking cite of Gardy Bloch, Co-founder of UML.

Not seldom, companies spend to less attention for a balanced infrastructure. Also the maintenance of existing fragments get shifted for some reasons. The management prefers to play with the news trends to catch more clients. And clients choose companies who have a giant list of buzzwords. But remember back to the 1970 ties, Tom De Marco [2] go it “people do projects”.


  1. Software Quality Report 2015 from CupGemini
  2. Tom De Marco, Peopleware, 3rd. Ed., Pearson Education, 2013, ISBN 9780133440713
  3. Scrum
  4. Prince2
  5. Kanban
  6. Johannes Siderleben, Softwaretechnik – Praxiswissen für Softwareingenieure, Hanser, 2003, ISBN 3-446-21843-2
  7. HS Merseburg, Studiengang: Technische Redaktion
  8. Robert C. Martin, Clean Code – A Handbook of Agile. Software Craftsmanship, Pearson Education, 2009, ISBN 0-13-235088-2
  9. Joshua Bloch, Effective Java 2nd Ed, Addison Wesley, 2008, ISBN-13: 978-0-321-35668-0
  10. D. Boswell & T. Foucher, The Art of Readable Code, O’Reilly, 2012, ISBN: 978-0-596-80229-5
  11. Liferay Ticketsystem
  12. GeoServer Projekt Management
  13. T. J. McCabe, 1976, A Complexity Measure, IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. SE-2, NO.4
  14. CodeCity Webseite

Über ElmarDott

Build-, Configuration- & Release Manager (Freelancer) Expert in Enterprise (WEB) Applications + Project Manager + Consultant + Writer + Speaker + Trainer +
Dieser Beitrag wurde unter Diaries in digital, Themes abgelegt und mit verschlagwortet. Setze ein Lesezeichen auf den Permalink.

Kommentar verfassen

Trage deine Daten unten ein oder klicke ein Icon um dich einzuloggen:


Du kommentierst mit Deinem WordPress.com-Konto. Abmelden /  Ändern )

Google Foto

Du kommentierst mit Deinem Google-Konto. Abmelden /  Ändern )


Du kommentierst mit Deinem Twitter-Konto. Abmelden /  Ändern )


Du kommentierst mit Deinem Facebook-Konto. Abmelden /  Ändern )

Verbinde mit %s