Link Details

They missed one reason: maybe he was pairing at other developers' workstations. :-)

I thought cartoons were supposed to be funny? Pretty lame.

That story happened in my previous company in January... the idea is to show the absurd things that happen in the software industry, giving them some sense of humor.

seen it happen, though not at an individual level.
Was part of a team working on part of an application as we as a team were reprimanded for not meeting our required KLOC count for 2 months running when doing major restructuring and cleanup of existing code.
That operation ended in the codebase shrinking by something like 20 KLOC over 2 months when the company had a requirement that we have a 100 KLOC result every month.
That -20 was of the result of scrapping some 150KLOC and creating another 130 while modifying something like 200KLOC but the simple metrics system they uses never showed that.
Almost cost us our performance bonus, hadn't the project manager stepped in and got that reprimand removed.

While I agree that LOC is a terrible metric, the cartoon is about doing only two commits during the last two months. Whether your refactoring or trying to tackle a big complex problem, you should be commiting every day or two. If you are worried about messing up the main code base that is why svn and cvs have tags and branches. People who don't commit changes often can be nightmare to work with and are often in need of a reprimand. (I have been reprimanded for it before, and I deserved it).

Would you guys mind to repost your thoughts in the codecomics website?
It would be great to have this information attached to the strips as comments.
Thanks in advance!