With the impending Borgification--yeah, I know I'm mixing sci-fi metaphors--of Sun (and thus Java) by Oracle, it seemed logical to hedge my cross-platform programming bets with .NET. A few months back, Microsoft more or less agreed to remove the legal cloud that had been hanging over Mono, an open-source, cross-platform implementation of parts of .NET. Big ups to them for that.
So I returned (after a multi-month hiatus) to the Mono website tonight, all set to start downloading and installing and "Hello, World!"ing, and...wait a minute...whaddya mean that Mono 2.2 implements something between .NET 2.0 and .NET 3.5? That's a little...imprecise. And, uh-oh, not all the APIs are documented...I don't even know what some of them do. Oops, and the on-site articles haven't been updated since 2007. A couple big red lights started flashing.
Okay, open-source usually means volunteer work: I get that. (I've taken enough flak about the deficiencies of code I've written on my own time--trust me, I understand the limitations.)
The problem I actually have is that the project is officially sponsored by Novell. It's not a SourceForge-hosted effort. Nor is it the silver standard, meaning a project under the wing of the Apache Foundation. (The gold standard being, of course, the Linux kernel itself.) I mean, we live in an age where companies will pay obscene amounts of money to slap their name on a ballpark. But here, Novell (a software company) has the opportunity to make a highly professional impression on a highly relevant customer demographic (programmers), but it puts its logo on a clearly under-funded, under-staffed effort.
The upshot is: Whatever money Novell has put into this effort in the name of marketing has had negative returns. I've blasted Adobe for the moldy crumbs it throws as "alms" to Flash/Flex developers on Linux. Novell doesn't come off as quite so high-handed, but it's the same essential bone-headedness at work. Unlike Adobe (who spawned Flex), Novell has the option of disowning their support of the Mono effort. Sure, they'll take some flak, but is that really worse than being so tight with their actual support? Me, I don't think so.
Closed-source companies supporting open-source projects isn't always so lame. True, I prefer Ubuntu Linux overall, but few years ago was successfully running OpenSUSE, which (ironically enough) is also sponsored by Novell. (I only went back to Ubuntu after the OpenSUSE had issues with a new motherboard.) Then, too, I see the regression test results from Sun Microsystems come through the Derby mailing list every day--which is all the more remarkable when you consider that Sun is thus supporting software originally developed by IBM.
I'm not arguing that companies that make software are in any way obliged to supply open-source project with money, staff, hosting, code or other resources. But, for pity's sake, none at all looks better than treating the open-source project like the proverbial red-headed stepchild. Master Yoda had the right of it: "Do or do not. There is no try."
Thoughts on computers, companies, and the equally puzzling humans who interact with them
Wednesday, October 14, 2009
Paging Product Manager Yoda
Tuesday, October 13, 2009
What's the cost of doing business...with you?
One cynical way to read this is, "Hmmm...I wonder whether this is the first step toward a merger?" Another is, "Great. Two 800 lb. gorillas become one 1600 lb. gorilla--it's not like we have enough of that in Corporate America..."
But the non-cynical takeaway for me was, "Wow, two corporate behemoths actually managed to get over themselves long enough to grok co-opetition!" But the point I want to hammer on is that one of the most sustainable ways to cut costs is to make it easy to do business in the first place. In the case of this partnership, a vendor only has to negotiate terms with one company, or send out a single invoice. Understandably, that reduces overhead for both customer and vendor. Which is a win-win if ever was. But. It requires giving up a certain amount of corporate self-centeredness. That, of course, is the difficult part. Companies like WalMart are notorious for squeezing vendors without taking any responsibility for reducing the cost of selling to them.
Although I've pretty much outgrown my taste for Mountain Dew and am extremely picky (and Wisconsin-centric) in beer, I do hope that the Pepsi-Anheuser partnership becomes a model of sorts. Assuming, of course, that this isn't just yet another exercise in racing to the bottom. Because there's a lot to be said for co-opetition. Most notably that it belies the zero-sum nonsense that passes for business strategy.
Monday, October 12, 2009
Why I can't afford discounted work
I was working earlier tonight with a lady who's trying to get her freelance career off the ground. She seems to be in the proto-business state, and her main objective is to build a client base. To that end, she was willing to work for half the rate she thought she should charge, something that wouldn't result in a living wage (particularly not with a three year-old involved).
Not to be all goody-two-shoes and conspicuously polish my halo in front of everyone, but I told her that any work she does on my behalf should be at full price. There are purely selfish reasons for that. One of which is my strong opinion that higher billing rates tend to demand leaner, effective processes, simply because each tick of the clock is so much louder at full price. When time costs less, there's less incentive to invest in what ultimately leads to an end-product that's worth the price. Similarly, triaging the non-negotiables vs. the nice-to-haves is sloppier when the lower rate gives you more flexibility in turnaround time. (You know, Fast, cheap, good: Pick two.) So I'd rather people working in a top-billing mentality, because anything else tends (in my experience) to encourage false economies.
To me, the only two choices that make sense are: A.) Charge full price, or B.) Do it for free. The reason for this binary attitude is simple. At the two far ends of the free-vs.full-price spectrum, you know exactly for whom you're working. When you're working for free, you're working for something other than money, which means there are no purse strings--in other words, you're working for yourself. In contrast, when you work at full price, you're working solely for the customer. But neither is 100% true anywhere else in the spectrum.
That's a problem. Maybe the customer won't recognize it as such, but the discount is a powerful incentive to discount the value of your work in your own mind. The cut-price mentality that results does little to nudge you toward ways of working faster and at a consistently higher quality level. Nor does it encourage investing--in the coin(s) of thought, money, or the pain of process change--in the longer-term relationship with the client. Why? Because the work--your fundamental connection with the client--become a means to an end (short-term cash-flow and/or portfolio trophy) rather than an end in itself (the longer-term collaboration).
Obviously, it's her career to develop as she sees fit. But it's not a path I'd willingly trod: The conflict of interest is virtually unavoidable, which doesn't jibe with the ultimate goal of forging partnerships.
Sunday, October 11, 2009
An all-too-Graceless evening
One of my "mentors" on the UWEC Forensics team and I ran into each other a few times in the two decades or since I lagged behind him on the Commencement stage in the arena, and we recently re-connected on Facebook. We're alike in that we both landed in technology despite majoring in something completely different. We likewise have a special appreciation for people who are fluent in both computer and human languages, which is probably why he linked this vintage David Letterman interview with Adm. Dr. Grace Hopper. The nine minutes and change capture the essence of a lady who was not merely brilliant, but a force of nature--and thus worth your time for that experience alone.
But what's not quoted in either the interview nor the Wikipedia biography is something that's stuck with me ever since I read it in a recap of her life. Namely that inventing a compiler and an English-like computer language (COBOL) were merely a means to the end of letting mathematicians get on with the work they are actually trained (and prefer) to do. Which is certainly not twiddling bits on and off. In the proverbial nutshell, computers should get the heck out of your brain's way while it's trying to solve the actual problem at hand.
That's hardly a new thought, and is by no means original to me. Yet as I delete and re-import a CD w/in iTunes (to force it to recognize the cover art for more than the last two tracks) while re-writing a whitepaper to stop it from obsessing over a feature that our product just happens [wink, wink] to have (as opposed to its actual benefit to the potential client), the ethos of keeping the computer out from underfoot is conspicuous by its absence. So I'm grateful to the afore-mentioned mentor for once again reminding me of what's really important in our industry.
Saturday, October 10, 2009
No Saturday post
Friday, October 9, 2009
Frivolous Friday, 10.09.2009: "SchadenFriday" limericks
Just now you're as mad as a Hatter:
The flash drive that backed up your SATA
Had Cheetos dust flushed
When it went through the wash
Which likewise scrubbed all your data.
Its details would be quite profound
In running this gremlin to ground.
Alas, IE6
Is back at its tricks:
Stating merely, "Object not found."
These slides you might want to re-do:
No amount of transitional glue
Could bind graphs and charts,
Pimped fonts and clip-art
With more bullets than World War II
When tracking a bug to its lair
Adds grey to a programmer's hair,
It's not the bug's kind,
But, rather, they find
It lodged between keyboard and chair.
Though far more artistic than lewd,
These photos of folks in the nude
Were not meant to thrive
On a networked hard drive:
Your career here's officially screwed.
Thursday, October 8, 2009
Kudos I didn't expect to give
As it turns out, I had my new license less than fifteen minutes later. Partly, I was lucky and just beat the early lunch-hour traffic. As I was leaving, I noticed an electronic sign that gave estimated wait times for those in line, a customer service amenity I don't recall from the last time I had to upgrade that all-important bit of plastic. But what I thought more interesting was the posted notice that the branch will be closed next Monday while its staff is on "unpaid furlough." Apparently, this affects all WI state employees via the budget. (I've worked for places that didn't offer paid vacation, but at least the actual timing of the vacation was on my terms.)
In short, it was a bit eye-opening to see how well our local DMV branch has adapted its processes (and deployed relatively simple technology) to serve more people with less time-wasting. And I thought that it deserved a shout-out for that.