Code Story episode
The Inventive Journey
May 27, 2021 · Season 4 · 27 min
The Inventive Journey
Originally posted at this link:
https://anchor.fm/the-inventive-journey/episodes/Surround-Yourself-With-Good-People-The-Inventive-Journey-Podcast-For-Entrepreneurs-w-Noah-Labhart-e10a14o
RECAST: Try to surround yourself with people who believe in you. So in that same example that I mentioned, that was my biggest mistake and biggest learning. My wife was absolutely amazing. She was a rock and, she was picking me up off the ground when I was in the corner crying and rocking back and forth when the project was going south. She was like, no, you've got to keep going this is just a part of the journey. We are going to get through it, and it will be fine. So she really picked me up. You have to surround yourself with people that are going to tell you that because there are going to be days where it just sucks, and it's not a good day. There are going to be days where this is the greatest job in the world, and you love it. Some days it's just nothing is going my way. You've got to be able to get through those. I think a huge reason why I was able to get through those days was my wife and the encouragement people were surrounding me with.
Checkout our episode stacks on Stacklist! https://stacks.codestory.co/
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
More episodes
Keep listening
Topics
Explore related conversations
Technical due diligence checklist for startups
A technical due diligence checklist for founders and investors: what reviewers examine across architecture, security, team and process, and how to prepare before a raise.
Fractional CTO vs full-time CTO: which does your startup need?
A practical comparison of a fractional CTO and a full-time CTO: cost, scope, when each makes sense, and the questions to ask before you hire either one.
CTO vs VP of Engineering: how the two roles actually differ
CTO vs VP of Engineering explained: who owns architecture, who owns delivery, when to split the roles, and how to avoid the overlap that breaks engineering teams.