
Advertise on podcast: Developer Reborn
Rating
5from
This podcast has
11 episodes
Language
EnglishPublisher
Jayme EdwardsExplicit
No
Date created
2026/01/03
Latest episode
2026/11/19
Average duration
17 min.
Release period
33 days
Description
Earn more respect, money, and time from your software development career—by creating a signature offer for a technical guidance service.
Unlock Developer Reborn podcast Email contact info,
Listeners & Audience details
Email contact information
Direct podcast contact details

Listeners
Audience numbers & engagement insights

Audience details
Podcast Insights

Podcast episodes
Check latest episodes from Developer Reborn podcast
AI Made Developers Own Every Mistake. Here's a Way Out.
2026/11/19
AI made writing code cheap, but it didn't make mistakes cheap. If you're an experienced developer, you're probably the one cleaning them up at 10pm. The productivity gains from AI became the expectation. Work that used to take four roles now lands on you "with AI." You review more code than you can understand, your name is on the PR, and when production breaks, it's still on you. That's how AI burnout catches senior developers who are good at their jobs.
Learn about the Solo Technical Consultant Workshop
In this episode I tell you about a developer in my last workshop who spent the week arguing with two managers over Slack about a weekend production release, during the same week he was supposed to be finding a way out. Then I show you why the mess AI is creating is your opportunity. Companies are shipping more code than anyone understands, which means growing code review backlogs, incidents nobody can trace, and deployments that "worked" until they didn't. Someone with a budget feels those problems, and that's what companies pay software consultants for.
You'll learn the difference between being trusted for your hands and being trusted for your judgment, how a consultant uses AI as a detective instead of a builder, and why AI ends generic consulting but not trusted diagnosis. I also take on the "End of Consulting" argument, and answer two questions I get a lot: won't companies just ask AI, and should you become an "AI consultant"? (Short answer on that last one: no.)
Before you finish, you'll write down one problem AI adoption created at a company you've worked at, and the name of one person who would recognize it.
(00:00:33) AI made developers responsible for everything
(00:01:45) How developers survive the burden of AI
(00:02:27) The opportunity created by AI's problems
(00:15:12) Getting started
(00:20:53) Objections to consulting on AI problems
(00:26:21) Moving from learning to action
(00:27:15) Forget Building Software. Companies Pay More For This.
Developers Go Solo Backwards: The 4 Stages That Get Clients
2026/11/17
If you're a software developer trying to go solo as a consultant, you've probably been doing it backwards.
Learn about the Solo Technical Consultant Workshop
Most developers start with the website, the LLC, the logo, or posting on LinkedIn. Building feels like progress. A website is a ticket you can close, and nobody can say no to a logo. You also only see the last stage of other consultants' businesses, not the years of conversations and referrals that came before it. After coaching over 150 developers, I point out this trap over and over.
In this episode I walk you through the 4 stages from employee to established solo consultant: Show Up, Deliver, Refine, and Amplify. You'll see which stage you're actually on, why each one earns what you need for the next, and how your first consulting clients can pay you long before you need a website. The LLC and contracts come after someone says yes. The branding comes even later.
Stage 1 runs alongside your day job, and it isn't sales. You talk with people who already know your work about one problem you see in their world, and you listen.
(00:00:33) Developers go solo backwards
(00:01:13) 1. Why developers get it backwards
(00:01:24) 1.1 Building feels like progress
(00:01:46) 1.2 Building avoids rejection
(00:02:12) 1.3 Comparing yourself to established consultants
(00:02:45) 2. The four stages
(00:02:49) 2.1 Stage 1: Show Up
(00:04:33) 2.2 Stage 2: Deliver
(00:08:10) 2.3 Stage 3: Refine
(00:13:02) 2.4 Stage 4: Amplify
(00:17:44) 3. Do the stages really matter?
(00:17:49) 3.1 Each stage earns you material for the next
(00:21:40) 3.2 People you know don't need proof
(00:22:58) 3.3 Only work on the stage you're on
(00:23:43) 3.4 Overthinking stops you from progressing
(00:24:55) 3.5 You don't have to quit your job to talk to people
(00:25:29) 3.6 Short-term sacrifice for long-term change
(00:28:04) 4. Getting started
(00:28:09) 4.1 Step 1: Stop spending energy on distractions
(00:29:08) 4.2 Step 2: Identify 5 people you've advised
(00:31:10) 5. Objections
(00:31:16) 5.1 "Don't I need proof?"
(00:32:41) 5.2 "I can't just quit my job!"
(00:33:07) 5.3 "I hate sales!"
(00:34:30) Moving from learning to action
Forget Building Software. Companies Pay More For This
2026/11/12
Frustrated with how AI is changing your job as a software developer? Building software isn't the best way to earn with your technical skills anymore. You need a new strategy.
Learn about the Solo Technical Consultant Workshop
In this episode, I share a consulting method I stumbled upon while consulting for a large international grocery chain. Companies will pay you more to diagnose their problems than to build their software.
To get started, find a company with an urgent problem and assess it so they know what to do next. Identify 3-4 areas that could be contributing to the problem, then choose the investigative activities you'll use to diagnose each one. Timebox the work to 16 hours (not counting outreach) and price your first engagement at $8k to $10k.
An assessment doesn't require a technical interview. You're paid a fixed price, not by the hour. And many clients will want you back after you deliver it so they can improve their score.
(00:00:33) Developers Were Born To Assess Problems
(00:01:39) 1. A New Strategy for Developer Income
(00:01:49) 1.1 Technical Skills are No Longer a Differentiator
(00:02:10) 1.2 Being More Efficient Doesn't Pay More
(00:02:46) 1.3 More Responsibility Means Less Work/Life Balance
(00:03:39) 1.4 Perception of Lower Skill Means Stagnant Wages
(00:05:30) 2. How Diagnosing Problems Gives Developers Leverage
(00:05:42) 2.1 Urgent Problems Enable Charging Higher Fees
(00:07:26) 2.2 Higher Income Enables Margin in Your Life
(00:08:31) 2.3 You Don't Own The Problems You Assess
(00:11:31) 2.4 Technical Diversity is a Strength
(00:14:02) 2.5 No Technical Interview for Assessors
(00:15:33) 3. Software Consulting Assessment Components
(00:15:44) 3.1 Choose 3-4 Problem-Contributing Areas
(00:17:01) 3.2 Score the Assessment Areas
(00:18:52) 3.3 Choose Investigatory Activities
(00:22:22) 3.4 16 Hour Cap for Activities and Meetings
(00:27:39) 3.5 Price First Assessment at $8k-$10k
(00:29:36) 3.6 Your First Engagement is Least You'll Make
(00:31:34) 4. Getting Started
(00:31:41) 4.1 Identify a Recurring Problem
(00:32:44) 4.2 See if Someone You Know Has The Problem
(00:34:51) Moving From Learning to Action
What Developers Should Say in a Consulting Call
2026/10/30
Someone wrote back "yeah, we're seeing that too" and now you've got a call on the calendar. Here's how solo developers actually run that first 20 minutes.
Learn about the Solo Technical Consultant Workshop
Most developers picture a consulting call like the discovery calls agencies run: an hour of asking what the company is working on and pitching anything that might fit. A solo consultant's first call works differently. You already know the problem, because they told you they're seeing it too. So the call is short, they do most of the talking, and you're there to help them get clear on whether the problem is worth solving.
In this episode, you'll see what that call looks like, what you find out during it (how the problem gets in their way, what they've tried, what it's costing them, and what would be different without it), and what you walk away with even when nobody buys anything: a referral, permission to come back, or a sharper version of the problem you're asking people about.
(00:00:33) When Things Get Real
(00:01:28) It's Not a Discovery Call!
(00:03:04) The Big Picture
(00:03:58) What You Find Out
(00:06:22) What You Walk Away With
(00:07:00) When They Ask You
The Message That Gets Developers into Consulting Calls
2026/10/20
Going solo starts with one message to someone who already knows your work. Here's what to put in it so you get a call instead of "good luck."
Learn about the Solo Technical Consultant Workshop
Most developers who decide to go solo send the same first message. They say they're doing some consulting now, mention a skill, and ask people to let them know if they ever need help. The reply is almost always friendly, and it almost never turns into anything.
In this episode, you'll see why that message reads like a job request, and what a consultant sends instead. We'll rewrite the same message around a problem you keep seeing, figure out who on your contact list it should go to, and walk through what to say when someone writes back, so the conversation turns into a call instead of you giving away free advice in a reply.
(00:00:33) Why Most Developers Can't Get a Consulting Call
(00:01:23) The Skill Trap
(00:02:36) Holding a Problem
(00:04:56) Who To Send It To
(00:06:17) An Invitation
What Do Companies Actually Pay Software Consultants For?
2026/10/16
If you're figuring out how to start software consulting, the first thing to pick isn't your niche or your offer. It's choosing a problem you'll help clients solve.
Learn about the Solo Technical Consultant Workshop
Most developers start with whatever frustrates them most at work, and then wonder why nobody wants to pay for it. In this episode, you'll learn how to pick a consulting problem clients will actually pay for, using the five filters I walk the developers I coach through.
You'll see why the way you describe a problem matters as much as the problem itself, and what tells you a company's ready to spend money on it. We'll get into why a problem you've seen at more than one company is worth more than one you know inside and out at your current job, and how to tell if AI's already turning it into a commodity. You might even find out you've been consulting at your day job for years without getting paid for it.
If your problem makes it through, you don't need a polished offer yet. The next step is finding out if the people who already know your work are seeing it too.
(00:00:33) Choosing a Consulting Problem Clients Pay For
(00:01:34) Someone With a Budget Feels It
(00:03:15) They've Already Tried and Failed
(00:04:37) You've Seen it Multiple Times
(00:06:44) A Good AI Prompt Isn't Enough
(00:08:00) You're Already Advising On It
I Watched 50 Developers Try to Go Solo. Most Got Stuck.
2026/10/13
Thinking about going solo as a developer but you still haven't done it? I've coached over 50 software developers who wanted to become independent consultants, and the ones who got stuck kept hitting the same five problems. In this video I'll walk you through each one, and what the developers who got unstuck did instead.
Learn about the Solo Technical Consultant Workshop
The first one shows up before you've done anything. You've spent years estimating tasks as an employee, so you want every data point before you commit to a consulting offer. But nobody's holding you to your pick. It's your business, and your offer comes out of conversations about a problem you've already seen.
Then there's the comfort blanket. You're about to reach out to someone, a small question pops up, and next thing you know you're forming an LLC and building a website before you've had one real conversation. That detail can wait. The conversation can't.
After that, a lot of developers walk into client conversations like it's a job interview. They think they need every answer or they'll look stupid. In consulting your job is to ask, not answer, and good questions build way more trust than having everything ready to go. You'll also hear why "I don't know anyone who needs what I offer" usually isn't true. Your first consulting client is most likely someone who already knows you, including managers and directors you barely worked with.
Finally, we'll talk about the hidden talent the developers who made it had in common: judgment. AI is making hands-on coding less valuable, but companies still pay for someone they trust to tell them what to do first. That's how you go from selling your hours to getting paid for your expertise.
(00:00:33) What Keeps Devs From Going Solo?
(00:02:08) Choice Paralysis
(00:03:14) The Comfort Blanket
(00:04:32) The Wrong Candidate
(00:06:17) Assumption of Low Value
(00:08:17) Your Hidden Talent
Solo Software Consultants Should Be A Personal Brand
2026/01/06
Why solo developers should be the face of their business. Especially if you want to guide companies for a premium price without feeling salesy.
Learn about the Solo Technical Consultant Workshop
If you're a solo developer trying to land clients, it's tempting to hide behind a clever company name so you look "more legit." I used to think that too.
But over the years I learned the opposite is true: putting your name at the front of your business can reduce risk for the buyer and make it easier for them to say yes.
(00:00:33) Don't Create a Company as a Solo Consultant
(00:01:56) Clients Are NOT Companies
(00:03:18) 1. You Make Buying Easier
(00:04:22) 2. You Own The Results
(00:05:27) 3. No Headcount Pressure
(00:06:29) 4. Clients Know Who They're Getting
(00:07:46) 5. Pivot Without a Rebrand
I Found the Courage To Be a Solo Developer in The Bible
2026/01/06
One book helped me overcome fear and start working for myself when nothing else would. The Bible.
Learn about the Solo Technical Consultant Workshop
Ever wanted to quit your corporate tech job and work for yourself, but couldn't bring yourself to take the leap? You're not alone. I was stuck there for years.
In this episode, I share how I went from being a burned-out corporate tech employee to working for myself in tech for nearly a decade—and how faith played a central role in giving me the courage to move forward when there were no guarantees.
I talk openly about fear, control, money, and the illusion of security that comes with a traditional software engineering career.
If you're thinking about self-employment, consulting, freelancing, or building an independent business in tech, this video will help you reframe how you think about risk, control, and purpose.
I walk through four common lies the tech industry sells us about safety and success, and how Scripture helped me confront them.
(00:00:33) Disaster Struck When I Gave In To Fear
(00:02:36) The Lie of Self-Sufficiency
(00:05:41) The Illusion of Control
(00:08:47) The True Provider
(00:12:24) The Call To Purpose
How Solo Consulting Frees Developers From The Grind
2026/01/06
Solo technical consulting overcomes every frustrating aspect of grinding it out as a tech employee.
Learn about the Solo Technical Consultant Workshop
After nearly three decades in software, I've learned a hard truth: most developers never actually escape the grind—they just upgrade to a slightly nicer cage.
I hit that realization years ago when I opened my laptop to track my hours and suddenly saw it for what it was: the same deadlines, the same pressure, the same feeling that no one really cared what I thought.
I wasn't consulting… I was just coding for a different employer.
I walk through the GRIND acronym to show why the industry keeps you stuck as a task-runner, and how shifting into a specialized, technical guidance-driven way of working gives you autonomy, stability, and respect.
(00:00:33) I was doing fake consulting at first
(00:01:46) Being a generalist traps you in a cycle of low value
(00:04:18) Relying on employment for stability is unrealistic
(00:06:23) You'll be invisible until you communicate your value
(00:07:49) Don't normalize being a victim of the tech industry
(00:09:30) Consultants never defer to clients, they lead
Welcome to Developer Reborn
2026/01/03
Developer Reborn is a podcast for experienced software developers who feel like being an employee is holding them back.
This show is about becoming a premium consultant—not freelancing, not billing by the hour, and not doing whatever random work a company wants done.
If you work in the software industry and feel like being an employee is holding you back, you're not alone. After working in this industry for 30 years I can tell you that being an employee isn't just frustrating. It's a broken system.
8 years ago, I was a highly paid consultant in Austin, Texas. But I got hit with chronic insomnia and was forced to resign. I was an addict and suffering from depression. I had tried everything to cope with the tech industry grind. I was headed towards losing my marriage and kids. I needed a different way to make money in tech.
So I quit the corporate grind to go solo. Like many developers, I had already tried doing the SaaS thing over my career 3 times. Even though we had strong beta programs, my startups didn't work out. I knew how to build products. What I didn't know was how to build a business.
That all changed once I began coaching developers online on their career. I shared some of the strategies I'd used as a consultant to cope with the grind. I stumbled my way through learning just enough marketing, sales, and product management to work for myself. I grew the YouTube channel Healthy Developer to over 180k subscribers, cut my work hours to 20 per week, and still made over $100k per year. Along the way, my faith in Jesus Christ began shaping how I think about work and responsibility.
But in 2024 I started seeing a trend. Developers were getting hit with chronic job instability. AI began scaring people into fear-based career decisions instead of helping them create leverage.
So I took everything I learned as an employee, consultant, and career coach and created a workshop to help developers go solo. And to do it safely, alongside their day job—and build respect, leverage, and freedom that employment can never deliver.
That led to this show.
On Developer Reborn, I'll help you become a technical guide with a signature offer.
This isn't freelancing or billing by the hour for whatever random work a company wants done. You decide what to do, who to work with, and they sign your contract. You get paid by asking for a percentage of the business results, not hourly.
If you're done jumping through interview hoops, hoping your employer rewards your sacrifices, and starting your reputation all over again every time you take a new job, this is the place for you.
You can also watch these episodes on the accompanying YouTube channel with the same name if you prefer.
Welcome to Developer Reborn.
Podcast sponsorship advertising
Start advertising on Developer Reborn relevant audience podcasts
You may also like to advertise on these Podcasts

4.66267310
True Crime with Kendall Rae
Mile Higher Media & Audioboom Studios

4.73456789
The Ancients
History Hit

4.89197320
The Why Files: Operation Podcast
The Why Files: Operation Podcast

51088171
Middle Children
Jessie Jolles and Chris Burns

4.8265172000
Morning Wire
The Daily Wire

4.518808383
American Scandal
Audible

4.689571234
Get Sleepy: Sleep meditation and stories
Slumber Studios

4.79026375
Life is Short with Justin Long
Audible

4.714149353
Bad Friends
Bobby Lee & Andrew Santino

4.7133275
10 to Life
Annie Elise