Often towards the end of the day, I wander into Umesh's office, sit down with a sigh and lament how much of my time was spent in meetings vs. writing code. It's kind of a ritual --- he typically counters with a story about some new coding fad or technology that he's having to deal with. "Old wine in new bottles" he says, and proceeds to teach me something intereresting ... why I should care about OData, how the heck "yield return" really works, or why extension methods aren't evil (still don't buy that one).
His talent for teasing out the meaning out of all the crap that churns through our industry is pretty impressive. And the good news is, he's writing down some of these lessons in a new blog called Engineer By Day. He's just getting started, but already has a couple of great posts up there. For anybody interested in complex engineering topics described in simple language --- highly recommend you check it out!
Engineer By Day