Why Do Most Programmers Who Start Companies Fail?

If you're a programmer tired of the corporate grind, and thinking about starting a software company - watch out. I tried this twice and failed, but the third time went much better. Here are some practical tips to avoid pitfalls as a software engineer if you want to start a software company - and be successful! Join my Patreon:  https://thrivingtechnologist.com/patreon Learn about one-on-one career coaching with me: https://thrivingtechnologist.com/coaching TechRolepedia, a wiki about the top 25 roles in tech:  https://thrivingtechnologist.com/techroles The Thriving Technologist career guide:  https://thrivingtechnologist.com/guide You can also watch this episode on YouTube.  Chapter markers / timelinks: (0:00) Introduction (1:05) 8 Mistakes Programmers Make Starting Companies (1:19) 1. Picking a Product That's Fun To Build (3:54) 2. Choosing a Viral Business Model (6:26) 3. Overengineering (9:00) 4. Having a Fixed Mindset (12:59) 5. Spend Too Much Time Building The Product (15:14) 6. Poor Financial Management (18:27) 7. Failing To Build Networks of Help (21:18) 8. Low Self-Confidence Visit me at thrivingtechnologist.com

Om Podcasten

If working on software teams feels complicated, frustrating, and filled with politics - that's just because your eyes are open. Unfortunately, you do need to make a living! So how do you keep up with the demands of your tech job and still have a life outside of work? Hi I'm Jayme Edwards, and I've had a 26 year career in the software industry filled with thrilling victories - and maddening drama. With so many problems in our industry, the more money I made the more ridiculous people's expectations were. I’m sharing the biggest mistakes I made in my career, and the insights I learned along the way. This podcast is the audio version of the Thriving Technologist YouTube channel, where you can find new episodes every Monday. Podcast versions appear on Wednesday of the same week. Subscribe and join us! Let’s help each other grow a community of healthy software developers.