It is not a secret that I am not too fond of targets. I think they harm flexibility and hence service.
Targets are fun if you reach them: most of the time they are rewarded as a financial bonus. But if you really need to push trying to reach certain targets, they are counterproductive.
I was recently confronted with a new password policy: my password needed to be a combination of 8 to 12 characters with only numbers and letters. And the numbers were not allowed to be at the beginning or end. My solution was a combination of a standard word with my zip code. But I am not convinced that it is a good password. I will not be able to remember it easily, as it differs from all my other password.
The more you work with computers, the more passwords you generate. I have to remember so many passwords that I use a program to store most of them. It is not the best option but I can only remember so much.
Talking freely about SOA has always been a bit embarrassing. I live in The Netherlands and the acronym SOA stands for “Sexual Transmitted Disease” in Dutch. STD translates into SOA. So when I talk about SOA, I immediately know if I am talking to a techie or not. Despite all the buzz talk, SOA has not yet been as viral as expected. SOA has been around for quite some time – some even call it yet another reinvention of an old concept – but it seems very hard to get it implemented. This is mostly because we are taught not to fix something that isn’t broken and the truth is that most point-to-point connections just work. So there is no obvious need to start using a SOA.
I started a new blog (in Dutch) with my collected recipes!
