Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Learn. Reflect. Repeat.

Learn. Reflect. Repeat.

As developers, we’re constantly learning: whether it’s figuring out how to solve new problems and bugs, or focusing on new skills and knowledge to apply to our work. At FutureLearn, we reflect our company mission of providing the best learning experiences to everyone, within the way we work as well. We have a culture of learning and supporting each other, encouraging everyone to pursue the skills they want to have. This talk will help you make learning a more integral part of your processes, and explain how to run internal events, like hackdays and lightning talks, to support this.

Melinda Seckington

September 12, 2015
Tweet

More Decks by Melinda Seckington

Other Decks in Technology

Transcript

  1. 2002 Studying Computer Science i’m not good enough i don’t

    belong here i should know everything i can’t admit i don’t know @mseckington
  2. 2012 Started Miss Geeky Geeks of L ondon Finished My

    Masters Started My Own Company @mseckington
  3. “Many people think it means accept failure with dignity and

    move on. The better, more subtle interpretation is that failure is a manifestation of learning and exploration. If you aren’t experiencing failure, then you are making a far worse mistake: You are being driven by the desire to avoid it.” ~ Ed Catmull, Creativity, Inc.
  4. “Trusting others doesn’t mean that they won’t make mistakes. It

    means that if they do (or if you do), you trust they will act to help solve it.” ~ Ed Catmull, Creativity, Inc.
  5. "If you treat an individual as he is, he will

    remain how he is. But if you treat him as if he were what he ought to be and could be, he will become what he ought to be and could be." ~ Johann Wolfgang von Goethe
  6. "If I keep on saying to myself that I cannot

    do a certain thing, it is possible that I may end by really becoming incapable of doing it. " ~ Mahatma Gandhi
  7. Feedback: I don’t like your commit messages. Constructive feedback: Your

    commit messages should explain the value of your changes, rather than just focusing on the implementation details. Have you tried describing the problem you’re trying to solve and the context behind it?
  8. learn on your own learn from each other learn from

    the community learn by teaching
  9. “There are two parts to any failure: There is the

    event itself, with all its attendant disappointment, confusion, and shame, and then there is our reaction to it. It is this second part that we control. Do we become introspective, or do we bury our heads in the sand? Do we make it safe for others to acknowledge and learn from problems, or do we shut down discussion by looking for people to blame? ” ~ Ed Catmull, Creativity, Inc.
  10. Repeat Repeat Repeat Repeat Repeat Repeat Repeat Repeat Repeat Repeat

    Repeat Repeat Repeat Repeat Repeat Repeat Repeat Repeat