It is common to talk about resources. Unfortunately what we mean is often people who we want to help us with something. A project need resources to be able to solve the task.
November 30, 2013
October 15, 2013
Ian Kelly called the System Under Test, SUT, the System Under Specification, SUS, at his session “Testing++ – Working with Spock and Geb” on Java Developer Day in Krakow.
September 30, 2013
What is a hero?
A hero in an organisation is someone who is considered to be indispensible. The organisation will not survive without this person. The hero is the only person with a specific knowledge. A hero sacrifices himself for the organisation.
July 31, 2013
I watched a presentation by Zsolt Fabok a while ago and saw a technique I hadn’t thought of before. How do you verify that a parameter is used in a simple way? Feed the method with something that usually doesn’t work and verify that something happens.
June 30, 2013
What is the problem with one hero that always solves any problem? One answer is that those who get problems solved never learn how to deal with the problem and solve them. What is the problem with this? One answer is that you build an organization where the bus count is one. One person always solves any issues and the organization doesn’t know how to do it. When this person steps out in front of a bus and doesn’t show up at work, then there is a real problem.
May 16, 2013
Do you need to change the path to a binary a Windows sevice is executing? Maybe you want to change the location of where a service is installed?
April 2, 2013
There is a big difference when teaching a large group and teaching a small group. I recently had the pleasure of teaching the same material in a few different scenarios. One of them with a large audience of about 70 participants. It took me approximately 2.5 hours to go through all slides and coding an example. Two other scenarios was with small groups with less than 10 participants. The exact same material took a little over a little over 3 hours to complete.
March 2, 2013
Kent Beck wrote a very nice book eXtreme programming explained with the subtitle “Embrace change”. But what he really want to embrace is uncertainty. What is uncertainty? It is those things that will happen but you are uncertain of. Possibly so uncertain that you haven’t even thought about them in a risk analysis. It is the very nature of uncertain things, you don’t think they ever will occur and can therefore not even think they might happen. They will therefore never turn up in a risk analysis.
This is what Agile and XP is all about. Handling uncertainty. Instead of taking long leaps, you frequently stop, inspect and adapt. You always tries to have the shortest possible feedback loop. You deliver working software and evaluate if it brings the values you expected it would bring. Then decide what to deliver next.
Inspecting and adapting doesn’t mean that you shouldn’t think and try to come up with reasonable risks that you want to prepare for. But at the same time, it doesn’t mean that you should stop and think forever about the risks and never deliver anything.
So embrace the uncertainty and make sure that the way you work support you as much as possible.
February 24, 2013
Maven is a build tool for Java. You define a project with Maven, build and test your product.
Usually you hate Maven or you love it. Before you have understood how things work, you usually hate it. If you persist, then there is a chance that you will like it.
I have met many developers that claim that Maven is either “To complicated” or “Impossible to understand”.
I have even been asked “Don’t you feel dirty using Maven?” during a session at an Agile conference. My answer was “No, why should I feel dirty for using a good tool?” This question and an opinion stated at another conference triggered me to write this. I aim to show you how Maven can solve some problems, using baby steps and starting from the simplest possible solution that could work. My goal is to write an easy to understand getting started guide. If you think I take a too large step somewhere on the way, please give feedback and tell me where I take a large step. If you think my steps are to small, then you probably already know enough about Maven so you don’t need this introduction.
January 31, 2013
Testing is all about verifying that something works as expected. What are the challenges then? There are many, one very obvious is to actually know how it should work. Another challenge is to isolate the system under test so that it is possible to know what is tested and determine if that specific part works as expected.