Skip to main content

Always Put Your Name on Your Work

Last week I got an e-mail from a manager.  “I saw your name on some source code.  Nice job.  Here is some information that might interest you.”  Sweet.  By just  typing my name, I got information I needed, plus I have someone thinking nice things about me.  If you do good work, put your name on it.  If you do not do good work, well, you can stop reading right now.

Early in my career, I started adding my name to everything I created. Ever since, new acquaintances would comment, “Ah, I know you. You wrote that informative manual,” or, “You wrote those useful Scheme programs.”  This name recognition helped launch my consulting career and even got me a girlfriend.

You never know which project will end up giving you this kind of publicity, so whenever you create something, write your name first. Don’t wait. It’s perfectly natural to begin by writing your name, but as time goes on it gets more awkward.

Most companies recognize that the author’s name is essential information–it tells where to get support.  But in the end, it’s not your intellectual property.  If they delete your name, accept it. If they ask you to remove your name, comply.

Still, finding and erasing your name is their job. Your job is to always put your name on it.

Comments

Popular posts from this blog

The Reef Lounge

When I was about four, we vacationed at the Handerly Hotel & Resort in San Diego (formerly the Stardust Motor Hotel).  That place was heaven on earth as far as I was concerned. I loved the pool. Next to the pool there was a bar, and behind the bar was an underwater theater. It was here that I saw one of the most outlandish scenes I have ever witnessed.

Build with CMake in Eclipse

Cross-platform CMake can generate a wide variety of build systems.  The CMake 2.8 project generator for Eclipse does not work, so you must create the project and configure it to build with GNU Make .  Here’s how to do it on Linux.

Use Multilingual UTF-8 Strings with any OpenAccess Version

In this article I show you how to use multilingual UTF-8 strings with standard, unmodified OpenAccess oa-22.04p028 release. In the last  article , I introduced UTF-8, the popular 8 bit encoding of Unicode into multibyte character strings that can represent virtually every written language in history.  I presented the OpenAccess software changes required to fully support UTF-8 and showed you how to convert your existing application software to properly manipulate UTF-8 in the OpenAccess oaString class.