Blogs about meta
Way back in 2013, I decided that it would be good for my professional development for me to attend some conferences. I had just started a new job, with some savings left over from unemployment time, and so I even had some budget to attend conferences on my own dime. I had met Carter Rabasa (founder and long-time organizer of CascadiaJS) by attending the SeattleJS meetup in the previous year. So I arranged a trip to Vancouver, BC for CascadiaJS in November. On the Hacker Train up from Seattle to Vancouver, I met Tracy Hinds, who had organized the Hacker Train all the way up from Portland.
CascadiaJS 2013 was an absolute blast. The talks were interesting and educational, and I met a bunch of new (and now long-time) conf-friends and even got mistaken for a speaker! I followed new friends on Twitter, and CascadiaJS on Github. Not too long after coming home, I wrote up and posted some of my notes and published them on this blog. I knew I would be ready to do it again in 2014.
And I did. CascadiaJS 2014 was in Portland, and I bought a ticket and lodging nice and early. Beyond being excited about attending, I had even begun to think I might be able to speak. I had even submitted a talk. It was pretty awful, but that's the first step. 2014 was just as wonderful as the last year - I made sure to thank Tracy and Carter (head organizers for that year) personally, since I knew it was a ton of work to organize something so big and so lovely. (Organizing a conference is kinda like organizing a wedding, every year.) Since I followed the CascadiaJS repo, I was able to observe many parts of the organization process, and contributed some (hopefully!) helpful thoughts for the next year.
So, there you go. I got involved by attending first, providing useful feedback to the organizers, and participating in the community.
A while ago, I interviewed for a job with a company that I was absolutely in-love with. I'd been excited to see that they were looking for a front-end developer and I applied right away.
Back to the interview, we'd gone though a few basic questions and the interviewer had moved on to the algorithm questions. It was a little more complicated than Fizz Buzz, but it wasn't too tricky. But I flailed around for a while trying to both understand what the interviewer was asking, as well as trying to logic out the solution. I didn't solve the algorithm easily enough, and I didn't get any further in the interview process.
Why evaluate a front-end developer based on a algorithm? It's such a very small part of the job, and especially over a video conference after a full day of work, and it's the wrong test to get the front-end developer to demonstrate their best. It's like evaluating an NFL kicker based on their tackling skills - sure, they need to do it sometimes, but a proper blocker will always be more skilled at tackles.
Bottom line - your events (from meetup to conference) and even your open source projects need a code of conduct. What is a code of conduct?
- It is an explicit statement about what is - and isn't - appropriate in your space. It sets a social contract that every attendees agrees to, and encourages active enforcement of that social contract.
- It is a promise from you (the organizer) to me (an attendee or speaker). If you break that promise, I am 100% free to leave your project / event without any repercussions.
- It compels a response, even when the organizer would rather ignore a situation.
Let me tell you precisely how a code of conduct works to change interactions during an event.
Last year, I attended a conference as a workshop volunteer. After the workshop, a speaker from the previous day wanted to ask me some follow-up questions about the workshop. While he spoke a little English, he wanted me to step outside to the plaza where his translator was. I agreed.
Let's review the power dynamic here: me = unimportant volunteer, him = very important speaker.
He was from a country where (I suppose), it's common for men to escort women by leading them by the elbow. While we were walking outside, he put his hand on my elbow, and I (being perfectly capable of finding the doors outside) removed it. He again put his hand on my elbow and tried to lead me towards the door. I again removed it, and looked him directly in the eyes and said "no". I then stomped through the doors and found the translator. With the help of the translator, the speaker apologized if he had offended me. I said that I was fine and I answered his questions from the workshop.
Here is how the conference's code of conduct worked: I knew that - regardless of any power imbalance - the conference had my back. I was empowered to enforce my own boundaries and I did so. I was a bit irritated by the incident, but I took care of it myself. Situation resolved, no escalation, no problem. That's how a code of conduct works.
If you're trying to hire software developers (and who isn't?), then local developer conferences (and even meetups) can be really great recruiting opportunities for you. Mozilla, npm and IBM have done pretty well for themselves at CascadiaFest and JSConf in the last year.
To a degree, this depends on who you send to the event. At a developer conference, attendees probably aren't particularly keen on talking to another recruiter; but many would be open to hearing front line stories about your deployment process or upcoming projects. Send members of your technical teams to developer conferences.
Don't send jerks or dudebros. A few months ago, I was at a SeattleJS meetup and happened to be sitting near two fellows from a large and well-respected company. One of them (who really had enough salt in his hair that he ought to have known better) was fooling around with his skateboard in the office meeting space. He insisted that his colleague "video my kick flips"; and inevitably smacked other peoples' chairs when he lost control of his skateboard. Don't send that person. Send your outgoing and thoughtful developers, who can talk in detail about your organization's work without insulting other technology choices.
Do remember to compensate your people with time off if these events fall outside normal working hours. Your developers shouldn't have to do free recruiting work in their off-hours.
If you're organizing a conference, one of the most important tasks is selecting speakers who will give unique and interesting talks to your attendees. But you've also got your budget to worry about...
Whether or not you can pay for your speakers' conference ticket and travel costs is one of the biggest factors in determining who can speak at your conference. There are few types of people who are generally more able to speak at conferences than others. To illustrate this, let us take a look at Earth 517, where StickerConf (the nation's most prestigious annual conference for sticker designers and developers) has just opened their speaker application process. These are some of the people who are thinking of applying:
Logan is the best there is at making stickers, bub. His sticker consultancy has been in business for decades and he is a common fixture at conferences. He is a popular speaker, but his well-worn talks always seem to cover the same material.
Just like last year, Logan will apply to speak at StickerConf, and will pay travel and ticket costs with his company's finances.
Scott is a committed single father. As a widower, he is the sole wage-earner and caretaker for his children Rachel (4 years old) and Nathan (1 year old). Scott's independent shop has been a leader in the sticker-making industry since the beginning, but these days he only has time for two things: parenting and making stickers.
Scott can't afford to pay his own way to StickerConf; there are college funds which need to be filled. Taking days off from his work to prepare a talk and to speak at StickerConf is already a significant commitment. If StickerConf won't cover his travel and ticket costs, Scott won't apply to speak.
Ororo is an industry longtimer and senior director at the largest sticker factory in the US. Her first priority is her career and managing her team at the sticker factory. The factory doesn't cover conferences, so she uses her own vacation time to attend and speak at a few conferences each year. Due to her busy schedule, she often neglects her own personal time.
Having already agreed to speak 2 other conferences this year, Ororo has room for perhaps one more new talk in her schedule. She will apply to speak at StickerConf if her costs are covered, but otherwise is considering taking a real vacation.
Hank is a tenured professor at a university where he teaches several courses on sticker making. He has a well honed stage presence, and years of experience teaching the traditional and theoretical methods. However, without any real world experience, his talks haven't changed much over the years.
Hank gets ample time off during school breaks, and a yearly stipend from the university for conferences and travel. He enjoys learning new things at StickerConf, and will apply to speak every year.
Warren is an entrepreneur who founded StickrIO a few years ago. He has managed to speak at a few conferences in the past year, and he has had a really great time talking to the community and increasing awareness of StickrIO.
Warren will apply for every speaking slot he can find, polish up his slide deck in the week before the conference, and StickrIO will pay his travel costs.
Kitty is attending state college on a full ride scholarship, and next year she will graduate with a degree in Sticker Sciences. As a full-time student with no parental support, she is broke as heck. But she is heading straight towards a career in sticker making and has been watching StickerConf's talk videos on YouTube for years.
She would like to share her fresh perspective with the professional sticker community; as well as to meet all the people that she has admired from afar. A quick peek ahead in Earth 517's timeline shows that one face-to-face conversation with Scott will give Kitty an insight which enables her to complete the breakthrough new sticker adhesive that she's got brewing in the school lab. But if StickerConf won't cover her ticket and travel expenses, Kitty can't speak.
Based on these profiles, if StickerConf does not cover travel and ticket costs for their speakers, they will only receive talk proposals from Logan, Hank, and Warren. However, if StickerConf is able to cover speakers' costs, they will have a much wider variety of talks to choose from. In fact, the lack of expense reimbursement tends to play a larger role in talk submissions for under-represented people than it does for those who are not.
More blogs about meta: