July 06, 2012

Getting frustrated with IDE´s

Working with eclipse never seemed so cumbersome. A bunch of plugins which seem to behave in an arbitrary and non comprehensible way. It´s even getting worse from release to release and installation. Is there something better?
Along my career I used several IDE´s. Starting from old DOS txt file editing to current eclipse or myeclipse IDE:
  • DOS console text file editing. 
  • WJed text file editing with syntax highlighting.
  • JBuilder IDE.
  • Eclipse 2.x  until Indigo.
Sure, demands are getting complex:
  • Versionmanagement. (Subversion Plugin)
  • Build-Management. (Maven Plugin)
  • Faceted Projects (Web application, EE applications, Persistence, etc.)
  • Annotations (Hibernate,JAXB,Dozer tools plugin)
But, I begin to doubt the eclipse implementation. Eclipse costs me dearly. Eclipse uses too much time for configuration and reconfiguration. Worse; Sometimes the workspace "breaks-down" even irreparable.

Yes, Eclipse is free. No, I don´t like it anymore. I am looking for alternatives. The first try of IntelliJ already made me think:
  1. Is the eclipse IDE at its final end when it comes to productivity? 
  2. Should we waste production time and efficiency for a free tool? 
I´m ready for a change, what about you?

June 11, 2012

Quick-Learning Programming Languages

Web tutorials for several programming languages. Can be performed online without any installation. It's fun and it certainly shares some enlightenment:

June 05, 2012

Processes in Software Development

What you should have implemented:
  • Continuous Integration
  • Configuration Mmanagement
  • Test Driven Development (TDD)
  • Documentation
  • Build Management
  • Ticket-/Issue/Taskmanagement
  • Version Management
  • Code Review

What You Should Know As A Software Professional

Have you ever wondered what you should know to name yourself a software developer? From the book Clean Coder:

  • Design patterns. You ought to be able to describe all 24 patterns in the GOF book and have working knowledge of many of the patterns in the POSA books.
  • Design principles. You should know the SOLID principles and have a good understanding of the component principles.
  • Methods. You should understand XP, Scrum, Lean, Kanban, Waterfall, Structured Analysis, and Structured Design.
  • Disciplines. You should practise TDD, Object-Oriented design, Structured Programming, Continuous Integration, and Pair Programming.
  • Artifacts: You should know how to use: UML, DFDs, Structure Charts, Petri Nets, State Transition Diagrams and Tables, flow charts, and decision tables.
Sounds pretty much but distributed in a 20 year career its a pretty reasonable career plan. What's harder:
  1. Being able to apply the knowledge in your local work environment.
  2. Being able to remember it. I usually tend to forget most design patterns in a matter of months.

February 22, 2012



I encounter the word "innovation" more and more often. Where does it comes from? Who propagates this term currently?

Please, bear in mind: Innovation is a necessity, no solution for problems!

Only introduce and define innovation in a healthy IT environment.