Suits my way of looking at things too.
The question of course is: When exactly is the last responsible moment? Usually when building software it is tempting to work with the assumption that the last responsible moment is right before I write the line of code related to the decision. Works well with the way 'agilistas' despise Big Design Up Front too.
Funny when you start to compare software development with the real life. (After all: That's what object orientation is all about, right? Modelling the real word with software representations? But let's take that at another time and come back to the subject at hand.
While I literary roamed the world in 2011 the concept of planning with regard to the "Last Responsible Moment" made the rounds on some of the mailing lists concerned with agile software development practices.
I on the other hand tried to live a 'normal life'. writing software and preparing material during the daytime, while spending the evenings with everyday pasttimes - in my case Aikido. Never mind if you have never heard of Aikido - although you might want to look it up at Wikipedia.
To cut a long story short - in the real world the latest responsible moment is not when you reach a bus stop a couple of miles of the central public transport axis of dubai, shortly after your last training buddy has left.
Especially if the area temporarily has no cell phone reception and that particular bus stop is only serviced until half an hour earlier at this time of the year (mentioned in the small print)
Post a Comment