There are many good reasons why using a new library, framework, or programming language (later referred as a tool) is not worth it. However, for some reason the most common reason I hear is: We don’t have time to learn how to use it. It is easy to think that this argument is used by […] Read more

One of the misconception that is often associated with agile software development is that agile teams won’t write any technical documentation. I assume that this misconception is so common because the agile manifesto states that we should value working software over comprehensive documentation. Also, since some of us have experience from writing long technical documents […] Read more

There was a time (not so long ago) when we designed everything before we wrote any code. We gathered the requirements of our application and wrote the requirement specification. We took these requirements and designed an architecture that helped us to fulfill them. We wrote an architecture design document as a guide that we followed […] Read more

Every developer must understand two things: Architecture design is necessary. Fancy architecture diagrams don’t describe the real architecture of an application. The real architecture is found from the code that is written by developers, and if we don’t design the architecture of our application, we will end up with an application that has more than […] Read more

I have noticed that some Finnish IT professionals are complaining that being just a good employee isn’t good enough anymore. These people argue that they cannot get a job because: Their work experience isn’t worth anything because they have no experience from technology X that is hot right now. They are too old (over 40). […] Read more