Geeks With Blogs
Thomas Pepe

Though software fundamentals, patterns, and anti-patterns are by far more important and intellectually stimulating to discuss, sometimes it's difficult to move to a new set of terms. When I first learned to program, .NET was pre v1.1 and the java community was getting ready for v1.4. Naturally, I preferred java because of its price, stability, and all my college classes were java. When I got work developing .NET (a few years later) I had to interpret some of the key words from java to .NET.

For instance, getters and setters were replaced (with syntax sugar) with properties, event-interfaces were replaced by event-listener methods, and so on. When I would ask about a super class I would sometimes have to rephrase and ask for a base class to better communicate with my coworkers.

Recently I moved back to java development and a lot has changed, including me. Now I find myself on the other side of the fence. Just last week I had to replace IDictionary with Map. I have only been doing this for a couple of months now and I am starting to think more java like again. It feels good to leave the I off of the front of my interface class definitions and put my curly brackets on the same line again.

I first learned source control in Subversion but for the last 3 years I have been using TFS. I am trying to speak in TFS's terminology but SVN is so ingrained to my thinking. Check-in is the TFS for commit. I still use the word blame when I should use the TFS word annotate.

It appears that my office is sticking to TFS for java development on my eclipse. So I will continue to teach myself TFS's terminology. Perhaps this link will help me or you if you are having the same trouble:

What are your thoughts? Have you had a recent change in terms at work? Do your coworkers understand you or do you need a X to Y dictionary from your previous language to your current?

Posted on Sunday, July 31, 2011 8:28 AM Team Foundation Server , TFS , Java , C# , .NET | Back to top

Comments on this post: Java VS .NET, Subversion VS TFS: a personal history of terminology

# re: Java VS .NET, Subversion VS TFS: a personal history of terminology
Requesting Gravatar...
Thanks for the feedback. I couldn't agree more! The principals that govern good code can be applied to any language and the principals that govern good code management can be employed by TFS or SVN. Some tools make doing things by the book more simple and other tools seem to hinder our efforts.

A feature by feature compassion is a good idea for a future post. This post is about getting comfortable communicating with new terms and some of the confusion that occurs in that process. When I get a chance I will make it more apparent in this post that terms are never as important as the meaning they are used to convey.
Left by Tom on Aug 01, 2011 5:22 PM

Your comment:
 (will show your gravatar)

Copyright © tom | Powered by: