It really was too good to be true…

I had written earlier about how online shopping does make my book purchases easy. Well, it was too good to be true anyway. I’d pre-ordered (like many others) last book in the Harry Potter series with the fond notion of getting it either on the 21st or on 22nd of July 2007. 22nd July was a Sunday when this year began, so I’d have guessed that the folks at the online bookstore factored that in when promising delivery. Today I get a mail saying “If you are not located in any of in any of the following cities : Delhi, Mumbai, Bangalore, Chennai, Kolkatta, Ahmedabad ,Cochin, Hyderabad: your book will reach latest by 24 July 2007 . All books were shipped on 21 July , however there is transit time of 2-3 days (excluding Sunday)“. It does suck big time when you cannot watch television since some m0r0n news channels are actually divulging the bits of the story and you are breathlessly awaiting the arrival of a book which now seems to be delayed all the more.

UPDATE: They claim to have been overwhelmed by over 15000 pre-ordered books, but managed to deliver it albeit a day late.

Does it work for you ?

Jack retasking can be defined as automatic re-assignment of audio jack functionality based on device type being plugged in. For example, when a microphone is plugged into a speaker jack, the system can automatically re-route the mic data to that jack. Intel says that Intel HD Audio also provides improvements that support better jack retasking. So, on your new and shiny Linux distribution, does jack retasking work ? Additionally, when you figure that it works, do you receive any notification saying Device A (where A can be speaker/mic) has been plugged in ? I’d be happy to know the results – use $SUBJECT: Jack Retasking and mail to sankarshan {dot} mukhopadhyay {at} gmail {dot} com to let me know. Chipsets which are relevant are listed here.

And then there were none…

Social networks are addictive. In most of them I am “barely” present – the profile is kind of like a pebble or a placeholder that is there on the off chance that I may meet up with some old friends. These days one such pebble has unleashed a flurry of conversations between friends long since disconnected. As it is wont to happen slowly but surely the talk comes around to one of the following topics: wives/partners/marriage, children, jobs, parents, houses/cars/material things once the novelty of talking about the “good old days” wears off. So some weeks back (stop passing snide remarks – this blog is actually a lost+found draft) we ended up talking about jobs – the job environment ie the social commune at workplace and of course the managers. On hindsight even though the representative sample size was woefully inadequate, a strange pattern emerged – [1] working in a monolithic corporate does not automatically mean that folks are happy/unhappy [2] managers are nearly completely responsible for enjoying current workplace commune [3] working from $HOME in India at least is more often than not counterproductive [4] many fear the query “what am I doing today” and thus do nothing
[2] above is kind of surprising since it is a general dogma that factors like payouts, bonuses, freebies, workmates etc among other things determine the kind of joy of work. From a sample size cutting across broad general classes like Medical, BFSI, IT and Education, 20% agreed that they had managers who “managed by walking around” and they liked talking about issues at work during the walks. Of the remaining once the concept of MBWA was explained, they contrasted with their current protocol of fixed meeting times/days and arrived that MBWA might be a good idea in the flux jobs they had. Especially since MBWA includes the element of making notes of the “hot bricks” and attempts to get these out of the way as soon as possible. What was more surprising is that only 25% of the sample have scheduled, invariant one-to-one meetings with their managers on a regular basis. The remaining just have ad-hoc interactions. Note, in cases where the layer of a {Tech|Team}Lead is between Manager and associate, the MBWA bits apply both to the manager and the Lead. This is a bad jolt actually since the first thing that collapses when a company scales (and this is most seen in startups than anyplace else) is the MBWA and effectively clear communication. Folks become too busy in work that is not ordered according to priority and talking with the team breaks down.

However what bothers me more is [4]. When I started out, one of my mentors had drilled into me that “Fear is the Key” but don’t let it cramp your style, instead use its presence to chart out new work areas and attempt new things. When I see that a large number of my friends and associates get all hot in terms of “let’s not take risks” I feel a bit unhappy. Taking risks is something about pushing the limits of one’s capacities. Sometimes some risks do border on foolhardiness and on rare moments they are pure idiocy, but just because risks would push one out of the comfort zone of a well defined role does not mean that one should not take risks. Fear of failure is not unusual – in fact it might as well be one of the natural human reactions. What I observe is the fear of success. Since if the risk is successful one would be out of the current comfortable presence and start working on making the same if not more comfort appear in the new venture. One has to fear the moment in the future when we wake up and the brain pops the question “what have you done till now ?” As the quote goes

“Ah, but a man’s reach should exceed his grasp, or what’s a heaven for?”

Books and stuff…

Finished reading A Long Way Gone – normally I am a very fast reader, but this book just holds you on to each page and makes you think over what is written. Highly recommended. Currently on the second reading of Strange Pilgrims and All Quiet on the Western Front. This does mean that my “ToRead” book list has become very short with only 3 books read to be gone through. For a month’s worth of reading it has been a nice trot.