Not long ago I bought Seven Languages in Seven Weeks from the Pragmatic Bookshelf (electronic, of course ;-) with the sole aim of learning new languages I can then exploit to produce code in myriad forms and shapes. I asked in Twitter for recommendations of books that a geeky developer like me should read and
Yep, we got it. Without hesitation our suggestion of using some work time to improve our professional selves was accepted. Most parts of our discussion was spent on implementation details. We argued back and forth between fixed time slot and free placement. The end result was to go for the free placement, since you really
I’m on my winter holiday, Yay! I was thinking that I will spend most of the free time practicing my art of coding. I am not very familiar with maven, Hudson nor Sonar so I am planning to write a piece of software using all three of them. It may seem odd that something as
Every time I read an interesting book I try to usher others to at least skim the book before declining to read it. Almost every time my gentle suggestions get turned down. There are numerous reasons for not reading that book, here are the most common ones: It is work related, why would I want
Usually when an organization takes the path of an agile transformation, they have to revise the roles they used to have. Previous project managers are now product owners with new tasks and responsibilities. There are scrummasters without real power and then there are teams consisting of people with mixed backgrounds. There might even be an
I have spent countless hours thinking about personal motivation and enthusiasm and how big role they play in individual improvement. When you are enthusiastic about something you are at an excellent position to absorb as much new knowledge about that subject as possible. Use this opportunity and improve yourself. Try to take conscious steps to
Everyone has stepped into their office feeling that they would rather be somewhere else. We get mired in our daily work from time to time. You can do much by yourself with self-guidance. For example, turn the situation upside-down and think how well you can do your boring chores. Do them with excel! This does
“Release early, release often” goes the Scrum mantra. What to do when the system to be released seems to be too big for that? I have identified just two ways. Big Bang -release Small incremental releases The problem with a big bang release is that it requires a lot of synchronization. I mean a lot.