Live-Tweeting for Fame and Fortune

That’s a joke. I have made $65 off 4 years of live-tweeting, and it’s more than I ever expected. As far as fame, the point is not for me to get famous, but to promote some amazing speakers as they do their thing.

I don’t know about you, but I have about 20 tabs open in my browser with technical talks that I’m excited about seeing and will get around to anytime now. As soon as I have 45 minutes that I’m not doing something else. Don’t @ me.

It is hard to make space in our lives to consume technical talks. It is much easier to consume a tweetstream that summarizes the key points of the talk.

So what is it that makes live-tweeting successful, and what are some things to avoid?

Tools

Hardware

I use an iPad as my main conference-going computer. It’s powerful enough to write on, remarkably unfussy about connecting to a conference wifi, and small and cheap enough that losing it will not be catastrophic. I also present from my iPad, but that’s a different story.

I’ve paired that with a bluetooth keyboard that I bought with some of my donations. I like the combination because I can set it in my lap or use in in a number of weird orientations. I’m a pretty fast touch-typist, so I can take notes quickly enough that I can capture most main points.

I have a wifi hotspot that I keep in my go bag. I’ve had very few problems at conferences in the last year or two, but before that, there was a pretty good chance that a technology conference would overwhelm whatever wifi infrastructure the venue had set up.

My final hardware investment is an iPad case that allows me to prop it in several different configurations, including horizontal and vertical. I always choose the ones in screaming pink/fuschia/etc, because I’m pretty sure that “girly” looking technology is less likely to be “accidentally” picked up by someone else. Also, it’s very on-brand!

That’s me, in the pink hair, live-tweeting from The Lead Developer New York 2017. You can see the keyboard and iPad balanced in my lap. (It’s a great conference!)

Software

I am an enormous fan of NoterLive by Kevin Marks. I met him at Nodevember in 2016, I think, and he has created an amazing tool for live-tweeting.

  • Prepends the conference hashtag(s) and speaker name for every tweet, so you don’t have to retype them every time (although if you get it wrong, it will be a lot wrong)
  • Automatically threads until you tell it to stop
  • Local caching and logging

Pretty much all I have to do is set the conference hashtag by the day, start a new thread, set the speaker, and then I can type without worrying about it and the tweet is sent every time I hit enter.

It’s aware of character limits and will give you notice when you’re approaching it. The only thing that’s a tiny bit hinky, and I still don’t know if it’s happening, is that it will sometimes attempt to make a link if I have some combination of a period and spaces. It doesn’t send the link, but it throws the character count off.

💖

I use TweetBot on my iPad to watch the conference hashtag and retweet things that are cool and relevant that I didn’t get noted or didn’t see. The new TweetBot for Mac just came out, and they finally have a dark theme and a much better way of handling and viewing lists.

I used Storify to compile all the tweets about my talks and weave a loose story about the experience, but it’s gone and I am very sad and I’ve not yet found a replacement.

Techniques

For Speakers

  • Put your handle on every. single. slide. No, I am not kidding. I want to be able to attribute your stuff properly, and if I slide in 2 minutes late and miss your first slide, then I have to spend 3 minutes hacking around the conference site to find it.
  • Put the conference you’re at in your Twitter display name. That allows people to mute if they want, and it makes you easier to find and correctly identify.
  • If you don’t use Twitter, give us some other way to attribute you, because attribution matters.
  • Follow the code of conduct. A live-tweeter in your talk is a great force for good, until you piss them off, and then they’re going to take pictures of your offensive slides and drag you.
  • Turn off all notifications before you get on stage. It’s super distracting to have your phone freaking out at you while you’re trying to speak and even worse if it’s your laptop.

For Tweeters

This is actually just the set of rules I try to follow for myself. There isn’t really a journalistic code of ethics for tweeting.

  • Attribute ideas properly. If a speaker is quoting someone else, do your best to make that clear.
  • If you are making an aside, try to set it off in some way. I use (parentheses), and @lizthegrey uses [ed: ], but as long as it’s clear you’re commenting on the content and not reporting, anything works.
  • You do not have to exactly quote what someone says. Paraphrasing is the norm. If there’s some especially unique phrase and you have space to get it in, you can put quotes around it, otherwise you can just do your best to approximate the concepts.
  • If you’re taking a picture to go with a tweet, it doesn’t have to be perfect, but do avoid making the speaker look unreasonably dippy. It turns out it’s hard to speak without sometimes making extremely weird faces.
  • Use hashtags and threads to make it possible for your regular followers to block the tweetstorm out. Not everyone is here to read 200 conference tweets.
  • Put the conference you’re at in your Twitter display name. That allows people to mute if they want, and it makes you easier to find and correctly identify.

Let’s Not

There are some anti-patterns that I’d like you to try to avoid:

  • Just transcribing the slides for a talk
  • Commenting on anything about the speaker’s appearance
  • Negativity in general, really. I mean, why waste your precious conference time and dollars hate-watching a talk and tweeting about it? Get up and go do something else. You’re allowed.
  • Violating a speaker’s publicity preferences. If they have a “No Photos” lanyard, don’t take photos.

Add To Your Lists

@lizhenry – the OG livetweeter, the one I learned so much from. Good for Mozilla information, politics, and feminist poetry.

@cczona – the mind behind Consequences of an Insightful Algorithm AND @Callbackwomen. Excellent at pointing out connections between different threads of technical talks and the implications of them.

@lizthegrey – Google SRE, badass speaker in her own right, and excellent at documenting and commenting on lots of topics, especially resiliency.

@EmilyGorcenski – livetweeting not just technical conferences, but resistance politics.

@CateHstn – Thoughtful blogger and live-tweeter operating at the intersection of dev and management.

@bridgetkromhout – indefatigable DevOps organizer and excellent live-tweeter. She actually manages to take pictures and livetweets from her phone. I’m in awe, honestly.

@whereistanya – a systems thinker who managers to pull tweets and blog posts together and make you see a side of the talk that you might not have recognized.

@GeekManager – conference organizer and integrative thinking on the bleeding edge of the humane treatment of developers who end up managing.

@QuinnyPig – Not always a perfectly accurate rendition, but always funny (and clear) about the divergence

@MattStratton – brings an insider perspective to talks, which allows him to point out connections you may not have thought of.

@skimbrel – technical expertise from an unapologetically queer viewpoint. It’s not paranoia if they’re really out to get you.

Using Airtable to Manage Conference Submissions

I know, it’s not a very catchy title, but it is descriptive.

A large part of my current job is speaking at conferences and talking about feature flags, systems resiliency, and whatever else I can talk people into. And part of speaking at conferences is applying to lots and lots of conferences. But how do you keep track of it all?

At first I tried to use Google Calendar, but that did’t work. I tried Trello, but there weren’t enough dimensions. I wanted to track these elements:

  • Name
  • Location
  • Start date
  • End date
  • Talks submitted
  • Submitted/accepted/rejected/conflict
  • Speaker tasks
  • Tasks remaining

That’s a lot! I complained about the problem, and Thursday Bram suggested Airtable, as a beautiful mashup of a taskboard and a spreadsheet. Since then, I’ve suggested it to several other developer relations people and I know some of them are using it. I’m now paying for the full version, which gives me the calendar view, and that’s been my killer feature. It really helps me to be realistic about how conferences stack and overlap with each other.

Spreadsheet

Airtable main view

This is the main view. I have it sorted so that conferences that are over or that have not accepted any talks from me are not showing, because I really only need to know about what is coming or may be coming. I’ve grouped it by the Talk Accepted dimension and then the date. At a glance, I can tell what I have coming, and what talk I’m giving (if I remembered to enter it, because I’m sometimes not great at that, as you can see.

Cards

I can drill down into any talk title for a card that has a bunch of information on the talk. Frequently I include the proposal I submitted here, along with information about how far along in the process of creation the talk is, all configured by me. Have I drafted it? Made slides? Practiced it on my own or in front of other people?

Cards Pt. 2

Further down on the talk card, I can see all the conferences I submitted the talk to and whether it was accepted or not. That gives me a good overview of whether a talk is “wearing out” or less likely to be accepted than another kind of talk. It’s useful information.

All of those features are available at the free level, and it’s powerful enough for most people, but did I mention I apply to a lot of conferences? More than there are weeks. You probably don’t need the full version.

Calendar View

Airtable calendar view

This view right here is worth everything I spend on Airtable, and I’m certainly not a power user. But it tells me about conflicts in a way that has been very hard for me to predict from just looking at dates. (If we were all good at predicting conflicts from dates and times, we would not have Outlook Meetings Calendar, is what I’m saying) Now I can tell ahead of time that I can only accept one of those three conferences starting on the 24th, and that allows me to be a more polite speaker. Sometimes it’s possible to look at this and make better arrangements. For example, DevOpsDays Chicago is a great event, but it’s literally the day before I need to be in Dusseldorf. Rather than discombobulating myself or the conferences, I can ask now, months ahead of time, to speak on the first day of DevOpsDays Chicago and toward the end of SRECon. That gives me an error budget for weather/flights/etc. Most conference organizers are lovely about helping me out with these things.

Conclusion

Airtable is a super useful tool for being able to organize data when some parts of it are fixed and some parts change and you need to be able to keep the associations together. There are bigger, more heavyweight databases that can do that, of course, but this is a pretty, friendly, usable implementation of the theory.

If you’re interested in trying it yourself, here is a link to the original workspace I set up: Heidi’s Conferences. Feel free to give it a spin or fork it for your own needs.

This job is undoing me

… in the best way possible.

My protective casing of hard-earned cynicism is being rubbed away by all this genuine kindness, cooperation, good culture, and all that jazz. It’s honestly kind of uncomfortable, like molting.

You need to understand – I have this hard-ass candy shell for a reason. My first job in technology was 1996. My first college boyfriend introduced me to BBSing through what we would now call a troll community. I have been “one of the guys”, and “that girl”, and “the writer, whats-her-name”. I have gotten my ass grabbed at work and gotten dirty texts and chats from co-workers and been propositioned in creepy ways at conferences. The technical writer is hired too late and fired early in the startup process, but I love startups. No company has ever previously make me feel like I have valuable things to contribute and they consider themselves lucky to have me.

I thought at first it was perhaps due to the change in my role, this exciting new job title that means I never have to write release notes, but today I realized that it wasn’t that. I was walking with the new person on my team, and trying to download to her what I’ve learned about the company and the things I asked about and can just tell her.

  1. You will not get fired because The Internet Hate Machine is angry about something. We know about the internet hate machine and don’t consider them valuable feedback.
  2. No one is going to yell at you if you mess up your expense accounting, especially at the beginning. We’re all working from a place of mutual respect and shared interested and assumed good intentions.
  3. You are not required to sacrifice quality of life to save company money. Be reasonable, stick to the budget outlines, but it is worth a hotel night to have you bright and functional instead of trying do do a conference after an early morning flight.
  4. You have time to learn your job. We’ll be happy as soon as you contribute, but you need time to ramp up and that’s expected and normal.
  5. It’s ok to ask questions. No one expects you to know everything, we hired you because we think you have the potential to learn. Very few of us knew about this technology or industry when we started. You don’t have to know it all when you start.
  6. Maintaining human relationships with your coworkers and other people in our ecosphere is important, and will be counted as work, not fluff.
  7. If something happens at home while you’re on a business trip and you need to leave, it’s ok to just leave. No single event is more important than your outside-of-work life.

How am I supposed to maintain a cheerful cynicism about people who genuinely like working together and also sometimes hanging out at tea parlors with a kid in tow? How is my cool detachment going to go when I get raises and positive feedback without even asking for it? What if it doesn’t feel like high-stakes gambling to be able to bring my whole self to work, even the wacky futurist parts and the parts that can’t code and the parts that are noisy feminist politics? What if “being me” is not high stakes, but table stakes, for everyone?

This job is breaking me because all of that shielding and cynicism were adaptive for other companies, but not actually very useful at this one, and in order to succeed here, I need to take all that armor off and be real, and vulnerable, and let people help me. It’s terrifying, and I wouldn’t have it any other way.

@wiredferret is so composed, informative, and present as a speaker

I Have Something To Say

That was the tagline for the late lamented Technically Speaking organization, and I really like it because it captures one of the really important parts of speaking – all of us have unique insights and perspectives, and even if you say something, I still have something to say that will be different.

As I learn and grow in the craft of speaking and giving talks, I have been thinking about what it is that I’m trying to achieve, what I would consider growth and leveling up. It’s important to not rest on our previous accomplishments – that leads to stagnation and that miserable stuck feeling.

I want to improve my delivery. I want to improve my slide construction. I want to branch out into different types of conferences. And I want to give a keynote.

When I told my manager this, he challenged me to identify what it is about a keynote that I want to have, that makes it different from the talks I’ve been doing already. After a bit of thought, I realized that the nature of a keynote means that you have a chance to talk to an audience who would not normally select your talk in a multi-track conference. No matter how good my documentation talk is, only people who care about documentation will choose to attend it, even though the people who need a documentation talk may not. I want to reach that reluctant audience, the people who don’t think they need to be in my talk.

What is a keynote?

In a technical conference, a keynote is addressed to the entire conference, and usually happens at the beginning or end of the day. Keynotes are thematically linked to the conference, or are presented by “big names”. They are the one experience you can expect everyone at a conference to share. Even single-track conferences have keynotes – they might be longer than the rest of the talk, or include a special introduction, or the speaker might be a promotional pull.

By content, a keynote either has something relevant to the community, like Matz’s Ruby updates at RubyConf; or it’s something that is broader than any one kind of technology, like Carina Zona’s “Consequences of an Insightful Algorithm”.

Organizationally, keynotes are almost always invited, rather than being part of the CFP/application process. The organizers select speakers and reach out to them with a specific invitation. The topic may be negotiated, but keynote speakers traditionally have a lot of latitude in their topic choice.

How might I get one?

Keynote elements

I think there are three elements involved in being invited to give a keynote:

  • Professional reputation
  • Proven speaking and delivery ability
  • Timely, relevant topics

I feel like I can work on all of those points, in different ways.

My professional reputation will depend on me continuing to do what I do as well as I can – speaking, teaching, mentoring, coaching, being available to help people with their needs whenever I can.

Speaking ability – I only have a smidgen of training in this. My high school didn’t have speech and debate, I didn’t participate in college, I’ve been pretty much getting along with a lot of self-education. I am thinking it might be time to get some real training and coaching. This is probably the aspect that scares me most — it’s really hard to get coached on something, especially if you think you’re pretty good at it. But it’s a way to get better, just like watching the talks I’ve done helps me get better, even though I really hate doing it. If you watch yourself speak enough times, you sort of burn past the shame and get to the place where you can improve by watching.

Timely topics — You always have to lead your target, and I want to put together a couple proposals for general-interest topics that haven’t been extensively covered yet. More on that later.

What I’m going to do

So my plan is multi-part. It all is underpinned by me doing a lot of work to remind myself that it is ok to publicly want a thing and publicly talk about wanting it. That’s hard to do.

Ask

I am trying to talk to all the people I meet in my conference rounds about wanting a chance to keynote. This has three effects:

  • It gets people to think of the possibility of inviting me
  • It normalizes people asking about keynoting, especially if they aren’t in the normal demographic of CEO/powerful person/known famous coder
  • It teaches me more about how to ask for big things, and gives me more experience in doing slightly anxiety-inducing things.

Write

I need a couple topics to tease people with – things that are interesting, timely, and appropriate for a larger audience. Here are the two I’m thinking about, in CFP pitch format

Master Builder and the Growth Mindset

A lot of us got told we were smart growing up, and looking around at our pretty nice lives, it’s easy to believe that. But what if I told you that you are successful despite this compliment, not because of it? It’s bad for our sense of experimentation and willingness to fail to be told that we’re smart. We tend to gravitate to learning and doing things we’re good at with less effort. We avoid things that we won’t be good at instantly because we don’t know how to be mediocre.

Getting into technology is like being able to assemble a Lego set – there are easy instructions, you assemble the modules, and you end up with what you saw on the box. But not all of us are issued a box. Some of us have had to learn to be master builders, able to design and construct new and weird things that are not part of the kit. This experimentation and improvisation can provide us with flexibility and insight in a rapidly-changing industry.

This talk is intended for people who are interested in designing and working on teams full of people who value experimentation as well as execution.

Everything Is A Little Bit Broken
-OR-
The Illusion of Control

Humankind is extremely superstitious and we are operating systems way above our actual level of comprehension. To keep our limbic systems from freaking out, we have a set of beliefs that makes us feel like we have control over things that happen around us – but are we right? Let’s talk about how error budgets, layered access, and function over form are the building blocks of the ability to get on with work without decision paralysis.

This talk is about how we shift risk around with both process changes and magical thinking, and how we can use our tendency to be fearful to actually make things safer, instead of just feeling safer.

This talk is intended to challenge and shake up people who think that failure is a single state or that doing everything right will lead to predictable results.

Study and Learn

I’m going to find myself a speaking coach, or maybe a course. Something to take what I already have and polish and refine it. No one knows how to do a triple lutz on their own, and coaching is the difference between talent and success. Like I said, this is really hard for me. Like a lot of gifted kids, I’ve gotten a long way on sheer talent without having to be bad at something. Luckily for me, I also have spent sometime sucking at things, being coached, and getting better. It took me 6 years to learn to serve a volleyball overhand, but I got there. I want to level up my speaking from “good enough/pretty good” to “reliably excellent”.


It’s a big goal, but I think I have a good plan in place, and I’ll let you know how it goes.

Welcome!

Teaching and learning

At LaunchDarkly, we’ve been hiring really aggressively, because we’re doing amazing things. (Come work with me!)

That means that we are also doing a bunch of training, and I’ve been working on doing the training for our non-technical employees, folks like marketing, design, outbound sales. They’re important to our success and they have a TON of domain knowledge that I don’t have, but we’re all going to work together more successfully if they know what they’re selling. Also, selfishly, the more people who can help work a table at a conference, the easier it is for everyone working at the conference.

Me, I’ve been doing tech for 20 years, at all levels, including hardware through to cloud. I bring a ton of domain knowledge with me every time I start a new job. But for this training, we need to explain enough about the software lifecycle to be able to talk about the problems that LaunchDarkly solves. That gave me a chance to really dig in and figure out how to explain the basics in a way that’s useful to people who haven’t been accidentally drinking from the devops firehose.

  • What are developers trying to do? What does their work life look like?
  • What is deployment and how is it hard?
  • How does software get to the user?
  • What are waterfall and agile and how does that relate to us?
  • What are APIs, SDKs, CDNs, CI/CD, devops, feature flags, polling and streaming updates?
  • What’s a monolith vs a microservice?
  • Why wouldn’t everyone just build their own software?
  • What is Software as a Service?

It was satisfying to realize that I can define and describe all of that in pithy and accessible terms for people. It’s the same thrill I get from writing a really solid document. I know that I am helping actual humans by describing something they need at the moment they need it.

I hadn’t thought about internal training as being part of my job duties, but when we realized we needed it, it seemed logical and easy to do it. After all, my whole purpose is explaining the product to people, and understanding and explaining people’s pain points to my company. This is a natural fit. Plus it was super fun!

In my infinite free time, I’m thinking about recording these explanations with a couple slides, so we have bite-sized concepts when people want to look them up.

 

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.