Surround SCM 5.0 and killer robots

So a few weeks back Seapine released Surround SCM 5.0, the first ever SCM system that not only tracks code but also washes your car, cooks you lunch, and if you buy the premium support that goes with it, will hunt down and kill telemarketers just like a Terminator.

All right, that’s not entirely true. Actually, it isn’t even mostly true. Surround SCM does keep track of your source code though. And to that end there is a cool new feature in Surround 5.0 that doesn’t get as much love as the fancy schmancy configurable workflow, the Address bar. Here is a practical demonstration of this new functionality.

So let’s say Yan sends me an instant message that goes something like this:

Yan: d00d, u need to c this l33t code i jst chekD n.

Me: What the hell are you talking about? And where are your capital letters? Back in my day we had shift keys and we liked them.

Yan: wutevA grandpa, jst chek out d code

Me: *Sigh* Alright. What do you want me to see?

Funny side bar to all this IM speak, on my birthday last year we were meeting up with a friend of mine at an outdoor festival that had a local band playing. I get there and my cell phone gets a text message asking where I was. Thinking I’ll be all cool like the kids these days I decide to text back and use the fancy T9 interface.

I figure saying something like “I’ll be right there” would suffice so I start typing away only to send the following:

“Biscuit”

Nothing confuses a text message recipient faster than replying to a question with a type a breakfast pastry. And yes, it was my 30th birthday and my wife made me promise to never try to T9 text again lest I embarrass myself further. Back to the IM’s…

Yan: sscm://localhost:4900/MacMainline/MacMainline/Cybertron/optimus.cpp

I fire up the Surround client, paste that line into the address bar, and it shows me the file in question:

location.jpg

This takes me straight to the file’s location in the system, the branch, the repository, everything. It’s a little pointer to where we are right now without the confusion of where we’ve been. It’s us and the file looking into the future that is unwritten, just like the end of Terminator 2 taught us. That is until Terminator 3 came along and said, “Yeah, about that unwritten future business, sorry, we lied. You’re basically hosed, enjoy the nuclear winter.” Darn killer robots.

A quick view of the file let’s me see his changes:


if (autobots.transform() && rollout())
{
   driveToKickDecepticonAss();
}
else
{
   cutToCommerical();
}

Nodding, I send a message back to Yan…

Me: I like it. It’s subtle, but there is more to it than meets the eye. ;-)

About Grant

I grew up on the mean cul-du-sacs of Troy, Ohio, USA. I first started "programming" at the age of five on an Atari 400 when I used BASIC to draw an ASCII picture of robot with wheels on his feet. Why the emphasis on feet with wheels? At the time it was a big deal, I didn't have wheels on my feet which forced me to walk everywhere. I would have been so much cooler to just skate around. Since then I've gone on to work on all manners of different technologies, but rest assured if I ever write another robot program he won't just be walking around. Perhaps some tank treads...
This entry was posted in Surround SCM, T9, Transformers. Bookmark the permalink.

One Response to Surround SCM 5.0 and killer robots

  1. Grant says:

    As the very observant have pointed out, the link sent from Yan points at localhost instead of an actual hostname. I got gun shy at the thought of posting a real hostname on the internet, largely because I sit right next to the sysadmins and I don’t want them flinging spare computer parts my way.

    Oh, and Yan also points out that you just click on that link directly and it will open Surround. No need to cut and paste even.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>