Speak at a meetup

Dear new developer,

Go out and speak at a meetup. This will have the following benefits:

  • Decrease your fear of public speaking
  • Increase your knowledge of a topic
  • Help build a community of developers
  • Build your public profile
  • Teach others something useful

You don’t have to do this every quarter or every year, but I challenge you to do this at least twice because the benefits are so large.

How can you do this? Let me give you a six step process.

  • Think of a topic. Two options:
    • Consider a problem you solved recently. Could be on a side project, could be on a work project (if it is directly related to company IP, discuss with your manager at a one-to-one), could be something you just read about and dug into.
    • Alternatively, think of something new you have heard of, whether from a friend, a colleague, an online community or someplace else, that you want to learn more about.
  • Spend 15 minutes outlining what you’d talk about, if you were to give a talk on this topic. A set of bullet points is fine at this point in time.
  • Search for a meetup in the technology you are using in your geographic area (if you want to present in person) or one in a good timezone (if presenting on Zoom is ok). All other things being equal, I’d suggest presenting in person for your first time, as audiences *feel* more sympathetic in person.
    • Don’t use the meetup search engine, it’s really hard to use. Use Google instead. Here’s a good search term if you were in Colorado and wanted to present something related to the Ruby ecosystem: ruby meetup colorado USA.
  • Send a message to one to three interesting meetups: “I’d like to present on <topic> at your meetup. I’m a new software developer.” Follow up two times since people are busy. Make sure you understand the amount of time you have and the exact date they want you to present, including timezone. It’s best to commit a few months out if you haven’t written the presentation already.
  • After they say “yes”, get to work on writing the presentation. Don’t be fancy, just expand the outline. Bring your own story and touches. Some people like to sprinkle humor (like memes), others personal touches, others code examples. It’s all good. You can watch presentations on youtube, sometimes from that same meetup, if you want to learn more.
  • Show up and present.

Once you have the organizers attention, they will want the following before you can present:

  • Talk title
  • Talk description
  • Bio

Some of them may want:

  • A picture of you. Use something that looks professional; anything you would feel comfortable being on LinkedIn. If you don’t have a headshot (no reason you would), have a friend take a photo of you from the shoulders up dressed professionally in front of a white/light background. Don’t obsess about this.
  • Your presentation. Ask when they want it and deliver it. I like google slides if you will have network access, but any presentation software package will work.
  • Examples of previous presentations. Here, feel free to explain you haven’t presented in the past (if that is true); this meetup may not be a good fit.

Common objections include:

  • Will my work allow this?
    • Ask. If you are doing it on your time, not portraying yourself as a representative of the company, and not revealing work secrets, most employers will have no problem with this.
  • It sounds like a lot of effort.
    • Yes, the first time it is. It gets easier. You may want to find a few meetups to give the same talk to, so that you can amortize the effort.
  • I’m not a public speaker!
    • Did you know how to ride a bike the first time you hopped on one? Not everyone can be a great public speaker, just like not everyone can ride in the Tour de France. But everyone can be a good public speaker.
  • I don’t have time.
    • Can you carve out 5-10 hours over 3 months? That’s enough time.
  • What are the benefits again?
    • You’ll learn a new skill, help promote a software community, make new friends, have something you can put on your resume, learn a topic more deeply and become known to other developers in the area (either geographic area or technical area).

Final suggestions:

  • Don’t bail. Ever.
  • Follow up with them a week before to reiterate your commitment and availability.
  • Ask if you can publicize it, and share it with your network. Some other folks may be interested in showing up to learn things and/or supporting you.
  • If you have to bail, give plenty of notice and see if you can find someone else to give a similar presentation. The organizers may not take you up, but the effort will be appreciated.
  • Practice it beforehand (I like to do that 2-3 times), but realize you won’t have it perfect.
  • Realize that by dint of your effort, you will be one of the experts in the room. That can help with your confidence.

Doing this will at least a few times challenge you and help you grow. You may find you love it. You may do two and never present again, but the ability to teach in public is a skill that will be helpful to you in many work scenarios.



Your network increases optionality

This is a guest post from Karl Hughes. Enjoy.

Dear new developer,

I was in your shoes in 2011. I was finishing up a degree in mechanical engineering that I would never use and looking for a way to join a startup as a software developer.

Maybe it was the entrepreneur in me, and maybe it was just naivety, but instead of applying for jobs, I decided to start emailing interesting companies instead. I made a list of technology startups in the education industry and emailed each of them my pitch.

Two of them got back to me and one (Uloop) had an office three hours away in Nashville. I drove to meet their CEO and after a few conversations, they brought me on as a freelancer. When I graduated a few months later, they offered me a full-time role managing their blog and writing custom WordPress plugins.

Since then, I’ve worked at three different edtech startups and never once had a formal “job interview.” Every company I’ve worked for has hired me because I met someone there and stayed in touch for months. When a job opened up, they reached out to me to see if I was interested.

My first job hunt showed me that your strength as a software developer is not in your resume, your knowledge of algorithms, your ability to keep up with the hottest frameworks, or even your problem-solving skills. The most powerful tool you have is your network.

The Employer’s Perspective

As a job-seeker, you know that looking for a job is scary, but from an employer’s perspective, hiring is scary too.

After sitting in the hiring manager’s seat several times in the past few years, I can tell you that I’m as scared of hiring the wrong person as you are of screwing up the job interview. If I make a bad hire, I look bad to my boss, and my team’s productivity will suffer. Having to fire someone kills morale and hurts the manager’s reputation, so nobody wants to do it.

This fear is why managers look for people in their networks or work with recruiters. The very last place employers look for applicants is the cold resume bin.

How I Built My Network

If you want to avoid the black hole of submitting your resume online, you need to build a network. I don’t know you well enough to give you a perfect formula for your situation, so I’ll just tell you how I built my network. I hope some of these ideas resonate.

First, I started as a freelancer before I ever had a “real” job as a programmer. Most people don’t recommend this approach for new developers, but it forced me to learn to “sell” myself really well. When I started with Uloop, I often had no idea how to accomplish a task, but I bet that I could learn it before they discovered I was making it up.

After getting that first job, I started attending meetups and conferences regularly. Uloop was a small company, so there wasn’t much opportunity to network within the organization, but I had moved to Chicago, where there were plenty of programming meetups and tech events to attend.

I tried meeting people at these events, but it was hard. I’m not that outgoing, so instead, I would email the event’s speaker or organizer afterward and invite them to a one-on-one coffee or lunch. Some of the people I met like this are among my closest mentors and friends today.

As I attended more meetups and got to know speakers and leaders, people started inviting me to give back. I was little more than a junior developer at the time, but I was asked to speak at bootcamps, meetups, and even a couple of small conferences because of my network.

Naturally, I was nervous the first few times I got up in front of a group to share my experience. I knew there were people in the crowd with decades of experience on me, and I expected them to stand up and call me out if I made any mistakes. I found that practice and gradually increasing the stakes helped me. By trying a talk out at a local meetup and slowly working up to larger audiences at a conference, I gained confidence over time.

Giving a talk at a meetup or conference is a lot of work, and you don’t typically get paid for it. That said, I knew how helpful it was hearing developers who were more experienced than me back when I was first learning to code, so I have always enjoyed the opportunity to give back.

One side effect of speaking is that you get even more opportunities to increase your network. At some point, I switched from being the one asking speakers to meet with me to the one that attendees were asking to speak with. I always enjoy these interactions with new developers, and the opportunity to encourage or help others is my primary motivation for speaking and writing this letter.

Keeping in Touch

Everyone who talks about networking tells you to go out and meet more people, but that’s worthless if you don’t keep in touch with anyone. As I started to meet more people in Chicago, I realized that I needed to come up with a way to have more encounters with each of them.

“It takes on average about 3 encounters — and by that I mean intentional rather than passing interactions where you’ve gotten together primarily to just hang out — to really see if there’s potential for a relationship with someone.” – Brett McKay

The first step was to start a spreadsheet of people I wanted to keep up with. Most of them were more experienced than me, but many were peers or newer developers I “clicked” with or found interesting.

Next, I made a reminder to reach out to 1-2 people on the list every week. I’d ask how they were doing and see if they wanted to get lunch or coffee sometime. I tried to find organic reasons to connect (birthdays, an article related to their industry, etc.) and ask them questions about their lives. One of the easiest ways to make someone like you is to get them talking about something they like. People love talking about themselves.

While this sounds calculated, I do genuinely enjoy these conversations. We’re all busy, but having a system like this ensures that I don’t forget to maintain my network. If I ever feel like I’m no longer getting along with someone, I remove them from my list and no harm is done.

The reason most people don’t do this is that it takes a lot of time. I still spend 4-6 hours per week keeping in touch with or expanding my network. It may seem like a lot, but the investment has paid dividends and afforded me many interesting conversations and relationships along the way. This strategy of intentionally staying in touch with people has led to friendships, co-workers, job offers, and clients.

Make It Yours

No career advice will work for everyone.

I didn’t write this letter to give you a formula for networking, but rather to let you know that unconventional approaches can work. My network has been an invaluable asset, but luck and privilege played a huge part too.

If I hadn’t been able to drive three hours to take a meeting with my future boss, would he have hired me? If I needed to be home after work to help care for a family member, would I have been able to network at Meetups? If I weren’t a white male in an industry dominated by white males, would people have taken the time to meet with me?

I don’t know.

I have no idea what your career path will look like, but I hope my story gives you the courage to build a path that works for you.


Karl is a former CTO and freelance writer. He’s currently the founder of Draft.dev where he helps companies create content that reaches software developers.

Confessions of a conference speaker

Dear new developer,

When I was newer to development, I thought that conference speakers were experts in their area, harbored no doubts, and that they knew exactly what they were doing. Speaking about technology seemed scary (until it wasn’t).

I enjoyed this post, “Confessions of a Conference Speaker”, pulling back the veil on the experience of a prolific tech conference speaker–20 talks in 2019. (She also has a post about being a conference attendee.)

I particularly enjoyed this section, titled “The Audience is Rooting for You”:

People come to conferences and attend your talk with the hope of getting value for their time. But that’s what is important to remember. They WANT to have chosen a good talk. They WANT you to succeed!

Being a speaker can be nervewracking for any number of reasons. There is so much prep that goes into it. Not every talk will go perfectly. But it helps to remember that the audience is rooting for you. This is especially true with those live coding mistakes. They’ll enjoy helping out 🙂

And the tips about a tech check and adding your author info on every slide were spot on based on my limited experience.

I can’t recommend public speaking enough for a a way to level up your skills. It can be terrifying, but you’ll learn:

  • how to dig into a topic
  • how to present something in a coherent fashion
  • the confidence of knowing that you (likely) know more than anyone else in the room on this topic
  • the value of connecting to your peers

If you are considering doing a talk, I’d suggest starting at a meetup or a lightning talk at a conference. Read the whole post to get Laurie’s inside view.



Speaking isn’t as scary as you think, eventually

Dear new developer,

I remember one of the first times I spoke in public. I was talking about J2ME (which was a technology for building mobile apps, pre iphone) to the Boulder Java Users Group. I threw up some slides showing the flow of data across the system, and made a joke along the lines of “sorry if this is confusing, but at least it isn’t UML”. The audience all laughed, and I went on with my talk.

Guess who the next speaker was?

Grady Booch, inventor of UML.


Public speaking is a great way to do a number of things for you as a developer.

  • Raise your profile in your company and in the community. Standing in front of a crowd and talking about a topic will get you noticed. Even if it is a crowd of 10 at your local meetup.
  • Teach you how to educate people. The way to help someone understand something is not intuitive. Speaking gives you a chance to practice it, and that will help you in your work life, since a large part of development depends on helping other people understand what you mean.
  • Force you to really understand your topic. Trust me, the pressure of being up in front of a group of people will cause you to dive deeper than you otherwise would have. (Kinda like writing an ebook.)
  • Let you learn something new. Related to the above point, you can learn something new when you are presenting. This can either be ancillary to the topic you are talking about, or, in some cases, can be the topic of your talk.

Some tips for getting started:

  • Find something you are interested in. Brainstorm ideas around that. Think about cross sections: “Using javascript in marketing” or “what do SQL and devops have in common”. Both technical skills like javascript, SQL or design and “soft” skills like interviewing and communication can be good topics.
  • Join a meetup. Go a few times as a regular member, learn who the organizers are. Then go to the organizer and say “I’m a new developer, but I’d love to speak sometime. Do you have any slots open?” (You can also join Toastmasters.)
  • When you get a chance to talk, practice it multiple times, at least once in front of someone. Remember that you are likely the most expert person in the room. If possible, start off with a joke or self deprecating remark, and ask for audience participation. More tips.
  • Look for local conferences. Then, look for Calls for Proposals (“CFPs”) at such conferences. Submit. Don’t spend too much time polishing a submission. Submit any proposal to multiple conferences. Papercall is good for that. (I confess, I’m not an expert at this process, so this is more based on advice I’ve read.)
  • When you go to conferences or meetups, walk up to speakers and ask how they got started. I’d suggest avoiding the superstars. Regular speakers will still have useful advice, but fewer folks surrounding them.

By the way, it is terrifying, but many things are the first time you do it. I mean, do you remember learning to ride a bike?

Public speaking is a great way to stretch yourself, learn new skills and meet new people. Highly recommended.