Stories are a window into life. They can if they resonate provide insights into our own lives or the lives of others.They can help us transmit  knowledge, pass on traditions, solve present day problems or allow us to imagine alternate realities. Open Source software is an example of an alternate reality in software development, where proprietary has been replaced in large part with sharing code that is free and open. How is this relevant to not only developers but people who work in technology? It is human nature that we continue to want to grow, learn and share. For my work, as a Community Manager I get to interview speakers at various Oracle and other conferences. That is great but everyone is not a speaker. For them, I started 60 Second Developer Stories. I have a mobile kit when I am on the road that consists of just my iPhone, microphone and a mono-pod and anyone who wants to can come and share their story. Below are some of the ideas I give as a suggestion, as well as some FAQs. I look forward to meeting you at a future User Group Meeting, Oracle Code event, Oracle CodeOne, Oracle Open World or another event.


60 second developer story.JPG


  •       Share what you learned on your first job
  •       Share a best coding practice.
  •       Explain how  a tool or technology works
  •       What have you learned recently about building an App?
  •       Share a work related accomplishment
  •       What's the best decision you ever made?
  •       What’s the worst mistake you made and the lesson learned?
  •       What is one thing you learned from a mentor or peer that has really helped you?
  •       Any story that you want to share and community can benefit from


Here are some FAQs about the 60 Second Developer Story


Q1. I am too shy, and as this is live what if I get it wrong?

A1. It is your story, there is no right or wrong. If you mess up, it’s not a problem we can do a retake.


Q2. There are so many stories, how do I pick one?

A2. Share something specific an event that has a beginning, middle an end. Ideally there was a challenge or obstacle and you overcame it. As long as it is meaningful to you it is worth sharing.


Q3. What if it’s not exactly 60 seconds, if it’s shorter or longer?

A3. 60 Seconds is a guideline. I will usually show you a cue-card to let you know when you have 30 secs. and 15 secs. left. A little bit over or under is not a big deal.


Q4. When can I see the results?

A4. Usually immediately. Whatever Periscope/Twitter handle we are sharing on, plus if you have a personal Twitter handle, we tweet that before you go live, so it will show up on your feed.


Q4. What if I am not a Developer?

A5. We use Developer in a broad sense. It doesn’t matter if you are a DBA or Analyst, or whatever. If you are involved with technology and have a story to share, we want to hear it.