Showing posts with label source control. Show all posts
Showing posts with label source control. Show all posts

Thursday, September 20, 2012

We’ll be emailing our code to you at noon and four.

Support said they’re populating the pager list based on who’s touched the code in the last six months. We’ve elected you to be the only person with check in rights

This reminds me of stories about people gaming bug fixing for earning extra money, gaming lines of code to skew metrics about performance (counting lines to determine performance is idiotic. It's the surest way to enforce { } on separate lines, if that's your preference.  And if your line counter is smart enough to ignore those, there are ways, culminating in just bad, do-nothing, code), and any number of policies that don't result in the behavior expected.  I don't even think developers game it for reward in all cases, sometimes it's just to see what will happen.

For example, we had a revolving door on the back of our building with a pass access system.  The first weeks it was in, developers were back there trying to determine if someone could get in while someone else was going out, if two people could get in at the same time, if you could reach back and swipe for the next person as you entered, and numerous other edge cases.  The end result was not changes to the revolving door to fix what they found, but an order from on high to knock it the hell off.

Title: We’ll be emailing our code to you at noon and four.
Snarky: Support said they’re populating the pager list based on who’s touched the code in the last six months. We’ve elected you to be the only person with check in rights.

Thursday, June 21, 2012

They must have put that in place before the TFS checkin policy on changeset comments.

Snarky: They must have put that in place before the TFS checkin policy on changeset comments.

This is one of the Snarkies based on a real life incident.  What confuses me is that you'd want to prevent people from putting the word "Hack" in a checkin comment.  Then they're just going to make a hack and hide it under a less obvious name, like "Date modification requested by business in under one hour".  We did a similar Snarky around TODO and HACK before.  This is just another facet of the same bit of humor.

By the way, if you've never heard about Hackety Hack before, it's an IDE for teaching kids how to code.  It's related to Shoes, which I've played with before teaching my daughter how to code.

"The two largest similar projects are Scratch and Alice. There are two major differences: Both of these projects use a graphical programming language based on the concept of "blocks," but Hackety Hack teaches Ruby. Both Scratch and Alice are university projects out of MIT and CMU, respectively, and Hackety Hack has no university affiliation."

Title: They must have put that in place before the TFS checkin policy on changeset comments.
Snarky: Whose changeset has the checkin comment "Hackity Hack Hack"?