I used to do that, but now I try not too because I look at it like this....
"[Company] are paying for the code, they own it. Although it's nice that they would have to come to me and I can charge what I want 'cus they'd be desporate... it's a bit like getting a builder in to paint your living room and he choosing a colour that only he can supply, even though you're the one paying for the paint".

Sometimes I can't help it, like I made a short function to do something (won't bore you with the details), and I called it the SQLCodeSelectStringCreator, which makes sense to people who know what code is, but I had to type that out 30 odd times so I just called it "SSC" (the 'SQL Code' bit being ignored), which means that nobody outside of my head would know what that does without looking at that function.

The trouble is, when Developer 2 comes along, they'd ask me what on earth that does, which means it takes more time explaining it.
( G/PP 💩💩💩💩💩&#128, Sat 30 Oct 2010, 12:11, 1 reply, 15 years ago)

Good analogy.
The other month I refused to pay a contractor who finished a job, left it working, and sent me the code. It had no words on it at all. I had written in the specification that a description of the code was required. His reposte that "it works, doesn't it?" cut no ice with me.
( Bartleby A dead man on vacation, Sat 30 Oct 2010, 12:17, Reply)