RambleOn

Not yet far enough

They said that the Internet had gone too far.

[insert reverberating demon-sheep like whisper of "too far" here.]

We say. NO! It has not yet gone far enough.

[find some aluminum foil. Or a lightning storm. Or both. You'll need some thunder.]

I present:

More Higgins

Sun Nostalgia

I liked Sun, I didn’t like Java. But I’ve had a long relationship with Sun hardware and the OS – dating back to the time when it was the hot thing replacing the DEC equipment both at work and at school. It always served me well in the roles where I used it.

I’m actually going miss the Schwartz.

What a long strange trip it was.

You know what today needed?

More Higgins.

Needs More Higgins is the new Needs More Cowbell.

( thanks to Rich Phelps for my new catch phrase. Everyone needs a catch phrase.. )

Re: Re: iPad

Faruk, Faruk, you could learn a few things from the old people

I don’t disagree with your assertion “The iPhone and iPad are shifting it even further towards consumers, away from the tinkerers of old, the small little “elite” that excludes the vast majority of people.” – I guess I said the the same thing.

But I disagree vociferously with the assertion that this has changed:

” When they were young, doing anything with a computer required a strong understanding of mathematics, the ability to think in binary and the perseverance to keep exploring things without any book or person around to guide you.”

That has not changed To be a programmer today – you better damn well be able to do that. Objective-C on the iPhone OS absolutely requires that. How on earth did you get to be a programmer at all without some understanding of computing architecture? Even a web programmer?

As far as building your own tools – you can’t – from Apple’s own guidelines:

3.3.2 An Application may not itself install or launch other executable code by any means, including without limitation through the use of a plug-in architecture, calling other frameworks, other APIs or otherwise. No interpreted code may be downloaded or used in an Application except for code that is interpreted and run by Apple’s Documented APIs and built-in interpreter(s).

I think that’s part of Mark’s concern, part of Tim’s concern, and it’s my own concern. I disagree a bit with both that I think the platform is good for the general population – and agree with you on it’s benefit – but I completely disagree with your assertions that the world has changed for the programmers. I’m glad we don’t have punch cards and toggle switches anymore – and that I never had to use them. And I’m damn glad to not have to write Pascal anymore. But effective development still requires logic and still requires architectural understanding of the platform.

Pup Face of the Week

Re: iPad

I’m concerned too.

There’s not one line of Mark Pilgrim’s Tinkerer’s sunset that I disagree with. I respect Mark a tremendous amount. But I think my concern is less about the sunset for the tinkerers. Though Mark’s lament really is less about the general sunset and more about the sunset in Cupertino.

Tinkerers will tinker.

I think I’m more concerned we’ll see the intellectual equivalents of the App Store reviewers use increased controls in the operating system to do whatever control freaks do. But I remember then that they already do in most IT environments.

I’m Mark’s age. But my background is, and certainly my abilities are, different.

In third grade I went to Fuller Magnet School in Raleigh – seeing my first computer ever – and having a chance that few lower-middle class kids from the rural suburbs had then – and few chances that they have today. I had electives, I was able to take a computer class. I learned LOGO on Apple II’s – and then BASIC.

“Learn” is a misnomer. I used it. I don’t know if I was taught loops or not, I don’t think so, but I don’t remember, but even if I was, I’m not sure in third grade I could have understood them. So I wrote hundreds of repetitive “Plot” statements – I stayed late after school waiting for my mom to come pick me up – the buses didn’t run from Raleigh to rural Garner where I commuted to the school – to print out “NC State #1″ on the screen. Most of my classmates gave up long before I did in that pre-Ritalin era. But there I was, plugging away, line after line after line.

My first computer I had at home was a Timex Sinclair 1500 I think it had BASIC too, but I don’t think I understood that. Instead I spent hours loading Frogger from cassette tape, waiting for 5+ minutes for it to load, and then eventually crash, at which I’d load it again, lather, rinse, repeat. My friends usually gave up on it, and went down the street to play on the Commodore 64 – that had cartridges and better graphics.

I ended up getting a “Sharp Scientific Calculator” – a luxury that very few kids had in the rural schools I went back to when the commute to downtown wasn’t working out so well. In my pre-algebra and pre-geometry years I didn’t have a clue what any of the functions on it meant. But I learned I could type line after line after line of Print statements in the tiny one-line screen – which I did, using the attached 2.5 in thermal printer to plot out ascii graphics. And when I got the spaces off, I’d go back and retype all the lines again, lather, rinse, repeat.

My schools didn’t have any computers, not for the kids at least. I didn’t touch computers again until, as an alternate to the Math program at the NC Governor’s School in 1990 – I got to try out “Assembly Language” and “Pascal” I remember vaguely that I had classmates like Mark, kids that I was awed of that parlayed hard work, opportunity, and brilliance into becoming programming contest winners light years beyond me. And it’s safe to say that I had opportunities to that point – and that tenacity – that put me light years ahead of the kids back home.

The rest, well, with my first “real computer” – is history – 19 years of computing support, system administration, and even software programming – 19 years of using multiple computer platforms and a handful of languages, shooting myself in the foot with every last one of them, and fixing the mess. 19 years of helping others to do the same. Lather, rinse, repeat.

I worry about Apple. I can understand Richard Stallman’s dystopic vision. I fear that too.

Here’s the hope. That OS, that hardware, is paradoxically more accessible to far more people than most things that have come before it. The tinkerers will tinker, but the general population – even the academic population – does not. They won’t even lather, rinse, repeat. 19 years of supporting them has shown me that.

In spite of my freedoms being limited, in spite of the DRM, in spite of the restrictions, in spite of my own hypocrisy – my iPhone is the greatest computer I’ve ever owned – much better than that Timex Sinclair, much better than that Sharp, much better than that Emerson. Even better than that PowerPC 6100AV. I don’t miss the 10,000 lines of Plot X,Y. Maybe I should, but I just want the damn thing to work. And while I can write Objective-C programs – I don’t.

And neither do most. But they use the iPhone and the iPod Touch. They use it like they’ve never used any computer before it. It’s their window into the freedom0-powered web that enables them to connect to each other in ways – similar to the ways they always have in their local communities – but in wider ways in the larger world. It’s letting those that never could connect well within the local community – kids like me that were spending hundreds of hours on thousand of plot lines – to connect too.

I don’t want to settle for mediocrity. I don’t want to give up freedoms to gain them. But these devices – and more – that web – are bringing down command-and-control IT overlords in the process.

The iPad is going to do that. And more. It’s going to change computing. It’s going to screw some and vastly enable others. Just like every platform has before it. Lather, rinse, repeat.

I don’t welcome my Apple overlords. But I welcome the change, at least for now.

Link wasting

Exhibit A:

“I Want Flash”

Exhibit B:

From just a few moments ago in another tab.

I think it’s safe to say I won’t be returning to Exhibit A.

Dear NC Congressional Democratic Candidates

I’m not a one issue voter by any stretch of the imagination. But one issue that I’m most likely to actually speak up about is Network Neutrality. It’s one of a few issues that I could claim some amount of in-depth understanding about – and it’s one of the issues that I look for in any candidate for Congressional office (and it was one of two issues that first attracted me to the candidacy of President Obama – well before the Republicans completely lost any semblance of rational behavior and put Palin on their ticket and firmly nailed that coffin for my vote).

Richard Burr is one of the top recipients of telephone utility PAC money – and added his signature to a letter (PDF) (source: Cecilia Kang’s Washing Post column) on October 13th, 2009 to the FCC from GOP Senators expressing “fear” that the pro-Network Neutrality position that the FCC took in September 21, 2009 speech were “counterproductive and risk harming the great advancements in broadband speed and deployment that we have witnessed in recent years and will limit the freedom of the Internet.”

(p.s. Dear Senators – can you actually, you know, put your names in plain text on these letters? Some of you have absolutely unreadable signatures. To verify for myself that Burr signed the letter – I had to go through list of official statements and find another letter authored directly by Senator Burr and compare signatures.)

So, I think – it’s likely safe to say what position Senator Burr will take. It’s very definitely safe to say that I’m in opposition to Burr’s likely position.

So what about the Democrats? Well honestly, I have no idea.

Both Ken Lewis and Elaine Marshall have followed me in twitter – most likely because they are trying to follow folks in the region that follow President Obama’s twitter account – or some other NC Dem list of twitter accounts. Who knows. I seriously doubt they are going to get anything out of my twitter account that guides them to the thinking of their constituency.

But hey, the more the merrier, at least they aren’t following me because they think I front Owl City.

But I really wish that the campaigns would actually get a clue about Twitter and social media. When one of your constituents asks you a question in Twitter – say, I don’t know, Network Neutrality (p.s. Ken, your twitter “handle” was so much nicer, approachable and “human” when it was KennethWLewis).

Here’s the first clue: answer them back. It will take your campaign a few seconds. And I realize that your staff is pretty busy and probably already overwhelmed – but this is a substantive question – it’s a way to stake a position – or just engender goodwill. You don’t know me from Adam, maybe I’m a likely contributor, maybe I’m a likely volunteer. What I am – if I’m using the medium to ask you – is someone comfortable in it and most likely to echo and amplify your answers with others.

I’m not naive enough to believe you’ve actually developed a position on the matter. Your campaigns are likely just still developing your market and party tested sound bites on health care, immigration, national security, the economy. But you don’t need it. Here’s all you need: “@jasonadamyoung – thanks for the question – we’ve been focused on starting up our campaign so far – tell us what you think about it” You know what – you can use that, free of charge. Use a service like CoTweet to help spread the paste load among several of your staff.

Be human, answer questions, respond to folks. Don’t treat things like “Twitter” as a checkbox on your list to what a campaign needs – it’s not any different than having a ham biscuit on saturday morning in the country store in the myriad communities that make North Carolina great – have your ham biscuit with me and 1,000 other of your constituents in Twitter.

Either use or lose it folks – that’s your free “new media” advice of the day.

The Audacity to Review

The Audacity to Win: The Inside Story and Lessons of Barack Obama’s Historic Victory by David Plouffe


My rating: 3 of 5 stars

I am coming up this summer on 18 years experience in my chosen career profession – starting humbly by inventorying cabinets of RS-232 cables and BNC connectors and all kinds of leftover watchamacallits from my employer’s years of government contracting – to today where I do, um, er, I do, well, “computing things”

You know, I have the hardest time describing what I do. I say that I do “systems administration” and “software development” and “project management” or sometimes “cat herding” – but all of those are 10,000ft views of my job.

It gets even worse when I try to tell people what I know. One of my colleagues asked recently “How did you know that?” – and about the best I could say was well, “I just knew”. Sure, I could rattle off a whole list of technologies, but I’d forget to list more than I’d remember to list – and for anyone outside my profession – and likely for most of the people in my profession, it would sound like some mishmash of buzzword bingo. I’m a problem solver. I’m good at it, as you would hope to be after 18 years in multiple computing platforms and roles and tens of thousands of little computing problems, tens of thousands of little failures and hopefully a few successes day in and day out that burn in neural pathways so that you just know.

I get the feeling that David Plouffe is a bit in the the same boat. The man clearly just knows how to run a campaign. He helped engineer the successful presidential campaign of Barack Obama – where words like “breathtaking” “amazing” “historical” even themselves can’t capture the event. I’m not sure that it’s all that possible to use hyperbole to describe the win. No matter your politics – even those with crazy conspiratorial theories – could really counter just how much of an watershed event that win was, particularly as a “professional” endeavor.

With that win, Plouffe has likely cemented his place in the history books as one of the best, perhaps the best, campaign managers ever. The environment conditions were right for an Obama win, and David just knew how to build and manage an organization that worked within those conditions. But he has the hardest time telling you how.

The Audacity To Win does highlight some of the tactics used in the campaign, and it provides some mention of the strategy – but with a few exceptions – it all feels incredibly generic. I guess I was expecting more details, more stories, more insight into the day to day decision making. It all feels like a 10,000ft view “We met our metrics, our supporters got nervous, we stuck to our guns, we laughed, we cried, we won.”

I’m being a bit hyperbolic – the book is better and more detailed than that – but most of the time it feels like that. You just know that David is the best at what he does, but you don’t get enough information as to why or how. I don’t think that’s a flaw – it’s really, really hard, at least in my own experience, to do that. The only way I know how to do it is to tell stories and weave them together in illustrative ways. And I guess that is what I was looking for – I was looking for more stories like this (Chapter 5, “Win or Go Home” – in the run up to the Iowa Caucuses):

“In early December on a Saturday night…, all thoughts turned to the Des Moines Register poll, which was scheduled for release in the next day’s paper… Generally, polls are a dime a dozen in a presidential race, and the sheer number of them makes each one seem less important. But the release of the Register poll is considered an event. Time stops and waits for the results.

My first experience with the poll was in 1990 when I was working on Tom Harkin’s Senate race. This was before the Internet, so if you wanted the scoop on the poll you had to go down to the Register’s loading docks around midnight and persuade one of the truck drivers to give you a copy before he left on his route. Harkin’s campaign manager called me into his office on a Saturday afternoon and told me to stay out of the bars that night and instead to go down to the Register building at midnight, get a copy of the paper, and then call him at home (cell phones were just large, toaster-sized oddities in those days) to give him the results and read him the story—then he would call the senator.

Sounds pretty pro forma and uneventful, but to a wet-eared twenty-three-year-old kid it was a high honor; it made me believe I must be doing a good job to be trusted with such an important task. Since then I have never seen a Register poll without thinking of that night and of how seemingly insignificant moments like that can have an outsized impact on your professional trajectory. Now I got to play the old hand: I told our mostly under-thirty staff about how we used to get the Register poll down at the docks because there was no Internet, and they would roll their eyes and look at me like I had escaped from the set of Cocoon.”

More of those would have made the book a five star book.

You certainly don’t walk away from this book empty handed, I’ve bookmarked a number of pages in my Nook – because I think there are some tactics that the campaign employed that highlight strategies for the ways in which you successfully engage people these days. Hints to the answers to questions about how you take an organization, use technology and communication – and engage people “on the ground where they are” – and what you choose to focus on and what not to focus, even in the face of the conventional wisdom. By all measures, the Obama campaign was an incredible success – and one that seems to be built on more bedrock principles than normal – and there are things to learn from that.

I just wished there had been more insight into the day to day execution. More stories, more 10ft views rather than the 10,000ft views.

View all my reviews >>

How to lose an hour and a half without really trying.

Log in to your work gmail account and see:

(the “chat” block goes on ad infinitum)

And then watch your MailPlane application – and then Safari completely go into spinning beach ball of death. Then you:

• Test another account – works
• Test Firefox – works
• Test Chrome – works
• Remove labs, themes, clear out the inbox – go back, doesn’t work
• Uninstall flash – doesn’t work
• Resinstall flash – doesn’t work
• You try to run Safari’s dev tools before it locks up  – get incomprehensible error codes from google’s minimized js
• You get locked out of your gmail entirely because you keep trying too many different browsers
• Lather, rinse, repeat

This is the kind of stuff I really don’t enjoy about my job anymore.