In my daily life, Git has 2 major advantages: version control and comparison of versions even when I’m not connected to the internet (you have your own actual repository, not just a working copy), and its speed. It takes less time to clone a whole repository of code than it does to check out a working copy using CVS or SVN! It’s really worth checking out.

I imagine Git will become the new CVS – the new standard, until something better comes along to supplant it.

The transition from writing free-form web applications, to writing modules for Drupal, or APEX customizations for Salesforce, is another set of lessons in protocols and constraints. First, it’s not enough to understand the syntax and form of the language (this is especially true for APEX – and beware the required test coverage!) One has to understand how the surrounding application works – what APIs or methods one can use, and how. And unlike long standing languages, there aren’t lots of detailed cookbooks and that sort of thing lying around – a lot of it is learning from other folks, as well as just learning by trial and error.

And, in my small forays into learning frameworks like CakePHP, Ruby On Rails, and others, it seems like these days, coding for the web is many lessons in constraints – which is a good thing, I think. Even though it feels like beating my head against a wall, it’s nice to know that I won’t “dump core” and break Salesforce (although I for sure have broken Drupal on occasion!)