Me. On a horse.
08.29.2010 – As a teenager at the end of the seventies I was a graphic arts geek and a computer nerd. There was almost no overlap.
¶ At the end of the eighties these two worlds collided beautifully for me in Macintosh software called Hypercard, a self-contained programming and playback environment with integrated graphics tools. (I’ve written about HyperCard before in When Multimedia was Black and White.)
With projects and practice I was programming
¶ I had some previous experience with Basic, so I knew some programming concepts. With HyperCard and then SuperCard I was able to become competent enough to design and program touch screen kiosks for museums.
¶ After a few years of frequent coding I was thinking up software in smart modular ways. With my bare hands and a computer I could imagine all kinds of interactive wonder full of picture and sound and responsiveness — and then just make it happen.
Success begat bigger teams and specialization
¶ Our business grew and we hired programmers to use new tools to create cross-platform work for CD-ROMs. I concentrated on interface design, graphics and mentoring. Working in teams we made some great stuff. My experience as a programmer helped, but I wasn’t working the same brain muscles.
¶ When I looked into the new tools for myself, the cryptic syntax chilled me. The English-like syntax of HyperTalk helped me learn to program, but the skills didn’t magically transfer. Instead, I got really good with Photoshop.
Then the Web came along and the ground shifted.
¶ All of the interest in interactive shifted from media rich audiovisual experiences delivered on CD-ROMs or kiosks to mostly text augmented with pictures delivered by computer network. Rich multimedia was completed trumped by connectivity and easy delivery. (And rightly so.)
¶ Bandwidth scarcity made small file sizes essential. I was already good at making files small from cramming interactive experiences onto floppy disks. As I trusted other people to work on the programming, I put effort into being a studio graphics guru. Of course, I did lots of my own HTML, but that was just mark-up. Server-side was a complete mystery to me.
¶ At the end of the nineties I was a creative lead on web sites who used his skills as a one-time programmer to help communicate with back-end and Flash developers.
Then the web replaced itself with itself.
¶ Client-side scripting, CSS, increased bandwidth, oh my! I didn’t have to learn client-side scripting to challenge developers to make cool stuff once I saw examples that convinced me almost anything was possible. As a ‘creative’ I kept my focus on front-end skills and I learned CSS. I was pretty happy make better typography.
¶ I did a few projects were I managed to cobble together some other folks’ JavaScript into something that worked how I wanted, but if I wanted it to work differently I had to find different JavaScript, since I couldn’t really follow it.
I like to be able to finish things myself
¶ In recent years I realized I needed to be able to program more fluidly again in something to be able to explore some ideas. I found JavaScript and the DOM hardly inviting compared to the unity of HyperCard. And I still wanted to believe the messy web world of interconnected technology was somehow going to be magically replaced with something more unified.
¶ I played around with HyperCard’s progeny, Runtime Revolution, and made a good execution of bubble wrap, but it didn’t feel like an answer. I looked at other possibilities, but nothing felt right. I was beginning to think I may never really program again.
¶ At the end of the oughts I found myself wanting to program but having no language.
Fifteen years later, I learn to ♥ the web
¶ The recent Wired declaring the Web dead was just trolling. The Web is the open platform that we have, and it’s improved beyond my wildest expectations. Having been burned by proprietary platforms that made dumb moves resulting in extinction that orphaned my skills, I should have a personal stake in open systems.
¶ At Smackerel we compared notes and I was convinced it’s neither too late nor a waste of my time to learn JavaScript. For one, we need to make web pages with our own hands. For two, it’s not like the ‘document’ is the only object JavaScript might control. For three, if I could learn this I would have a leg up on every other language that doesn’t look like HyperTalk.
¶ This last month as I rebuilt my web site I faced some problems that I realized would be solved so much easier if I could just write some JavaScript.
¶ So this time I learned. I crammed some tutorials, read some of my books, and worked through some examples. And then for my web site I wrote some stuff that worked. Then I rewrote it better.
¶ While I would hardly call myself a JavaScript programmer now, I look at code that once was chicken scratch and now it makes sense.
¶ I’m back on the horse.