Guest post: UX Booth

I wrote a 2018 User Experience Prediction at UX Booth. Amy Grace Wells asked me what I thought was going to be a leading theme in UX in the next year, and I said, “better accessibility”. I think that’s both a serious prediction and a hope, because there is never enough accessibility, but I also think we are getting better.

So many things that are designed for accessibility, but that we don’t always understand that way when they happen, and frequently we mock them as lazy or luxurious. Backup cameras on cars seem silly – why not just turn around? Until you physically can’t turn around, and then you realize how much they matter. Pre-chopped vegetables, electric can-openers, and velcro shoes seem laughable – unless you’ve ever been unable to hold something in both hands at once. In the same way, building web and mobile apps to respond to a variety of command styles may not occur to us if our fingers are nimble or our voices clear, but will matter immensely to people who are not in that category.

Since before I was employed at LaunchDarkly, I’ve been fascinated by the ability that feature flags offer designers to customize user experience. We haven’t had a good test case yet that I know of, but it will come, and I’m looking forward to it.

Peeled oranges in plastic containers

Pre-peeled oranges for accessibility

The sticker bag

I talked about this a little bit in Lady Speaker Small Talk , but let me expand.

I have a bag of stickers that I take to every conference I go to. This week, I leveled up my game from “gallon ziploc bag of significant antiquity” to “bespoke bag”. It only took me a little while to sew, but I’m super pleased with it, and it uses a fastener I got on my last trip to New York City’s garment district.

A black fabric envelope about the same size as a gallon ziploc bag of obvious age. Black envelope style bag with silver bias edging and a fancy silver buckle fastener.

I made the effort because the sticker bag is important to me — part personal brand, part conversation starter.

Array of various technology stickers More technology stickers spread on a table

I go to over 20 conferences a year, and at each one, I collect vendor and conference stickers, and I talk to the people who give them to me, and then I spread them out on a table at lunch or at the evening party and invite people to come poke through them and take away whatever they want.

This is the most genius spontaneous idea I’ve ever had, because what it gets me is:

  • Low-key, low-pressure opportunities to talk to even shy people
  • A way to talk about different technologies and what people are interested in and looking for
  • A way to gauge what a community of conference attendees is excited about
  • Memorability
  • An extremely keen understanding of the market demands and constraints around stickers

What stickers mean

I am the age to have been a Lisa Frank person growing up. I distinctly remember spending science fair reward money on freakin’ holographic unicorns. It turns out a lot of us have never entirely lost the joy of neat stickers. We put them on our computers, water bottles, notebooks, suitcases, beer fridges, whatever we can get to hold still.

We use them as affiliation identifiers. It may be an obscure sticker to everyone else, but if you care about Debian, you know when you see the Debian sticker on someone else’s gear. You know that they will probably talk to you about Debian. Now imagine leaving that kind of conversational hook twenty times over.

We use them as political statements. An EFF sticker means something, as does a sticker that says “Support your sisters, not just your cis-ters”. Rainbow/pride stickers fly out of my collection, because it’s so important to say “not everyone here is straight”.

Some people have rules about what kind of stickers they’ll use. “I only put stickers on for projects I pay money to.” or “I only use stickers from projects I use.” or “Only funny stickers” or “My laptop has a color theme.”

That all makes sense to me. In many ways, our laptops are a proxy for our faces, especially at conferences. We are hiding behind them physically or metaphorically. When we give a presentation, they peek up over the podium. When we are working in hallways, they identify our status.

Secret Sticker Rules

I think there are some generalizable rules about technology stickers. I feel so strongly about this that when I showed up for my one day in the LaunchDarkly office before I went out into the world, I spent 2 hours talking about stickers, and what I wanted to hand out.

My ideal stickers

  • Small – 2 inches is ideal. Unless you work for a company, you do not want to give them 1/6th of your available laptop space.
  • Tileable – circle stickers are selfish, because you can’t stack them or budge them against any other stickers. I prefer the hex shape, which is relatively standard, especially in open source projects, thanks to RedHat. PS – Heroku, right shape, slightly too big, and it breaks the tiling. I’m judging.
  • Funny – the Chef “sprinkle on some DevOps” stickers are hilarious, cute, and not insulting to anyone. They’re probably optimal. I also really like the Logstash stickers that were a log. With a mustache. And I begged a whole package of the “I ❤️ Pager 💩”. Because people find that hilarious. You don’t have to be funny. Other options are cute, completely straight, or your-logo-but-with-colors.
  • Have your name on them. I cannot tell you how sad it was for Influx Data when they had adorable animals with gems in them, but their name wasn’t anywhere on the stickers, and so I was like, uh, it’s a kiwi bird? From someone? Isn’t it cute? Put your name on the sticker unless you’re, like, Target or Apple.
  • Are not sexist, racist, or otherwise jerkish. I pulled out a bunch of stickers that said “UX-Men”, because while the pun was cute, the exclusion was not. I won’t put out Sumo Logic stickers, because I feel like it’s an ugly caricature. Basho was also right on that line.

I really loved the stickers the LaunchDarkly designer, Melissa came up with. Most of them are hexes, a couple are very small oblongs that fit almost anywhere, and the surprise best-moving sticker is unusually big, a representation of our astronaut, Toggle.

Parents love Toggle, love that Toggle is not gendered, and they take home a sticker for each of their kids.

Other handouts

As I’ve been going to conferences representing a company that isn’t just me, I have figured out some other things that work for me. Feature Management is a new enough market space that people don’t always know what I mean, or want something to take back to their team to explain it. Melissa and I worked together to create a small postcard that has some brand identity on the front and a couple paragraphs on the back explaining our business case. It’s small enough to shove in a pocket or conference bag, and when you get back to your desk, you may read it again to remember why you picked it up.

I also carry business cards, so that people have a way to contact me particularly. I serve as an information conduit between people thinking about how we could solve their problems, and the folks on my team who can definitively answer their questions. So if you say to me “Heidi, I’d love to do feature management, but does it respect semver?” I give you my card and you write me and then I find out yes, we have that coming in this quarter. Yay!

And, of course, I keep a few sets of LaunchDarkly stickers that are not mixed in with the general chaos of The Sticker Bag, so that I can hand them out to people as we are talking about LaunchDarkly in particular. For reasons that mystify me, while Moo has excellent card holders for their tiny cards and business cards, they don’t make ones for the postcards in either size, and looking on Amazon and Etsy was just a journey into despair and disambiguation.

So I expensed some materials and made my own, and as soon as I sort out my authentication with Instructables, I’ll post the process, but look, I made a card holder for all my cards!

Navy leather card holder in clutch size Card wallet interior, with postcards, stickers, and business cards.

The postcard side is gusseted so I can stack a few postcards in it, and the business card holder side can also hold stickers. And the whole thing is sized to fit in my hoodie pocket, because that’s what I’m wearing 95% of the time I’m on a conference floor.

What I Don’t Hand Out

T-shirts. Such a nightmare, because they’re bulky and sizing is variable, and I’m traveling light. If you want a t-shirt, write us and we will ship it to you. 😉

Socks. Because we don’t have any yet, but I continue to hope that we will get socks before the technology sock craze (Started by StitchFix, those cunning geniuses) dies out. I love tech socks. At last count, I have 22 pairs of tech socks, and my current favorite pair is from Sentry.io because they come in a version that has SCREAMING CORAL as the cuff color.

To Sum Up

When interacting with people, it’s nice to give them something tangible, but not burdensome, so they remember you fondly. Also, I’m glad I bought a sewing machine, even though it’s one of the three weeks a year a fat bike would be useful.

When the cat’s away….

…the mice will self-organize?

My manager is on vacation. Like really a lot on vacation. Logged out of Slack, not on email or phone, not showing up for meetings, none of that. This appears to be what he’s doing:

Hawaiian beach

And he’s been gone, like weeks. OK, I think it’s 2 weeks. But it is significant and meaningful, even during the weird holiday bit at the end of the year.

I have several observations about that:

  • I would like to keep working places where management gets significant breaks and takes them as breaks. It means that I also feel ok taking time off, even though it’s sometimes a little harder for my co-workers when I’m gone. Culture does come from the top, and when your culture involves actually having a life outside of work, it shows.
  • When the person you usually get your answers from is not around, you’re forced to develop alternative sources of information. This is great in a lot of ways. You don’t get rigid about your information, and the organization practices redundancy.

When you think about it, real vacations are chaos engineering for teams.

  • We did find a few little glitches in the system, things that we can either fix ahead of time or work around for next time. For example, he’s the one who schedules our retrospective, it’s not on a set day. None of us know what the parameters are. But we just didn’t have it, and next time we can set it up so it’s not a deal. Iterate.
  • On a psychologically safe team, it’s ok to make decisions without your manager around. I pushed a deadline. A coworker told me her priorities for my work. I worked with a team mate to decide where to allocate money in the coming year. It felt safe to do that, because we can trust that when our manager comes back, he’ll be glad we did our jobs instead of waiting for him.
  • The last email he sent before he left reminded us that he trusted us to do our jobs, that we could ask each other for help, and that it was ok to go to the management team if we had a need. What more could a person ask for? Autonomy and trust go so far toward making us the best and happiest we can be.
  • He’ll be a better manager for having taken time to stare at the sun and the sand without looking at a computer screen or performing work emotional labor. It is exhausting to do hiring at our current pace, because hiring is hugely emotionally intensive, if you’re doing it right. Him taking care of himself means that those of us on his team can trust that he will be available to us when we need him. That’s good planning.

So many of these observations can be summed up as trust. Leaving your team takes trust. It’s important to be trusted to do your job without close supervision. It’s really really important to feel valued without feeling like you’re trapped or obligated.

Being essential is not the same as being valued.

Have a great vacation, boss! We’ll catch you on the flip side.

Well, that didn’t go like I imagined

The Toggle Talk

As a speaker, there are three things I count on to give a talk:

  • Slides
  • Narrative flow
  • Speaker notes

My dependence on these elements decreases as I give a talk multiple times, but I use the slides to help me remember where I am in the narrative even if I don’t refer to the speaker notes often.

This fall, I designed a new talk and built it in Twine, a game engine for choose-your-own-adventure games. Each slide was actually an HTML page rendered by the game engine, and the narrative was supplied by the audience choosing from several options. This was a radical departure from my usual method, but I’d practiced it, and tuned it, and wrestled with the CSS and I felt pretty confident I could make it work, even though I wouldn’t have speaker notes or a unified narrative through-line.

Because I hadn’t solved the hosting problem yet, I needed to “play” it from my laptop, but that was no problem – I had a USB-C to HDMI adapter. The talk before mine ran long, but I only have technical problems a tiny handful of times in my talks, so I didn’t think I’d need much time to get set up.

I had reckoned without the USB-C/USB-3/HDMI problem, because it had never happened before. I always present from my ipad, and it’s usually a rock-solid toolchain. So I get up there, I’m rushed for time because of the talk before, I’m nervous because it’s the first time I’m giving this talk, and because it’s so “weird”, and…. it failed. The combination of cable/laptop/projector failed so hard that my computer rebooted and came back looking weird, and I had to accept that I might have just bricked my brand-new work laptop, in front of an audience, in a talk that had already technically started.

I had no slides.

I had no notes.

I had no narrative.

I had practiced, but I had not practiced the complete failure scenario, because it had never occurred to me that it could fail this hard.

I still managed to pull a coherent technical talk out and I only ran 10 minutes short, and honestly, it’s one of the accomplishments I’m proudest of in the last year. Literally everything went wrong and I still delivered value.

Afterwards, when I was trying to quietly dump adrenaline, I could only think about how I had failed to achieve any part of my goals. My hands were shaking, my throat was tight, and I felt a little like crying.

That wasn’t how it was supposed to go!

Later, I got to talk to people who had been in the audience, and they asked questions that they could have had if they’d gotten the real talk. That was cheering. I joked that this was the worst this talk could possibly go, because there wasn’t anything left to fail!

Then I got the speaker evaluation cards, and people were universally complimentary about my poise under tough circumstances. It hadn’t felt like poise, it felt like literal flop-sweat, like a drip from my shoulderblades to my waist. But they couldn’t feel my sweat, they could only experience my description of a brand-new talk focused on something that they had to imagine.

The webinar

One of LaunchDarkly’s goals for the year is to nurture and encourage customers to feel comfortable telling their stories, whether on stage or in a blog post. To that end, we are offering some people speaker training. Remembering my fall experiences, I solicited nice people on Twitter to come to a beta of my talk. That would give me a chance to try out the tool, the content, the process, before we offered it as a finished product.

I learned so much! Almost all of it was a little painful.

  • I need to log in early because I’m a panelist, not a host, so we need to coordinate that so I can show my slides to the webinar.
  • I did test my A/V setup!
  • I didn’t realize how unnerving it would be for me to talk to dead air. For all of my teaching/preaching/tech talks, I’ve had an audience. I can make eye contact with them, hear them start to fidget if they are checking out, notice their grins and twinkles and coughs to stay connected to them. But obviously, none of that happens when I’m talking into a headset with the audience on mute.
  • I need to do some work on the content. Not too bad, but I always have to give a talk at least once to live humans to get the suck out.
  • The lack of response makes me so nervous I talk even faster than usual. SLOW DOWN, ME.
  • I have to figure out a better way to wrap up/end the webinar. I didn’t think about how to tie it up neatly, because talks work differently.

So this is all great. When I do the webinar “for reals”, those are all mistakes that I’m not going to need to make because I know where they are.

The meta-lessons

  • It is hard to predict how you’re going to fail, but it is possible to build in a reasonable degree of redundancy.
  • Tests in isolation are not going to catch systemic problems.
  • It is better to degrade what you provide rather than failing entirely.
  • Test with a subset of users so you can predict how your solution will scale.
  • Don’t get so distracted by your failures that you fail to notice surprising data or silver linings.*

* One of the most beautiful night skies I’ve ever seen was on a winter night in the middle of a widespread blackout. I was stomping across the yard to get firewood, and I happened to look up and see the stars without light pollution. A lot of things had gone wrong, but if they hadn’t, I would not have had that moment of starlight bright enough to reflect off the snow, and the milky way like a second snowy stripe in the sky.

Shoes and software

I bought a new pair of shoes when I went to New York City the last time. I am trying to find shoes and boots that look good with both skirts and pants, fit properly, and are good for a full day of standing/7 miles of walking. This is a pretty tall order, as you know if you buy many women’s shoes. I found a pair I thought was promising and broke them in by walking 30 miles in a week in them. There was just one rub. Right over my left toe.

I complained about this to my friend when I got back, and she told me that since I’d bought them from an actual store that specializes in shoes, I could take them in and get the store to stretch a little spot over the rub. And they did! And the spot stopped rubbing. But by then I’d irritated it enough so that my regular shoes were rubbing it. Well, it’s in no way serious enough to see a podiatrist over, kind of a normal thing that happens to feet, and the advice is to wear shoes that fit you properly.

I fell down a research rabbit hole, and did you know? You can buy shoe lasts and little carved nubs that fit into the holes in the lasts, and you put them in your shoe and add some shoe stretcher, and you can tailor your shoes? Those of you in certain age and class categories, who grew up wearing leather shoes, did know this. I just learned this, in the start of my fifth decade, and it’s almost as revolutionary as when I realized I could just sew my own dresses so they fit properly. I don’t have to accept that my feet or body are just going to be slightly ill-served by the average, I can fix it. If I have the right kind of shoes and the money for the tools, which is another post.

I think this is an essential difference between software users and software creators. Software users almost always have a rub, a spot where they have to conform to the way the software expects them to behave, an irritation point. They don’t know that they could change it or they don’t have the tools to change it. It’s very “fixed mindset”. This is how the software behaves, and that’s just how it is. Software creators understand that there is almost always some way to tweak their tech to fit them better. A software package is not immutable, but rather something that you can tinker with and change – a “growth mindset”.

I want more of the world to have a growth mindset about their tech – everything from rooting their phones to eliminate software they don’t want, to turning off push notifications, to hiding screens they don’t care about. That’s one of the things I’m excited about in my work with LaunchDarkly. Currently we’re working at much larger scales than individual preferences – think about the revolution in shoes when we started designing for left and right feet – but eventually the idea that you can customize your experience of technology will get more and more accessible and democratic. That’s thrilling, because everyone should have shoes that fit their particular feet and software that fits their particular needs.

Talk slides are not a presentation deck

This year, I watched a talk called “I’m Judging Your Slides” or something like that. I watch a lot of conference talks. No, more than that. As if it were my full-time job, which it pretty much is. 25 conferences x 2 days (rough average) x 6 talks a day. Plus recorded talks.

As such:

  • I’m not going to go find the link to that presentation, sorry.
  • I have a lot of opinions about talk slides.

In this new job, I have a designer. Someone paid to have professional aesthetic opinions. This is AMAZING, and super exciting. I’m pretty sure she gets heartburn every time she looks at the spectacular pinkosity of my current slide style. She’s given us a Google Slides template to work with, and it is all branded and lovely and works with our website and has the right hex codes just built in so you can always find them instead of wandering around a color picker. I was super excited to port my slides over to the new style.

 

And then I tried to do it, and it is hard. There are a bunch of slide styles that I would never use in a talk, and I’m missing some that I really need, like section headings. What was the disconnect?

Talk Slides Are Not Presentation Slides

I realized that I wanted slides for giving talks, and the template she gave me was slides for giving presentations. That seems like a pretty subtle distinction, but it’s a very different audience and intent, so key parts are different.

If you ask someone for a presentation deck because you missed a meeting, you would get something that gave you a lot of information – facts and figures and decisions and charts. If you got the slide deck from a well-designed technical talk, it would be an unhelpful amalagam of cat pictures and command prompts.

Talk Slides

When I’m designing slides for a talk, I visualize a room that can seat about 100 people. I’m at the front of it, I have a projector with an HDMI connection, and a slide clicker. I’m standing to one side of a screen. It’s the middle of the day, and these people are sitting in hotel banquet chairs to listen to what I have to say and fight off the waves of sleepiness from catered lunch. I need to be energized, my slides need to be punchy, and my points need to connect with their needs. I am here to inform, entertain, educate, provoke thought.

Presentation Slides

Presentations are an entirely different thing. They’re being displayed on a large tv in an office meeting room. The audience is people who are thinking of themselves as “in a meeting”. The slides exist to guide thought and discussion around action items that need to happen and information that needs to be evenly distributed across a group of people who have very similar interests. Presentation slides have agendas, and points that you move through, and they are a persuasive medium in themselves, instead of relying on the speaker to add the persuasion.


Given those two very different goals, I can see why it’s hard to design slides. The majority of the advice and templates are geared toward the common case, which is a presentation deck. I have a friend who says that she works on presentation decks “every ding-dang day”. It’s no wonder that we learn to design slides with articulated points on them as the default.

I never had to do that kind of slide construction, so I didn’t build that habit, and when I started doing technical speaking, I found the spare, almost wordless style was much more effective for that audience. I was reasoning from the opposite direction.

Talk slides best practices

Given that I am probably a disaster at presentation decks, I’m not going to talk about how they should work, but here is what I feel strongly about talk slides:

  • Put your twitter handle or attribution on EVERY SLIDE. That way if you say something memorable halfway through the talk, people can attribute it properly, and every slide has the possibility to work as a standalone photo.
slide screenshot

Slide example 1

  • Except for your handle and attributions, 36 point font is a bare minimum, and I really want something closer to 48-60. Giant font means fewer words, and that’s good, for talk slides.
  • One thought per slide. You can explain it at whatever length you want, but whatever you put on the slide only needs to be a place for people’s eyes to rest while they are digesting the one thought. That thought is tied to your slide in their memories. When you switch to the next thought, change slides.
  • If you have the luxury, go look at a  presentation in the room you’ll have. Different projectors and ambient light sources can mean that a dark background or light background will work better.
  • Remember that your slides are not the persuasion, you are. I try to put information in my speaker notes for other people, but that’s a very secondary use case.

Talk write-up: Choose Your Own Deployment

Yesterday, I was in Phoenix for their first DevOps Days.


The interesting thing about doing this talk in Twine instead of my beloved Google Slides was how much I had to learn to make it look anything like I wanted. There’s a lot of CSS and Twine-specific syntax. At first, it felt like I was wasting my time and being slow because I know other people know this better than me, but as the project went on, it was honestly delightful to learn something new and get my pages to look like I wanted. There was a lot of fist-pumping success in getting a font to work.

It’s still not perfect, and I need to do some pretty drastic revisions for version 2, but now I know which of the resources are most useful to me and I have a conceptual model that I didn’t have when I started, so I think it will be easier to learn the parts I still don’t have.

It’s been a long time since I’ve had to learn something that had immediate tangible results, instead of concepts and pitches and taking what I already know and distilling it down. It was good to do that, and I should remember to schedule it into my life sometimes.

The virtuous thank-you cycle

We talk a lot about vicious cycles, and how it’s easy to end up in bad places because the incentives are all bad, but let me tell you a story.

It’s a pleasant Saturday, my family is watching Star Trek: TNG together, and I’m in my home office, working on a side project and slightly resenting it. It’s the collateral for a workshop Carol Smith and I are giving at LISA about the non-technical part of interviewing, and we think it’s really an important part of helping people get jobs. So the workshop will be great and important, but I’m currently wishing I was doing something else. And then this comes across my twitter:

Marie says she uses the principles I espoused in that talk even when she starts side projects, like Call My Congress. Because she set it up to be easily localized, anyone could come through and easily add instructions in Spanish or Somali, without having to fight the project to do it.

I gave that talk 17 times. I took it to a different continent. I got most of my expenses paid, and I got an honorarium exactly once. I figure I spent 60 hours researching and writing it, and and 3-5 hours in prep and rewriting each time I gave it. I was working for myself, so no one paid me for that time.

A thank you note like this makes that all worthwhile. I give technical talks for the same reasons that novelists say they have to write – because it’s something burning in me, and I need and want to share everything I have learned the hard way so that other people don’t have to. In my grandiose moments, I think of it as reducing the entropy of the technical world, giving people a boost up the ladder. Most of the time I think it’s funny that all of my teacher-mother’s children have found our own ways to teach, far from school classrooms.

Now I have a job that pays me for development time for talks, and means that travel and conferences are not lost productivity for me, and that means the world to me, but most of the technical speakers you see at conferences are like I was — working evenings and weekends and taking vacation time to battle entropy with education.

I’m going to try to remember to do better about saying thank you, and thus spread the cycle of appreciation further and wider. A virtuous cycle perpetuates because the rewards are so good. Thank your mentors, and the friends who want you to expand your horizons, and the organizers who make safer spaces to speak in, and the bosses who don’t make you take vacation days. Thank them publicly and specifically.

Writing exercise

As a developer advocate for LaunchDarkly, I need to understand the product in a bunch of different ways – at a technical level to give summaries of how to make integrations work, at a business level to explain how feature flags can save time and money, and at a rhetorical level, so I can quickly gauge my audience and explain it to them in the most efficient way possible. Usually when I start a new project, I’m elbow-deep in documenting how it works and I have to work backward to why people want it to work one way or another. But this time I have the luxury of learning why a product adds value first.

I wanted to make sure I was grasping it, and as my friend Laura’s dad use to say to doctoral chemistry candidates, “If you can’t explain it to this ten-year old, you need to go back and work on it until you understand it yourself.” There is an apocryphal Einstein quote to the same effect. I think the modern version of making sure you really understand something by explaining it derives from Randall Munroe’s brilliant XKCD comic, Up Goer Five. Theo Sanderson built a little text editor with a linter that rejects all the words you can’t use, which is, um, almost all the words. But if you can conceptualize something really clearly, you may be able to describe it with the extremely constrained set of words. Here is my attempt to do so for feature flags:

Computers think in lines. Sometimes we want computers to think in a new line, but it’s hard to change lines all at once. We have to build the new line before we can change to it.

When we build the new line, we give it a cool name and hide it from the computer thinking. When we are ready, we change to the new line and lose the old one. The computer thinks the new line with the cool name is the only line. We can make the computer think with the cool name line or the old line any time. Cool/old, back and forward, when we want.

Sometimes, we want only some people to see the cool-name line. We put them in a cool-name group. Every time the computer gives them a thing, they get the cool-name thing from the cool-name line. Other people still get the thing from the old line. Who is happier? Cool-name group or old-line group?

We try to keep our computers happy and not too busy. Sometimes a new line of thinking takes more work for computers. Instead of making all the computers think the new line at once, which makes them slow and sad, we only tell some of the computers to think the new line. Then we add more and more computers thinking the new line, a few at a time. Soon, all the computers are thinking the new line, but none of them got too busy.

When we are finished with the old line, we make it go away. Now cool-name line doesn’t need a cool name anymore, it is just Line. We change its name to Line. When we want to write a new cool-line, we start over!

I’d love to see the results of some of you explaining your product using a thousand words. It’s not really useful as a way to explain things to people, since we want to teach customers our words and tune our language to their needs, but it’s very useful to show us if we understand something.

New employment: LaunchDarkly

Last week I told you about my exciting new job title, Developer Advocate.

This week, let me tell you about my exciting new employer! On Monday I started a job with LaunchDarkly, a startup that does feature flags as a service.

Feature flags are a way to distribute software with reduced risk. For example, if you had a holiday-themed CSS page that you wanted to activate after Thanksgiving, but you didn’t want the risk of deploying something that might break your holiday shopping experience, you could wrap the CSS in a feature flag. Using the feature flag, you can decide when to turn on the stylesheet. You can set the percentage of people who see the stylesheet. You can even hit the emergency kill switch for the stylesheet if it does cause problems.

Feature flags can also be used to test new features for part of your audience, or to replace conditional text, or to control which customers can access premium or paid features.

There are a bunch of implications that spin off from the ability to turn features on and off quickly and reliably – it changes some core thinking about what deployment is, how we think about a product, and what we do when something goes wrong. I’m really especially looking forward to working with customers to make sure that we are using and respecting their use cases. For example, while I was at DevOpsDays, I ran into someone who asked me how LaunchDarkly worked with HIPPA standards. I get to either find or write a white paper that gives them coverage for their needs.

It’s exciting to be an an inflection point in how we think about things. It’s happened to me a couple times — full disk encryption, multi-cloud management. I think this one may be another one. Ask me about it!