Yet another in my series of critiques of my coworkers.
Greg is a true asset to the timing team. He is an excellent programmer, and unlike me, he understands the core timing and EDA infrastructure well. He agreed to debug a problem that we were having last night. In this business people draw up boundaries, assign blame and are rarely willing to help. Greg in sharp contrast gets in, gets his hands dirty, and has a positive upbeat attitude with a slight sardonic overtone (he likes to mimic his coworkers). I went home at like 8:30pm, seeing that there was no more than I could do. When I got into work today I found out that Greg and Alex had solved the problem (which, to my surprise actually wasn't in my code after all). I called Greg with the cover story that I was finding out what I needed to run with the fix (although I already knew), but really with the intent of thanking him for his hard work. To which he responded: don't mention it; that was a fun one.
Update: This entry was about Greg as a cricket fan.
Greg is a true asset to the timing team. He is an excellent programmer, and unlike me, he understands the core timing and EDA infrastructure well. He agreed to debug a problem that we were having last night. In this business people draw up boundaries, assign blame and are rarely willing to help. Greg in sharp contrast gets in, gets his hands dirty, and has a positive upbeat attitude with a slight sardonic overtone (he likes to mimic his coworkers). I went home at like 8:30pm, seeing that there was no more than I could do. When I got into work today I found out that Greg and Alex had solved the problem (which, to my surprise actually wasn't in my code after all). I called Greg with the cover story that I was finding out what I needed to run with the fix (although I already knew), but really with the intent of thanking him for his hard work. To which he responded: don't mention it; that was a fun one.
Update: This entry was about Greg as a cricket fan.