There are probably a lot of people who have read books like "Getting Things Done", and alike, which aim to be more effective at work and become more productive. Although these books all have valid points and are all a way to be more effective, most of these books aim for the 'wrong' goal.  These books aim to be more productive/effective so that you can do more work and make your boss happy. But this book turns it around and says: "Be more productive so you can do your work in less time and have more spare time!". Now that's a way to get someone motivated! Be more effective/efficient and in return you have more spare time to do whatever you like! The book just takes about every point made in all those other books, but converts them into a profit for You, the reader. Not your boss or your company! And this is why this book gives you the feeling you already know the points made and yet be totally different!

The fun part about the book is that you can implement the ideas as you are reading them. When you're not reading, you are contemplating on where you can apply the things you have just read... And it pays off instantly! Just a few of those simple things; Email is a distracting medium. Yet everybody believes it is crucial to your work, so you have it running in the background. But the fun part is. It almost never is actually crucial! Tim explains he only reads his email 1 time a week! Now that's ridiculous for us mere mortals. So he suggests an alternative (I don't know if he actually does, but I do this now on a daily basis and if it is not in the book I based it on his theory) you open your email client just twice a day. One time at 12:00 and one time at 17:00 and try and stick to it. And while you're at it, create a mind block for yourself that you don't open any 'fun' web pages as well and close your instant messaging apps.

With the mailbox closed, no fun pages open in the background, and no IM, there is nothing that can disturb you in your work. Your work gets a speed boost, and before you know it you have your daily tasks 75% complete by the time it is 12:00! Now you open your mailbox, check your mail, and respond to the mail. In the first day I applied this technique, I realized that the important mails could be counted on just one hand. And no one was mad about the fact that I replied passed 12:00.  And of course, there are moments you need your mail client before 12:00, say when you work on something and you receive the data needed to continue working, these are exceptions. Not the rule! And in these cases it is fine to open your client.

After lunch I continued my work and was done at about 15:00. Then I picked up "The 4-hour Workweek" again and continued reading till 17:00 or so. Had diner, and I had a whole evening to do whatever I wanted.

So the result after this little experiment?

• A highly efficient morning where I had completed 75% of what I had planned to do for the day.
• A great feeling of accomplishment for the day (which in turn makes you motivated and more productive)
• Done working at 15:00 (instead of 17:00)
• Had time to read the book
• Still had time to do relaxing things in the evening

You can see I was actually able to step back from work and live like I want to instead of the continuous stream of tasks and chores which feels like it takes forever and gobbles up your entire day. And after you're done working, it still feels like you haven't done anything useful. I felt liberated and alive!

So to conclude, what's great about being this efficient is that you can get all the time you need for yourself. You can do whatever you want and keep your boss, or clients happy! Just make sure you do your work as efficient as possible and you'll find out you receive a lot of extra time in return to live again.

For the people reading this, I try you suggest this little experiment as well. If it works, I would suggest you buy the book and read it!

Leave me a comment if you tried and/or what you thought of it.

A few months ago I came across an advert of "Star Wars in Concert" on one of the online forums which I regularly visit. As a Star Wars and John Williams fan I was immediately interested in this event.

What is it? A music event? A movie? A musical? A classical recital? It has everything of the above but at the same time you can not say it is all of the above.

Is it a music event?

Yes; because it is clearly an on stage event in which a group of musicians give a music show.

No; because it doesn't give you the feel of a live on-stage music event as you probably have visited in the past

Is it a movie?

Yes; because it tells the "Star Wars" story from start (ep1) to finish (ep6).

No; because it doesn't give you the experience a movie gives. You could say you get the "bullet points" from the movie, but you are not enveloped in the story.

Is it a musical?

Yes; because you get a story told in a musical-ish format.

No; because it is not so in the way you expect a musical to be

Is it a classical recital?

Yes; because a grand orchestra plays the well known StarWars music.

No; because it is all amplified and presented in a grotesque and entertaining way which removes the clarity and fidelity a classical recital can give

So, what the hell is it?! I would say it is a superb experience of the StarWars classical music presented in a way that is entertaining for a broad group of people. It won't go to the extremes in either of the above, but the combination of them all make it an epic event which is, at some times, really breath taking! The interaction of music, video and light is amazing! Yes, it is StarWars and yes you probably have to be a Star Wars fan to really appreciate it all. But; WOW! It was a great experience! And I'm very glad I went too see it!!

So there aren't any downsides to this event?

Well, in my opinion, there is one downside. Because the show is "entertainment-driven" and it is presented to a large audience (aprox. 12.000 people) , the sound is amplified. This amplification has a negative influence on the music. Some parts (mostly trumpet parts) where less amplified and sounded great. But overall it can't be compared with the acoustics and clarity of sound which is produced at a classical recital. My hopes were just a tad higher.

But, to conclude, once I got passed this little downside (which was after about 10 minutes or so) the whole event can be concluded in 2 words: Totally Awesome!

If you're a fan of Star Wars and it's music, this is a Must See!

I came across this movie and was intrigued by the title, its rating on IMDB and a short excerpt of a user review in which the person in question said it made him a bit like when watching "Close Encounters of the Third Kind". These where enough reasons for me to take the plunge and watch the movie.

The first 15 minutes you (well, at leas I did) feel like: "what the hell is this about?". The movie sure doesn't look like it was made in 2007. But bare with the movie for a minute and you will find it intrigues you in more ways than you can think of. It is kind of hard describing the movie without giving away what the movie is about and where it is heading, so I'll head to describing some things about the characters in the movie.

The thing that balances this movie perfectly is the fact that the main characters can all be considered as experts in their field of work. And because of these expertise (which is not explicitly mentioned in the movie) everything becomes plausible and everything makes sense. Just in moments where you think "ey, what is that about?" it is backed by one of them explaining the ins and outs of it.

When you're 30 minutes into the movie you will be really eager to know how the story will continue and where it will lead to.

I don't want to spoil too much of the movie, but after you have watched the movie, you will surely know you haven't thrown away 90 minutes of your life. I'll bet you will be thinking about the movie for a while and consider the implications of what you have experienced. You won't probably consider "what if this movie was real" but I do know that there will be moments that you will remember  about certain aspects of the movie and think "Wow, it could be true.. And what if that was true... Well, then....".

Bottom line:

If you're a movie lover who needs to be entertained by CGI and Action: don't watch this movie

If you like being surprised once in a while, I can highly recommend watching this movie!

Verdict: 8.5

A while ago I posted about some wild idea's where you could go around the SMTP block of your ISP by running your mail through another (non blocked) mailserver and forward it to your mailserver which is running on a different port. Today, we go beta with a service which makes this possible for everyone!

The road from 'Proof of Concept' to 'Finished Product' was, as always,  a bit longer than expected. First of all I switched from developing in PHP to Django (to expand my knowledge) and secondly, there are some pitfalls when you want to make this kind of service for more people than just yourself.

For the people who don't know what the fuzz is all about, a short rundown. There are ISP's in the world which believe that there are a lot of people who don't know what they are doing. So when those people run a mailserver chances are rather large that they don't configure their mailserver correctly, and they become an open-relay and thus, open for spammers to be used as spamming machine.

Although these ISP's are in their right to do so, we believe the clients (and especially the business clients) should have the chance to be able to run a mailserver if they completely understand the risks.

By default (and according to everyone and everything on the internet) a mailserver listens on port 25 for incoming mail messages. Because this is the default, ISP's block this port (incoming and/or outgoing).

Fortunately we have thought up a way around the ISP's who are actively blocking port 25.

As a lot of people (mostly unix administrators) know, you can run a mailserver on a different port than port 25, say port 26. However, the email world does not know this. So when a mailserver (for example the google mailserver) wants to mail to you, it tries to connect to port 25. And so you have to find a way to let the other mailserver think you are on port 26. But this can't be done easily and without your ISP.

It can be done via our new service: RerouteMAIL. The trick is that we listen on port 25. And then relay the incoming message to your mailserver running on port 26!

And the best part is, we have a fee free version which everyone can use, a hassle free registration, and no questions asked.

If you are interested or curious please have a look at: www.reroutemail.com or leave a comment on this blog!

I have been developing (web)applications for some time now. And although some people might consider the 8 years as being "new", I consider it long enough to be able to point out some important reasons to why projects fail.

Although it was really really hard, I tried to make up a top 10 list of things that can (and have gone!) wrong. And because if I have experienced these problems. You can bet others (you?) have and will too! So, here goes. My top 10 reasons:

10. Not all things have been taken into account

It sounds too obvious to be true. But it is. When people start a project they mostly don't take time to step back for a moment and consider the implications of the project. I haven't been in a meeting which went like this: "Hey! Is this really as easy as it sounds? Or are there hidden problems lying low and ready to jump at us when we least expect it!?". Most of the time people are too excited about the project and feel like they can take on the world! And they realize halfway through the project (if you're lucky!) that they didn't realize feature X would take as much time as it did! And so, their deadline creeps up on them and BAM... The deadline can not be met.

9. It's a rush job!

How many times haven't I heard this one: "I know it's a rush job! And we are aware of it!". Only to hear a few weeks later: "But how is it possible that this bug exists?! We just CAN'T have these kind of bugs!". And most of the times these bugs only surface after it has gone live for a few days.

8. There are no milestones

No proper milestones have been set for a project. And this is not good. Not for you, nor for the customer! If you don't have milestones, you have no way of measuring your progress. And even when you think you are on the right course, you can never know for sure. More so, you cant update your client (or customer) on the progress. Because you just don't know!

6. The customer lacks technical insight/knowledge

It can be a real problem when the customer (or your manager) is not as technically endowed (on this subject) as you are. But realize it is as much of a problem for them as it is for you! They wonder why you take so long to create feature X which seemed soooo easy to them. The biggest problem is not their perception of complexity, because this you can explain. The biggest problem is that they will not be able to explain their wishes to you in detail enough so you can make a correct estimate on the project length.

5. Ad-Hoc projects / Prolonged FireFighting Mode

Your morning at work starts and your manager runs into the room yelling and screaming: "WOEAAAH!!!!!! WE NEEEEEEEEED BUG 1337 FIXED RIGHT NOW!!!!". The sky has fallen! All customers have ran off and the cash has stopped pouring into the bank account of the company! All because of this bug! Or... so your manager led you to believe! You rush yourself to your computer and work long and hard to fix the bug as soon as possible! Finally! the bug is fixed! And you can continue your daily work on bug 1884. But then, after lunch, it starts again: "AHAHAAAAAAAA!!!!! THERE IS A PROBLEM WITH X AND Y! THIS CAN'T BE HAPPENING!" and of course you need to fix it right away! This scenario continues some time.. Until at the end of the day, the things you had to work on that day didn't finish. A day passes by and you fix some "MUST BE FIXED NOW" bugs until one moment: "WOEAAAAH! WE NEED BUG 1884 FIXED!! AND IT SHOULD HAVE BEEN FIXED 2 DAYS AGO!". And the circle is complete... Because you were fixing bugs which seemed critical, you are not able to work on your daily routines. Which in turn, turn out to be "need to be fixed now"-bugs eventually.

The biggest problem with this is that you will always keep a feeling of behing behind all the time. And escaping from this vicious circle can be very hard. Although you can't prevent this problem directly, you can discus the matter before fixing the "need to be fixed now"-bug. Ask your manager "Is this 1337 bug really more important than bug 1884? And if so, are you okay with delaying 1884?". This will probably make your manager think the request over and it will allow you to fall back on the conversation when 1884 became a real "need to be fixed now"-bug

4. Communication problems (or lack of communication) "

It happens quite a lot. A salesperson has promised feature X to customer Y and has told the Project Manager to make it happen. It slips the mind of the PM and the salesperson didn't remind the PM about the feature. Until the time approaches that it should be delivered to the customer and the salesperson asks the PM about this. "Damn!". The PM wraps up some developers and a technical lead and you'll hear something like: "We have promised the customer a month ago we have feature X in the release for the end of this week so build it and build it right!".

Everybody should know this is a recipe for disaster. You just can't build a feature in a week (or less)! No arguments. You just can't!

3. Total lack of specifications

You think you have done everything right. You talked to the customer, written things down, had the customer sign the document on what to deliver. But you don't write the specs. You didn't work out the details of the features and think you can manage it along the way.

Just Face it! In the larger projects (even if it is still a one man job) it is almost impossible to do things right the first time. And unless you have calculated a lot of refactor time (and I really mean a lot!) into your project, your deadline's will slip. And you will have an unhappy customer. Just take your requirements and work them out. Just make small mock-up of what you are going to create. Write down some flows. And be sure to show them to your customer and have them comment on them.

You don't have to create full detailed Interaction Designs. Work out all the Use Case Scenario's and write pseudo code for every function. Just make sure the outlines are there and have them approved or reviewed.

2. A Sales person determines the deadlines without consulting programmers

This I hate the most!

Operations come's to you and says: "Yeah we have to create X, and it has to be completed before end of the week!"

"Que?"

Damn, they have done it again! They promised stuff to the customer, and we don't even know if it is technically possible to do so! And even if it is possible, we don't know if we can have it production ready in that time...They haven't even discussed it with the PM or a TL.

1. There are no, or incomplete, requirements

This one is also very classic, and very easy to make. "We need a program that can do this and do that, <explanation of what and how etc>.. can you make it?". Sure you can! And there you go happily programming and creating what the customer asked. And after some hard weeks of working and finally delivering the program, you receive the following reply: "Ah, yes.. But... This is not how we wanted it. It should work like this and that!". So you reply: "But.. Why didn't you say so?". And the customer replies: "Well, er, it is  obvious that it should work that way!". And there you go.. Throwing away a big part of the program, starting over again..

And the biggest problem is, there is really no one to blame! It's just that people won't exactly, with 100% certainty, know what the other person really means or thinks. So, even when you have requirements, it is quite hard to say "Well we decided this and that and I made it that way. So, its your fault!" because with that attitude you will only get your customer mad and create an atmosphere in which you can't work.

The solution? Make sure you agree on what is required of the project, and make sure you write them down. Have your customer specify what the program has to do to make it acceptable for him. And finally make sure you live the project as much as your customer does!

Well there they are! My list of reasons why a development project can and will fail. They are based on my personal experience in the passed years.

Have you experienced these reasons as well? Or have experienced others? Leave a comment!

I would like to wish everyone the very best for 2010! I hope everyone will have a great, healthy and prosperous year!

I am looking forward to hearing from all of you some time in the future!

The native language of the movie is German. So it is some getting used to for some people. For me it took me about 10 minutes or so and after that it didn't bother me anymore. Although the movie is shot in 2001, you can really sense it is a dated setting. In addition the dialog and scenes are set up in a way which gave me a strange feeling. A bit of a "Eh.. what is this about?" feeling. Although a bit strange it is totally appropriate and gets you into the story even more.

There are no special effects, blazing fire's, cutting edge sound effects and booming subwoofers in this movie. Instead it has sound effects which gives you a suspicious feeling and makes you want to hold your breath from time to time in anticipation of something happening.

The story is told in an a-typical way. It is told with some occasional unannounced flash backs which, the first few times, feels like you are missing something. Truth be told, after about 40 minutes I felt as if it took forever to get the story up and running. I even had a moment where I was thinking "Im gonna stop, go to bed, and watch it tomorrow night!". However I didn't turn it off as I was rather curious to find out how the story continues. Luckily the pace picked up and there was progression in the story. And from that moment the story totally grabbed me and dragged me right into the movie. I felt compassion and felt connected to the characters in the movie. You could feel what they where feeling. Their emotions, their reactions, their commitments. I felt anger, hatred! I wanted to go in there and punch him in the face!  AAarg!!!!!

In those moments I didn't realize it, but after the movie ended I found out that the story was built in such a great a way that I slowly, unconsciously and without really noticing it, bonded with the characters. And because of that the movie made an even bigger impression on me.

The strange story telling, the unexpected connection and the great performances in this movie left a lasting impression!

A recommendation for everyone who wants to see something else from time to time. But be warned, it is not an action movie.

I don't wanna give it an 8 because it felt a bit too strange from time to time

So I'll give it a 7.5!

I really had no idea what I was getting in to watching 9. A SciFi movie alright. And a rather short one, as it only lasted 90 minutes or so. From the start the setting was clear. A rather grim setting which is accompanied with great animation. To me it gave the same feeling as I felt when watching Wall-E, when he is working on earth. Silent and alone...

But that soon changed, only a few minutes into the movie the pace picks up and you have the feeling you are left behind in terms of the story. Things are happening, but you don't really know what or why. At that moment I was curious. And after a shock moment, I thought to myself: "Yes. This will probably be a great movie!". But I was kind of wrong, at least, in my opinion.

The drive of the characters is not really clear. You can guess but can never know for sure. The movie keeps you in the dark. Normally this is not a problem at all. But because I was unable to connect with the movie on any level, it was kind of annoying.

Only somewhere at the very end I had  a feeling  of a connection (although very small) with the characters. And when the movie actually ended, it left me with mixed feelings. Sure the movie was entertaining. And sure it was intriguing. But it never really caught my attention. Therefor I was kind of relieved when the movie ended.

I was glad I watched the movie! It sure has things which justify the 7.1 on IMDB. But for me, the overall feeling of the movie was just a tad off.

Sound wise everything is great. Lot's of use of the LFE in a correct way (I never had the feeling it was overdone). And the music was done rather nicely. Speech was a bit different. Sometimes I had the feeling the dubbing was a bit off. It just didn't feel like the voices where appropriate for the (animated) characters.

I wouldn't want to mis this movie, but as a final score I give it a solid 6.

Now although this is true, the problem lies where you can't keep track of what you owe who, or who owes you what. And although you know it's okay, it just doesn't feel right. Especially when it concerns larger amounts. For example, you go on vacation as a group. Decide that everyone will pay amount X as a money stash for group activities. But you know it is a matter of time before the plan becomes a bust. Eventually someone forgot his card and could not make a withdrawl. The account was empty sooner than expected. Etc. etc. In the end person X has deposited €400 person Y €600 and peson z only €200 because of whatever reason.

Now I have, on multiple occasions, decided to make a nice little Excel sheet which can handle these kind of problems. You enter the money you have spent (its a friend case so you trust everyone supplies accurate numbers) of each of the members, and it calculates neatly what the average amount spent is, and you can see who owes what to whom. Further, if person Z afterwards gave person X some money for something else, it is handy that these numbers can be specified too. So it will always reflect who has already settled his debt and who hasn't. The biggest problem is you have to manually keep track of changes. If someone pays somebody (partially or full), and didnt notify me, I can't keep track of the changes. And so it is a matter of time before it is not accurate anymore so you can't rely on it.

Because I (we) have these problems. I'd think I'm not the only one! So I think about making some simple application which can handle these kinds of troubles. Attach a mail service to it so people can easyly be reminded of his debts or request for information. Combine this with some type of grouping of friends and you have a centralised application to handle all current and future money oweing problems without worrying about who paid who (or didnt).

So, today started as a slow day. I couldn't get myself to doing something really usefull, so I decided to have a look at my blog and spice it up a little. But when I was tinkering around with it I soon realised that I had to invest a lot of time to get it working correctly with everything WordPress supports. And even if I got it working, the design wasn't my best design. So that design had to be done too!

After a while I decided it was not the way to go. And I went clicking through the "featured themes" of the WordPress appearence section and found a new design for my blog which kind of suits what I was looking for. A few minutes later it was up and running, and I was happy again

Sure it has some quircks, but overall it saves me time.