Healthy Software Developer

Ever thought about stepping into product management—just to try something totally different from engineering? Want expert guidance to grow? Apply for 1-on-1 tech career coaching with me. 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. You can also watch this episode on YouTube.  Visit me at healthydeveloper.com

You ever notice how sometimes the people around you see what's really going on before you do? That's what happened with this channel. I tried to go broad, help everyone in tech, chase what the “experts” and the algorithm said people wanted—but you knew better. You told me what made this channel special wasn't the hype or some generic success formula. It was the real talk. The raw stories. The focus on staying healthy, sane, and actually living your life while you write code in an industry that rarely cares about either. In this episode, I'm owning up to where I lost the plot—and why I'm bringing it all back to what *actually* matters. We're going deep on why “Healthy Developer” is the right home for this community (and for me), what's staying, what's changing, and what you can expect from here on out. If you're here to argue or troll, you won't like this one. But if you're tired of the tech grind, and you want real strategies for staying grounded and growing as a developer *without* burning out, you're in the right place. Thanks for holding me to a higher standard—and for helping me find my way back. Let's build something better, together. You can also watch this episode on YouTube.  Visit me at thrivingtechnologist.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. You can also watch this episode on YouTube.  Visit me at thrivingtechnologist.com

Ever feel like tech work has turned you into a robot? Just crank out code, stay in your lane, and don't ask too many questions? Yeah—same. → Find Out If You're Ready To Go Solo in Tech In this real, unfiltered coaching session, I work with Charlie—a creative technologist who's been wrestling with how to bring *real* artistry back into his work. After running his own 3D animation business and helping other creatives thrive, he's now stuck between paying the bills with soul-draining contracts... and figuring out how to build a career where he actually gets to make things that matter. We talk about time management, identity, and how hard it is to self-promote when your creativity feels personal. If you're a developer or designer who's ever wondered “How do I get back to making stuff I care about?”, this one's for you. You can also watch this episode on YouTube.  Visit me at thrivingtechnologist.com

Today, I'm sharing a real conversation I had with Matt—an experienced developer who's been wrestling with where to take his career next. If you've ever felt like you're stuck doing the same thing over and over, or like your potential is being wasted, this episode is for you. → Find Out If You're Ready To Go Solo in Tech Matt's been on a journey to figure out what he truly wants, beyond just writing code. We dug into some deep topics—like whether he's truly competitive, how to test his business idea, and finding clarity between stability and ambition. It's a powerful session where Matt starts to rediscover his entrepreneurial drive and get real about what he wants to build. I think you'll find a lot of takeaways you can apply to your own journey.  You can also watch this episode on YouTube.  Visit me at thrivingtechnologist.com

Ever feel like you're living in the tech job twilight zone? One minute you're daydreaming about quitting, selling everything, and disappearing into the mountains. The next? You're convincing yourself, “Eh… it's not that bad.” Yeah—I've been there. → Find Out If You're Ready To Go Solo in Tech For years. I spent nearly a decade gaslighting myself out of leaving corporate life, ignoring burnout, and pretending I was just “in a rough patch.” But after coaching over 120 devs since going solo, I've learned this: most of us know we're done. We're just too skilled at lying to ourselves. So in this episode, I'm calling it out: Here are 5 signs you shoulda quit years ago—and 5 actions you can take right now to start your escape plan. No fluff. No "just follow your passion" nonsense. Just hard-earned lessons from someone who's been in your shoes—and walked out the other side. We'll discuss: Why being too good at your job is actually a trap How apathy about tech might be a deeper signal The sneaky way your side projects are trying to tell you something What your unused vacation days really mean And why your coworkers' loyalty is starting to feel cult-like You can also watch this episode on YouTube.  Chapter markers / timelinks: (0:00) Introduction (1:41) 1. 5 Signs You Should Have Quit Working in Tech Years Ago (1:53) 1.1 You're Too Good At Your Job (2:49) 1.2 You Stopped Caring About the Tech Stack (3:50) 1.3 Your Side Gigs are Your Real Job (5:01) 1.4 You're Hoarding Vacation Days (6:10) 1.5 You Get Annoyed By Other People's Loyalty (8:00) 2. 5 Immediate Actions to Start Breaking Free (8:25) 2.1 Quit Caring About Your Next Performance Review (9:45) 2.2 Sell Some Old Tech Gear (10:45) 2.3 Reclaim an Hour From Your Job (12:17) 2.4 Pitch a Fake Client Proposal (13:58) 2.5 Burn One Bridge of Responsibility (16:30) Tech Solopreneur Readiness Scorecard Visit me at thrivingtechnologist.com

Ever feel stuck in analysis paralysis, trying to figure out if you should go solo or stick with a stable tech job? In this live coaching session, I help Ben—a seasoned engineering manager and Agile coach—shift his focus away from fear and toward action. Find Out If You're Ready To Go Solo in Tech → https://scorecard.thrivingtechnologist.com/tech-solopreneur-readiness?utm_source=podcast&utm_medium=episode-description&utm_campaign=can-this-dev-manager-escape-the-grind We break down: Why even a stable tech job can still feel uncertain How fear of the unknown keeps devs stuck—and how to move past it The real way to test your next move without risking everything How to balance financial security with the drive for independence If you're a developer, tech lead, or engineering manager who's thinking about making a big career move but unsure where to start, this conversation is for you.  You can also watch this episode on YouTube.  Visit me at thrivingtechnologist.com

Most people get into software development for the money—and hey, I get it. The tech industry can be insanely lucrative. But if your end goal is to break free from the corporate grind and work for yourself, could a high income actually be holding you back? Grow Faster in Your Tech Career: https://thrivingtechnologist.com/coaching Join the Thriving Tech Community: https://thrivingtechnologist.com/community In this episode, I dive into my own career stories—when money was a good motivator, and when it turned me into a "perfect programmer slave." I've seen it all—from promotions I didn't even care about to chasing startup dollars and, finally, finding freedom through coaching and serving others. You can also watch this episode on YouTube.  Chapter markers / timelinks: (0:00) Introduction (1:27) 1. How Loving Money Prevents Self-Employment (1:39) 1.1 Story: Early Raises (4:19) 1.2 Story: Starting Up to Cash Out (7:11) 1.3 Story: Starting Up to Serve (10:43) 2. 3 Ways to Find Freedom from High Income Dependence (11:18) 2.1 Reduce Monthly Expenses (13:10) 2.2 Focus Effort on Your Highest Value (14:44) 2.3 Quit Your Corporate Gig (15:10) Take the DevPathfinder Career Assessment (16:54) Join our Discord Community Visit me at thrivingtechnologist.com  

The days of stable employment in tech jobs as a career is over. I don't say this to scare you, but so you take some action to be less dependent on companies that couldn't care less about you! Grow Faster in Your Tech Career: https://thrivingtechnologist.com/coaching Join the Thriving Tech Community: https://thrivingtechnologist.com/community In this episode, I share some of the latest developments in my time coaching over 120 software professionals. One of the biggest things I've learned, is that practically everyone is miserable. This year I have some exciting new announcements to make though - I'll be helping you escape the corporate grind! You CAN have a career in tech, but you have to step up, take more responsibility, and give up the delusion that corporate employment is a long-term strategy anymore. Those days sadly, are long behind us. You can also watch this episode on YouTube.  Chapter markers / timelinks: (0:00) Introduction (2:14) What I Told My Son about The Tech Industry (3:24) The Low-Value Career Death Trap (4:08) Employment is Now Maximum Risk (5:14) AI Has Made it Easier to Start a Business (6:45) Willful Ignorance Has Consequences (8:15) Temporary Employment is Honorable 9:16 Career Stability Is Possible Visit me at thrivingtechnologist.com

Are you helping or holding your team back? In this episode, I explore why sharing technical answers with your development team might not be the best way to help them grow. Instead, learn how to use resourceful questions to empower your team members to think critically, solve problems independently, and build long-term confidence. This coaching strategy is rooted in co-active coaching principles and can transform how you mentor junior developers or lead your software team. Grow Faster in Your Tech Career: https://thrivingtechnologist.com/coaching Join the Thriving Tech Community: https://thrivingtechnologist.com/community As a tech lead, manager, or mentor, it's natural to want to provide answers when your team is stuck. But constantly solving problems for them can create dependency and stifle their growth. By shifting from a directive approach to a coaching mindset, you'll help your team develop essential skills, foster ownership, and reduce your own workload in the long run. In this video, I'll share practical examples and techniques you can start using today to guide your team effectively without always giving them the solution. If you've ever felt the pressure to be the “go-to expert” on your team, this episode will challenge that belief and show you a better way to lead. Coaching your team to solve their own problems not only benefits them but also makes you a stronger leader. Watch now to learn how to implement these strategies and take your leadership to the next level! You can also watch this episode on YouTube.  Chapter markers / timelinks: (0:00) Introduction (1:14) 1 Bringing Out The Best in Your Software Team (1:31) 1.1 Solving Problems For People Holds Them Back (2:48) 1.2 Let People Struggle (4:36) 1.3 The Role of Resourceful Questions (11:30) 1.3.1 Examples of Resourceful Questions (11:35) 1.3.1.1 "Have You Broken This Up Into Smaller Pieces?" (12:33) 1.3.1.2 "Have You Really Considered ALL Your Options?" (14:07) 1.3.1.3 "What if I Wasn't Available?" (15:09) 1.4 Shifting From Expert to Coach (22:36) 1.5 The Long-Term Benefits of Coaching (26:16) 2 How To Start Leading Like a Coach (26:48) 2.1 Start Small (28:50) 2.2 You Don't Need Formal Training (29:50) 2.3 Where to Start Coaching (30:02) 2.3.1 Code Reviews (31:08) 2.3.2 Design Reviews  (32:46) 2.3.3 Project Planning (33:30) 2.3.4 Debugging Sessions (34:30) Get Help with Leadership Visit me at thrivingtechnologist.com

Ever had a manager who expects you to be Superman? No matter what you do, they keep asking for "more, more, more." Earlier in my tech career, I thought it was my manager's fault. But when I learned the art of setting healthy boundaries at work, I realized that the power to push back was in my hands. Grow Faster in Your Tech Career: https://thrivingtechnologist.com/coaching Join the Thriving Tech Community: https://thrivingtechnologist.com/community In this episode, I'll share insights gained from working with over 20 software companies as a developer, architect, and management consultant on setting effective boundaries with managers. Getting this right can bring immense peace and prevent burnout. Without clear boundaries, it's easy to feel overwhelmed by unreasonable expectations—and the result is often exhaustion or even job burnout. Managers often respect employees who assert boundaries more than those who don't. It may seem counterintuitive, but consider it: would you respect someone who allows themselves to be treated like a doormat? You can also watch this episode on YouTube.  Chapter markers / timelinks: (0:00) Introduction (1:20) Setting Boundaries with Your Manager (1:40) 1 Agree on Responsibilities for Your Role (3:13) 2 Determine Unacceptable Expectations (4:20) 3 Assign Consequences (6:17) 4 Communicate Your Boundaries (8:55) 5 Have a Backup Plan Visit me at thrivingtechnologist.com

Are you a tech professional who feels your creativity is being stifled by corporate culture? In this episode, I explore the impact of corporate culture on creativity in the tech industry. I share my personal journey—from leaving behind my passion for music to embracing programming as a new creative outlet, only to find that corporate constraints in tech began to suppress my creative spirit.  Grow Faster in Your Tech Career: https://thrivingtechnologist.com/coaching Join the Thriving Tech Community: https://thrivingtechnologist.com/community I'll delve into how creativity in tech is often threatened by corporate environments that favor predictability over innovation. Discover why expressing creativity is vital for personal fulfillment and how the suppression of creativity can drain your energy. We'll discuss strategies to navigate tech workplace culture and reclaim your creative energy for your personal pursuits. Join the conversation about creativity suppression in tech. Have you experienced the stifling effects of corporate culture on your creativity? Share your stories and insights in the comments below. Let's work together to keep the flame of innovation alive in tech companies - and our personal lives! You can also watch this episode on YouTube.  Chapter markers / timelinks: (0:00) Introduction (1:11) A Story of Creative Loss and Redemption (3:24) 1 The Unmatched Value of Creativity (3:50) 1.1 Fueling Personal Fulfillment (4:36) 1.2 Enhancing Problem-Solving Skills (5:34) 1.3 Driving Innovation & Growth (6:53) 2 Navigating Corporate Constraints on Creativity (7:21) 2.1 Preference for Predictability (8:31) 2.2 Creatives Seen as Disruptors (9:37) 2.3 Leadership Suppressing Creativity (11:49) 3 Preserving Your Creative Energy (12:14) 3.1 Respect That Creative Energy is Finite (12:38) 3.2 Avoiding Creative Burnout (14:11) 3.3 Allocating Energy to Personal Pursuits Visit me at thrivingtechnologist.com

Grow Faster in Your Tech Career: https://thrivingtechnologist.com/coaching Join the Thriving Tech Community: https://thrivingtechnologist.com/community 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. 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

What if the real risk isn't leaving your corporate job, but staying in it? If you're comfortable in your tech job today, layoffs aren't the only risk you face. The myth of job security is a common cause for staying stuck and growing complacent. 7 years ago my life was turned upside down when I realized for the first time - just how trapped I'd become. I developed chronic insomnia and anxiety, and it eventually emptied my bank account. All because I refused to accept that I'd outgrown working for corporations. I wasn't sure if I wanted to be an entrepreneur or just work solo as a consultant - but I knew I was done with having a boss. In this episode, I'd like to help you get a sober view at what staying in corporate jobs can cost you. Unfortunately, job security is a myth. I hope this content about overcoming fear of self-employment helps you find the courage to explore more empowering ways of work - if you've outgrown the corporate tech job grind. Whether you want to become an independent software development consultant or start a SaaS (software as a service) business, tech professionals in IT jobs and at software companies don't have to stay chained to their corporate jobs forever. There is no such thing as a "secure job"! But you'll have to step into the unknown waters of being a solopreneur - if you want to experience self-empowerment. 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:41) 1 The Lie of Corporate Stability (1:55) 1.1 Cognitive Biases (4:40) 1.2 Hidden Risks (6:38) 1.3 Opportunity Costs (9:19) 2 How Self-Employment Can Reduce Risk (9:31) 2.1 Diversify Income Streams (11:34) 2.2 Growth & Adaptability Mindset (16:42) 3 Overcoming Fear of Self-Employment (16:44) 3.1 Challenge Fear of The Unknown (19:31) 3.2 Embrace Risk as Opportunity Visit me at thrivingtechnologist.com

Thinking of quitting the tech industry grind to start a profitable software business yourself? Before you take the plunge, don't make the same mistakes I did! The secret to finding a profitable software idea, is that it must come from your customers. Unless you know a real pain that people who would use your software are experiencing, you can easily fool yourself into thinking it's good enough to build a software product business on. In this episode, I share what I've learned about finding real software product ideas. I use a combination of IBISWorld, ChatGPT, and a book by Dane Maxwell to help my software development coaching clients discover software startup ideas. IBISWorld Businesses  https://www.ibisworld.com/industry-statistics/number-of-businesses/ Start from Zero by Dane Maxwell https://www.amazon.com/Start-Zero-Business-Experience-Freedom/dp/1950367185 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:42) Finding a Profitable Software Idea (1:54) 1. Select a Customer Market (2:50) 2. Determine How to Contact Customers (4:37) 3. Ask Customers for Their Biggest Problem (6:05) 4. Ask People Who Responded To Meet (7:03) 5. Ask Them 5 Questions (7:15) Make Sure You're On The Same Page (7:29) How Are You Solving It Today? (8:15) What Happens When You Don't Solve This Problem? (8:50) If You Could Wave a Magic Wand, How Would You Solve It? (9:36) Would You Pay for That Solution? How Much? (10:48) Identify Consistent Profitable Problems Visit me at thrivingtechnologist.com

If you've ever been jealous of programmers who seem to write code faster than you - take heart. The myth of the "10x programmer" is misunderstood in many software teams and tech companies. What's important to companies is NOT that you're actually 10x faster at writing code. It's that you help the company produce features 10 times faster. Wake up call - you're not the only member of the team! Over my career, I've met software developers who come into companies and write code super fast - but end up slowing the project down. They bossed around the other junior developers and thought they were God's gift to programming. It was a real disaster. Instead, use these 6 techniques I learned as a software consultant. They'll speed up the project, make you popular on your team, get results for your company - and actually make your tech job easier! Besides, what's more important: that you can write code fast, or that you can avoid writing more code in the first place? 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:36) 6 Techniques Used By True 10x Programmers (1:50) 1. Technological Empathy (3:29) 2. Negotiate Streamlined Features (5:06) 3. Cross-Technical Insight (7:59) 4. Reject Ambiguity (9:42) 5. Minimize Architectural Complexity (11:53) 6. Document Innovation Visit me at thrivingtechnologist.com

If you've ever been on a software project and you can't get your boss to listen, I've been there. Many of us are technical types, so we often think facts are enough to convince management to support us. In this episode, I share 4 strategies I've used to actually get your boss to listen. These take some patience, but if you want to see real results - they do work. No matter what tech job you work on, you'll eventually run into problems that can only be solved if you can win support from management. If you practice these strategies, they can unlock new opportunities in your career that few other professionals in IT ever get to experience. 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:45) 4 Strategies to Influence Management  (1:58) 1. Frame Your Feedback in Terms of Impact (7:44) 2. Build Allies and Gain Support (10:51) 3. Choose Your Battles Wisely  (12:43) 4. Present Solutions in Steps Visit me at thrivingtechnologist.com

Have you ever felt like your software project was doomed from the start, almost as if it were the plot of a bad movie? Well, if so, you're not alone. I've been through my share of nightmarish projects, but one in particular stands out. It involved shady characters, SWAT teams, and a project that was destined for disaster from the beginning. If you've ever felt like your software project was spiraling out of control, this story might make you feel a little better—or at least a little less alone. 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: (00:00) Introduction (01:40) Part 1: Red Flags (10:44) Part 2: Turning a Blind Eye (17:10) Part 3: S$!t Hits The Fan (24:15) Part 4: The Fallout (30:58) Episode Groove Visit me at thrivingtechnologist.com

LinkedIn is a great resource for connecting with people, but it can also cause serious mental health challenges - and even lead to burnout. If you're looking for a job or just trying to find customers, there are some features of LinkedIn that can ruin your personal peace and drive your anxiety through the roof. In this episode I share some ways I've helped my tech career coaching clients avoid LinkedIn becoming a problem. Most of these center around avoiding comparing yourself to other people. As Gary Vaynerchuk famously recommends, "produce don't consume". If you follow some of the tips in this episode, you'll be able to responsibly use LinkedIn - and not let it use you! 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:16) 5 Ways to Keep Calm on LinkedIn (1:38) 1. Avoid Accomplishment Signals (4:08) 2. Use, Don't Consume (7:45) 3. Don't Engage Rage Bait (11:02) 4. Don't Attend Unjustified Meetings (14:19) 5. Keep Your Network Relevant Visit me at thrivingtechnologist.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Are you a programmer, or in any individual contributor tech role really? Considering switching into management? Be VERY careful. Most companies will not prepare you for what it takes to really be an effective manager. If you've ever been upset with a manager or felt like they weren't equipped to do their job, it's probably because they were promoted due to their success as an individual contributor - but weren't taught effective management techniques and strategies. In this episode, I'd like to help you avoid being looked at as incompetent by other programmers or anyone in any software development role. You already know that programming and other tech jobs require intentional and ongoing study and improvement. Management is no different! 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:56) 5 Skills To Become a Great Manager (2:06) 1. Holding People Accountable (4:24) 2. Taking Responsibility for Others (8:45) 3. Making Yourself More Available (13:17) 4. Studying and Practicing Management (15:56) 5. Being an Incentives Translator Visit me at thrivingtechnologist.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

If your tech career isn't what you want it to be, it could be a mild annoyance - or something urgent. Knowing how ready you are to actually make a change is important before you take any action that could change the course of your life and career. When I started career coaching, I noticed sometimes tech professionals would come to me frustrated about their career but not really willing to change. After a while I began using motivational interviewing. This is a technique I use to help me figure out how ready someone is to really make a change in their tech career. If you're thinking of getting a promotion, switching roles from perhaps programming to something like product management, UX, or data science; or looking to just find a better job - you should assess how urgent the change really is. In this episode I offer 5 stages of readiness for change along with symptoms you can experience at each of them. I hope this helps you know if your tech career is actually in a better place than you thought - or if it truly is time to make a change today! 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:06) 5 Stages of Readiness for Tech Career Change (1:16) 1. Contemplation (1:56) 2. Mild Irritation (2:30) 3. Active Exploration (3:41) 4. Serious Consideration (4:37) 5. Urgency and Desperation Visit me at thrivingtechnologist.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Today most tech companies engage in agile signaling - without even knowing it. They do nothing to make it easy to adapt to change, but put on a show to pretend they're agile. Many software developers and other professionals in the industry, even those with long careers, have never been on project with a truly agile software development process. And so it's not uncommon to hear software engineers and project managers talk about how much they "hate agile" behind closed doors. A select few understand what being agile really means. It means working together in a way where adapting to change is easy. For those unfortunate people, it can feel like gaslighting to work for these companies. Tech workers all over the industry are expressing more disgust with scrum and agile than ever. And when the SAFe, or "Scaled Agile Framework" arrived - it signaled a final nail in the coffin of many companies ever being able to realize the true benefits of being agile. In this episode I'd like to help you understand two things. First, we we need agile development more than ever today. With the arrival of AI, software projects are getting disrupted faster than ever and need to adapt. And who knows what the future could bring! I'll also help you understand 4 key events in the history of the software industry that caused the definition of the word agile to essentially mean "anything BUT change"! 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:31) 1. Do We Even Need Agile Development? (1:37) 1.1 Inability To Respond To Market Change (3:55) 1.2 Over Budget and Late Projects (5:50) 2. 4 Key Events That Co-Opted Agile (6:16) 2.1 Burn-Down Charts and Velocity Tracking (9:21) 2.2 Jeff Sutherland's Book (12:47) 2.3 Agile Certifications  (15:51) 2.4 SAFe (Scaled Agile Framework) (21:12) Episode Groove Visit me at thrivingtechnologist.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Does programming ever get tiring? Are you frustrated by being left out of key decisions by the company? You may begin to wonder if you should become a manager. In this episode I'd like to share 5 important considerations before switching from being a programmer to management. It's common advice that "all programmers must become managers eventually", and I don't agree with this. There are many ways to grow in our career, and management is just one path. However, for some people it may be the perfect next step. I hope this episode helps you know what you're walking into before you take the step to become a manager. 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:13) 5 Signs It's Time to Switch to Management (1:32) 1. You're More Concerned with People than Technology (3:42) 2. You Want More Organizational Insight (5:37) 3. You Hate The Technical Interview Process (9:39) 4. You Want To Work Less Overtime (12:39) 5. You're Tired of Learning New Technology Visit me at thrivingtechnologist.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Many programmers are stuck in their career today, but they place the blame on everyone else. Yes, there are some difficult things going on in the tech industry. But one of the biggest reasons programmers stop growing, is they don't get help. In this episode, I'd like to share the things I've learned after coaching over 100 software professionals that keep us from getting the help we need. 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 (4:56) 6 Reasons Why Tech Workers Stay Stuck (5:06) 1. Skepticism of Marketing and Sales (8:28) 2. False Sense of Uniqueness (12:43) 3. Knowledge-Inflated Pride (14:45) 4. Fear of Relational Intimacy (17:10) 5. Internet Addiction and Distractions (20:57) 6. Opportunity Cost of Inaction Visit me at thrivingtechnologist.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Want to quit working for companies as an employee, make more money, and choose the clients you work with? It might be time to go solo - as a technology consultant. To be successful, you need to be smart about how you start. In this episode, I share the exact steps I took to become a solo technology consultant offering software architecture and a variety of other professional services. Whether you're a programmer, in QA, DevOps, do Product Management, Data Science, or any other software development technology role - a technology consultant is not a contractor. You are actually starting a business, and so you need to think like one! I hope this episode helps you avoid some of the pitfalls that software engineers and other tech professionals can fall into when they try to work for themselves. Learn about SoloDev, a coaching package to bootstrap your solo consulting business https://thrivingtechnologist.com/services/software-development-coaching/solodev-coaching-package/ Join my Patreon:  https://thrivingtechnologist.com/patreon 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: (2:55) 10 Steps to Become a Solo Technology Consultant (3:00) 1. Design Your Services (6:38) 2. Discover The Client (8:51) 3. Price Your Services (11:16) 4. Build Client Awareness (13:37) 5. Incorporate (16:33) 6. Acquire Clients (19:01) 7. Negotiate Contracts (23:34) 8. Manage the Engagement (26:16) 9. Keep Financial Records (30:27) 10. Finish Strong and Get a Reference (34:15) Episode Groove Visit me at thrivingtechnologist.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Programmers have to learn an incredible amount of information to even BEGIN to be effective at their job. So it's only natural that we don't like to find out something we learned - is wrong in a different context. With so much invested, being open to the possibility that there's a better way to do things can be hard. In this episode, I share some mindset limitations that we can fall into in tech job roles. We can feel so strongly about experiences we've had, that they blind us from being open to other equally valid perspectives. Every one of these is a mistake I've made more than once in my career. I hope by being aware of these, you don't end up believing lies. Instead, this information can help you make wiser decisions on your software project - so you don't end up looking like a fool. Join my Patreon:  https://thrivingtechnologist.com/patreon TechRolepedia, a wiki about the top 25 roles in tech:  https://thrivingtechnologist.com/techroles The Thriving Technologist career guide:  https://thrivingtechnologist.com/guide Learn about one-on-one coaching with Jayme:   https://thrivingtechnologist.com/coaching You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:43) 5 Mindset Limitations Programmers Believe (1:53) 1. Binary Thinking (5:16) 2. Anecdotal Overconfidence (12:12) 3. Absolutist Stances (16:05) 4. Recency Bias (19:03) 5. Vanity Metrics Visit me at thrivingtechnologist.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Ever seen management bring in a technology consultant, and suddenly they're open to ideas you've been telling them all along? When this first happened to me, I figured technology consultants were probably just better at selling snake oil. But halfway into my career I became a software development technology consultant, and I learned they were masters of one thing I sucked at - communication. Here's the good news: you don't have to become a technology consultant to be a master of communication. It's simply a decision you make to focus on it. In this episode, I share 9 ways you can communicate like a consultant, that will get people to stop and listen to what you have to say with more authority and urgency on your software projects. Whether you're a software engineer, in QA or DevOps, or a product or product manager - we all respond to persuasive and informed communication the same way. I hope this helps you get unstuck in your career in technology, and achieve things you never thought were possible on your software development project! Join my Patreon:  https://thrivingtechnologist.com/patreon TechRolepedia, a wiki about the top 25 roles in tech:  https://thrivingtechnologist.com/techroles The Healthy Software Development career guide:  https://thrivingtechnologist.com/guide Learn about one-on-one coaching with Jayme:   https://thrivingtechnologist.com/coaching You can also watch this episode on YouTube.  Chapter markers / timelinks: (3:10) 9 Ways to Communicate Like a Consultant (3:17) 1. Be Business-Focused (5:11) 2. Presentation Skills (8:20) 3. Adapt To Your Audiences (12:25) 4. Frequent Feedback Loops (15:26) 5. Negotiation Skills (18:02) 6. Healthy Resistance to Rushing (20:34) 7. Project Documentation (23:38) 8. Client Relationship Management (26:34) 9. Continuous Learning (30:20) Episode Groove Visit me at thrivingtechnologist.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Most programmers have considered self-employment at one time or another, but fear grips them when they think about how to even get started. When I began working for myself 7 years ago, I had no idea how to transition to being self-employed, but I knew I couldn't stand working for corporations any longer. In this episode, I'll share the most common fears any programmer faces when they think about what it might be like to work for themselves. And for each of these fears, I'll offer some perspective on how I did it, and you can too. With the uncertainty of the software industry today (and really any tech job), relying on corporations for employment over our entire career may not be wise in the long run. I hope this episode offers some hope that self-employment isn't impossible as a programmer. But there is no escaping that you'll need to face your fears head on - and overcome them! Join my Patreon:  https://thrivingtechnologist.com/patreon TechRolepedia, a wiki about the top 25 roles in tech:  https://thrivingtechnologist.com/techroles The Healthy Software Development career guide:  https://thrivingtechnologist.com/guide Learn about one-on-one coaching with Jayme:   https://thrivingtechnologist.com/coaching You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:38) 1. 3 Reasons Programmers Fear Self-Employment  (1:44) 1.1 Financial Uncertainty (2:46) 1.2 Lack of Business Skills (3:54) 1.3 Comfort With Current Tech Job (5:46) 2. How To Overcome Self-Employment Fears (5:54) 2.1 Financial Planning and Savings (9:02) 2.2 Gradual Skill Development (11:53) 2.3 Start Small and Build Confidence Visit me at thrivingtechnologist.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards  

It's finally sinking in. Your software project is FAKE agile. Is there anything you can really do about it? The sad reality is that more companies have fake agile software development processes than those that are authentic. You can fight tooth and nail to try and change the system, or you can accept when there's nothing you can do. Being a truly agile software company is not usually something any individual programmer or manager can change. It has to start from the top. If the company doesn't do agile budgeting and have a culture of adapting to feedback, they are a typical feature factory focused on output over outcomes. In this episode, I offer some practical ways to let to of your frustration and do the best job you can given the circumstances. If you're the type of software engineer, manager, or any other tech job role that considers themselves a change agent - you may be challenged by this one. But this episode isn't for everyone. It's for those of us who are experiencing mental health issues, burnout, and anger over our software project being fake agile. I hope it offers some relief. Join my Patreon:  https://thrivingtechnologist.com/patreon TechRolepedia, a wiki about the top 25 roles in tech:  https://thrivingtechnologist.com/techroles The Healthy Software Development career guide:  https://thrivingtechnologist.com/guide Learn about one-on-one coaching with Jayme:   https://thrivingtechnologist.com/coaching You can also watch this episode on YouTube.  RELATED EPISODES Spot a Fake Agile Team in Under 7 Minutes! https://youtu.be/H6GdK-dChtY An Agile Budget Keeps You From Being a Code Monkey https://youtu.be/pG4wNLopMZA Is Your "Agile" Backlog Really a Waterfall Project? https://youtu.be/OosYzkP-pLk Can User Stories Make Software Projects Late? https://youtu.be/NavlPobhj7A Are Programmers Really To Blame For Bad Estimates? https://youtu.be/m5A1Wg8hYGo Chapter markers / timelinks: (0:00) Introduction (1:30) How to Cope With FAKE Agile Development (3:25) 1. Stop Forcing Change (5:10) 2. Exercise (7:25) 3. Become a Requirements Lawyer (10:33) 4. Charge for Changes (13:12) 5. Protect Your Reputation (15:12) 6. Define Your Own Success (21:54) Episode Groove Visit me at thrivingtechnologist.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

If you're bothered by the problems in the tech industry, I am too. But while every day we seem to hear more and more negative news about it - we're actually paying attention to the wrong problems. There are many things wrong with the software industry, but very few we can control. And one thing we can control, is how much we understand each other. Programmers complain that managers set unrealistic deadlines. Managers complain that programmers are lazy. And these are just two examples of the many different tech job roles where misunderstanding each other causes us to feel frustrated and hopeless. In this episode, I'm sharing my vision for how we can help each other get out of complaining about the tech industry - and DO something about it. While none of us is empowered to fix every problem out there, we can at least fix what's right in front of us. This episode marks a new chapter for the channel. I'm renaming it to Thriving Technologist! Thriving because we don't just need to be healthy in tech - we need to thrive and succeed. Technologist because we need to help not just software developers thrive, but everyone in the tech industry. Only when we have empathy for each other and stop seeing each other as enemies, can we stop the anger and begin building a better tech industry for us all to work in. So this is an official welcome to all the people who are not programmers over the years to join us in the effort to create a healthier, more sustainable workplace in tech for us all. Join my Patreon:  https://www.patreon.com/HealthySoftwareDeveloper  TechRolepedia, a wiki about the top 25 roles in tech:  https://healthysoftwaredeveloper.com/techroles/ The Healthy Software Development career guide:  https://healthysoftwaredeveloper.com/guide/ Learn about one-on-one coaching with Jayme:   https://healthysoftwaredeveloper.com/coaching/ You can also watch this episode on YouTube.  Visit me at healthysoftwaredeveloper.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Learning new technologies, frameworks, and processes as a programmer gives you a feeling of accomplishment. But unchecked, learning can become a dangerous addiction that damages your software development career. In this episode, I share how software engineers can cap their earning potential if they fall into common traps when learning is the absolute wrong thing to do. If you want to have a long career in software and get the rewards, recognition, and success you deserve - knowing when to (and not to) learn is essential. Join my Patreon:  https://www.patreon.com/HealthySoftwareDeveloper  TechRolepedia, a wiki about the top 25 roles in tech:  https://healthysoftwaredeveloper.com/techroles/ The Healthy Software Development career guide:  https://healthysoftwaredeveloper.com/guide/ Learn about one-on-one coaching with Jayme:   https://healthysoftwaredeveloper.com/coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:22) 1. How Learning Addiction Harms Tech Careers (1:28) 1.1 Procrastination (3:03) 1.2 Sunk Costs (3:57) 1.3 Declining Value (5:41) 1.4 Social Avoidance (7:15) 1.5 Work/Life Imbalance (8:48) 2. How To Know When Learning is a Trap (8:54) 2.1 Self-Delusion Your Project Requires It (10:01) 2.2 Self-Delusion You Need It To Get a New Job (11:20) 2.3 Influencer Hype and Vanity Metrics (13:03) 2.4 Tech Industry Pushes Fear of Missing Out (FOMO) (15:10) 2.5 Current Challenge Looks Easier in New Tech Visit me at healthysoftwaredeveloper.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Have you ever seen another programmer who wasn't as skilled as you get promoted? Did you tell yourself management was making a mistake? Earlier in my career I didn't realize I was doing some things that caused managers to lose confidence in me. I would spend all my time writing code and never think about how I came across to other people. In this episode, I share some harsh truths I've learned about how being a software engineer can cause us to do things we think the company wants - that actually hurt our reputation in the long run. Companies are actually paying you for confidence as a programmer. And this episode is full of practical strategies for making sure you don't fall into traps that stop you from getting recognized for the great code you write as a programmer - before your career is really getting started! Join my Patreon:  https://www.patreon.com/HealthySoftwareDeveloper  TechRolepedia, a wiki about the top 25 roles in tech:  https://healthysoftwaredeveloper.com/techroles/ The Healthy Software Development career guide:  https://healthysoftwaredeveloper.com/guide/ Learn about one-on-one coaching with Jayme:   https://healthysoftwaredeveloper.com/coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:19) 1. What Companies Really Want From Programmers (2:12) 2. How To Build Employer Confidence as a Programmer (2:22) 2.1 Minimize Communicating Problems and Doubt (5:42) 2.2 Repeat Management's Desires (7:46) 2.3 Anonymize Blame on Dependencies (10:57) 2.4 Reduce Your Throughput (14:52) 2.5 Elevate Your Coworkers (17:05) 2.6 Over-communicate Status (20:11) 2.7 Highlight Discovered Shortcuts (22:20) 2.8 Document Verbal Decisions (26:58) Episode Groove Visit me at healthysoftwaredeveloper.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Making videos, podcasts, or blogs could be just what your career as a programmer needs. But it could also be a complete waste of time. Many programmers become influencers, but there are two very different reasons for doing so. In this episode, I share the difference between being a pure influencer, or posting online for content marketing. Content marketing is helping people solve some problem they have with your content to encourage them to consider doing business with you. If you're considering working for yourself by starting a software product company, becoming a consultant or freelancer, or selling courses on software development or engineering - becoming an influencer through content marketing is the key to making sales and actually having a business. Join my Patreon:  https://www.patreon.com/HealthySoftwareDeveloper  Download my free career guide:  https://healthysoftwaredeveloper.com/guide/ Get access to TechRolepedia, a data hub about the top 25 roles in tech:  https://healthysoftwaredeveloper.com/techroles/ Learn about career coaching:   https://healthysoftwaredeveloper.com/coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:27) 1. The 2 Purposes of Online Content (1:31) 1.1 For Social Status and Influence (3:49) 1.2 Demonstrating Competence (6:09) 2. How Content Marketing Helps Your Career (6:14) 2.1 Getting a Better Job (7:38) 2.2 Sell Products and Services (10:03) 3. 5 Myths of Content Marketing (10:12) 3.1 Your Ideas Must Be Original (12:31) 3.2 You Have To Post Everywhere (13:40) 3.3 You Have To Post All The Time (17:04) 3.4 You Should Post a Variety of Topics (20:40) 3.5 You Must Post in All Mediums (23:51) 4. Building a Business Through Content (24:13) 4.1 Give Away Something Valuable (26:37) 4.2 Have a Contact Form (29:40) 4.3 Get Referrals Through Shares (32:53) Episode Groove Visit me at healthysoftwaredeveloper.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Six years ago I was suddenly struck with chronic insomnia where I couldn't sleep more than 3 hours a night. This lasted for nearly 3 years, and I struggled through sleep studies, behavioral changes, and all the typical tips you read online about overcoming insomnia. Working as a programmer in the tech industry can create a lot of anxiety because we work with our mind. And if your mind is stressed out, add on to that the pressure of personal relationships and finances - and you've got a recipe for horrible sleep problems. What ultimately treated my insomnia and helped me heal was a combination of psychological, behavioral, environmental, and physical changes I made. In this episode I share 25 practical steps you can try if you're personally struggling with getting a good night's sleep. I hope if you've lost hope that healing your insomnia is possible, my story and what I did gives you the courage to give it another try. Join my Patreon:  https://www.patreon.com/HealthySoftwareDeveloper  Learn about the CBT-i app:  https://www.ptsd.va.gov/appvid/mobile/cbticoach_app_public.asp  Download my free career guide:  https://healthysoftwaredeveloper.com/guide/ Get access to TechRolepedia, a data hub about the top 25 roles in tech:  https://healthysoftwaredeveloper.com/techroles/ Learn about career coaching:   https://healthysoftwaredeveloper.com/coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:15) Negative Effects of Insomnia (2:19) Categories of Insomnia Solutions (2:29) 1. Psychological Sleep Solutions for Insomnia (2:35) 1.1 Wrap Up Your Workday (3:57) 1.2 Keep a Notepad By Your Bed (5:03) 1.3 Schedule Worry Time (7:04) 1.4 Do 1 Thing You're Putting Off (8:41) 1.5 Reduce Social Media Use (9:21) 2. Behavior Sleep Solutions for Insomnia (9:27) 2.1 Set a Realistic Sleep and Wake Time (11:54) 2.2 Don't Look at The Clock (12:58) 2.3 Only Use Your Bed for Sleep or Sex (14:10) 2.4 Stay off Devices for an Hour Before Bed (15:19) 2.5 Quit Drinking or Doing Drugs (16:35) 3. Environmental Sleep Solutions for Insomnia (16:40) 3.1 Keep Your Room Dark and Cold (18:28) 3.2 Use a Fan or White Noise Generator (19:37) 3.3 Use Tungsten Light Bulbs (21:32) 3.4 Use a CPAP Machine or Tape (23:05) 3.5 Side Sleeping with a Tall Pillow (24:20) 4. Physical Sleep Solutions for Insomnia (24:24) 4.1 Don't Eat or Drink After Dinner (25:33) 4.2 Cardio Exercise Every Morning (28:45) 4.3 Reduce or Eliminate Caffeine (31:07) 4.4 Drink Water Throughout the Day (32:29) 4.5 Get Enough Magnesium Visit me at healthysoftwaredeveloper.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

We programmers love to "do it ourselves", and this can help us stay productive and keep ourselves busy. But the dark side of this tendency, is that it can make it harder to get help - when we actually need it. In this episode, I share some ways I've learned that software engineers are trained by society, the workforce, and the software industry to resist getting help from others. Then I offer some practical questions you can ask yourself to know if you're in a situation where you should really adopt the DIY mindset - or avoid getting trapped into learning something you don't need to. Join my Patreon:  https://www.patreon.com/HealthySoftwareDeveloper  Download my free career guide:  https://healthysoftwaredeveloper.com/guide/ Get access to TechRolepedia, a data hub about the top 25 roles in tech:  https://healthysoftwaredeveloper.com/techroles/ Learn about career coaching:   https://healthysoftwaredeveloper.com/coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:22) 1 3 Reasons Why Programmers Don't Get Help (1:28) 1.1 Individualized Education (2:02) 1.2 Corporate Reinforcement (2:41) 1.3 Gossip over Substance (4:49) 2 5 Reasons DIY Can Be a Bad Idea (4:57) 2.1 Low Repeatability Activity (6:41) 2.2 Outside Your Core Skill Set (7:41) 2.3 You've Failed 3 Times (9:23) 2.4 You Keep Putting It Off (10:41) 2.5 Easy Access to An Expert (12:33) Episode Groove Visit me at healthysoftwaredeveloper.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

Ever try to sell someone on why you're the right person for them to hire in tech? Or maybe you have a software product or offer freelance IT consulting services you need to sell? I'll bet you've run into the situation where the other person you're talking to doesn't seem to "get" why you're the best solution to their tech problems. In this episode, I share what I've learned through digital marketing about how to really connect with the person you're convincing in tech, so they can understand the value you offer - and buy your idea. This can help you escape the corporate grind and work for yourself as an entrepreneur, consultant, coach - or sell courses. But it can also help you with the everyday challenge of convincing software architects, managers, and anyone you work with to support any idea you have. Download my free Career Guide here:  https://healthysoftwaredeveloper.com/guide/ Get free access to TechRolepedia here:  https://healthysoftwaredeveloper.com/techroles/ Need help with your career? Learn about career coaching:   https://healthysoftwaredeveloper.com/coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (3:02) Episode Outline (4:25) 1 How Aware Is Your Prospect of The Problem? (5:10) 1.1 Problem Unaware (7:27) 1.2 Problem Aware (9:46) 1.3 Solution Aware (10:43) 1.4 Ready to Buy (13:46) 2 How Well Do You Know Your Prospect? (14:44) 2.1 Basic Demographics (16:12) 2.2 Industry-Specific Demographics (18:21) 2.3 Psychographic Profile (21:29) 3 Are You Selling To The Right Prospect? (21:37) 3.1 Who's The Ultimate Buyer? (23:52) 3.2 What's The Prospect's Budget? (25:47) 3.3 How Urgent Is Solving The Problem? Visit me at healthysoftwaredeveloper.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

On the first software project of my career, I thought doing a good job was all that mattered to move ahead. And while I was successful, I was manipulated by many other programmers through political games. After that experience, I was tempted many times in my career to fight dirty. And sometimes, I made the wrong decision. In this episode, I share the reasons why we're tempted as coders on software projects to throw ethics to the wind when the temptation for money, power, or prestige are strong. And how falling prey to that temptation may get you ahead in the short term, but it hurts you in the end. I hope you find some encouragement to take the high road when faced with political games on software development teams, and refuse to bend to other people's will who are unethical! Download my free Career Guide here:  https://healthysoftwaredeveloper.com/guide/ Get free access to TechRolepedia here:  https://healthysoftwaredeveloper.com/techroles/ Need help with your career? Learn about career coaching:   https://healthysoftwaredeveloper.com/coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (2:04) 1. Why Programmers Are Tempted To Fight Dirty (2:09) 1.1 High Stakes Competition (3:00) 1.2 Visibility and Recognition (3:50) 1.3 Fear of Obsolescence (5:32) 1.4 Cultural and Structural Encouragement (8:22) 1.5 Misguided Notions of Success (9:37) 2. Resisting Corruption in Tech (10:31) 2.1 Long Term Results & Reputation (12:39) 2.2 The Power of Networking (14:54) 2.3 Personal Peace and Satisfaction (17:17) 2.4 The Ripple Effect of Positivity (18:42) 2.5 Faith In Doing The Right Thing (20:10) Episode Groove Visit me at healthysoftwaredeveloper.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

After my first decade of coding, I learned so much I thought: "I must be at least somewhat intelligent, right?". But there was something more valuable I lacked - wisdom. Without wisdom, you'll make decisions in your career that look right in the short term - but turn out disastrous over time. Wisdom is the ability to make decisions when the rules don't apply. There's no book you can read, no guide to follow, and no clear cut answer. It's derived from experience, sound judgment, a broad perspective, and considering the ethical implications of a decision. And if you learn to cultivate wisdom, you can achieve the things that really matter in your career - and life. In this episode I share why people in tech careers often mistake intelligence for wisdom. Then I'll help you understand why our industry is so prone to making unwise decisions. I'll go on to help you see the dangerous outcomes of short-term thinking. And finally, I'll share some practical things you can do to become a wiser programmer - and technologist in general. Download my free Career Guide here:  https://healthysoftwaredeveloper.com/guide/ Get free access to TechRolepedia here:  https://healthysoftwaredeveloper.com/techroles/ Need help with your career? Learn about career coaching:   https://healthysoftwaredeveloper.com/coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:23) Defining Intelligence and Wisdom (2:14) Stories of Intelligence and Wisdom (5:10) 1. How Tech Jobs Confuse Intelligence and Wisdom (5:20) 1.1 Equating Problem Solving with Broad Insight (6:27) 1.2 Prioritizing Speed over Sustainability (7:51) 1.3 Specializing vs Holistic Understanding (9:44) 2. How Ignoring Wisdom Hurts Us in Tech (9:51) 2.1 Ethical Implications (12:42) 2.2 Short-Term Over Long-Term Thinking (13:45) 3. How To Be a Wiser Technologist (13:52) 3.1 Expand Your Breadth of Knowledge (16:35) 3.2 Get a Mentor (18:30) 3.3 Reflect and Be Mindful (22:02) 3.4 Seek the Counsel of Generalists (25:02) 3.5 Engage with Non-Technical Communities Visit me at healthysoftwaredeveloper.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards

If you want a lasting career in software development, you've got to be wiser than your average coder. There's a lot of advice that promotes short-term thinking around programming, and if you aren't careful you can burn your bridges before you reach the finish line. In this episode, I share what I've learned about why most programmers don't last in their career. There are 8 laws to a lasting career as a programmer. If you follow these laws, you'll not only move ahead much faster than most programmers - you'll be able to develop software in a healthy way! Download my free Career Guide here:  https://healthysoftwaredeveloper.com/guide/ Get free access to TechRolepedia here:  https://healthysoftwaredeveloper.com/techroles/ Need help with your career? Learn about career coaching:   https://healthysoftwaredeveloper.com/coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:33) 8 Laws to a Lasting Programming Career (1:52) 1. Embrace the Imposter (3:08) 2. Make Technology Stupid Simple (4:27) 3. Buffer and Delay Commitments (7:21) 4. Skip the Leveling Grind (9:29) 5. Pick Your Battles (11:18) 6. Always Be Networking (12:40) 7. Know When You're The Code Monkey (14:27) 8. Get Out While You Can (17:50) Episode Groove Visit me at healthysoftwaredeveloper.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards  

The familiar question "should I stay or should I go?" is common to programmers, or really anyone in a tech job. But it's tempting to just bail the moment you don't like some aspect of the job, hoping for greener pastures. The flipside of this is when you probably should have left a long time ago but you stick around! Hey, I've been there. It's easy to have fear and blind spots make it hard to know what to do. In this episode I share 7 signs it may be time to quit your toxic tech job and move on to something better. If you only see several of these signs, that's actually pretty normal. But if you're stacking up a bunch of these (or a few are particularly bad) you need to take action! Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:57) 7 Signs it's Time to Quit Your Tech Job (2:42) 1. Personal and Professional Stagnation (3:32) 1.1 Self-Serving Pitching of Opportunities (4:42) 1.2 Career Advancement Opportunities (6:15) 2. Misaligned Goals or Ethics (6:22) 2.1 Unethical Asks by Company (7:19) 2.2 No Passion for Company (8:20) 3. Toxic Work Environment (8:30) 3.1 Poor Decisions by Management (9:47) 3.2 Micromanagement (10:56) 3.3 Lack of Support  (11:50) 3.4 Overwork Culture (13:15) 3.5 Undervalued Employees (14:25) 3.6 Rife with Politics (15:56) 4. Work/Life Imbalance (16:04) 4.1 Unsustainable Work Hours (16:59) 4.2 No Flexibility (18:28) 5. Compensation Below Industry Standard (19:08) 5.1 Mismatch betweeen Qualifications and Pay (20:27) 5.2 Lack of Benefits (21:31) 6. Diminished Quality of Work (21:42) 6.1 Lack of Motivation (22:28) 6.2 Overlooked Contributions (23:24) 7. Better Opportunities Elsewhere (23:41) 7.1 Talk to People When Employed! (25:14) 7.2 Failure to Follow Industry Changes (26:32) Episode Groove Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on LinkedIn as jaymeedwards  

You already know working in tech while staying in a romantic relationship is hard if you spend a lot of time on the computer. But there are other even more dangerous aspects of a tech job that can risk losing your romantic partner if you aren't careful. In this episode, I share lessons I've learned while married for 25 years to the same woman - and working in tech at the same time. It wasn't easy and I almost lost her a few times. But eventually I learned how to both be a successful programmer - and stay married. I hope this episode helps you avoid divorce or breakup if you're trying to balance a healthy relationship with a romantic partner with progression in your tech career. Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (2:15) 1. 5 Ways Tech Sabotages Relationships (2:45) 1.1 Long and Unpredictable Work Hours (6:14) 1.2 Communication Breakdown (7:58) 1.3 Financial Stress and Lifestyle Inflation (11:01) 1.4 Lack of Shared Interests & Experiences  (14:55) 2. 3 Ways to Keep a Relationship Healthy Working in Tech (14:13) 2.1 Schedule & Prioritize Quality Time (17:56) 2.2 Open Communication of Stress & Expectations (22:35) 2.3 Establish Boundaries With Work and Home Life Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards

If you've never been an addict, you may be surprised to know many programmers (and other people in tech job roles) struggle with drug use. Nobody working in tech is a stranger to stress and pressure! But sometimes the ways we cope are unhealthy. If you're currently using, I've been honest and transparent with you - I've been there. I was a marijuana addict for 25 years, and often used it with the rationale that it helped me manage the stress of my job. However, I learned the hard way that using drugs to cope with work creates more problems than it solves. In this episode, I'd like to help you understand WHY drug use is so prevalent in the tech industry. I'll also share the consequences to your career that arise from ongoing use of drugs. And finally, I'll offer some healthier ways to cope with the inherent problems that programming and tech related jobs introduce - rather than turning to drugs as a coping mechanism. I hope this helps you have some compassion for your coworkers who may be trapped in addiction, do what you can to improve the conditions we all work in, and if you're currently struggling - get help so you can flourish in your career! Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:12) Three Stories of Drug Use in Tech (5:32) 1. Why Do Programmers Use Drugs? (5:36) 1.1 Attempt To Inspire Creativity (7:27) 1.2 High Stress and Pressure (11:09) 1.3 Isolation and Lack of Social Support (13:36) 1.4 Normalizing Culture (14:57) 1.5 Burnout and Mental Disorders (17:01) 2. How Drugs Make Work Harder (17:08) 2.1 Impaired Cognitive Function (19:23) 2.2 Damage Mental and Physical Health (21:50) 2.3 Legal and Ethical Consequences (24:21) 3.1 Supportive Community (26:53) 3.2 Adopt Prayer or Mindfulness (30:23) 3.3 Better Nutrition and Exercise (34:11) Episode Groove Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards

The popular thing to do when faced with a toxic software project - is to complain until you get out. But a healthier alternative, is to use it as an opportunity to get stronger in your tech career. In this episode I share some things I learned by reflecting back on my career through the lens of the book of Proverbs from the Christian Bible. It showed me that I actually have more opportunities to grow than I thought when I deal with difficult software projects. I hope that even if you don't believe in the Bible, it maybe causes you to step back and look at your suffering through a different lens. And if you do believe, it encourages you to put your faith to action whether you're a programmer, product manager, QA tester, in DevOps - or really any role on a software project! Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:07) 5 Ways To Grow From a Toxic Project  (3:11) 1. Gain Resilience Through Adversity  (7:40) 2. Enhance Problem Solving Skills  (12:20) 3. Improve Collaboration Skills  (18:39) 4. Grow Empathy and Leadership Skills (22:56) 5. Increase Appreciation for Positive Jobs (26:20) A Story of a Toxic Hire (30:00) Episode Groove Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards

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! Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (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 JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards

The software industry may be messed up, but I need to be straight with you. You're resisting help! If you really want your job and life to get better, and to achieve better things in your software career - the complaining needs to stop. You need to stop resisting the things you already know you should do - and DO them. You can't solve all these problems alone! In this episode, I'm going to share some harsh truths with you about your responsibility for why your career may suck. I don't share these to criticize you, but to help you confront the seriousness of your situation - and show you how you are truly more empowered to change it than you may realize. Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (4:55) 5 Ways We Stay Miserable  (6:34) 1 Tribalism (10:22) 2 Avoiding Responsibility (13:17) 3 Giving In To Fear (18:08) 4 Escapism (21:21) 5 Pride Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards

If you're about to get a new tech job, sometimes the red flags are obvious. But what happens when you want the gig anyway? The temptation to take a job when the pay is high, there's prestige, or it's a promotion are strong. In this episode I share some things I've learned about spotting these red flags, and resisting the temptations that come with the allure of tech company offers. I hope they help you take a more healthy job, and not get sucked into working for a company that drains your soul. Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (1:16) A Story of Deceit (6:32) 1. Red Flags of a Toxic Tech Company (6:52) 1.1 Vague Answers About Work/Life Balance (8:18) 1.2 Long Hours Are a Bade of Honor (10:02) 1.3 Suspiciously High Salary of Title  (11:34) 2. Why Do We Ignore Red Flags? (11:40) 2.1 Justifying Stress With Money (13:27) 2.2 "It's a Stepping Stone" (15:54) 2.3 Need to "Prove Our Worth" (18:03) 3. How Can You Overcome The Temptation? (18:12) 3.1 Make a Relational Impact List (20:13) 3.2 Ask Brave Questions (22:51) 3.3 Avoid Companies That Resist Transparency (24:22) 3.4 Listen to Your Gut! (26:20) 3.5 Write a Catastrophic Story (28:31) Episode Groove Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards

If you're tired to the deadlines, pressure, and unrealistic expectations - it may be time to take programming for money into your own hands. In this episode, I share 3 ways you can escape the corporate grind and make money in tech yourself. Being a solopreneur isn't easy, but it's very rewarding if you're willing to learn things like digital marketing. I weigh 5 aspects of considering being a solo IT consultant, starting a solo software product company, or selling what you know about technology through online courses in this episode. Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (0:34) 1. 3 Ways To Escape The Corporate Grind (0:48) 1.1 Solo Consulting / Freelancing (3:23) 1.2 Build a Software Product (5:49) 1.3 Sell Education Online (10:01) 2. 5 Aspects of Each Method of Escape  (10:12) 2.1 Effort vs. Income (15:20) 2.2 Marketing Effort (21:42) 2.3 Dependence on Others (27:19) 2.4 Transition Cost (34:53) 2.5 Learning Required Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards

Programming starts out like any other career - then one day you wake up addicted. In this episode, I share big problems with programming's impact on your work/life balance, and offer solutions. As a software developer, it's easy to get caught up in the endless cycle of coding and problem-solving, often at the expense of personal time and well-being. I discuss how this imbalance can affect your life and provide insights on how to manage it effectively. I also share some personal experiences and tips on maintaining a healthy balance between your programming career and your personal life. The video is not just about coding; it's about living a fulfilling life while pursuing your passion for programming. Remember, programming is an exciting and rewarding career, but it's important to balance it with other aspects of your life. Don't forget to like, share, and subscribe for more content on navigating the challenges of a software development career. Your support means a lot!  Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (01:45) 1 Signs Programming Is Taking Over Your Life (02:07) 1.1 Only Digital Free Time (03:42) 1.2 Stimulate and Chill Cycle (06:12) 1.3 No Quality Time with Friends or Family (07:58) 1.4 No Non-Technical Hobbies (10:50) 1.5 Living Paycheck to Paycheck (12:52) 2 Life Changes To Get Time Back from Programming (12:59) 2.1 Divorce Yourself from Software Industry Values (15:52) 2.2 Schedule Social Activity After Work (18:43) 2.3 Get Control Over Your Finances (21:56) 2.4 Explore Other Tech Job Roles (24:50) 2.5 Have a Career Exit Plan (29:10) Episode Groove Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards

Feeling swamped in your tech job? You're not alone! In this episode, I dive into the heart of what makes our programming world so overwhelming and, more importantly, how you can navigate it with ease. In this episode, I'm not just talking at you; I'm talking with you. We'll explore the common pitfalls that lead to feeling overwhelmed in tech jobs and share practical, actionable strategies to help you manage your workload and stress levels. Whether you're a seasoned programmer or just starting out, this video is packed with insights tailored just for you. Programming can be a rollercoaster of challenges and triumphs, and it's totally normal to feel overwhelmed at times. But don't worry, I've got your back! We'll look at how to prioritize tasks, set realistic goals, and create a work environment that supports your well-being and productivity. Remember, being overwhelmed doesn't mean you're failing – it's a sign that you're pushing your boundaries and growing. So, let's turn that overwhelm into empowerment together! Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (01:41) How To Stop Being Overwhelmed By Your Tech Job  (02:31) 1.1 Relentless Pace of Projects (03:17) 1.2 Pressure To Continuously Learn (04:32) 1.3 Glorification of Hustle Culture (05:47) 2 Signs of Being Overwhelmed (06:01) 2.1 Constant Fatigue / Lack of Motivation (08:36) 2.2 Brain Fog (09:41) 2.3 Feeling Inadequate Despite Achievements (10:36) 2.4 Anger at Requests for Help (12:13) 2.5 "Too Busy" for Social Activities (13:08) 3 How To Reduce Overwhelm (13:21) 3.1 Prioritize Your Tasks (15:38) 3.2 Learn To Say No (17:20) 3.3 Practice Mindfulness or Prayer (19:34) 3.4 Exercise and Get More Sleep (21:51) 3.5 Social Media Fast Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards

Let's get real about AI and how it impacts programming. There's a lot of propaganda and fear being thrown around related to artificial intelligence (especially in software development and engineering) - so let's cut through the noise together. I made this video for all you software developers, engineers, and programmers out there who want to get a real perspective on AI's role in our field. Whether you're deep into your software career or just starting out, I've got some insights that you'll find valuable. Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (0:00) Introduction  (4:01) 1. Who Stands To Gain From AI Hype? (4:10) 1.1 The Media (5:08) 1.2 Employers (6:04) 1.3 Startups (7:27) 1.4 Tech Training Companies (8:24) 2 A Rational AI Approach for Programmers (8:30) 2.1 Become an AI Generalist (10:00) 2.2 Spot The Sensationalism (11:52) 2.3 You Are The Compiler (14:38) 2.4 Use AI To Diversify Your Skills (18:11) 2.5 Build a Non-Technical Industry Product (20:22) 2.6 Teach Non-Technical Companies AI Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards

If you've been programming for a while and it doesn't seem as fun as it used to be, maybe it's time to take a step back and look at why. In this episode I'd like to help you figure out what the the root cause of your frustration with coding might be. It's only natural that if you started off writing code and eventually got good at it, you'd come to the conclusion that programming is the best tech job for you. But there could be a better fit, or you may need to double down on persuasion and some other skills than just writing code. When you're on too complicated of a tech stack, you haven't learned important soft skills like persuasion, and you make work your life - it's pretty likely that coding is going to start to suck. The good news is, you don't have to stay that way! By identifying which of these reasons for why you're not having as much fun programming apply to you, it's possible to start taking action today to get your tech career back on track. Get free access to TechRolepedia here:  https://jaymeedwards.com/access-techrolepedia/ Download my free Career Guide here:  https://jaymeedwards.com/developer-career-guide/ Need help with your career? Learn about career coaching:   https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks: (0:00) Introduction (0:40) Why Isn't Programming Fun Anymore? (0:56) 1. You're Not Challenged (2:16) 2. Programming Not Biggest Talent (4:23) 3. Your Industry Is Boring  (5:26) 4. Tech Stack Too Complicated (6:28) 5. You're Not Learning To Influence (8:09) 6. Your Job Is Toxic (9:30) 7. Work Is Your Life (11:18) Episode Groove Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards