Develpreneur: Become A Better Developer And Entrepreneur

The idea of hitting a plateau feels real—but according to Dr. Joseph, most growth ceilings aren't real at all. They're constructed. Understanding growth ceiling systems means recognizing that what feels like a business limitation is often a mental and behavioral system constraint. About Dr. Joseph Drolshagen Dr. Joseph Drolshagen is a business growth strategist and creator of the SMT Method™ (Subconscious Monetization Technology™), a framework designed to help entrepreneurs break through plateaus by reprogramming subconscious limitations. With a Doctorate in Psychology and over 30 years of experience—including a career as a VP of Sales—he combines mindset and strategy to help business owners scale faster and more effectively. He is the author of multiple books on growth, mindset, and transformation, and is known for delivering high-energy, practical insights that drive real results. Social: Facebook / Twitter / X / Pinterest / Youtube / Instagram / LinkedIn Website: Joseph Drolshagen's Websit

The dynamic visioning strategy is the missing foundation behind why so many developers and founders hit a plateau—and stay there longer than they should. Early in a business, momentum feels automatic. Ideas are exciting. Progress is visible. But eventually, that energy fades, and what replaces it isn't always a lack of skill or opportunity—it's a lack of clarity. That's where the real problem begins. About Dr. Joseph Drolshagen Dr. Joseph Drolshagen is a business growth strategist and creator of the SMT Method™ (Subconscious Monetization Technology™), a framework designed to help entrepreneurs break through plateaus by reprogramming subconscious limitations. With a Doctorate in Psychology and over 30 years of experience—including a career as a VP of Sales—he combines mindset and strategy to help business owners scale faster and more effectively. He is the author of multiple books on growth, mindset, and transformation, and is known for delivering high-energy, practical insights that drive rea

The question "will AI replace developers" is everywhere right now—and it's driving a lot of fear, confusion, and bad assumptions. While AI is clearly changing how software is built, the idea that developers will disappear misunderstands what the role actually involves. About Adam Korga Adam Korga is a veteran IT professional with nearly 20 years of experience across development, architecture, and cloud engineering. Known as a "BS detector" for the digital age, he focuses on cutting through hype and exposing where technology—and the systems around it—actually break. Through his writing and analysis, Adam explores failure patterns in tech, business, and beyond, emphasizing clarity, simplicity, and real-world thinking over buzzwords. His work blends sharp humor with deep, research-driven insight, helping both newcomers and seasoned professionals better understand the systems they rely on every day. Will AI Replace Developers? Only If You Think Coding Is the Job At the center of the "will AI

The gap between AI hype vs reality is growing—and it's causing more confusion than clarity for developers and businesses alike. AI is being positioned as a solution to everything, but if you've been in tech long enough, this pattern feels familiar. The real challenge isn't understanding AI—it's recognizing where hype ends, and reality begins. About Adam Korga Adam Korga is a veteran IT professional with nearly 20 years of experience across development, architecture, and cloud engineering. Known as a "BS detector" for the digital age, he focuses on cutting through hype and exposing where technology—and the systems around it—actually break. Through his writing and analysis, Adam explores failure patterns in tech, business, and beyond, emphasizing clarity, simplicity, and real-world thinking over buzzwords. His work blends sharp humor with deep, research-driven insight, helping both newcomers and seasoned professionals better understand the systems they rely on every day. AI Hype vs Reality:

AI system design determines whether your solution succeeds in production or fails once it leaves a controlled environment. In this part of the conversation, Matt Soltau highlights a critical shift: building AI is no longer just about capability—it's about control, adaptability, and governance. About Matt Soltau Matt Soltau is the Global Director of Strategy & Operations at IntelliPaaS. He specializes in helping organizations untangle complex, legacy tech stacks so they can successfully implement secure, compliant, and scalable AI and automation solutions. With a strong focus on integration and real-world execution, Matt works with companies to turn fragmented data into reliable systems that actually support AI initiatives. AI System Design Must Balance Openness and Control Organizations today are under pressure to: integrate more systems adopt new tools move faster At the same time, they must: protect sensitive data comply with regulations maintain control over system

Having a strong AI data foundation is the real starting point for any successful AI initiative, yet it's the part most teams overlook. In our latest conversation with Matt Soltau, one thing becomes clear early: companies are focusing too much on AI tools and not nearly enough on the systems those tools depend on. That mismatch is where most problems begin. About Matt Soltau Matt Soltau is the Global Director of Strategy & Operations at IntelliPaaS. He specializes in helping organizations untangle complex, legacy tech stacks so they can successfully implement secure, compliant, and scalable AI and automation solutions. With a strong focus on integration and real-world execution, Matt works with companies to turn fragmented data into reliable systems that actually support AI initiatives. AI Data Foundation Starts Before AI When organizations talk about AI, they usually start with: models platforms automation tools But none of those matters if the underlying data isn't ready.

The future of developers' AI is already unfolding—and it's not about developers being replaced. It's about developers evolving. As AI tools take over more coding tasks, the real shift is in how developers create value. Why Coding Alone Isn't Enough One of the biggest changes in the future of developers' AI is that coding is no longer the primary differentiator. AI can now: Generate boilerplate code Stand up projects quickly Handle repetitive tasks Developers who focus only on syntax will struggle as these capabilities become standard. Developer Skills in the AI Era To stay relevant in the future of developers' AI, developers need to shift their focus. Instead of: Writing code → Designing systems Knowing syntax → Understanding problems Building features → Integrating solutions Key skills now include: Systems thinking Integration expertise Rapid prototyping Context-driven development Your value is no longer just in writing code—it's in solving the rig

If you're trying to implement AI in your business, the best advice might sound counterintuitive: start small, think big AI. Most companies rush into AI expecting transformation, but without the right foundation, they end up accelerating broken processes instead of improving them. Why AI Fails Without a Foundation There's a growing pressure on organizations to adopt AI quickly—but most aren't ready. Most mid-market companies: Don't have documented processes Store data in scattered systems Lack of clarity in workflows Trying to implement a start small, think big AI strategy without fixing these issues leads to failure. AI doesn't create clarity. It amplifies whatever already exists—good or bad. How Start Small Think Big AI Actually Works The phrase start small, think big AI isn't just a mindset—it's a strategy. Instead of trying to automate everything: Start with one process Improve it incrementally Learn what works Expand from there This avoids the common m

An effective ERP implementation strategy starts long before any software is selected. Most failures happen not during deployment, but during planning—when organizations rush into tools without clearly defining outcomes, aligning teams, or preparing their processes. In this episode, Dustin Domerese shifts the conversation from failure to execution. Instead of focusing on what goes wrong, he outlines what a successful ERP implementation strategy actually looks like in practice—from defining problems to managing change and delivering results in smaller, meaningful increments. If the first part of this discussion explains why projects fail, the second part focuses on how to make them succeed. About Dustin Domerese Dustin Domerese is a recognized thought leader in the Microsoft ecosystem, specializing in CRM, ERP, and software transformation. He helps organizations recover failing initiatives and build scalable systems that deliver real results. Drawing on experience with Microsoft, Barclays, EM

Most ERP and CRM implementation efforts don't fail during execution—they fail before the project even begins. In this episode, the hosts sit down with Dustin Domerese, who brings nearly two decades of experience in SAP and Microsoft consulting. Early in the conversation, a clear pattern emerges: companies jump into ERP and CRM implementation without fully understanding what these systems actually are—or what they require from the business. If you've ever seen a project spiral out of control, take years instead of months, or fail to deliver value after launch, the root cause usually starts here. About Dustin Domerese Dustin Domerese is a recognized thought leader in the Microsoft ecosystem, specializing in CRM, ERP, and software transformation. He helps organizations recover failing initiatives and build scalable systems that deliver real results. Drawing on experience with Microsoft, Barclays, EMC2, HP, and multiple successful ventures, Dustin brings a proven track record of guiding busines

There's a point in every business where doing everything yourself stops being admirable and starts being the bottleneck. The shift from operator to leader doesn't happen automatically — it requires intention, structure, and systems built to outlast your own bandwidth. In this episode of Building Better Developers, Antwon Person pulls back the curtain on how he built and managed a virtual assistant team without creating operational chaos. What follows is a breakdown of his approach — and what other entrepreneurs can take from it. Hire for Zones of Excellence, Not Versatility A common early mistake: hiring one person and loading them with five different jobs. Graphic design, video editing, admin work, research, social media — all under one roof. It sounds efficient. In practice, it creates hidden friction and inconsistent output. When Antwon first brought on a VA, he made exactly this mistake. Spreading one person thin created skill gaps and unpredictable work quality. The fix was straightforwa

There's a big difference between being busy and building something that lasts. Many entrepreneurs don't realize they're stuck in that gap. They're working hard, juggling responsibilities, hustling nights and weekends — but the business isn't really moving forward. In this episode of Building Better Developers, Army veteran and founder of Skillful Brands, Antwon Person, breaks down what actually creates forward momentum in a business. And it's not hype, hacks, or grinding harder. It's mindset, structure, and knowing when to leverage. The Entrepreneurial Mindset Isn't About Hustle — It's About Structure When Antwon left a 22-year military career and stepped into entrepreneurship, he brought discipline and leadership with him. What he discovered quickly, though, was that discipline alone doesn't build a company. Like many new entrepreneurs, he was busy. Very busy. But busy didn't mean structured. He realized something that most founders eventually learn the hard way: being busy in your busin

If you've ever hit that point where you're "still functioning," but everything feels heavier—this episode is for you. In Building Better Developers, the hosts frame this season around getting unstuck and building forward momentum—even when life is busy, messy, and your energy is running low. In this conversation with Andrew Stevens, the throughline is practical: communicate early when you're behind, shrink work into achievable chunks, and put real AI guardrails in place so "helpful tooling" doesn't turn into a trust incident. Forward Momentum starts with honesty: communicate early When you're overloaded, the easiest mistake is to go silent and hope the schedule will magically work out. Andrew's advice is the opposite: you can be busy and even behind, but it has to be communicated—early and clearly—so stakeholders can react while there's still room to maneuver. This ties directly into the season's theme. Rob literally describes the season as "getting unstuck," "moving forward," and "getting ou

Building forward momentum isn't about moving fast. Rather, it's about moving intentionally — especially when transitioning from developer to entrepreneur. In Season 27 of the Building Better Developers podcast, we explore what it truly means to keep progressing when challenges, distractions, and new responsibilities threaten to slow you down. In this episode, Andrew Stevens — software engineer, multi-time founder, CTO, and board member — shares how building forward momentum has shaped his multi-decade journey through technology and startups. Instead of focusing on overnight success, his story emphasizes sustained curiosity, disciplined execution, and constant recalibration. Over time, momentum is built layer by layer, not in dramatic bursts. Building Forward Momentum Through Collaboration At first, Andrew's entrepreneurial journey didn't begin alone. It started with collaboration. During the early dial-up internet era, local ISPs were emerging everywhere. At that point, Andrew joined forces w

Most developers believe their biggest career challenges are technical. They're usually wrong. The real blockers tend to be invisible — habits, assumptions, and internal narratives that quietly control decisions, communication, and confidence. In this episode of the Building Better Developers Podcast, we talk with coach Kim Miller-Hershon about why talented developers get stuck and how a developer mindset shift creates real forward motion. Progress doesn't start when you learn a new framework. It starts when you change how you think. About Kim Miller-Hershon Kim Miller-Hershon is an international business coach, corporate trainer, and speaker who helps leaders and entrepreneurs get unstuck by thinking differently and taking action faster. She works with executives and business owners on essential leadership skills, including communication, management, and time management—always with a focus on authenticity. Kim also hosts the Unconventional Wisdom About Conventional Wisdom podcast, where c

If you've ever felt stuck despite having experience, skills, and a plan, the problem usually isn't effort. Most developers and technical leaders don't stall because they're lazy or unmotivated—they stall because their beliefs, motivation, and execution are misaligned. A strong getting unstuck isn't about pushing harder. It's about creating alignment so forward momentum becomes sustainable instead of exhausting. When progress slows, people often default to adding more tools, tighter schedules, or bigger goals. But without clarity underneath, those fixes rarely stick. Real movement starts when you trust the process, understand what's driving you, and design actions that actually fit how you work. About Kim Miller-Hershon Kim Miller-Hershon is an international business coach, corporate trainer, and speaker who helps leaders and entrepreneurs get unstuck by thinking differently and taking action faster. She works with executives and business owners on essential leadership skills, including communic

Measuring AI marketing ROI has become one of the most uncomfortable conversations in tech and marketing teams. Everyone knows AI is "important." Fewer teams can explain what success actually looks like. Even fewer can tie adoption to real outcomes rather than experimentation for its own sake. For developers and technical leaders, this isn't a tooling problem — it's a decision-making problem. The teams that win are the ones that slow down just enough to define value before they ship. About Meeky Hwang Meeky Hwang's journey resonates with entrepreneurs, technical leaders, and anyone navigating the intersection of technology and business. As CEO and Co-Founder of Ndevr, a digital solutions development agency, Meeky brings over 20 years of experience building resilient, scalable platforms for organizations including Johnson & Johnson, Pfizer, Forbes, PMC, and Bloomberg. Her work goes beyond website development—she focuses on long-term digital solutions that improve performance, streamline wor

The Developer to CEO transition rarely starts with a bold declaration like, "I'm going to run a company." More often, it begins quietly—by taking on one more responsibility, saying yes to a new opportunity, or stepping into a role that stretches just a little beyond your comfort zone. In this episode of the Building Better Developers podcast, part of our Forward Momentum season, we talk with Meeky Hwang about how that transition unfolds in real life. Her path—from developer to agency founder and CEO—reflects a pattern many experienced engineers recognize only in hindsight. Over time, those small decisions add up. You stop thinking only about code and start thinking about people, clients, sustainability, and direction. At some point, you realize you're no longer just building software—you're building a business. About Meeky Hwang Meeky Hwang's journey resonates with entrepreneurs, technical leaders, and anyone navigating the intersection of technology and business. As CEO and Co-Founder of

Regaining clarity at work is one of the biggest challenges developers face as responsibilities grow, distractions multiply, and expectations rise. Burnout rarely appears overnight. More often, it creeps in quietly—through constant context switching, mental fatigue, and the feeling that you're busy all day but not making real progress. For developers and technical leaders, clarity isn't a "nice to have." It's what allows you to make good decisions, focus deeply, and enjoy the work you're doing. Without it, even small tasks feel heavier than they should. About Andrew Hinkelman Andrew Hinkelman is a certified executive coach and former Chief Technology Officer who works with tech founders, CTOs, and engineering leaders to strengthen their leadership and people skills. With over 25 years of corporate experience, including 8 years as a CTO, Andrew understands firsthand the pressures technical leaders face as they move from hands-on execution to leading teams and organizations. His coaching focuses

For many developers and engineering leaders, executive coaching feels like something you turn to only when things go wrong. We're trained to solve problems, push through obstacles, and rely on our own expertise. So when progress slows, the default reaction is often to work harder—not to step back and reassess. That's exactly why executive coaching can be so valuable when used intentionally. At its best, coaching isn't about fixing weaknesses. It's about uncovering blind spots, challenging assumptions, and helping capable leaders see where their habits are limiting growth. When the fit is right, coaching brings clarity and momentum. When it's wrong, it simply adds noise. About Andrew Hinkelman Andrew Hinkelman is a certified executive coach and former Chief Technology Officer who works with tech founders, CTOs, and engineering leaders to strengthen their leadership and people skills. With over 25 years of corporate experience, including 8 years as a CTO, Andrew understands firsthand the pres