Subtitled "A little book that teaches you when to quit and when to stick" by Seth Godin. So what is the dip ? It is the strange valley after you start with something, causing that after initial quick success you will get worse before you can get better. Obstacles that you either overcome - or you quit. Seth explains that these obstacles are there for a reason - they separate those who want something badly enough from those who do not.

I've spent lot of time today reading. I am catching up with my reading stack. Between stuff I've finished was: Breaking Windows : How Bill Gates Fumbled the Future of Microsoft The impression ? Mixed feelings. Maybe I've expected something different. Lot's of details on internal politics and inner fights, not too flattering portrait of Bill G as control obsessed person with very questionable interpersonal skills. From technology perspective, very little what was both interesting and new.

As I noticed on Apple Website, the SDK for developing 3rd party applications for iPhone/Touch will be available in February. This solves the biggest problem - offline reading - because with SDK, storing a downloaded copy will be trivial. It also will most likely fix the annoying lack of updatability of calendar and add few more interesting apps. It is only matter of time until the other eBook formats will be be readable on iPod - such as CHM or PalmDoc (non-DRM-ed version).

Many good posts about programming, coding, business, aesthetics, with nice touch of wisdom, If you are into programming languages, do not miss this one, this and this. If you are more into process and management, try this and this or this. There also deeper and lighter stuff :-) As Reg says about popular bloposts One model for popular writing is that it panders to the reader's prejudices. Plain and simple. People like writing that validates them and especially their ideas.

Every software developer will tell you how frustrating it is to trace problem in your application up to the point of third party library call (jar file or .dll / .so - make your choice) - and then have to resort to trial and error exploration, because you have no source code for that particular library module. For this very reason, most developers always prefer working with libraries or toolkits that comes with source code attached - if they have a choice.