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
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
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
This week I read a blog post titled Where is the Foreman by Robert "Uncle Bob" Martin. It made me think. Uncle Bob suggests that a software development team should have a foreman who: He'd make sure everything was done, done right, and done on time.
A daily stand-up meeting is an essential part of agile software development. It is a meeting which takes place at the same place and time every working day. The agenda of this meeting is simple. Each team member must answer to three question: What
We have just started a new project to a customer who sells widgets. This customer is the leading widget provider of the whole world so the project can either make or break us. The project uses agile methods, and the Product Owner has come to talk