One good thing about Windows 8 preview

Making a computer behave like a web page on a tablet looks like a step backwards, albeit a pretty one, but there is one good thing in the following Microsoft video on Windows 8. The demonstrator half-drags another application onto the screen at 2:05 and 3:00 to create a resizable region so two apps can run side by side:

(Full article on

The is a logical evolution of the one thing I like about Windows 7 and use regularly, window snapping. It’s also one step closer to a desktop that works like the Eclipse IDE with various resizable panels for different elements like object browser, code editor, and compilation messages. Apple is also taking a tablet-inspired approach in Mac OS X Lion. It’s about time operating system vendors step up and do something about the sad state of application window management, but I don’t expect Windows 8 or Mac OS X Lion to bring perfect solutions because of their inspiration: Tablets make great content consumption devices, but I need something inspired by a content creation tool as my desktop.

In the meantime, I’m using a little open source app called Shift It to get something like window snapping on the Mac. It uses keyboard shortcuts rather than the Windows-style border collision which the Mac already uses for virtual desktop management, Spaces. Here’s my somewhat-Eclipse-inspired desktop with the Shift It menu exposed:

My Desktop with Shift It
Dock and Twitter on one side, desktop files on another, and a perfect half-width browser window (with too many tabs as usual) in the middle. Sized and positioned Chrome by shifting it left then center with Shift It.

Shift It isn’t a perfect solution. It has some problems with window size or position being a little off sometimes, and the top/bottom options are practically useless on a widescreen display. Most people won’t mind, but my particular pathological need to organize (also expressed by my obsession with The Container Store) requires precision and symmetry and flexibility.  Steve Jobs has a similar affliction, so I’m hoping Lion will be like digital Paxil for my application window management OCD.

When Relevance Attacks

I used to think all ads were spam. That sentiment had its origins in traditional media where some kind of adspace cosmological constant keeps pushing real content further and further apart, filling my field of view with a relevance vacuum of feminine hygiene, SUV, and sorority girl chat line commercials.

However, I’ve been coming around to V.’s way of thinking about ads in new media lately. I don’t mind as much because ads are at least loosely targeted to the topic-specific sites I frequent; sometimes I’m even grateful when I encounter something previously unknown and personally applicable.  That happens more when I’m willing to make Google privy to my electronic life or tell Hulu when ads are relevant. Old media pushes me further away while new media draws me into its less-adflated, more-relevant open arms.

So I came home from a MarkLogic event at The Palomar–ready to blog about some things they get that EMC is just starting to grasp–to find a new comment on an old post about the iPhone Clock app.  It was an ad (no surprise) but it was perfectly relevant to the post and even got me into iTunes to download the app (big surprise).  A few more things like this might even get cynical me to stop cringing whenever I see “please moderate” in my inbox.

The reward for that relevance is an extra plug.  I haven’t tried the app yet since there’s nothing to time at the moment, but I encourage you to take a look:

So, please do check out – you’ll find it to be a significant upgrade from the default Clock app. Oh, one last thing… its FREE!

Lies My Folder Objects Told Me

Pie is having some folder object problems [ Tip: A Documentum Folder’s Existential Crisis « Word of Pie ] and it’s no surprise to me.  I trust folder objects less than I trust an insane homicidal computer; at least I know for certain that GLaDOS is still trying to kill me.

I’ve fantasized for years about replacing dm_sysobject with something light weight and implementing things like folder location and versioning as interfaces applied to that type as needed. Pie might not have had hair pulling to do if dm_folder wasn’t bringing along all of dm_sysobject’s baggage.  It’s another example of the junk DNA rife through Documentum’s API and schema.

Documentum did add lightweight objects a few years ago, but they fell far short of my fantasy.  They turned out to be a hack to deal with bulk object creation instead of a fundamental refactoring of the object schema. I wasn’t surprised; implementing something like my fantasy would be an upgrade/compatibility nightmare; every single sysobject would have to be folded, spindled, and mutilated in the process. Just the database part of that upgrade could take days on big docbases, and those upgrades could fail in spectacular ways noticeable only long after the fact. Oh well.

It’s a lesson to inform the creators of new systems like Documentum. Of course there are scaling problems at the database level if those interface abstractions result in lots of separate tables and joins at the concrete level assuming a relational database infrastructure. I think that’s still a safe assumption since object databases haven’t gotten that much better and NoSQL databases don’t seem to be a good fit to this problem space on first blush. I wonder: Did Alfresco learn any of these lessons? Maybe I’ll go take a look under its hood and see.



Perl, I say!

At last week’s Philadelphia Perl Mongers meeting, I asked what’s new and exciting in Perl since I last used it exclusively, circa Perl 5.6.  Walt chimed in with say, a command that prints an expression and adds a new line at the end.  New and exciting?

Other languages have always had separate commands to display strings with or without newlines at the end.  Embedding escape codes like \n or using Perl’s smarts around concatenating and contextualizing work fine, so a separate command isn’t necessary like in some of those other languages with print and println or write and writeln.  “So why now?” I asked.

Some of the semi-glib responses to my follow-up touched on the venerated trait of laziness among Perl programmers and joking about doing more with less (i.e., two less characters from print to say). I say semi-glib because both of these comments hold kernels of truth about Perl that originally drew me to the language and explain my continued frustration with the “newer” languages that I now have to call bread and butter.

Perl has always been a programming language for the lazy, proud, and impatient.  From personal experience, I’m more likely to use print with a “\n” than without, so that little extra work spread out over the thousands and thousands of print “…” does add up. There is some sense in having a command whose default mode includes a linefeed.

Perl has also always been a language about packing–functionally and semantically. That’s earned it a reputation of being hackish or too clever for itself, but anything taken to an extreme can be bad.  My experience supports the perlish idea that less code written is less code to debug or relearn later.  Some languages, especially those fond of methods on literal strings instead of operators, provide flexibility at the cost of verbosity and ugliness.  The idea of packing more capability into two less characters is very, very Perl.

There’s talk of trying to reinvigorate the Perl base and recover some of the mindshare (and subsequent marketshare) that Perl’s lost over the last decade.  I don’t think say will convince legions of .Net or Java programmers to switch, but I’ll definitely use it my next script.

From the Perldocs on say:

  • say LIST
  • say

Just like print, but implicitly appends a newline. say LIST is simply an abbreviation for { local $\ ="\n"; print LIST } .

This keyword is available only when the “say” feature is enabled: see feature.

Beating a Dead dmHorse

Don't google "dead horse" for images.

My response to Pie’s Quality of Documentum Over the Years bears repeating, even if I am beating a dead dmHorse:

I started with version 2, back when I was just a newly-minted UNIX geek. One thing you missed with the transition to 4i was the introduction of the DFC. DMCL had a very UNIX feel; a simple, open API designed to be glued into any programming language. DFC was just Java then, with a COM layer growing over it later. That was also the point where EMC became more marketing-driven and started chasing the Internet bubble at the expense of their existing clients.

Both were attempts to capitalize on hot topics of the time, Java and the Web. I never bought that the DFC would make a whole pool of talent available; Documentum’s about the model, not the means. However, the marketroids successfully reframed it. Hiring managers now believe they can take Java people and mold them into Documentum people, and I hear gasps of disbelief when I say Java or Visual Studio aren’t requirements to do Documentum–a good Java programmer is not necessarily a good Documentum developer.

This Java mentality did increase the number of people with Documentum on their resumes, but the talent didn’t increase as much as the volume. It just diluted (maybe also tainted) the pool. It became harder to find good people in the now-mirky waters.

The lack of focus then is what brings us to the lack of quality now. Innovation at the model and server level is rare, and frankly I don’t give Documentum much geek cred anymore because of it. Great ideas like BOF and Aspects are stapled into an API rather than made an inherent part of the product. Too much work up the stack (and on vertical solutions) has made the product top-heavy and tottery. EMC continues to chase markets (i.e., case management) rather than concentrate on making a solid core product.

Documentum & The Private Option

I want a private equity fund to buy Documentum from EMC and give it a real shot at regaining its former glory.

#26698 Smart Cow Playing Dead To Avoid Going To The Butcher Shop Clipart by DJArtNoted rumor-monger  Brilliant Leap speculates about Documentum in a world without EMC. Tongues were already wagging at EMC World about the SAP-EMC partnership leading to something a little more intimate. It has enough of the smell of truth to make an irresistible rumor.

As rumors go, I still prefer the Microsoft angle because of the obscene anatomy kissing that IIG is still doing.  Truth is it’s just to easy to dispel: Why buy the cow when you get the milk for free? I doubt Microsoft will be stamping shrink-wrapped boxes of SharePoint with Documentum Inside! anytime soon, but I’d bet they have an infinite number of code monkeys banging away to make their own document management Hamlet. Once they do, it’s bye-bye Documentum! Then all those monkeys will get down to business and start flinging feces IIG’s way.

Part of Documentum’s doom was being a software company bought by a hardware company; however, it won’t be saved if another software company buys it next. Such companies (SAP included) would buy Documentum to augment their flagship product, not eclipse it.  With no Fairy Godmother rescue from being passed around from one wicked step-mother to the next, this story’s ending will be more Le Boheme than Cinderella. Or worse, a more-jackal-than-wolf company that hasn’t innovated for decades might gobble it up to suck the last trickle of marrow from its cracked bones.  *cough* computer associates *cough*

I am no Wall Street cheerleader, especially after my time in Big Finance, but the closest thing to a Fairy Godmother out there is a technology-oriented private equity fund. Such a fund buys troubled companies to turn them around and sell them for a profit. Unlike most of Wall Street, they take the long view of years rather than a quarter or the milliseconds around a stock’s uptick.

Their methods can be harsh, but their goal unlike any step-mother’s would be to make Documentum the best product and most profitable (and saleable) brand it can be.  There may still be an ounce of brand left to save. By going private, the recuperating Documentum wouldn’t be burdened with public company regulation or the tyranny of speculative stockholders. It’s an imperfect cure for the age of gratuitous IPOs and acquisitions fueled more by irrational exuberance than smart business.

We have a test case with AOL selling Bebo to Criterion Capital Partners, LLC instead of just shutting it down. Taking Valdes’s animal shelter metaphor a little further, I’m sure Criterion will euthanize Bebo and reap their own “meaningful tax deduction” if the old dog can’t learn new tricks. Sometimes I think I’d rather see that happen to Documentum than sit through the EMC’s little opera until the consumption takes it.

EMC discovers Magnetic Poetry

I can’t find a video of the Mark Lewis keynote from EMC World 2010. Instead I’m depending on reporting from the event like Ron Miller’s article [Documentum group gets new name and new direction] and Pie’s tweets and blog posts. It’s probably for the better; I never had a taste for gruesome videos since Faces of Death, and this may be EMC finally decapitating the Documentum brand.  Rather than plunging into a pages-long diatribe about EMC’s unconditional surrender to the commoditizing of content management or the latest dish of scorn Lewis served up to Documentum veterans, let’s talk names.

Information Intelligence Group is EMC’s new moniker for the product that shall not be named. Lewis breaks down the name for us on his blog [Episode 91: EMC World 2010 – The Birth of the Information Intelligence Group]. It’s hard to read–let alone say–the name with a straight face, and this breakdown doesn’t help. At least the cumbersome and uninspired Content Management and Archiving accurately conveyed something about the product.  This new name is too broad and inherently meaningless; it will continue to erode mindshare for a product that was the de facto definition of document management. Let’s hope this new name doesn’t prove itself a compound oxymoron to boot.

Magnetic Poetry

The “Intelligent” product silos aren’t much better. Granted, this is a product that has to publish a separate guide with each new release to map old product names to new. Not a sheet or a few pages, a document. However, these new silos are so vertically restrictive that EMC had to toss the content server into case management.  Having done case management and having paid my dues in lines of server code, I’m perplexed. It’s like they had a very limited box of magnetic poetry to play with.

The continuing erosion of a strong brand means less mindshare among potential customers. Everybody knows SharePoint even though most don’t know what it really is. I’ve seen first-hand how good marketing trumps good product. Documentum had that name recognition–still does in many parts–and EMC seems determined to stamp it out without something sticky to replace it.