Healthy Developer – Details, episodes & analysis

Ever thought about stepping into product management—just to try something totally different from engineering?

That's exactly where Monte found himself. After years in dev and even engineering leadership, he made a move he thought would lead to more ownership and product vision. But once he was in the role… something felt off.

In this coaching session, we unpack what actually happens when you chase product titles inside companies—and why the version you're offered often isn't what you imagined. Monte thought he was stepping forward. Instead, he realized he was just managing user stories and process artifacts.

If you've ever wondered, "Is this really what the role is supposed to be?"—you're not alone.

Work with me: https://healthydeveloper.com

In this real coaching session, I talk with John, a developer-turned-manager, who's navigating the messy middle of leadership. He's caught between two teams, two continents, and shifting expectations.

Sound familiar? 

We dig into:

• The difference between managing people and leading culture
• Why growth-stage teams break without intentional leadership
• How to lead without authority (especially when others outrank you)
• The startup → scale-up trap most companies fall into
• Ways to influence product direction by fixing culture first

This is one of the most honest, practical coaching conversations I've had on team culture, dev leadership, and transitioning into management. If you're a senior dev or manager trying to scale impact without losing your soul, you'll get a ton out of this.

Work with me: https://healthydeveloper.com

Is your tech job feeling a little too comfortable? You might be unknowingly putting your career at risk. In the fast-paced world of technology, complacency can lead to career stagnation, limiting your earning potential and jeopardizing your job security.

Grow Faster in Your Tech Career: https://thrivingtechnologist.com/coaching
Join the Thriving Tech Community: https://thrivingtechnologist.com/community

In this video, we'll uncover

The Hidden Dangers of Comfort in Tech Jobs - How staying in your comfort zone can make you obsolete in a rapidly evolving industry.

Signs You're Experiencing Career Stagnation - Recognize the red flags that indicate you're not growing professionally.

The Importance of Continuous Skill Development - Why updating your skills is crucial for career advancement and remaining competitive.

Strategies to Overcome Complacency - Practical steps to reignite your passion and drive in your tech career.

Exploring Self-Employment and Tech Consulting - How becoming self-employed or starting a solo venture can enhance your career growth.

Don't let the comfort of today become the regret of tomorrow. It's time to take control and ensure you're not left behind in the ever-changing technology industry.

You can also watch this episode on YouTube. 

Chapter markers / timelinks:

(0:00) Introduction
(1:29) 1 A Story of Me Getting Trapped 
(2:59) The Illusion of Security
(5:00) 2 Signs Your Tech Job is Too Comfortable
(5:26) 2.1 Lack of Learning
(6:18) 2.2 Routine Work with Repetition
(7:05) 2.3 No Networking
(8:44) 2.4 Content with The Status Quo
(9:25) 3 The Consequences of Complacency
(9:45) 3.1 Career Stagnation
(11:31) 3.2 Job Insecurity
(12:12) 3.3 Reduced Earning Potential 
(12:30) 3.4 Missed Opportunities
(13:19) 4 Solutions for Growth when You've Become Complacent
(14:41) 4.1 Continuous Learning
(16:50) 4.2 Skills Diversification
(18:29) 4.3 Consider Self-Employment Benefits
(19:28) Career Compass Tech Career Coaching Package

Visit me at thrivingtechnologist.com

Why do some software companies build exciting products with the freedom of a lean startup, while others deliver boring products like a feature factory run by control freaks?

In this episode I ask this question: "Does Your Company Feel More Like a Factory, or a College"?

Whether you're using agile methods like scrum, kanban, or any other process – up front design is still alive and well in many companies. To truly build innovative software products that cause your company to profit so you can get the rewards and recognition you want – people must let go.

When features are identified has a big impact on success. Many companies focus mostly on the features for their software that they can think of or hear from customers ahead of time. But it's those features discovered only after you release your product to them using devops and continuous delivery approaches, with an agile budget, that cause you to profit greatly.

This is the approach popularized by Eric Ries book "The Lean Startup". Companies run like a factory try to predict value, while companies run like a college discover value.

Companies run like a factory control people, while companies run like a college trust people.

Companies run like a factory use burn-down charts to measure progress, while companies run like a college use learning milestones.

Companies run like a factory use a project budget, while companies run like a college use a monthly budget.

Companies run like factory focus on measuring expenses, while companies run like a college focus on measuring profit.

Do you work at a company that feels more like a software factory (or feature factory), or a college?

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. 

Visit me at thrivingtechnologist.com

In the first decade of my career, I would get angry at everyone around me and turned to the Internet to vent my frustration.

It seemed like managers and other people who didn't understand software development had caused me to lose hope in my future.

In this episode, I share what caused me to lose hope, and many programmers I run across struggle with these symptoms as well.

If you're a programmer who has turned to escapism and joining the chorus of complainers – I implore you to reconsider!

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

(3:00) We're Forced to Cut Corners 
(4:33) Cognitive Overload 
(5:17) Low Perception of Value 
(6:50) High Income Forces Deeper Goals 
(8:31) Learned Helplessness 
(10:38) Say No With Grace 
(12:45) Communicate Uncertainty 
(15:28) Ask for Help Earlier 
(16:48) Develop Empathy 
(18:24) Surround Yourself with Positive Devs 

Visit me at thrivingtechnologist.com

If you want to be a calm programmer, you may want to consider cutting down on caffeine.

On a project that's truly agile, most people need extra patience. Especially if they have high anxiety from using coffee or other stimulants to get through the day.

In this episode, I share some things you may want to know if you want a sustainable career in software development.

Though you may not be able to completely cut out caffeine, it can wreak havoc on you and your team's ability to work together well.

When work is already difficult, and people are under stress, caffeine only tends to make things worse.

I hope these tips for avoiding caffeine withdrawal help you to stay a healthy programmer!

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. 

Visit me at thrivingtechnologist.com

Have you ever had an idea for something on your software project, but someone else takes the credit?

Plagiarism can be extremely frustrating, and it's typically caused by narcissistic personality types.

In this episode, I share why this happens, how to prevent it – and how to cope with it.

I also share a personal story of when this has happened to me.

This sucks, there's no way around it.

But if you're creative enough to come up with new software development ideas, you can do it again!

I hope this episode helps you avoid this situation in the future, and have a healthy mindset if you unfortunately do get plagiarized.

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. 

Visit me at thrivingtechnologist.com

Looking at what decisions others make about their career in software can be a big mistake.

Though having a career in software development can be exciting, there is also cause for serious caution.

In this episode, I share the 5 biggest lies I have bought myself, and I hope you don't about your career in software development.

With healthy decisions and a realistic mindset, you can advance quicker than others and not get stuck in common traps.

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

(1:40) Technical Skill Determines Your Success 
(2:40) Harder Work Gets More Done 
(4:16) Past Success Determines Future Results
(6:27) Bigger Companies Have Better Practices
(8:56) Promotions Are Proportional

Visit me at thrivingtechnologist.com

If you feel like a "code monkey" with pressure to work fast – you need an agile budget.

It took me many years, but I finally figured out the reason why.

Companies that try to build software like a manufacturing plant budget the wrong way.

This creates pressure on workers, and produces boring products that barely keep a software company profitable.

At companies that understand this, you'll be more creative and spend less time trying to estimate.

If the leaders at your software company don't understand this, they may still have a (barely) profitable business, but they'll be wasting tons of money.

In this episode, I share hard learned lessons about the software industry that every company should build their foundation upon.

Agile budgeting is a key to healthy software development company culture – and careers!

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. 

Visit me at thrivingtechnologist.com

If you've ever had to estimate software development work, you may have engaged in "planning poker".

This method of estimating brings with it some potential benefits.

But depending on the culture of your team, it can also cause big problems.

In this episode, I hope to avoid you falling into using this common practice if it isn't right for your team.

Planning poker might be just what your team needs – but you need to make the smart choice!

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. 

Visit me at thrivingtechnologist.com