Logo

dev-resources.site

for different kinds of informations.

Dennis Traub failed his way to success... and other things I learned recording his DevJourney (#133)

Published at
1/12/2021
Categories
devjourney
career
aws
failure
Author
timothep
Categories
4 categories in total
devjourney
open
career
open
aws
open
failure
open
Author
8 person written this
timothep
open
Dennis Traub failed his way to success... and other things I learned recording his DevJourney (#133)

This week, I published Dennis Traub's #DevJourney story on my eponym Podcast: Software developer's Journey. Among many other things, here are my main personal takeaways:

  • Dennis found his first love with computers at the age of 9, in form of a Commodore VIC20. He wanted to understand how it works so much, that he took it apart.. and that's how, a few months later, he had a Commodore64... and a non-functioning VIC20 😁 and like many of us, he learned how to code by typing listings from magazines. And even though he spent his entire youth in front of a computer, it didn't occur to him that it could become his job.
  • While studying something else entirely and trying to figure out life in general, he earned money by repairing computers, setting up printers, helping create networks, etc. doing fun things... which he only later realized was a legitimate profession.
  • But it took the World Wide Web in the early 90s to finally realize the gift he had and finally made a living out of it.
  • Dennis is a very curious person, borderline ADHD. He needs the freedom to explore and learn. If he doesn't have the chance to do this, his codebase will "look like a showcase of all the front-end frameworks of the decade". Thus, he has been nurturing jobs in which he had this chance to move around a lot. Dennis is, in his own words: a starter, not a finisher. A person is able to inspire others.
  • After his first 5 years of tenure at an Agency, Dennis was pretty burned out. He needed a change of scenery. So he went back to school and learned a new trade: avionics maintenance. During an internship, he realized that his knowledge of computers and avionics combined was very valuable and that became his next job.
  • "So much of our job is about failing". Creating software means making something new. Failure is inherent to this process. Dennis took this to its extreme when he joined AWS. He said: "Before joining AWS, I considered myself an expert [...] but AWS is the place people go if they want to feel like they don't know anything." And this is exciting to him!
  • Dennis describes his job as a developer advocate as looking at what is being built inside of AWS, and then turn around, show it to developers and inspire them to create fantastic things with it.
  • Dennis ended the tale of his journey by talking about the bystander-effect and encouraging us to speak up and ask questions when we are unsure.

Advice:

  • "If you feel in over your head, talk to someone, you are not the only one!"
  • "No matter how you feel, be aware that everybody feels the same"

Quotes:

  • "I am a starter, not a finisher. I can inspire people to do things."
  • "I don't really know what I am doing, I am not enough for this job!"
  • "Intuition is nothing else than experience"
  • "Before joining AWS, I considered myself an expert [...] but AWS is the place people go if they want to feel like they don't know anything"
  • "If you want to stop learning at some point and know what you are doing, find another job"
  • "When I started talking to people about my feelings, many people that I look up to, told me they feel exactly the same way"

Thanks, Dennis for sharing your story with us!

You can find the full episode and the show notes on devjourney.info or directly here on DEV

Did you listen to his story?

  • What did you learn?
  • What are your personal takeaways?
  • What did you find particularly interesting?
failure Article's
30 articles in total
Favicon
Story of a failed entrepreneur
Favicon
Embracing Failure - The Pathway to Success
Favicon
How a 2% Failure Turned into a Success: My CKS Exam Experience
Favicon
Making Releases Routine
Favicon
AWS Lambda Functions Failure Management
Favicon
How I Passed both AWS Professional Exams in 6 Months & Tips on how you can TOO!!!
Favicon
Why side projects die so quickly ...
Favicon
The Smile that Conquers Failure
Favicon
The Answer to Life, the Universe, and Project Estimate Failure (Spoiler: It's Not 42)
Favicon
Failure - An Opportunity to Learn and Grow for Software Developers
Favicon
Postmortem reports: How to get the most from failure for massive growth
Favicon
What is Design for Failure?
Favicon
Conquer Your Fear from a Failed Job Interview in 7 Simple Steps
Favicon
Dirty Reads in Oracle Database (is Oracle ACID across failure?)
Favicon
I failed my AWS exam, but I gave it my best shot. Tips for Exam Retakes.
Favicon
The True Costs of a Startup Failing
Favicon
It is Time For App Security Questions To Die
Favicon
How Dark Souls Helps You To Think About Failure
Favicon
Failing Digital Ocean Kubernetes Challenge
Favicon
Setting Yourself Up for Failure: Failing Better
Favicon
Setting Yourself Up for Failure: Culture
Favicon
Setting Yourself Up for Failure: My Epic Fails
Favicon
Dennis Traub failed his way to success... and other things I learned recording his DevJourney (#133)
Favicon
An Iterative Lifestyle
Favicon
SSRS Access woes
Favicon
Shattered or How to bomb interviews as a senior developer
Favicon
Three Unconventional Ways to Measure Value
Favicon
$50 coupon contest: Share your #FML moments to win
Favicon
Lambda Functions Are NOT Fault-Tolerant by Default
Favicon
Should comments in code be considered failures in coding?

Featured ones: