Developers Are The New Mainframes

This is another one of those rambling braindump posts. I may come back for some fierce editing later, but in the meantime, here’s some light weekend lunacy. Good luck getting through it. I believe in you.

I said that thing in the title with a straight face the other day, and not without reason. Maybe not good reasons? I like the word “reason”, I like the little sleight-of-hand it does by conflating “I did this on purpose” and “I thought about this beforehand”. It may not surprise you to learn that in my life at least those two things are not the same at all. In any case this post by Moxie Marlinspike was rattling around in the back of my head when somebody asked me on IRC why it’s hard-and-probably-impossible to make a change to a website in-browser and send a meaningful diff back to the site’s author, so I rambled for a bit and ended up here.

This is something I’ve asked for in the past myself: something like dom-diff and dom-merge, so site users could share changes back with creators. All the “web frameworks” I’ve ever seen are meant to make development easier and more manageable but at the end of the day what goes over the wire is a pile of minified angle-bracket hamburger that has almost no connection the site “at rest” on the filesystem. The only way share a usable change with a site author, if it can be done at all, is to stand up a containerized version of the entire site and edit that. This disconnect between the scale of the change and the work needed to make it is, to put it mildly, a huge barrier to somebody who wants to correct a typo, tweak a color or add some alt-text to an image.

I ranted about this for a while, about how JavaScript has made classic View Source obsolete and how even if you had dom-diff and dom-merge you’d need a carefully designed JS framework underneath designed specifically to support them, and how it makes me sad that I don’t have the skill set or free time to make that happen. But I think that if you dig a little deeper, there are some cold economics underneath that whole state of affairs that are worth thinking about.

I think that the basic problem here is the misconception that federation is a feature of distributed systems. I’m pretty confident that it’s not; specifically, I believe that federated systems are a byproduct of computational scarcity.

Building and deploying federated systems has a bunch of hard tradeoffs around development, control and speed of iteration that people are stuck with when computation is so expensive that no single organization can have or do enough of it to give a service global reach. Usenet, XMPP, email and so forth were products of this mainframe-and-minicomputer era; the Web is the last and best of them.

Protocol consensus is hard, but not as hard or expensive as a room full of $40,000 or $4,000,000 computers, so you do that work and accept the fact that what you gain in distributed stability you lose in iteration speed and design flexibility. The nature of those costs means the pressure to get it pretty close to right on the first try is very high, because real opportunities to revisit will be rare and costly. You’re fighting your own established success at that point, and nothing in tech has more inertia than a status quo whose supporters think is good enough. (See also: how IPV6 has been “right around the corner” for 20 years.)

But that’s just not true anymore. If you need a few thousand more CPUs, you twiddle the dials on your S3 page and go back to unified deployment, rapid experimental iteration and trying to stay ahead of everyone else who’s doing the same. That’s how WhatsApp can deploy end to end encryption with one software update, just like that. It’s how Facebook can update a billion users’ experiences whenever they feel like it, and presumably how Twitter does whatever the hell Twitter’s doing this week. They don’t ask permission or seek consensus because they don’t have to; they deploy, test and iterate.

So the work that used to enable, support and improve federated systems now mostly exists where domain-computation is still scarce and expensive: the development process itself. Specifically the inside of developers heads, developers who stubbornly and despite our best efforts remain expensive, high-maintenance and relatively low-bandwidth, with lots of context and application-reasoning locked up in their heads and poorly distributed.

Which is to say: developers are the new mainframes.

Right now great majority of what they’re “connected” to from a development-on-device perspective are de-facto dumb terminals. Apps, iPads, Android phones. Web pages you can’t meaningfully modify for values of “meaningful” that involve upstreaming a diff. From a development perspective those are the endpoints of one-way transmissions, and there’s no way to duplex that line to receive development-effort back.

So, if that’s the trend – that is, if in general centralized-then-federated systems get reconsolidated in socially-oriented verticals, (and that’s what issue trackers are when compared to mailing lists) – then development as a practice is floating around the late middle step, but development as an end product – via cheap CPU and hackable IoT devices – that’s just getting warmed up. The obvious Next Thing in that space will be a resurgence of something like the Web, made of little things that make little decisions – effectively distributing, commodifying and democratizing programming as a product, duplexing development across those newly commodified development-nodes.

That’s the real revolution that’s coming, not the thousand-dollar juicers or the bluetooth nosehair trimmers, but the mess of tiny hackable devices that start to talk to each other via decentralized, ultracommodified feedback loops. We’re missing a few key components – bug trackers aren’t quite source-code-managers or social-ey, IoT build tools aren’t one-click-to-deploy and so forth, but eventually there will be a single standard for how these things communicate and run despite everyone’s ongoing efforts to force users into the current and very-mainframey vendor lock-in, the same way there were a bunch of proprietary transport protocols before TCP/IP settled the issue. Your smarter long-game players will be the ones betting on JavaScript to come out on top there, though it’s possible there will be other contenders.

The next step will be the social one, though “tribal” might be a better way of putting it – the eventual recentralization of this web of thing-code into cultural-preference islands making choices about how they speak to the world around them and the world speaks back. Basically a hardware scripting site with a social aspect built in, communities and trusted sources building social/subscriber model out for IoT agency. What the Web became and is still in a lot of ways becoming as we figure the hard part – the people at scale part, out. The Web of How Stuff Works.

Anyway, if you want to know what the next 15-20 years will look like, that’s the broad strokes. Probably more like 8-12, on reflection. Stuff moves pretty quick these days, but like I said, building consensus is hard. The hard part is always people. This is one of the reasons I think Mozilla’s mission is only going to get more important for the foreseeable future; the Web was the last and best of the federated systems, worth fighting for on those grounds alone, and we’re nowhere close to done learning everything it’s got to teach us about ourselves, each other and what it’s possible for us to become. It might be the last truly open, participatory system we get, ever. Consensus is hard and maybe not necessary anymore, so if we can’t keep the Web and the lessons we’ve learned and can still learn from it alive long enough to birth its descendants, we may never get a chance to build another system like it.

[minor edits since first publication. -mhoye]

In Transit

The Tunnels

X22

Southbound On Spadina

Yonge Station @ 08:30

Selfie

A Minor Hack

This is a cute trick you can do with Firefox that I happen to like.

If you’ve got a bookmark saved in your bookmarks bar, right-click it and choose “properties”; there’s a checkbox there at the bottom, a feature that time forgot, that says “Load this bookmark in the sidebar.” For the most part this doesn’t do anything you’d want, but I’ve discovered that in a few cases, being able to take a quick peek at the mobile version of a site can be surprisingly useful.

So far I’m finding this works pretty well with:

… and pretty much any site mobile/responsive enough to fit in the sidebar nicely.

Keep is particularly useful – it’s one of the best services Google’s built in a long time, but now that I can get in and out of it quickly and it syncs across devices I’m using it a lot. Between this and using BarTab Lite X and Tree Style Tab to put my tabs on the right side of my page, I’ve got web-content front and center, tools to the left, tabs to the right, and I’m pretty happy with that.

Barbiephonic (redux)

Structure

I have a funny story about the recent Hello Barbie networked-device security failure. This is doubly a repost – it started its current incarnation as a twitter rant, and longtime readers may remember it from the dim recesses of history, but the time has come for me to tell it again.

Back in 2007 Mattel had a site where they’d charge parents two bucks to have one of Mattel’s franchise characters give their child a real phone call, because people still did that in 2007. They’d let you hear the call before paying, which I suppose was good of them, but I poked around a bit and pretty quickly discovered that whatever company Mattel had hired for this was not so good with the infosec.

The subject of the calls – Dora would say it’s important to learn to read or help around the house, Barbie would tell you to work hard in school, that sort of thing – was pretty pedestrian, harmless despite the weirdly Reagan-era-esque Kid-Celebrities-Help-You-Just-Say-No-To-Drugs vibe. But the indexes on the folders storing all those component sound files they’d assemble into your custom call were wide open.

And the other thing lying around on those open shares were recordings of names. To reach a wide audience they’d recorded some unstoppably perky young woman reciting kids’ first names, Aaron, Abbot, Abby, Abigail, Adana, Adena, in an upbeat barbie-girl voice, every single one. And there I was with a pile of free disk space, university bandwidth, wget and why not.

There were seventeen thousand of them.

After a bit of experimentation, I figured out how to stitch them all together with .4 seconds of silence between each. The resulting audio file was almost five hours long; four hours and forty five minutes of relentless Barbiedoll voice reciting seventeen thousand first names in alphabetical order.

To my knowledge, nobody has ever listened to the whole thing.

Of the six attempts I’m aware of, four were called off when the death threats started, one due to the near-breakup of the couple making the attempt, and one person drinking themselves to unconsciousness at about the 90 minute mark. I’m not saying that to make a joke. I’m telling you because this is real and it’s an SCP-grade psychic biohazard. No highly esteemed deed was committed here; this is not a place of honour.

So don’t say I didn’t warn you.

For your listening pleasure: here it is.

Have a good weekend, Internet.

UPDATE: Somebody made a Youtube video.

The Thousand Year Roadmap

I made this presentation at Seneca’s FSOSS a few weeks ago; some of these ideas have been rattling around in my brain for a while, but it was the first time I’d even run through it. I was thoroughly caffeinated at the time so all of my worst verbal tics are on display, right as usual um right pause right um. But if you want to have my perspective on why free and open source software matters, why some institutions and ideas live and others die out, and how I think you should design and build organizations around your idea so that they last a few hundred years, here you go.

There are some mistakes I made, and now that I’m watching it – I meant to say “merchants” rather than “farmers”, there’s a handful of others I may come back here to note later. But I’m still reasonably happy with it.

The Devil And Strong Crypto

Period scenery-chewing aside, this is largely how I feel about strong, backdoorless cryptography.

When the last wires were tapped, your last passwords broken and the State finally turns on you, how would you hide, with all your secrets exposed? The internet is a forest of crypto from coast to coast – the user’s crypto, not the State’s – and if you cut that down, and you’re just the man to do it, do you really think you could stand upright in the winds that would blow then? Yes, I’d give the internet’s worst users the benefit of strong crypto, for my own safety’s sake.

Burning Down The Future

There’s an old line in the military: amateurs study tactics and academics study strategies, but professionals study logistics. It doesn’t matter how good your grand strategy is if you can’t feed your troops, gas up the humvees and keep planes in the air for the duration.

In the same vein, in the political arena your amateurs watch poll numbers seesaw back and forth and economists follow policies, but professionals study demographics. That’s why most of the serious talk is about redistricting and immigration. Mostly about immigration.

There are now for the first time more Canadians over 65 than children under 14. This is to put it mildly a serious problem. It does however have an obvious, straightforward solution.

The difficulty is that our current government’s policies – and more importantly, that party’s electoral goals and messaging – are fundamentally racist and xenophobic. And to what should be our collective shame, that seems to be effective. Dog-whistle lines like “old stock Canadians” and arguments about wearing head scarf to a citizenship ceremony have made it perfectly clear that despite whatever thin veneer of politeness we like to pretend makes us special, Canada has always been what our current government wants us to be: racist, xenophobic and really, really shortsighted.

Who do we think are going to buy all these houses that the sitting Government believes we should all own? Whose taxes are going to pay for the Canada Pension Plan? Young people aren’t buying cars and old people won’t be driving for long, so what will all these houses we’ve built in the suburbs be worth? What do our cities look like, when so many of them start to empty out?

For now these questions seem superficial, and those cuts will come slowly, but they’ll cut deep and may not stop when they hit bone.

But somehow the obvious solution, the one thing that prevents a looming financial implosion isn’t even up for discussion. Everyone can see the cliff coming, but the people behind the wheel would rather steer us straight for it than let anyone else drive. So despite living in one of the richest, safest countries that has ever existed in recorded history of all human civilization, enough people can be convinced to be frightened enough that we’re apparently willing to bring an entirely avoidable crisis on ourselves. We are going to deliberately throw our children’s economic future into a garbage fire for no better reason than raw xenophobic fear.

It doesn’t need to be this way.

Maybe our country should be able to see forty years ahead, instead of four months.

Maybe you should run the numbers to see what happens if you live another twenty years, and ask yourself what that really means that your retirement plan is worth 70 cents on the dollar and your grandchildren will be too busy working two shit jobs to pick up the slack.

Maybe the people who’ve told you to be frightened and angry all the time are wrong. Maybe you don’t need to feel that way.

And maybe, just maybe, a woman’s choice of headdress is not a good enough reason to burn down the future.

The Bourne Aesthetic

“The difference between something that can go wrong and something that can’t possibly go wrong is that when something that can’t possibly go wrong goes wrong it usually turns out to be impossible to get at or repair.”

–Douglas Adams

I’ve been trying to get this from draft to published for almost six months now. I might edit it later but for now, what the hell. It’s about James Bond, Jason Bourne, old laptops, economies of scale, design innovation, pragmatism at the margins and an endless supply of breadsticks.

You’re in, right?

Bond was a character that people in his era could identify with:

Think about how that works in the post war era. The office dwelling accountant/lawyer/ad man/salesman has an expense account. This covers some lunches at counters with clients, or maybe a few nice dinners. He flirts with the secretaries and receptionists and sometimes sleeps with them. He travels on business, perhaps from his suburb into Chicago, or from Chicago to Cleveland, or San Francisco to LA. His office issues him a dictaphone (he can’t type) or perhaps a rolling display case for his wares. He has a work car, maybe an Oldsmobile 88 if he’s lucky, or a Ford Falcon if he’s not. He’s working his way up to the top, but isn’t quite ready for a management slot. He wears a suit, tie and hat every day to the office. If he’s doing well he buys this downtown at a specialty men’s store. If he’s merely average, he picks this up at Macy’s, or Sears if he’s really just a regular joe. If he gets sick his employer has a nice PPO insurance plan for him.

Now look at Bond. He has an expense account, which covers extravagant dinners and breakfasts at the finest 4 star hotels and restaurants. He travels on business, to exotic places like Istanbul, Tokyo and Paris. He takes advantage of the sexual revolution (while continuing to serve his imperialist/nationalist masters) by sleeping with random women in foreign locations. He gets issued cool stuff by the office– instead of a big dictaphone that he keeps on his desk, Bond has a tiny dictaphone that he carries around with him in his pocket! He has a work car — but it’s an Aston Martin with machine guns! He’s a star, with a license to kill, but not management. Management would be boring anyways, they stay in London while Bond gets to go abroad and sleep with beautiful women. Bond always wears a suit, but they’re custom tailored of the finest materials. If he gets hurt, he has some Royal Navy doctors to fix him right up.

In today’s world, that organization man who looked up to James Bond as a kind of avatar of his hopes and dreams, no longer exists.

Who is our generations James Bond? Jason Bourne. He can’t trust his employer, who demanded ultimate loyalty and gave nothing in return. In fact, his employer is outsourcing his work to a bunch of foreign contractors who presumably work for less and ask fewer questions. He’s given up his defined benefit pension (Bourne had a military one) for an individual retirement account (safe deposit box with gold/leeching off the gf in a country with a depressed currency). In fact his employer is going to use him up until he’s useless. He can’t trust anyone, other than a few friends he’s made on the way while backpacking around. Medical care? Well that’s DIY with stolen stuff, or he gets his friends to hook him up. What kinds of cars does he have? Well no more company car for sure, he’s on his own on that, probably some kind of import job. What about work tools? Bourne is on is own there too. Sure, work initially issued him a weapon, but after that he’s got to scrounge up whatever discount stuff he can find, even when it’s an antique. He has to do more with less. And finally, Bourne survives as a result of his high priced, specialized education. He can do things few people can do – fight multiple opponents, hotwire a car, tell which guy in a restaurant can handle himself, hotwire cars, speak multiple languages and duck a surveillance tail. Oh, and like the modern, (sub)urban professional, Bourne had to mortgage his entire future to get that education. They took everything he had, and promised that if he gave himself up to the System, in return the System would take care of him.

It turned out to be a lie.

We’re all Jason Bourne now.

posted by wuwei at 1:27 AM on July 7, 2010

I think about design a lot these days, and I realize that’s about as fatuous an opener as you’re likely to read this week so I’m going to ask you to bear with me.

If you’re already rolling out your “resigned disappointment” face: believe me, I totally understand. I suspect we’ve both dealt with That Guy Who Calls Himself A Designer at some point, that particular strain of self-aggrandizing flake who’s parlayed a youth full of disdain for people who just don’t understand them into a career full of evidence they don’t understand anyone else. My current job’s many bright spots are definitely brighter for his absence, and I wish the same for you. But if it helps you get past this oddly-shaped lump of a lede, feel free to imagine me setting a pair of Raybans down next to an ornamental scarf of some kind, sipping a coffee with organic soy ingredients and a meaningless but vaguely European name, writing “Helvetica?” in a Moleskine notebook and staring pensively into the middle distance. Does my carefully manicured stubble convey the precise measure of my insouciance? Perhaps it does; perhaps I’m gazing at some everyday object nearby, pausing to sigh before employing a small gesture to convey that no, no, it’s really nothing. Insouciance is a french word, by the way. Like café. You should look it up. I know you’ve never been to Europe, I can tell.

You see? You can really let your imagination run wild here. Take the time you need to work through it. Once you’ve shaken that image off – one of my colleagues delightfully calls those guys “dribble designers” – let’s get rolling.

I think about design a lot these days, and I realize that’s about as fatuous an opener as you’re likely to read this week so I’m going to ask you to bear with me.

Very slightly more specifically I’ve been thinking about Apple’s latest Macbook, some recent retrospeculation from Lenovo, “timeless” design, spy movies and the fact that the Olive Garden at one point had a culinary institute. I promise this all makes sense in my head. If you get all the way through this and it makes sense to you too then something on the inside of your head resembles something on the inside of mine, and you’ll have to come to your own terms with that. Namasté, though. For real.

There’s an idea called “gray man” in the security business that I find interesting. They teach people to dress unobtrusively. Chinos instead of combat pants, and if you really need the extra pockets, a better design conceals them. They assume, actually, that the bad guys will shoot all the guys wearing combat pants first, just to be sure. I don’t have that as a concern, but there’s something appealingly “low-drag” about gray man theory: reduced friction with one’s environment.

– William Gibson, being interviewed at Rawr Denim

At first glance the idea that an Olive Garden Culinary Institute should exist at all squats on the line between bewildering and ridiculous. They use maybe six ingredients, and those ingredients need to be sourced at industrial scale and reliably assembled by a 22-year-old with most of a high-school education and all of a vicious hangover. How much of a culinary institute can that possibly take? In fact, at some remove the Olive Garden looks less like a restaurant chain than a supply chain that produces endless breadsticks; there doesn’t seem to be a ton of innovation here. Sure, supply chains are hard. But pouring prefab pomodoro over premade pasta, probably not.

Even so, for a few years the Tuscan Culinary Institute was a real thing, one of the many farming estates in Tuscany that have been resurrected to the service of regional gastrotourism booked by the company for a few weeks a year. Successful managers of the Garden’s ersatz-italian assembly lines could enjoy Tuscany on a corporate reward junket, and at a first glance amused disdain for the whole idea would seem to be on point.

There’s another way to look at the Tuscan Culinary Institute, though, that makes it seem valuable and maybe even inspired.

One trite but underappreciated part of the modern mid-tier supply-chain-and-franchise engine is how widely accessible serviceable and even good (if not great or world-beating) stuff has become. Coffee snobs will sneer at Starbucks, but the truck-stop tar you could get before their ascendance was dramatically worse. If you’ve already tried both restaurants in a town too remote to to be worth their while, a decent bowl of pasta, a bottle of inoffensive red and a steady supply of garlic bread starts to look like a pretty good deal.

This is one of the rare bright lights of the otherwise dismal grind of the capitalist exercise, this democratization of “good enough”. The real role of the Tuscan Culinary institute was to give chefs and managers a look at an authentic, three-star Tuscan dining experience and then ask them: with what we have to hand at the tail end of this supply chain, the pasta, the pomodoro, the breadsticks and wine, how can we give our customers 75% of that experience for 15% the cost?

It would be easy to characterize this as some sort of corporate-capitalist co-option of a hacker’s pragmatism – a lot of people have – but I don’t think that’s the right thing, or at least not the whole picture. This is a kind of design, and like any design exercise – like any tangible expression of what design is – we’re really talking about the expression and codification of values.

I don’t think it’s an accident that all the computers I bought between about 1998 about 2008 are either still in service or will still turn on if I flip the switch, but everything I’ve bought since lasts two or three years before falling over. There’s nothing magic about old tech, to be sure: in fact, the understanding that stuff breaks is baked right into their design. That’s why they’re still running: because they can be fixed. And thanks to the unfettered joys of standard interfaces some them are better today, with faster drives and better screens, than any computer I could have bought then.

The Macbook is the antithesis of this, of course. That’s what happened in 2008; the Macbook Pro started shipping with a non-removable battery.

If you haven’t played with one Apple’s flagship Macbooks, they are incredible pieces of engineering. They weigh approximately nothing. Every part of them seems like some fundamental advance in engineering and materials science. The seams are perfect; everything that can be removed, everything you can carve off a laptop and still have a laptop left, is gone.

As a result, it’s completely atomic, almost totally unrepairable. If any part of it breaks you’re hosed.

“Most people make the mistake of thinking design is what it looks like. People think it’s this veneer – that the designers are handed this box and told, ‘Make it look good!’ That’s not what we think design is. It’s not just what it looks like and feels like. Design is how it works.” – Steve Jobs

This is true, kind of; it depends on what you believe your scope of responsibility is as a designer. The question of “how a device works” is a step removed from the question of “how does a person engage with this device”; our aforementioned designer-caricature aside, most of us get that. But far more important than that is the question of how the device helps that person engage the world. And that’s where this awful contradiction comes in, because whatever that device might be, the person will never be some static object, and the world is seven billion people swimming in a boiling froth of water, oil, guns, steel, race, sex, language, wisdom, secrets, hate, love, pain and TCP/IP.

Our time is finite, and entropy is relentless: knowing that, how long should somebody be responsible for their designs? Are you responsible for what becomes of what you’ve built, over the long term? Because if you have a better way to play the long game here than “be a huge pile of rocks” you should chisel it into something. Every other thing of any complexity, anything with two moving parts to rub together that’s still usable or exists at all today has these two qualities:

  1. It can be fixed, and
  2. When it breaks, somebody cares enough about it to fix it.

And that’s where minimalism that denies the complexity of the world, that lies to itself about entropy, starts feeling like willful blindness; design that’s a thin coat of paint over that device’s relationship with the world.

More to the point, this is why the soi-disant-designer snob we were (justly and correctly) ragging on at the beginning of this seemingly-interminable-but-it-finally-feels-like-we’re-getting-somewhere blog post comes across as such a douchebag. It’s not “minimalist” if you buy a new one every two years; it’s conspicuous consumption with chamfered edges. Strip away that veneer, that coat of paint, and there are the real values designer-guy and his venti decaf soy wankaccino hold dear.

Every day I feel a tiny bit more like I can’t really rely on something I can’t repair. Not just for environmentalism’s sake, not only for the peace of mind that standard screwdrivers and available source offers, but because tools designed by people who understand something might fall over are so much more likely to have built a way to stand them back up. This is why I got unreasonably excited by Lenovo’s retro-Thinkpad surveys, despite their recent experiments in throwing user security overboard wearing factory-installed cement boots. The prospect of a laptop with modern components that you can actually maintain, much less upgrade, has become a weird niche crank-hobbyist novelty somehow.

But if your long game is longer than your workweek or your support contract, this is what a total-cost-accounting of “reduced friction with your environment” looks like. It looks like not relying on the OEM, like DIY and scrounged parts and above all knowing that you’re not paralyzed if the rules change. It’s reduced friction with an uncertain future.

I have an enormous admiration for the work Apple does, I really do. But I spend a lot of time thinking about design now, not in terms of shapes and materials but in terms of the values and principles it embodies, and it’s painfully obvious when those values are either deeply compromised or (more typically) just not visible at all. I’ve often said that I wish that I could buy hardware fractionally as good from anyone else for any amount of money, but that’s not really true. As my own priorities make participating in Apple’s vision more and more uncomfortable, what I really want is for some other manufacturer to to show that kind of commitment to their own values and building hardware that expresses them. Even if I could get to (say) 75% of those values, if one of them was maintainability – if it could be fixed a bit at a time – I bet over the long term, it would come out to (say) 15% of the cost.

Late footnote: This post at War Is Boring is on point, talking about the effects of design at the operational and logistical levels.

Catching A Moving Train

I made a joke the other day on the twitters that I was writing a job req, how I needed a way to say “Experience surfing on top of a relentless, multichannel, broad-spectrum communications avalanche a major plus”. That didn’t go over fantastically well with HR, believe you me, but it’s a real part of life here; the price of openness and transparency worth paying, steep as it is some days.

When I started at Mozilla, onboarding wasn’t really a thing. Getting started wasn’t quite “here’s your desk, here’s your password and here’s your job”, but it wasn’t a lot more than that, and there were some things we either overlooked or got wrong that made it hard to be effective for a long time. As one example – my personal favourite – I was signed up for all the mailing lists I’d need to do my job two weeks before I actually started; so thirty minutes into my first day on the new job I was two weeks behind on my email.

As of now we’re going to start doing that better, a lot better, and we’re trying to do it the way we aspire to do everything: up front and open, with no special magic or secret sauce, where people can watch us succeed or fail, and learn and grow from either one. Over the next two weeks, we’re going to be bringing in a new hire and running daily sessions to help them ramp up on the tools, technologies, processes and skills they need to be effective as a Mozilla engineer, including sessions on:

  • Bugzilla
  • Build & Go
  • Firefox, Architecture & Product
  • Communication, Community and Mentoring
  • Javascript and the DOM
  • C++ and Gecko
  • Telemetry
  • Org Structure & Career Development

These sessions will be open to attend; not just for Mozilla’s engineers, but to any community member and contributor who wishes. This is the schedule of events; we also have a streaming video link that will go live on the day of (Flash required, sadly). We’ll be documenting the process and collecting it into a single place for consumption shortly afterwards.

I’m charged with Comms & Community, so that’s just me and whatever, but myself aside the list of participants for this thing is remarkable. I don’t know if I can be specific right this second – This List Is Subject To Change Without Notice, and so on – but there is some powerhouse engineering talent running the rest of those sessions. And if you want to be a part of that, you can. If you want to sit in, learn about some part of this organization and engines it drives, you’re invited.

We’ll be reviewing the whole process as it unfolds – what works, what doesn’t, what we can learn from it – and reviewing it weeks and months later, to evaluate success, see what we’ve learned, what we’ve missed, and how we can improve. If you have feedback, send it my way; we know we have to get a lot better at this fast, and the best way we know how to do that is together.

Straps

I was complaining on Twitter that almost everyone who makes shoulder bags makes terrible straps to go with them and that it’s the most important thing to get right and nobody does and everything is terrible. You know, as one does. And I mentioned modifying my bags to make the straps work right, and people seemed interested in what I did, so off we go.

Here’s a decent enough shot of what I’ve done to the bag I bought a while ago. Briefly:

P9110849

  • That entire buckle and d-ring assembly in the upper left does one job: it moves the place you cinch down the strap from the middle of my chest, where it used to live, to the bottom of the bag. This means that lifting the bag up and cinching it snug is a single motion in one direction, instead of trying to hoist the bag upwards with one hand to get some slack while pulling down with the other to tighten it down; it makes a big difference if you’re carrying a load.
  • The metal wire you see looped through the chest buckle is insurance; might be unnecessary, but I don’t quite trust that part of this exercise to stay put on its own.
  • The small strap you see hanging off the d-ring at about 11:00 is a quick-release; set up like this it stays nice and snug until I give little tug on that and it all comes slack. You can sort of see how that works here:

P9110857

  • You can’t clip your keys easily to this strap as shipped, which really sucks. The extra d-ring in that second picture is for that.
  • The bit with the two aluminum rings there is a replaced support strap, that works the same way; I can cinch it down easily once it’s on, one loop keeps the strap from dangling everywhere and putting a thumb through the lets me pop it off easily. There’s a cheap plastic caribiner hanging off the end of the bag that I can clip those to if I’m not using them, so they stay out of the way.
  • Finally, down in the bottom right, I’ve added some extra slotted-loop rings to the ends of the straps that hold the bag closed, so that they don’t flap around everywhere either.

So there you have it. About ten bucks worth of extra bits and a bit of extra thought has moved this bag from “very good” to “close to perfect”, quickly adjustable and a little more pleasant to interact with when you’ve got a lot to carry.

This is was I was going on about on Twitter, if anyone’s still reading at this point. It doesn’t take much; a bit of consideration, getting the parts, making the change. Repairability, as always, matters way more than it seems at first. Don’t buy a work bag if you can’t replace the straps with something worthwhile; I bet eventually you’ll want to. And when the part of a thing you interact with the most somehow gets the least attention, just that little bit of giving a damn can go a very long way.