I’m certainly not planning to keep people updated on every CSS selector change on the site (there will be a lot), but I have to mark the occasion of changing from the boring stock WordPress “Kubrick” theme to the first revision of Corporation Unknown’s graphic identity.

Most significant is the new logo done by our friends at SkyCubeMedia. Thanks to Sky (and my wife’s initial sketch), I now have a site identity I can carry around (in the form of business cards) to WWDC.

When you’ve been involved in (or just been watching) an industry long enough, you begin to see cycles. Or maybe they’re just ideas which were ahead of their time and eventually have come to fruition. (You can stop your smirking right now, Smalltalk advocates.)

Since changing from CVS to Subversion, one of these possible cycles has been tickling my basal ganglia: The change from CVS’ “every file on its own revision schedule” to Subversion’s “one revision for the entire repository state” has been both a blessing and a confusion, but it also reminded me of a revision control system from the pages of MacTech magazine. A few days ago, I finally remembered a keyword (“orthogonal”) at the same moment I had some time to do a bit searching, and I found it: VOODOO. From the stale MacUpdate entry:

The standard Cocoa method for a string with multiple replacements is [NSString stringWithFormat:]. To build a standard analogy string from the SATs:

hand : palm :: foot : sole

you would break out each of the replaceable elements into separate strings and replace them in the format string with the placeholder '%@'. (There are many other format specifiers—look up printf()—but '%@' is very common in Cocoa since it specifies an Objective-C object, not just a simple number or C null-terminated string.)

Well, here we go…

Corporation Unknown will serve to track the course of my progress to an intended career as an independent Mac software developer. No, I don’t hate my job (even though it’s not Mac development), but I do feel that this is the long-term path to my career happiness and further success. We will track milestones on the way to launch, and share insights gained along the way—both in business and code.

Obviously, there is a product planned; it’s not Web 2.0, and it’s not going to change the world as you know it (in version 1.0, at least). It will be easier to use than what’s out there, yet more powerful at the same time—and I already have plans for more powerful future versions.

Let us begin…