Bug on bug

while sending a patch to pidgin, I came across these two cutting edge -- next generation bugs. Smart ones, intelligent. Have a look ---

What the hell Ron Paul has to do with pidgin ??

And this is classic one. When I give you the best of juice from the most rare tree of the garden, they came back and say -- hey ya actually now I am used to others and like it more.

There were long discussions and numerous request on pidgin to provide "Escape' as shortcut key for closing a conversation (through UI). After sometime, they finally pulled that in 2.4.2 release.

But then someone came up with this bug: God knows what was his intenti... or may be God doesn't know.

Adieu ...

jab we chat

Guess it has started infected the blood and symptom are very much visible now as this one.

May be we take a break, get a blood transplantation -- 'n' I don't mind replace it with beer for few hours!!

Adieu ...

WTF

Last weekend, I thought I did well enough to survive to come office after being hit by some crappy internet experience. And when I thought I escaped, I caught up by traffic police.

Not much harm though. 100 bucks and it was over !!!
So here are few classic one's I faced last weekend:

I guess yahoo messenger has forgot its own address to download full messenger.


Yes, I need to remember that. Wish they should say "Remember to remember to remember your password!

Never thought there are so many. In the next version they might have two drop down option as select gender 1. Guy & 2. Male!!

How many cats do you see. And how many letters with cat??

And the most classic one

I think their idea for confirmation code is to save from those who cann't write automated scripts for arithmetical expression. A neck to neck battle with this classic.

Grr .... Guess I need a another break.

Retention plan ...

Did you check all the papers before signing? ;-)


Update 12:37 PM: (On the other side)
Found this in one of the resume

Deleting coments

I hope you already know how to delete comments from your post. That makes sense on analogy with human communication .

The other day I was trying to delete a comment (some casual one's) which I posted on someone's blog. Surprisingly to me, my comment got deleted instantly. You may find it useful, but my instinct that its a basic use case problem.

1) Making a analogy with man-2-man communication, deleting a comment is like taking your word back, like say "Nope, I don't want that". But it depends how others react. Some say "Whatever, mark your word", others say "Its okay". So point is when I delete my posted comment, it should send a notification to author for confirmation, cause once you post a comments, words belongs to post. You have control until you post.

2) Deleting immediately can make the complete comments thread senseless. Confirmation to author can help in reducing this. For the least, author may wish to remove the comments that are related to "to-be-deleted" one.

3) Taking about blogger, deleting a comments leaves a message. Something like "Post is deleted by author". That's really ugly.

What's you say ??

Now I need to look for ways to repost my comment at the same place :(

[Yeah, no liner in this post, now you know its not easy ;-) ]

Added at 11:47 PM:
And blogger doesn't even say who has deleted that message!!

Three reason why scrum sucks!

"No process is best. You need to find the lesser devil."

Actually there are many. (Title fits that well to pass on ...)

1. Stand up meetings

1. Doesn't work out. Those who don't want to do, will never do it. Those who will, will always.
2. More wasted time. One person each day for 15 min (however I didn't see anyone of them end in 15 min) for 7 people is more than one man day. Take average case of 30 min = 2 productive days lost.
   
3. Breaks work flow. We already have so many obstacles which breaks work flow. Why another ?
   

2. Three questions

Doesn't help. I can bluff them all along. Take me down to hell, but you would never be able to prove me wrong ....... that I'm bluffing.
"Yesterday I was investigating, today I will continue, if that works, will use it tomorrow"

3. More time in meeting & documents
Stand up meeting, scrum of scrum, follow up, impediments, version one, burn down chart .... keep adding.

At first they may sound useful, but we need to solve things than endless debatable topic. Many of above said ends up in that. Mean you catch any in India for a debate on Indian cricket future over a coffee. I can guarantee that you can drink all in the world but will never be able to end the debate. Apart from that, they makes us irresponsible. Take the example of impediments, you may solve many of them, but people just don't, they just report it.

Remember each meeting take more time than meeting time. Every meeting takes at least 10 more minutes than meeting.
Those who are working on scrum can answer this better: How time you actually spend on your task out of total time you spent scrumming !?!

4. Working at one thing at a time. (Independent sprint)
There are lot full of engineer who can do multiple at same time. Most of time you will find task which can better be executed in parallel. Take this one:
You have a task to write API for logging messages; & log messages for another module. You can do better in parallel. Anything can logically be divided as independent and vise versa.

5. Hierarchy
If you haven't use it wisely, you can end up screwing things more than it offer!
Scrum Master, Business analyst, Product manager, Project manager, manager, second line manager, tech leads -- & the engineer! So much to say.

6. No coach
Adopting any process without a coach is more harmful than a soccer team without a coach. At least team knowns how to play.

7. Last but not the least ..
Takes away your freedom to choose whom to answer!

'I don't mind if you don't agree with me, One day you will"