The Daily Parker

Politics, Weather, Photography, and the Dog

The Times gets my attention this evening

Three unrelated stories drew my notice this evening:

PATH service has resumed to Hoboken. Some years ago—never mind how long precisely—I lived in Hoboken, N.J., the birthplace of Frank Sinatra (really) and baseball (not really). I took the Port Authority Trans-Hudson train almost every day when I worked in SoHo, and about every third day when I worked in Midtown. Having experienced other ways of commuting to New York—in fact, the switch up to 53rd and Park finally got me to return to Chicago, after my commute stretched to an hour and 15 minutes and required three transit changes—I have a lot of sympathy for the people living in Hoboken and Jersey City who have had to make their ways across the Hudson without the PATH.

In the first days after 9/11, both the PATH and the MTA worried that the Twin Towers' collapse would breach the "bathtub" (the Towers' foundation) and flood both the PATH and the New York subway. No one knew how bad the damage would be, and were thankful when it didn't happen. Eleven years later, Hurricane Sandy showed everyone.

So reading today that the PATH Hoboken to 33rd St. line reopened after seven weeks made me smile. Not as much, I expect, as the thousands of people whose commutes can now return to tolerable lengths.

I'm visiting New York in a few weeks; I'll make sure to post a few photos in homage of the PATH.

Facebook's change to Instagram's terms of service has rightly outraged everyone paying attention. Instagram, a photo-sharing service that Facebook bought recently for $1 bn, this week published new terms of service that allow them to use posted photos any way they want, any time they want. Their goal, not surprisingly, is to make money. The people who use Instagram just want to share their photos with their friends.

The Times quoted Santa Clara University Law Professor Eric Goldman saying, "The interest of the site is never 100 percent aligned with the users, and the divergence inevitably leads to friction. It’s unavoidable." Well, yes, because Instagram's users are not Instagram's customers, as they are just discovering, because the customer is the one who pays you. If you use a service that is free to you, you are not the customer and therefore have nothing to say to the service's owners. I find the flap about Instagram's TOS so interesting because it seems as if none of their users has realized this key point yet.

Instagram swears up and down that the users continue to own their own photos. Of course they do. And of course you keep ownership. But if you post on Instagram, "you hereby grant to Instagram a non-exclusive, fully paid and royalty-free, worldwide, limited license to use, modify, delete from, add to, publicly perform, publicly display, reproduce and translate such Content, including without limitation distributing part or all of the Site in any media formats through any media channel...." So they don't own your photos, exactly, but they can act as if they do.

Under U.S. copyright law, the creator of a work owns it, unless he has signed away the creation right explicitly. (Example: I work for a great software company. I write software for them, under a work-for-hire agreement. Therefore, except for some explicit, written exceptions, all the software I produce that has commercial value is owned by my employer. If I write code in one of my employer's client's applications that makes 10th Magnitude a billion dollars, I don't own it, 10th Magnitude does. That's the deal I made when I took this job. I trust, however, that if I made my boss a billion dollars, he'd share.)

So if you take a photo on your phone, you own it. It's your photo. And Instagram's new TOS says, yes, of course you own it, but we can sell it if we want and pay you nothing.

Now, I've experienced a variety of contractual arrangements in my life as a creative person, so I'm not shocked when someone wants a piece of my income as a fee for finding the income-producing gig. As a software contractor, I've routinely signed away 25% or 30% of my earnings off the top, in exchange for someone else doing the legwork to find the income-producing gig on my behalf. (It's really hard to find gigs while you're working full time on one, it turns out.) And, as someone who hires software contractors now, I expect they'll agree, too. We call this a "commission," as have people in other professions for millennia.

Instagram, effectively, demands a 100% commission off your work. Not only that, but if Instagram finds that one of your photos makes Ansel Adams weep, they can market the crap out of it. You'll never see a dime. Why would someone license the rights from you, when Instagram is selling them cheap? And you can't stop Instagram from destroying the market for your work, because you consented to it by posting your photo.

Let me put it another way. Instagram is saying, "You own your car, of course. But if you park it in our garage, we get to use it as a taxi, without paying you a dime."

To sum up: the people railing against Instagram's new TOS are exactly right. It sucks. And I will never, ever post any of my intellectual property there, even if they change the TOS in response to the approbation they've received, because (repeat after me) I am not their customer.

Finally—and I assure you, this is not related to Instagram—I recoiled in horror at the latest religious stupidity, that the Taliban have started killing anti-polio workers in Afghanistan.

Full disclosure: I was a member of Rotary International for a few years, and I wholly support the organization's amazingly-successful efforts to destroy polio the way we destroyed smallpox. Polio is a sufficiently complex organism that it can't evolve as quickly as we can kill it, making it an ideal target for eradication (like smallpox). But you have to get immunized, and sufficient numbers of your neighbors do, too, or it will keep spreading.

So, these idiot religious fundies, who subscribe to any number of irrational fantasies already, have apparently decided that the people trying to keep their babies from dying of an entirely preventable disease are, in fact, American spies. As the Times reports, "the killings were a serious reversal for the multi-billion-dollar global polio immunization effort, which over the past quarter century has reduced the number of endemic countries from 120 to just three: Pakistan, Afghanistan and Nigeria."

Does anyone else see a coincidence between the three last outposts of a crippling, preventable disease and religious nuttery? Part of Rotary's success, by the way, has been in reassuring local populations that eradicating polio is no more and no less than it seems: a humanitarian effort to end a horrible disease forever. Wars have stopped to allow Rotary and the Gates Foundation to conduct immunizations. But the Taliban do not believe in reason. They would rather have hundreds of their children dead or crippled than accept the possibility that some American- (and British- and French- and Japanese- and South-African- and Namibian- and Saudi- and...) funded organization wants to prevent their children dying or becoming crippled.

Three countries still have polio. They also have air travel. Not everyone in the OECD has polio vaccinations today. So, if I can mention the self-interest of everyone able to read this blog post, who must therefore speak English and have an Internet connection, the religious nutters killing health workers who, but for being shot, would have eradicated a disease that has crippled millions, have made your life more perilous.

</ rant>

All right. Time to walk the dog.

PS: You may need to subscribe to the New York Times to read the linked stories. I apologize if this inconveniences you, but I recommend subscribing anyway. For $15 a month you not only get the entire newspaper online (and on any tablets you own), but you get to feel good about yourself. You also get to live Kant's categorical imperative, by behaving in such a way that the behavior could be universal. Isn't $15 an incentive worth aligning?

Why was Pinball removed from Windows Vista?

Microsoft veteran Raymond Chen explains:

The 64-bit version of Pinball had a pretty nasty bug where the ball would simply pass through other objects like a ghost. In particular, when you started the game, the ball would be delivered to the launcher, and then it would slowly fall towards the bottom of the screen, through the plunger, and out the bottom of the table.

Games tended to be really short.

Two of us tried to debug the program to figure out what was going on, but given that this was code written several years earlier by an outside company, and that nobody at Microsoft ever understood how the code worked (much less still understood it), and that most of the code was completely uncommented, we simply couldn't figure out why the collision detector was not working.

We had several million lines of code still to port, so we couldn't afford to spend days studying the code trying to figure out what obscure floating point rounding error was causing collision detection to fail. We just made the executive decision right there to drop Pinball from the product.

Chen's blog often goes into technical detail that many people might find off-putting, but he's a good person to read if you want to know more about how Microsoft works.

Evolution at IDTWHQ

Last night I continued reducing local computing costs by turning off my home desktop PC. The old PC has a ton of space and a lot of applications that my laptop doesn't have, plus a nifty dual-DVI video card. But a couple of things have changed since 2008.

First, my current laptop, a Dell Latitude E6420, has a faster processor, the same amount of RAM, and a solid-state drive, making it about twice as fast as the desktop. Second, Dell has a new, upgraded docking station that will drive two big monitors easily. (Sadly, though the docking station can drive two DVIs, my laptop's video chip can only do one DVI and one VGA.) Third, the laptop uses buttloads less power than the desktop. Fourth, portable terabyte drives are a lot less expensive today than in 2008—and a lot smaller. And finally, I take my laptop to and from work, meaning I have a minor hassle keeping it synchronized with my desktop.

Here's my office about three years ago (January 2010):

A few months later I got a second 24-inch monitor (November 2010 photo):

Notice the printer has moved to make room for the second monitor, but otherwise the setup remains the same. The monitors connect to the desktop under the desk to the left, while the laptop has its own cradle to the right.

Now this afternoon:

The printer has landed on the floor directly under where it used to sit (I print about 3 pages per month, so this isn't the inconvenience it seems), the laptop has moved over to the printer's old spot (and has connected to the monitors), and the old desktop machine sits quietly consuming 225 fewer Watts per hour. I also replaced the 10-year-old, no-longer-functioning 2+1 speaker set with a more compact set. The round thing between the keyboard and the laptop near the center of the photo is a speakerphone that I use with Skype.

I think everyone knows the dog under the desk by now, too. He's not happy that I rearranged his favorite sleeping cave, so I might get a couple of weeks without mounds of dog hair under my desk until he decides the printer is harmless.

So far today I have been unusually productive, whether because of the novelty or because I have a fire-under-the-ass deadline at work. So back to it.

Too many buzzwords on LinkedIn?

That's what LinkedIn's career expert says:

Back when I started working with LinkedIn, we released our very first ranking of the most overused profile buzzwords. I remember thinking how important it was to steer clear of “extensive experience” (the number one overused term in 2010) if you wanted to shine among the 85 million professionals who were touting their years in the trenches as their defining characteristic.

Well, it’s three years later and with over 100 million MORE professionals on LinkedIn, the stakes to stand out from this year’s very “creative” (this year’s most oft used adjective) crowd are even higher. Here are a few tips for saying what you mean with words that will get you noticed.

LinkedIn lists these as the most buzzy:

  • Analytical
  • Creative
  • Effective
  • Experimental
  • Motivated
  • Multinational
  • Responsible
  • Specialized

Just try writing a résumé without them...go on...

Stuff to read later

Yes, another link round-up:

Back to designing software...

Build, buy, or rent?

10th Magnitude's CTO, Steve Harshbarger, explains how the cloud makes economics better by giving us more options:

We know we could build every feature of a custom application from the ground up. We get ultimate control of the result, but often the cost or timeframe to do so is prohibitive. So as developers, we look to incorporate pre-built components to speed things along. Not only that, we strive for better functionality by incorporating specialized components that others have already invested far more resources in than we ever could for a single application. As a simple example, who would ever write a graphing engine from scratch with so many great ones out there? So, build is rarely the whole story.

What about buy? I think of “buy” not in a strict monetary sense, but as a moniker for code or components that get pulled into the physical boundary of your application. This includes both open source components and commercial products, in the form of source code you pull into your project, or binaries you install and run with your applications’ infrastructure. We all do this all the time.

But the cloud brings a third option to the table: rent. I define this as a service you integrate with via some API, which runs outside your application’s physical boundary. This is where smart developers see an opportunity to shave more time and cost off of projects while maintaining—or even increasing—the quality of functionality.

He also lists our top-10 third-party "rental" services, including Postmark, Pingdom, and Arrow Payments. (I'm using a couple of them as well.)

Still jamming; pre-Thanksgiving link roundup

Stuff sent to Instapaper:

Time to dash out for lunch...then more coding. Gotta finish today.

Jamming on the Codez

Over the last two days I've spent almost every working minute redesigning the 10th Magnitude framework and reference application. Not new code, really, just upgrading them to the latest Azure bits and putting them into a NuGet package.

That hasn't left much time for blogging. Or for Words With Friends. And I'm using a lot of Instapaper. Without Instapaper, I'd never get to read Wired editor Mat Honan drawing lessons from his epic hack last summer.

Going, going...

Two Chicago businesses find themselves on the ropes this afternoon, according to the Tribune. The first company, Groupon, has problems many people predicted long before their IPO:

Groupon and its compatriots in the much-hyped daily deals business were supposed to change the very nature of small-business advertising. Instead, it is the daily deal vendors that are racing to change as evidence mounts that their business model is fundamentally flawed.

Critics say the torrid growth that enabled Groupon to go public at $20 a share just a year ago was fueled by merchants buying into a new type of marketing that they didn't fully understand. The discounts offered through the Groupon coupons have turned out to be costly, and the repeat business they generate uncertain.

A Raymond James survey of roughly 115 merchants that used daily deals services during the fall found that 39 percent of merchants said they were not likely to run another Groupon promotion over the next couple of years. The top reasons cited were high commission rate and low rate of repeat customers gained through offering a promotion.

Yeah, no kidding. These flaws have been obvious from Groupon's beginning. I have one outstanding Groupon and one outstanding Living Social deal, and I'm not sure when I'll get to use either. After that, meh.

The other company, Hostess, has hit an unexpected and possibly fatal labor dispute that may force it into out of reorganization and into liquidation:

On Friday, Hostess-employed members of the Bakery, Confectionery, Tobacco Workers and Grain Millers International Union began to strike nationwide, blaming a “horrendous contract” that they claimed could cut wages and benefits up to 32%.

Workers picketed or honored the strike in Sacramento, Los Angeles, Oakland and Seattle and in states such as Ohio, Tennessee, Illinois and Montana. Hostess said in a statement that the walk-offs could lead to layoffs for most of its 18,300-member workforce and a sale of its assets “to the highest bidders.”

“A widespread strike will cause Hostess Brands to liquidate if we are unable to produce or deliver products,” according to the statement. The Irving, Tex.-based company, which was founded in 1930, acknowledged that “the concessions are tough.”

So if you like Twinkies and Ho-Hos, you'd better stock up. (Don't worry; they keep.)

The Romney campaign's software epic fail

Politico's Burns & Haberman explain:

[ORCA] was described as a mega-app for smartphones that would link the more than 30,000 operatives and volunteers involved in get-out-the-vote efforts. PBS profiled it a few days before the election. The app was created and managed by the Romney campaign and was kept a secret among a close circle in Boston, according to POLITICO sources.

It's been reported the system crashed at 4 p.m., but multiple sources familiar with the war room operation said it had actually been crashing throughout the day. Officials mostly got information about votes either from public news sources tracking data, like CNN.com, or by calling the counties for information, the source said. Officials insisted the day after the election that they had still believed they were close, and that they had hit their numbers where they needed to, even as Fox News and other outlets called the race.

The post links back to a Romney volunteer's description of how ORCA failed in the field:

On one of the last conference calls (I believe it was on Saturday night), they told us that our packets would be arriving shortly. Now, there seemed to be a fair amount of confusion about what they meant by "packet". Some people on Twitter were wondering if that meant a packet in the mail or a pdf or what. Finally, my packet arrived at 4PM on Monday afternoon as an emailed 60 page pdf. Nothing came in the mail. Because I was out most of the day, I only got around to seeing it at around 10PM Monday night. So, I sat down and cursed as I would have to print out 60+ pages of instructions and voter rolls on my home printer. ... They expected 75-80 year old veteran volunteers to print out 60+ pages on their home computers? The night before election day? From what I hear, other people had similar experiences. In fact, many volunteers never received their packets at all.

Now a note about the technology itself. For starters, this was billed as an "app" when it was actually a mobile-optimized website (or "web app"). For days I saw people on Twitter saying they couldn't find the app on the Android Market or iTunes and couldn't download it. Well, that's because it didn't exist. It was a website. This created a ton of confusion. Not to mention that they didn't even "turn it on" until 6AM in the morning, so people couldn't properly familiarize themselves with how it worked on their personal phone beforehand.

The project management antipatterns are apparent: Blowhard Jamboree, Smoke and Mirrors, Throw It Over the Wall, and basic Project Mismanagement, for starters. I haven't seen the code, but I can't imagine the management and deployment problems didn't lead to design and construction problems as well.

We software professionals have learned, through painful experience, that software developers have a better understanding of how to develop software than corporate executives. Go figure. Since Mitt Romney ran as a father-knows-best, authoritarian candidate, it should surprise no one that the people he hired couldn't run a software project.