Notes from You Got This 2019

About a week ago, I was at You Got This 2019, a conference that bills itself as an event for “juniors on skills needed for a happy, healthy work life”. I’d seen the schedule on Twitter, thought it looked interesting, and decided to attend on a whim. All the topics had a strong focus on wellbeing, not technical content.

This post has my lightly edited notes from the conference and the sessions.

General vibes

Everybody I met was friendly and nice.

All the talks were good, and perhaps more notably, consistent. Usually when I go to a conference, there’s at least one or two talks that leave me feeling a bit “meh”, and that wasn’t the case here. Every session was interesting, well-presented, and left me with at least a few new ideas.

The emphasis in the introduction was that these are “topics we should be talking about more” – which is precisely why I decided to go.

I care a lot about running inclusive events, and have a long list of ideas for doing so. For a first-time conference, I was pleased by how many of them they hit:

And here’s some stuff that felt a little odd:

No conference gets inclusivity perfect, and the gold standard for me is still AlterConf London – but this was pretty good, overall. I’d happily attend again.

If you read the post and think sounds interesting, there’s a sequel planned for January 2020, with a mailing list on the website.

The talks

These are based on my handwritten notes, which are the bits I found most interesting, not a comprehensive summary of the talks. They’ll give you a flavour, but they’re not a substitute for watching the talks.


Impostor syndrome, perfectionism and anxiety, by Jo Francetti

She started with a story of “Mo”, a young developer who was feeling overwhelmed at work, and the sort of things she was feeling. Wondering if she knows enough, if she’s being judged by her co-workers, overworking and ruining her mental health. It was a good way to set up the topic – a sort of “Do you recognise this?” moment.

Editor note: I was wondering how she chose the name “Mo”, and can’t believe it took me to now to spot it.

There are some common issues, which she went through in turn:


Knowledge sharing and self-worth, by Sascha Wolf

Knowledge sharing can take many forms: blog posts, answering questions, speaking at conferences.

A big part of this talk was Sascha talking about his struggles with depression and exhaustion, and what felt a lot like burnout. (I don’t remember if he actually used the word “burnout”.)

He talked about how he built a new frame of mind, and that “we’re more than just a walking tech stack”*. In other words: we shouldn’t define ourselves solely by our technical work or our technical skills. As part of that, he talked about his experiences with therapy, which made me happy. (I think therapy is a really useful tool, I’ve been to therapy multiple times, and it’s good to hear it discussed on stage.)

A key attribute of a successful team is psychological safety – people feeling like they can take risks, and b supported by their team.

“Tech enables us, but it doesn’t define us.”

How to find knowledge you can share:

I really liked the framing of this talk: the introduction was “Hi, I’m Sascha”, and a list of technical skills and background. Then at the end of the talk, another slide “Hi, I’m still Sascha”, which had a similar list that covered much more of his life.

There is more to you than your profession.


Where did all my money go? by Paula Muldoon

Notable for starting and ending with a violin recital. (Although not the first time I’ve heard music on stage at a tech conference!)

Some general advice:

If you want to get your spending under control, there are two key steps:

  1. Understand your beliefs about money.

    For example: “I’ll never have enough money”, “I’ll always have enough money” or “money is evil”. You might believe all, some or none of these – whatever, knowing your beliefs is useful.

    Some useful resources:

    Talk about money! It’s often a taboo topic.

    </li>
  2. Take some practical steps.

    You want to understand your current money habits – but exercise self-compassion. Don’t beat yourself up over everything you think you’re doing wrong.

    Suggestions:

    • Have a spreadsheet. Calculate all the numbers: exactly how much you’re earning each month, and your regular bills (rent, utilities, tax, etc.). What’s left is your budget.
    • Automate everything. If you have to remember to pay bills, there’s a risk you’ll forget and take a hit to your credit rating.
    • Max out your workplace pension. (Note: I scribbled down “needs research” next to this, because I’m not sure how I’d do this, what it means, and suspect the best thing to do with pension stuff is probably more complicated than simple.)
    • Use bank accounts that help you track your spending, like Monzo or Starling.
    • Get free credit reports from Experian and Equifax.
    • If you have a credit card, keep your credit limit at an affordable level. (I’ve heard conflicting advice on this one. My credit limit is several times my monthly salary, and I rarely max it out – but by paying it off regularly it’s slowly inched up, and might be useful in an emergency. Hasn’t bitten me so far.)
    • Advanced moneying: have side gigs, negotiate a pay rise.
  3. </ol>

    Paula also wrote a blog post with a summary and some resources.


    Junior.next(), by Tara Ojo

    Slides: https://speakerdeck.com/tyeraqii/junior-dot-next-yougotthisconf

    I love the phrase “career crushes”.

    Everyone has to start as a junior, so how do you progress?

    If you’re a junior looking to progress:

    There’s a sweet spot of “stretch” between comfort (easy, minimal learning) and panic (bad, a source of stress) – that’s where you want to be.

    You want a mixture of base knowledge skills and depth in specific areas.

    If you’re a supporter trying to help a junior:


    Self-care beyond the hashtags, by Taylor Elyse-Morrison

    Looking at the #selfcare hashtag. What is it?

    Taylor is a “ritual builder” – helping people build rituals.

    In order to care for yourself, you need to listen to your body. You want stillness, observation, reflection. Be consciously aware of your body.

    When you reflect:

    1. Pick an interval
    2. Ask “When did I experience tension?”
    3. Ask “When did I feel supported?”

    For building rituals, you want an emergency toolkit for when you’re in a bad moment. This might include:

    Self-care means listening to your body and responding in the most loving way possible.

    Our self-care needs will change with time, so keep listening and responding.


    Morality and ethics, by Sam Warner

    What’s the definition of ethical technology?

    Notions of good/bad are fuzzy; one possible alternative is effective altruism.

    Tech is a relatively young and immature industry, but “we shouldn’t be ashamed of being immature if we mature well”.

    A Stack Overflow survey (admittedly not representative, with “some demographic challenges”) – a majority of developers think they should think about the ethics of the software they build, but only a minority think the ultimate responsibility lies with them. We should be empowering developers to feel like they have that responsibility (and power).

    Three principles of ethical software:

    1. People come first
    2. Create accessible and useful services for everyone
    3. More diverse teams give better visibility ethical factors

    We all make mistakes; what matters is how we get better. (The speaker used an example of Facebook – Mark Zuckerberg didn’t realise he’d create the monster he did – but some of the early iterations of Facebook were pretty sketchy, so I’m reluctant to give Zuckerberg a pass.)

    A useful resource: the Ethical OS toolkit. A checklist of useful things to think about when building ethical software. (I wondered: does it cover online harassment and abuse?)

    Things to think about:

    1. Unethical software isn’t more profitable
    2. Don’t hide behind contracts
    3. You can make a difference (e.g. Project Maven, in which Google’s engineers successfully protested a contract with the US DoD)


    Understanding and building independence, by Violet Peña

    Slides and notes: https://violet.is/files/you-got-this.pdf

    We are problem solvers.

    Independence is the ability to understand and construct solutions. It’s not about working alone.

    Here’s a framework for solving problems:

    1. Have a plan.

      Check you understand the problem: the data, the conditions, the unknowns.

      Break your plan down into steps. How long will each step take? How can you track progress?

      Be honest with yourself and your team. Are you progressing?

      Be aware of how you’re performing. It’s okay to say “I need more time”, “I need more help”, “I need to do something differently”. (And she had us all say them out loud to get used to saying the words!)

    2. Use your tools.

      Use the tools you have, but don’t be afraid to change modalities; to try new tools or technologies if needed.

      Find a related problem (similar data, conditions, unknowns), and try to solve your problem in a similar way.

    3. Ask for help.

      It’s a great thing to do: it builds your knowledge, shows your respect for your colleagues, shows you don’t have a massive ego.

      You want to “build a Voltron” – a group opf people who can help with particular topics.

      You should ask for help when you’re stuck, can’t get past a particular problem, or need a rethink.

      The more certain you are somebody has seen this before, the earlier you can ask for help.

      How do you ask for help?

      • Give context
      • Ask a specific question
      • Tell them what you’ve already tried
      • Thank them for their time/help


    The power of junior developers, by Sam Morgan

    Two topics:

    1. Be suspicious of the word “junior”
    2. Advice for people who want to support junior developers

    If you say “junior”, what are you suggesting? You’re saying that:

    You only have permission to learn if you’re:

    This is a false dichotomy.

    Here’s how to build a structure for learning:

    Provide context for problems:

    Set goals:

    Provide resources and help:

    There are several types of question somebody might ask/opportunities for learning, and they need to be treated differently:

    Have a structure for feedback:

    1. Require intentionality. Ask: What do you want feedback on?

      This allows you to get feedback early, rather than waiting for perfect or completed specimens, and early feedback is better.

    2. Keep it tight. Don’t overwhelm somebody with information, or provide comments on irrelevant areas.

    3. Demand iteration.

      When they’ve addressed your feedback, they should come back for more. The model of “get feedback once, then finish” is an odd one, and not so helpful (exams are weird).

    A question for the junior devs in the room: how are you going to transform the businesses you work in?