DiscoverHealthy Software Developer
Healthy Software Developer

Healthy Software Developer

Author: Jayme Edwards

Subscribed: 222Played: 2,833
Share

Description

If working on software teams feels complicated, frustrating, and filled with politics - that's just because your eyes are open. Unfortunately, you do need to make a living! So how do you keep up with the demands of your tech job and still have a life outside of work? Hi I'm Jayme Edwards, and I've had a 26 year career in the software industry filled with thrilling victories - and maddening drama. With so many problems in our industry, the more money I made the more ridiculous people's expectations were. I’m sharing the biggest mistakes I made in my career, and the insights I learned along the way. This podcast is the audio version of the Healthy Software Developer YouTube channel, where you can find new episodes every Monday. Podcast versions appear on Wednesday of the same week. Subscribe and join us! Let’s help each other grow a community of healthy software developers.
140 Episodes
Reverse
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
How does being a software architect differ from a typical programmer? In this episode, I share the 10 aspects I've approached software architecture from that I learned over 20 years of doing it. I was promoted to be a software architect at just 20 years old, and while I was qualified with some aspects of software engineering - I didn't really know what I was getting myself into. Being a great software architect takes a variety of skills that a typical software developer will also benefit from, but are actually essential to software architecture. Yes, using coding patterns, knowing how to interview as a software architect, and making technology selections are required. But there are also other things that if you don't focus on, can hamper your ability to pursue a software architect role either at your current job, or the next one. I hope this episode helps you understand that while there is some overlap between a software architect and a programmer, the less "fun" aspects of the job are actually essential to being a really great one. 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:51) 10 Aspects of Being a Software Architect (1:03) 1. Zoom In / Zoom Out (2:17) 2. Domain Sensitive (3:07) 3. Understand Tradeoffs (4:02) 4. Selfless Decision Maker (5:02) 5. Embrace Change (5:44) 6. Communicative Mastery (6:26) 7. Infrastructure Aware (7:40) 8. Strategic Coder (8:50) 9. Consider Scale (10:28) 10. Cost Sensitive (11:49) Episode Groove Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards
One of the biggest challenges for all software developers in 2023 (and leading into 2024) - is simplifying their tech stack so work can get done. The continued explosion of boutique frameworks and libraries is making it harder than ever to manage complexity as the stack of tools and technologies we use on our projects grows. Whether you're a software architect, senior engineer or developer, or any other role that encounters tools and technologies on a software project - the decisions we make about what frameworks, APIs, libraries, and other pieces of technology to use on a software project impact us all. In this episode, I'd like to help you simplify your tech stack by sharing some of the things I've learned as a software architect about making informed and reasoned decisions about tech stack choices. I hope it helps you avoid some of the typical pitfalls we programmers can fall into when we select tools and technologies as soon as we find them - instead of stepping back and finding out if they're really high value enough to the team to adopt using them. 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 (1:07) 1 THE DANGERS OF TECH STACK COMPLEXITY (1:12) 1.1 Tool Overload (1:40) 1.2 Decision Fatigue (2:03) 1.3 Integration Challenges (2:34) 1.4 Cost Implications (3:26) 1.5 Diluted Focus (3:44) 2 SIMPLIFYING YOUR TECH STACK (3:52) 2.1 Prioritize Value (6:35) 2.2 Embrace Versatile Tools (7:39) 2.3 Standardize and Document (8:50) 2.4 Seek Community Input (10:01) 2.5 Regular Review and Upgrading (11:33) Episode Groove Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards
Burnout is one of the most common dangers to programmers over their career, and I was no exception. Software development and programming can make it difficult to find a healthy balance between work and life. My burnout was a combination of self-inflicted bad decisions, things done to me, and circumstances in my personal life.  In this episode, I share the story of my own burnout and how I lost nearly everything. Through it all, I found what really matters in life - and work became a smaller part of it. I hope this episode encourages you to share your own struggles to get help. Maybe some of the things I learned after going through burnout can also encourage you to keep going. My wife Angie's podcast, "A past, repainted" is here:  https://apastrepainted.com/content/podcast/ 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:59) 1 SELF-INFLICTED BURNOUT CAUSES  (1:05) 1.1 People Pleasing  (1:41) 1.2 Overextending at Work  (2:03) 1.3 Side Gigs  (2:15) 1.4 High Expenses  (2:51) 1.5 Drug Addiction  (3:18) 1.6 Guilt and Shame  (3:59) 2 OTHER-INFLICTED BURNOUT CAUSES  (4:16) 2.1 Political Lies and Manipulation at Work (5:31) 2.2 Recurring Project Firefighting (6:42) 2.3 Betrayed by a Coworker (8:04) 3 CIRCUMSTANTIAL BURNOUT CAUSES (8:34) 3.1 My Child Struggled With Dangerous Addiction  (10:07) 3.2 My Father Died At a Young Age (10:45) 3.3 9/11 Work Culture Changes (12:04) 3.4 My Wife's Abuse  (13:36) 4 BURNOUT TRIGGERS (13:42) 4.1 Startup Partner Exited (14:27) 4.2 Marriage Became Distant (15:13) 4.3 Recurring Relapse of My Child (15:54) 4.4 Company Bought Out  (17:04) 5 MY BURNOUT SYMPTOMS (17:12) 5.1 Chronic Insomnia (19:03) 5.2 Uncontrollable Anger (19:47) 5.3 Forced to Resign (20:25) 5.4 Spent Emergency Savings (21:29) 5.5 Spent Remaining Cash (21:49) 5.6 Sold All My Stocks (22:09) 5.7 Fell Behind on Mortgage (22:54) 6 STRUGGLING THROUGH RECOVERY (23:05) 6.1 Tried Quitting Development (23:33) 6.2 My Wife and I Found God (26:11) 6.3 My Addicted Child Moved Out (27:03) 6.4 I Started on YouTube (28:32) 6.5 I Started Career Coaching (30:43) 6.6 My Sleep Improved (32:01) 7 HOW BURNOUT CHANGED ME (32:11) 7.1 Recovery is Daily (32:31) 7.2 Confronted My Addiction (33:09) 7.3 Became Aware of My Limits (34:01) 7.4 Embraced My Suffering (34:24) 7.5 Motivated By Change (36:50) 7.6 I Began Tithing (39:03) 7.7 Learning To Live Sober (40:13) 7.7 Focus on The Positive (41:09) 7.8 Reject Being Defined By Work (43:56) Episode Groove Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards
Trusting people is getting tougher than ever these days, and nobody seems to have a harder time than programmers and managers. In this episode, I'll teach you how to get some hard evidence to determine whether your manager is trustworthy or not. The goal is for you to find out YES and just have a healthy relationship with your manager. But if there are trust issues, you'll have some tough decisions to make about your software development career. This episode can help anyone who has a boss on a software project (programmer, QA, DevOps, etc.), but since there are some unique ways programmers can have their trust broken by managers - I'll focus on that. 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? Book a free career consultation:  https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks:  (0:00) Introduction (2:36) 1 WHY DON'T PROGRAMMERS TRUST MANAGERS? (2:48) 1.1 Manager Can't Do What Programmers Can (4:17) 1.2 Limited Visibility in Command and Control (6:35) 1.3 Hearsay (8:05) 1.4 Power Dynamics of Reporting to Someone  (9:43) 2 WHY DON'T MANAGERS TRUST PROGRAMMERS? (9:55) 2.1 Can't Comprehend All of Their Work (11:01) 2.2 Past Bad Experiences (12:26) 2.3 Remote Visibility Problems (13:36) 2.4 Assumptions of Immaturity (15:30) 2.5 Anxiety Due to High Cost (17:26) 3 HOW TO LEARN IF YOUR MANAGER IS TRUSTWORTHY (17:41) 3.1 Micro-Commitments (19:49) 3.2 Corroborate With Coworkers (22:14) 3.3 Corroborate With "Skip Level" Boss (24:55) 3.4 Set and Track Measurable Objectives (27:48) Episode Groove Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards
Just the name Tech Lead has this kind of prestigious ring to it, and if you're like most programmers you might think it's the job to shoot for. But 20 years of my career have been spent leading software teams, and you might be surprised to know that tech lead is actually the worst job for most programmers! Some of the information in this episode applies to IT professionals in any technical leadership role: whether that be leading programmers, UX, DevOps, QA - or any other discipline related to software development. But several of the points are more specific to programming leadership. 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? Book a free career consultation:  https://jaymeedwards.com/services/software-development-coaching/ You can also watch this episode on YouTube.  Chapter markers / timelinks:  (0:00) Introduction  (1:20) 1 TECH LEAD MYTHS  (1:29) 1.1 Smartest Team Member  (2:11) 1.2 Writes The Best Code  (2:59) 1.3 Chooses Key Technologies  (3:45) 1.4 Most Highly Compensated  (4:12) 1.5 Motivates Through High Standards  (5:19) 2 WHAT SHOULD A TECH LEAD DO?  (5:22) 2.1 Improve Team Effectiveness  (6:35) 2.2 Defend Team Members  (7:52) 2.3 Congratulate Team Publicly  (9:00) 2.4 Getting Team Consensus  (10:19) 2.5 Help When Things Get Hard  (12:57) 3 HOW BAD TECH LEADS GET PROMOTED  (13:28) 3.1 Strong Individual Contributor  (14:13) 3.2 Company Promotes Out Of Fear  (15:01) 3.3 Management Misunderstands Role  (15:25) 3.4 No Desire To Lead  (16:15) 4 BECOMING A TECH LEAD  (16:34) 4.1 Practice Defending Your Team  (18:19) 4.2 Practice Congratulating Team  (19:30) 4.3 Read Books on Leadership  (20:46) 4.4 Work Closely With Others  (21:52) 4.5 Learn More About the Business  (23:28) Episode Groove  Visit me at JaymeEdwards.com Find me on X as @jaymeedwards Find me on Instagram as jayme.c.edwards
As programmers, we often follow practices because of hidden desires - and "self-documenting code" is chief among them. In this episode I'd like to share some of the tradeoffs and implications of choosing to add comments to your code or not, to help you make the best decision for your software development career. When I first started developing software 25 years ago, the company I worked at mostly used C++ with a little Visual Basic and Java. At that time, all the other software engineers I worked with added comments to their code. And at the next two software product companies I worked for, programmers also chose to add source code comments as a regular practice. But once I moved to Austin, Texas 15 years ago and got my first job as an IT consultant I noticed something interesting. None of the other programmers on my team added ANY comments to their code! When I asked them about this, they would often say "the client is paying for features, not comments". I didn't find this a very acceptable reason for not adding comments to code, but I did my best to play along. Around this time the popular programming practice of "self-documenting code" first showed up on my radar. The idea being if we write our code with a clear enough intent, but using business terms and clean designs for the software we write, comments are unnecessary. But upon closer inspection I found this to be (in my opinion) wishful thinking rooted in laziness, upon a host of other factors. I hope this episode helps you make an informed decision about whether the benefits of code comments are worth writing them, or whether you should continue to practice self-documenting code as a principle. I believe we can have the best of both worlds: well-written code that reflects the business domain and is simpler to read, but with accompanying comments to reduce the time it takes for our software development team to use the APIs, helper classes, and other functionality our code and libraries provide. You can also watch this episode on YouTube.  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/ Chapter markers / timelinks:  02:50 Why Practice "Self-Documenting" Code? 02:56 #1 Laziness 04:43 #2 Reduce Visual Clutter 05:43 #3 Refactoring Burden 06:39 #4 Overconfidence in Simplicity 07:56 6 Benefits to Commenting 08:03 #1 Reduce Comprehension Effort 08:50 #2 Accelerate Business Understanding 09:50 #3 Use Comment Features in Editor 11:03 #4 Surface Code Behavior 12:07 #5 Additional Documentation Opportunities 12:48 #6 Treat Code Like a Product 13:51 Episode Groove Visit me at JaymeEdwards.com Find me on Facebook at JaymeEdwardsMedia Find me on Twitter as @jaymeedwards
loading
Comments (1)

Gary Stokley

I'm interested in participating in programming-related discussions, but I'm relatively new to this field. Any opportunity to exchange experiences is incredibly valuable to me. Additionally, I frequently encounter challenges when completing tasks. That's why programming homework help has become an indispensable resource for me https://www.programmingassignment.net/ It allows me to consistently prepare on time and even achieve high grades for my work.

Feb 5th
Reply
Download from Google Play
Download from App Store