
Advertise on podcast: Develpreneur: Become a Better Developer and Entrepreneur
Rating
5from
This podcast has
1032 episodes
Language
EnglishPublisher
Rob BroadheadExplicit
No
Date created
2017/11/14
Latest episode
2026/11/17
Average duration
27 min.
Release period
4 days
Description
This podcast is for aspiring entrepreneurs and technologists as well as those that want to become a designer and implementors of great software solutions. That includes solving problems through technology. We look at the whole skill set that makes a great developer. This includes tech skills, business and entrepreneurial skills, and life-hacking, so you have the time to get the job done while still enjoying life.
Unlock Develpreneur: Become a Better Developer and Entrepreneur podcast Email contact info,
Listeners & Audience details
Email contact information
Direct podcast contact details

Listeners
Audience numbers & engagement insights

Audience details
Podcast Insights

Social media
Check Develpreneur: Become a Better Developer and Entrepreneur social media presence
Podcast episodes
Check latest episodes from Develpreneur: Become a Better Developer and Entrepreneur podcast
From Two Buttons to a Nationwide Marketplace: Ari Kimmelfeld on Building Commonplace
2026/11/17
Building a successful business does not always begin with a revolutionary technology or a complicated application. Sometimes, it starts with identifying one frustrating problem and creating a simple way to solve it. For developers and entrepreneurs, the challenge is often resisting the temptation to build everything at once and instead focusing on what customers actually need.
In this episode of Building Better Developers, hosts Rob Broadhead and Michael Meloche welcome Ari Kimmelfeld, founder of Commonplace, a marketplace designed to make buying and selling large secondhand items easier. From fitness equipment and appliances to furniture, saunas, and hot tubs, Commonplace handles much of what makes these transactions difficult, including inspections, pickup, delivery, and payments.
Ari shares how a website with just two buttons evolved into a nationwide business, the unexpected complications of combining software with physical logistics, and why understanding customer problems matters more than building another feature.
About Ari Kimmelfeld
Ari Kimmelfeld is the founder and CEO of Commonplace, a U.S.-based marketplace specializing in large secondhand products, including fitness equipment, furniture, appliances, hot tubs, saunas, and other difficult-to-transport items.
Ari and his wife, Naomi, built the business around making secondhand shopping more accessible by addressing challenges such as inspections, logistics, secure payments, and delivery. The company evolved from TradeMySpin, a narrowly focused service for buying and selling used Peloton equipment, into a broader marketplace serving customers nationwide.
A graduate of Macaulay Honors College at the City University of New York, Ari brings an entrepreneurial approach that emphasizes identifying customer pain points, testing simple solutions, and improving operations through real-world experience.
Through Commonplace, he continues to explore how technology and hands-on service can work together to make complicated transactions easier.
Connect with Ari and Commonplace:
Website: https://trycommonplace.com
LinkedIn: https://www.linkedin.com/in/arikimmelfeld
Starting Small: The Two-Button Business Model
Ari's entrepreneurial journey began with a problem he had experienced personally. Having bought and sold secondhand products since childhood, he understood the opportunities available through platforms like Craigslist and Facebook Marketplace. However, he also recognized a major limitation: purchasing something large, expensive, or difficult to transport was rarely convenient.
During the COVID-19 pandemic, many people purchased Peloton exercise bikes for home workouts. As gyms reopened, some of those expensive machines sat unused. Ari saw an opportunity to connect people who wanted to sell their equipment with buyers looking for a bargain.
Instead of developing an elaborate marketplace, he launched a basic Shopify website called TradeMySpin. It featured two simple options: buy a Peloton or sell a Peloton.
That simplicity made the concept immediately understandable. Customers knew what the website offered, and search engines could recognize its purpose. According to Ari, the business attracted significant organic interest as people discovered an easier way to buy and sell used exercise equipment.
For developers, this is an important reminder that a minimum viable product does not need to demonstrate everything your technology can do. It needs to demonstrate that your solution solves a real problem.
Building a Marketplace That Solves More Than the Transaction
Traditional marketplaces do a good job of connecting buyers and sellers, but the transaction itself can still become a frustrating experience. Buyers may need to negotiate prices, inspect products, arrange transportation, and coordinate with sellers who sometimes stop responding.
These problems become considerably more complicated when purchasing a refrigerator, treadmill, or hot tub.
Ari realized that Commonplace needed to provide more than a place to post listings. The real opportunity was to remove the obstacles that prevented secondhand transactions from happening.
Commonplace developed a service model that includes inspections, delivery coordination, payment processing, and installation where appropriate. The company also introduced a pay-on-delivery approach, allowing buyers to reserve an item for one dollar and complete payment after inspecting it.
This was not simply a feature Ari assumed customers wanted. He explains that the team experimented with different purchasing processes before discovering that even a small financial commitment produced better results than allowing buyers to reserve products entirely for free.
The lesson extends well beyond online marketplaces. The best software solutions often emerge from understanding customer behavior rather than making assumptions about how people should use an application.
When Every Order Requires a Truck
As Commonplace expanded beyond Pelotons, its greatest challenge was not necessarily building additional website functionality. It was creating the operational infrastructure necessary to deliver different types of products safely and consistently.
A refrigerator requires different handling than a treadmill, and moving a hot tub may involve plumbing, electrical connections, specialized equipment, or even a crane. Each product category introduces requirements that must be reflected in the business processes and the software supporting them.
Ari explains that Commonplace developed a nationwide network of more than 3,000 trained, vetted, and rated delivery professionals. Its systems coordinate drivers based on location, qualifications, product categories, and job requirements.
Scaling this operation required more than assigning additional deliveries. The company had to develop dispatch processes, driver training, qualification checks, and specialized workflows for individual product categories.
This illustrates a challenge developers frequently encounter when working with real businesses: the software is only one component of a much larger operational system. Building an application that technically functions is different from creating one that consistently supports the people doing the work.
Learning From the Problems That Go Wrong
One of the most valuable parts of Ari's conversation is his explanation of how Commonplace improves its processes through experience.
The company uses inspection checklists containing approximately 30 to 50 points for individual products. Those checklists can vary based on the manufacturer, model, and category. When something goes wrong during a pickup, inspection, or delivery, that experience becomes an opportunity to improve the next transaction.
A problem discovered while moving a particular hot tub in Texas, for example, can lead to updated inspections and training that help prevent the same issue during a future delivery in Maryland.
Ari describes these lessons as the price of learning. Rather than treating every operational problem as an isolated failure, Commonplace uses those experiences to strengthen the entire network.
For developers, this approach closely resembles continuous improvement in software development. Bugs, failed deployments, unexpected user behavior, and process breakdowns provide valuable information when teams take the time to investigate their causes.
The goal should not simply be to fix a problem once. It should be to improve the system so that the same problem becomes less likely to happen again.
Trust Is Part of the Product
Buying an expensive secondhand item online requires confidence. Customers need assurance that the product is in the expected condition, that delivery will happen, and that someone will help when something goes wrong.
Commonplace addresses these concerns with multiple inspection checkpoints, photographs, videos, delivery coordination, and a parts warranty. Customers can even communicate with delivery crews during pickup to ask questions about an item before completing the transaction.
These additional services create a level of trust that a traditional listing alone cannot provide.
For developers and entrepreneurs, the larger lesson is that customer experience includes everything surrounding the software. A polished interface cannot compensate for unreliable fulfillment, poor communication, or unclear expectations.
Technology becomes more valuable when it supports a dependable service rather than simply adding more functionality.
Building Better Developers: Solve the Problem Before Expanding the Product
Ari's journey from TradeMySpin to Commonplace demonstrates how a focused solution can grow into something much larger. What began as a straightforward way to buy and sell Pelotons eventually required sophisticated logistics, specialized inspections, payment workflows, and a nationwide delivery network.
The growth did not come from attempting to build an entire marketplace on day one. It came from identifying a meaningful customer problem, building something simple enough to test, and expanding the solution as new requirements emerged.
As developers, we sometimes measure progress by how many features we deliver or how quickly we can write code. However, the real measure of success is whether our work removes obstacles, improves operations, and creates value for the people using it.
Before starting your next project, consider what your version of those original two buttons might look like. Find the smallest useful solution, validate it with real customers, and let the lessons from actual usage guide what you build next.
That is how we move beyond simply writing code and start building better solutions.
Stay Connected: Join the De
You Might Also Like: The Ben Shapiro Show
2026/11/17
Introducing Ep. 2527 - Allie Beth Stuckey Dismantles a Feminist In One Clip from The Ben Shapiro Show.
Follow the show: The Ben Shapiro Show
James Talarico lies fluently on CNN to try to wheedle Texas voters; Newsweek pushes the cutesy and fun version of murderous socialism; and Hasan Piker is absolutely gobsmacked at our new movie, Confession.
Ep. 2527
Check out Allie's upcoming app Ana Kate at: https://www.anakate.com
Listen to her podcast "Relatable" at Blaze TV: https://get.blazetv.com/allie
Follow Allie Beth Stuckey on Youtube here: https://youtube.com/@alliebethstuckey
Allie's book "Toxic Empathy: How Progressives Exploit Christian Compassion" is available here: https://a.co/d/0aonj8Qd
Learn more from JP Lindsley at Under Fire News: https://underfire.news
- - -
Today's Sponsors:
Policygenius - Head to https://policygenius.com/SHAPIRO to compare life insurance quotes from top companies and see how much you could save.
Golden Crest Metals - Right now GoldenCrest metals will send you a free investor kit, a free portfolio review, and up to $25,000 in free silver on qualifying purchases. Text BEN to METALS—that's 638257—go to https://GoldenCrestMetals.com/Ben, or call (888) 429-3999.
PreBorn! - Just $28 sponsors one ultrasound. And every ultrasound is another opportunity for a mother to meet her baby for the very first time. To donate, dial #250 and say the keyword "BABY" or give securely at https://PreBorn.com/BEN
- - -
DailyWire:
Become a Daily Wire Member and watch all of our content ad-free: https://dailywire.com/subscribe
🇺🇸 Get 3-Months of DailyWire for just $17.76 📜
📲 Download the free Daily Wire app today on iPhone, Android, Roku, Apple TV, Samsung, and more.
🍿 Watch Run Hide Fight: Infidels https://www.dailywire.com/videos/run-hide-fight-infidels
📰 Follow me on the Daily Wire app or DailyWire.com to read my daily articles and receive my Friday newsletter.
📘 My book "Lions and Scavengers: The True Story of America (and Her Critics)" is available here:
https://dwplus.shop/LionsandScavengers
👕 Get your Ben Shapiro merch here:
https://dwplus.shop/BenShapiroMerch
- - -
Socials:
YouTube — https://youtube.com/@BenShapiro
Facebook — https://www.facebook.com/officialbenshapiro
Instagram — https://www.instagram.com/officialbenshapiro
Snapchat — https://www.snapchat.com/officialbenshapiro
TikTok — https://www.tiktok.com/@real.benshapiro
X — https://twitter.com/benshapiro
- - -
Privacy Policy: https://www.dailywire.com/privacy
Learn more about your ad choices. Visit podcastchoices.com/adchoices
DISCLAIMER: Please note, this is an independent podcast episode not affiliated with, endorsed by, or produced in conjunction with the host podcast feed or any of its media entities. The views and opinions expressed in this episode are solely those of the creators and guests. For any concerns, please reach out to [email protected].
Beyond Vibe Coding: Own the Software Development Lifecycle With AI
2026/11/12
Artificial intelligence has dramatically accelerated software development, allowing developers to generate applications, build infrastructure, and automate repetitive tasks in a fraction of the time previously required. However, writing code faster does not necessarily mean delivering better software. Without clear requirements, thoughtful architecture, comprehensive testing, and proper documentation, AI-generated applications can introduce problems just as quickly as they solve them.
In this episode of Building Better Developers, Michael Meloche and Rob Broadhead continue their discussion about building a career beyond the code by examining how AI is transforming the software development lifecycle (SDLC). Their conversation focuses on why developers must take ownership of the entire process rather than relying on AI to generate working code.
Beyond Vibe Coding: Building Software With Purpose
Vibe coding has become an increasingly popular approach to developing applications with AI. Developers describe what they want, allow AI to generate the implementation, and refine the results until something appears to work. While this approach can produce rapid prototypes, it may also create applications with missing requirements, security weaknesses, or architectural problems.
Michael compares some AI-generated minimum viable products to structures held together with toothpicks. They may function initially, but their underlying design can lack the stability needed for production environments.
The solution is not to abandon AI-generated code. Instead, developers should use AI throughout the development process while maintaining responsibility for the quality and reliability of the result.
Start the AI Software Development Lifecycle With Requirements
Before generating code, developers must understand the problem being solved. Requirements define what the application should accomplish, how users will interact with it, and what conditions determine whether it works correctly.
Michael emphasizes the importance of requirements traceability, particularly as AI makes it easier to generate substantial amounts of code without fully understanding the intended behavior. A requirements traceability matrix connects requirements to implementation and testing, helping developers verify that important functionality has not been overlooked.
AI can assist with requirements analysis by identifying missing information, organizing acceptance criteria, and developing implementation plans. However, developers must review those outputs to ensure they reflect actual business needs.
Build Testing Into Development From the Beginning
Testing should no longer be something developers postpone until the end of a project. AI makes it possible to generate test scripts, configure development environments, and create automated testing infrastructure early in the lifecycle.
Rob recommends establishing development and QA environments alongside the initial application setup. Tools such as Docker can help developers create repeatable environments, while continuous integration and continuous delivery (CI/CD) pipelines can automatically execute tests and quality checks.
Michael also recommends simplifying repetitive processes through automation. If running the complete test suite requires several commands or tools, developers can create scripts that execute those steps consistently.
The goal is to make testing easier to perform and harder to overlook.
Prevent AI From Overengineering Your Application
Although AI can generate sophisticated architectures, more complexity does not necessarily produce a better solution. Rob describes situations where AI expanded relatively simple projects into unnecessarily elaborate environments, introducing additional components, testing steps, and infrastructure that offered little practical value.
This creates a different form of development risk. Instead of failing to implement enough functionality, AI may implement far more than the project requires.
Developers must review proposed architectures and question unnecessary complexity. AI should support project objectives rather than continually expanding them.
Clear requirements, defined boundaries, and regular progress reviews help prevent scope creep and keep development focused on the intended outcome.
Use Markdown Documentation to Maintain Context
One of Michael's practical recommendations is using Markdown files to maintain project context throughout AI-assisted development. Large AI conversations can become difficult to manage, particularly when multiple tasks, implementation decisions, and revisions occur over time.
A structured Markdown document can capture the problem being solved, requirements, implementation steps, completed tasks, outstanding questions, and decisions made during development.
Developers can instruct AI to update this documentation as work progresses, creating a record that supports code reviews, handoffs, and future maintenance.
This approach also helps prevent AI from losing focus. Instead of relying entirely on conversational history, the model can reference an approved project document that describes the current task and its boundaries.
Make AI Part of Your Quality Assurance Process
AI should not be limited to writing code. Developers can use it to review implementations, evaluate test coverage, inspect infrastructure, and identify weaknesses before submitting changes for peer review.
Rob recommends giving AI explicit review checklists rather than relying on broad requests such as asking it to find problems. A structured checklist can direct attention toward error handling, security, missing requirements, coding standards, and potential runtime failures.
Michael also describes using AI to understand undocumented legacy applications. By analyzing existing code and infrastructure, AI can help generate preliminary documentation that developers can verify and improve.
These capabilities make AI valuable for both new development and maintaining established systems.
Focus on Solving Problems Instead of Using AI Everywhere
Rob raises an important consideration: developers should not adopt AI simply because it is available. The starting point should always be the problem that needs to be solved.
Some tasks benefit significantly from AI-assisted analysis and development. Others are better handled with straightforward automation or conventional programming.
AI can help developers determine the appropriate solution, but human judgment remains essential when evaluating cost, complexity, reliability, and long-term maintainability.
The objective is not to maximize AI usage. It is to improve the effectiveness of software development.
Own the Entire Development Process
AI is changing how developers work, but it does not eliminate the need for strong software engineering practices. Requirements, architecture, quality assurance, documentation, security, and deployment remain essential components of successful applications.
As AI takes on more implementation work, developers have an opportunity to devote additional attention to these responsibilities. Instead of measuring productivity only by the amount of code produced, teams can focus on delivering reliable solutions that solve meaningful problems.
Stay Connected: Join the Developreneur Community
👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development.
Additional Resources
The Power of Clickable Demos in the Software Development Lifecycle
Software Development Requirements: Staying True to Specifications
AI Governance Framework: Why Guardrails Help AI Move Faster
Building Better Developers Podcast Videos – With Bonus Content
Beyond Vibe Coding: Ryan Drumheller on Building Better Products with AI
2026/11/12
Artificial intelligence has dramatically reduced the time and effort required to develop software, but building a successful product still demands more than generating code. Developers must understand customer problems, evaluate technical decisions, maintain quality, and create solutions that people actually want to use. In Part 2 of their conversation with Ryan Drumheller, Building Better Developers hosts Rob Broadhead and Michael Meloche explore how AI is reshaping product development and what that means for developers looking to build a career beyond the code.
About Ryan Drumheller
Ryan Drumheller is a technology leader, entrepreneur, author, and co-founder of Dogleg Digital. With more than two decades of experience spanning IT operations, infrastructure, development, technical leadership, and business strategy, Ryan has focused much of his career on connecting technology with the people and organizations it serves.
He graduated from Western Governors University and advocates for professional education, mentorship, and continuous learning. His book, From Firewalls to Fairways: How a Career in IT Led Me to Golf, shares lessons from his career and explores how setbacks and unexpected opportunities can lead to personal and professional reinvention.
Connect with Ryan and learn more about his work:
LinkedIn: https://www.linkedin.com/in/ryan-drumheller/
Personal website and book: https://ryandrumheller.com/
Dogleg Digital: https://doglegdigital.com/
Stop Selling Yourself and Start Solving Problems
Rob begins the second part of the interview by exploring an interesting observation from Ryan's career. Despite years of technical expertise and leadership experience, Ryan found it difficult to confidently sell his consulting services. However, when he began developing a product designed to solve a specific problem, that hesitation largely disappeared.
The difference was not simply confidence in his technical abilities. It was confidence in the solution.
Rather than asking potential customers to believe in his experience, Ryan could demonstrate a product shaped by their needs. His team had spoken with people in the golf industry, identified operational challenges, and incorporated that feedback into its development decisions.
This shifted the conversation away from selling technical expertise toward explaining how a solution could improve a customer's business.
For developers considering entrepreneurship or consulting, the lesson is significant. Customers are generally less concerned with the technologies used to build something than they are with whether it solves a problem that matters to them.
Finding Customers Through Genuine Conversations
Michael followed Ryan's comments by asking how he identified and connected with his target audience, particularly when traditional networking and face-to-face business relationships can be difficult to establish.
Ryan explained that his interest in golf initially developed as an escape from professional burnout. After spending years immersed in technology, getting outside and playing golf provided an opportunity to disconnect from work.
However, his technical curiosity eventually followed him onto the course.
As Ryan visited different golf facilities, he began observing their operations, software, booking processes, and business challenges. What started as a recreational activity became an opportunity to understand an industry from the customer's perspective.
He began asking questions, connecting with golf professionals on LinkedIn, publishing observations, and participating in industry discussions. Those conversations eventually helped shape Dogleg Digital's product direction.
Rather than building something first and searching for customers afterward, Ryan and his team used customer relationships to identify which problems deserved attention.
The approach provided valuable feedback while also establishing connections with potential future customers.
AI Makes Experimentation Easier, but Quality Still Matters
Rob then shifted the conversation toward AI and its ability to reduce the cost of experimenting with new software ideas.
Ryan acknowledged that modern AI tools make it possible to build products that would have required significantly more time and resources only a few years earlier. His original idea for Dogleg Digital had existed for approximately three years, but the economics of traditional development made the project more difficult to pursue.
AI changed what his team could realistically accomplish.
However, Ryan cautioned against confusing development speed with product readiness. Generating functional code is only part of the challenge. Developers still need to consider security, usability, reliability, and the experience delivered to the customer.
He specifically distinguished AI-assisted development from simply accepting whatever code an AI tool produces.
Developers with strong technical foundations can use AI to accelerate implementation while recognizing weaknesses, correcting mistakes, and making informed architectural decisions. Without that expertise, organizations risk releasing products that appear complete but lack the quality required for real-world use.
For Ryan, speed to market is important, but it cannot come at the expense of proper testing and quality assurance.
The Human Advantage in an AI-Driven Industry
Michael expanded the discussion by asking whether faster AI-powered development could reduce demand for traditional services as businesses increasingly build solutions themselves.
Ryan acknowledged that some industries are already experiencing this pressure, particularly creative and marketing-related professions. Organizations may view AI as an opportunity to reduce costs, even when doing so sacrifices valuable human experience.
However, he argued that experienced professionals remain essential because they understand how to use technology effectively.
An AI tool can produce an output, but an experienced developer or business specialist can evaluate whether that output makes sense, identify missing requirements, and recognize problems that automated systems overlook.
Ryan recalled that his approach to AI consulting involved identifying the employees who provided an organization with its greatest competitive advantages. Those were the people he wanted involved in AI adoption because their expertise could make the technology more effective.
The same principle applies to software development. AI should enhance the capabilities of knowledgeable professionals rather than become an excuse to eliminate critical thinking.
Leading Development Teams Beyond Vibe Coding
Rob connected Ryan's perspective to the responsibilities of effective leadership. A strong technical leader does not simply assign tasks and disappear. Leaders provide direction, participate in problem-solving, mentor their teams, and help ensure that the final work meets expectations.
Ryan described how Dogleg Digital combines traditional development expertise with AI-assisted processes.
His business partner creates detailed product requirements documents that outline functionality, interface expectations, and visual examples. These specifications provide developers with a clearer understanding of what needs to be built before implementation begins.
AI can then help accelerate the development process, allowing team members to spend more time refining functionality, improving security, and reducing defects rather than repeatedly interpreting incomplete requirements.
Ryan explained that this approach makes it easier for the entire team to understand development progress. It also allows a relatively small group to pursue an ambitious product roadmap that would have been substantially more difficult using traditional methods alone.
The result is not development without developers. It is a process where developers spend more of their time applying judgment and improving the finished product.
Building Better Developers Means Understanding the Entire Process
Ryan's experiences reinforce a recurring theme throughout this season of Building Better Developers: Technical ability alone is no longer enough to define a successful development career.
AI may change how code is written, but it does not eliminate the need to understand customers, establish clear requirements, manage risk, or evaluate whether a product delivers meaningful value.
The developers who thrive in this environment will be those who can connect technical capabilities with business outcomes. They will know when to use AI, when to challenge its recommendations, and when human experience must guide the final decision.
Ryan's journey from corporate technology leadership to building Dogleg Digital demonstrates how those skills can create opportunities beyond traditional employment.
The future of software development is not simply about writing code faster. It is about understanding the problem, building the right solution, and using AI to make the entire process better.
Follow Building Better Developers for more conversations with technology leaders, entrepreneurs, and professionals who are creating opportunities beyond the code.
Stay Connected: Join the Developreneur Community
👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development.
Additional Resources
AI-Native Development Without the Hype: Kevin Riedl on Building Better Software With AI
AI Security for Developers: Protecting Your Code, Data, and Intellectual Property
2026/11/10
Artificial intelligence is changing how developers build software, but it is also changing how we think about security. AI can generate applications, analyze complex systems, and identify vulnerabilities much faster than traditional development processes. While these advancements provide tremendous opportunities, they also introduce new risks for developers, businesses, and anyone responsible for protecting sensitive information.
In this episode of Building Better Developers, co-hosts Michael Meloche and Rob Broadhead explore AI security for developers and the challenges of protecting code, data, and intellectual property in an increasingly connected world. As part of Season 29, Building a Career Beyond the Code, their discussion examines why developers must expand their skills beyond writing code and begin taking greater responsibility for the systems they create.
Why AI Changes Software Security
For years, developers relied partly on the complexity of software systems to discourage unauthorized access. Although security by obscurity was never a reliable security strategy, understanding or exploiting certain vulnerabilities often required significant time and technical knowledge. AI is changing that equation by making it easier to analyze code, automate tests, and explore potential weaknesses.
Rob explains that developers can no longer assume a system is secure simply because finding its vulnerabilities would take too much effort. AI-assisted tools allow someone to investigate far more possibilities than traditional manual testing, increasing the importance of deliberate security practices.
However, these capabilities are not limited to attackers. Developers can use AI to improve their own testing processes, examine unusual scenarios, and identify potential weaknesses before software reaches production. The same technology that creates new security concerns can become an important part of the solution.
Protecting Intellectual Property in the AI Era
Michael raises another significant concern: protecting proprietary software and business information when developers increasingly rely on external AI services. Many organizations have invested years in developing specialized applications, internal processes, and unique business logic that provide competitive advantages.
While common software components and established programming patterns are widely available, certain implementations and combinations of business rules may represent valuable intellectual property. Sharing that information with an external AI service requires careful consideration of the provider's data-handling policies and the permissions granted to the tool.
The concern extends beyond source code. Technical documentation, customer records, internal processes, and business strategies may contain information that organizations cannot afford to expose. Developers must understand what information they are sharing and why an AI system needs access to it.
AI Security Starts With Data Protection
One of the central lessons from the conversation is that protecting information begins with limiting unnecessary access. Rob compares this approach to established security practices in regulated industries, where sensitive information must be handled according to specific requirements.
Developers should apply those same principles when working with AI. An application may need access to a database credential to perform a task, but the AI model helping build that application generally does not need to see the credential itself. Likewise, customer information can often be replaced with representative test data when debugging software.
Practical safeguards include:
Keep passwords, API keys, and other secrets out of AI prompts.
Limit AI access to the specific files and information required.
Separate sensitive business data from application code.
Review AI providers' privacy, retention, and training policies.
Use appropriate access controls for repositories and internal systems.
Test applications for vulnerabilities before deploying them.
These practices reduce unnecessary exposure while allowing development teams to benefit from AI-assisted tools.
Local AI Versus Cloud-Based AI
Michael and Rob also discuss whether running AI locally provides additional protection. Local AI systems can offer greater control over where information is stored and processed, making them attractive for businesses handling proprietary or sensitive material.
However, building a private AI environment introduces additional considerations, including hardware expenses, maintenance, access controls, and network security. A locally hosted model is not automatically secure simply because it operates on internal hardware.
For many developers, a hybrid approach may offer a practical balance. Sensitive information can remain in controlled environments while less sensitive tasks use external AI services. The important decision is not whether every organization needs private AI, but whether developers understand the risks associated with each approach.
Use AI to Strengthen Your Security Practices
Rather than viewing AI exclusively as a potential threat, developers should consider how it can improve software quality and security. AI can assist with generating unit tests, reviewing code, examining authentication logic, and identifying scenarios that might otherwise be overlooked.
For example, instead of asking whether an application works under normal conditions, developers can ask AI to identify unusual inputs, possible permission failures, and unexpected interactions between components. These questions encourage a more comprehensive approach to development and testing.
AI-generated findings still require verification, but they can help developers investigate problems more efficiently and focus attention on areas that deserve closer examination.
Building a Career Beyond the Code
The changing security landscape reinforces the broader message of Season 29. Developers increasingly need the ability to evaluate systems, understand business requirements, recognize risks, and make informed technical decisions.
AI can accelerate programming, but it cannot remove the developer's responsibility for the resulting product. Understanding what information should remain private, how components interact, and where vulnerabilities may exist becomes essential as software development grows more automated.
The future of development is not simply about generating applications faster. It is about building software responsibly, protecting the information that matters, and using AI as a tool to strengthen the entire development process.
Stay Connected: Join the Developreneur Community
👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development.
Additional Resources
AI Governance Framework: Why Guardrails Help AI Move Faster
AI Governance Implementation: Turning AI Policies into Everyday Practice
AI Governance Framework: Why Every Business Needs Guardrails Before AI
Building Better Developers Podcast Videos – With Bonus Content
From Firewalls to Fairways: Reinventing Your Technology Career with Ryan Drumheller
2026/11/03
A successful technology career does not always follow a straight path. Developers and IT professionals often start with a clear idea of where they want to go, only to find that layoffs, industry shifts, burnout, and unexpected opportunities can completely change their direction. In this episode of Building Better Developers, hosts Rob Broadhead and Michael Meloche welcome Ryan Drumheller to discuss his journey from hands-on technology work to leadership, consulting, and eventually entrepreneurship.
About Ryan Drumheller
Ryan Drumheller is a technology leader, entrepreneur, author, and co-founder of Dogleg Digital. With more than two decades of experience spanning IT operations, infrastructure, development, technical leadership, and business strategy, Ryan has focused much of his career on connecting technology with the people and organizations it serves.
He graduated from Western Governors University and advocates for professional education, mentorship, and continuous learning. His book, From Firewalls to Fairways: How a Career in IT Led Me to Golf, shares lessons from his career and explores how setbacks and unexpected opportunities can lead to personal and professional reinvention.
Connect with Ryan and learn more about his work:
LinkedIn: https://www.linkedin.com/in/ryan-drumheller/
Personal website and book: https://ryandrumheller.com/
Dogleg Digital: https://doglegdigital.com/
Finding a Passion for Technology
Ryan's interest in technology began long before he entered the professional world. As a child, he struggled to find a traditional artistic outlet, but computers gave him the freedom to experiment and create. He spent countless hours taking computers apart, putting them back together, exploring early internet technology, and learning how systems worked.
That curiosity eventually led him through technical support, networking, development, engineering, and leadership. While his technical skills opened doors, his ability to connect with people helped shape the next stage of his career.
Michael related to Ryan's experiences, having grown up during the same era of dial-up internet and bulletin board systems. Their conversation highlighted how early experimentation developed problem-solving skills that remain valuable today.
However, Ryan acknowledged that his curiosity sometimes created challenges in professional environments. He frequently wanted to understand why a problem existed rather than simply applying the requested solution. Over time, he learned to balance his desire to explore with the practical needs of the business.
Building a Technology Career in the Age of AI
As their discussion shifted toward artificial intelligence, Michael asked an important question: How should developers entering the industry today build the experience needed to remain valuable?
Ryan emphasized that AI has fundamentally changed the opportunities and expectations facing technology professionals. While AI can generate code and accelerate development, understanding how systems operate remains essential. Developers must recognize mistakes, evaluate security concerns, and determine whether a proposed solution actually works.
Rather than relying exclusively on one technical specialty, Ryan encourages professionals to develop multiple complementary skills. Understanding different technologies, industries, and business processes creates opportunities that cannot easily be replaced by automated tools.
The objective is not to compete against AI at everything it can do. Instead, developers should combine their knowledge with AI to deliver better results.
When the Traditional Career Path Stops Working
Ryan's career followed a familiar progression from individual contributor to technical leader. However, professional success did not provide immunity from organizational changes.
After losing one position, Ryan completed approximately 20 interviews and found another opportunity within 35 days. That role allowed him to work internationally, expand his experience, and continue growing professionally.
Unfortunately, another organizational shift eventually eliminated that position as well. This time, Ryan encountered a very different employment market, influenced by economic uncertainty and the rapid adoption of AI.
Michael shared a similar experience involving the elimination of his team following a corporate acquisition. Their discussion reflected a growing concern among experienced professionals: Even a strong technical background and years of demonstrated performance do not guarantee employment stability.
These experiences encouraged Ryan to reconsider what he wanted from the next stage of his career.
Networking Is More Important Than Ever
One of Ryan's strongest recommendations for professionals navigating career uncertainty is to build meaningful relationships before they urgently need them.
He considers LinkedIn a valuable platform for sharing expertise, discovering opportunities, and connecting with people already working in roles or industries of interest. However, he cautions against approaching every interaction with the expectation of receiving something in return.
Instead, networking should begin with curiosity. Ask questions, participate in discussions, share useful information, and develop genuine relationships over time.
For professionals who feel overwhelmed by networking, Ryan recommends simply starting. A few meaningful interactions can create opportunities that would never emerge from submitting another application.
Turning Career Setbacks Into New Opportunities
Ryan eventually discovered that consulting was not necessarily the professional environment where he felt most comfortable. Although he possessed extensive technical expertise, he found selling his personal services more difficult than communicating the value of a tangible product.
That realization helped him revisit an earlier business idea that eventually evolved into Dogleg Digital, a technology ecosystem designed for the golf industry.
His path toward entrepreneurship was not an immediate success story. Ryan described Dogleg Digital as his fourth attempt at building something. Each previous experience provided lessons about his strengths, his interests, and the type of work he wanted to pursue.
Ryan's perspective challenges the idea that a career setback represents permanent failure. Experimentation, changing direction, and learning from unsuccessful attempts can all contribute to finding a better opportunity.
From Firewalls to Fairways: Lessons Beyond Technology
Ryan's book, From Firewalls to Fairways, connects his professional experiences to the lessons learned during a round of golf. Each chapter uses a different hole to explore topics such as career development, networking, salary negotiations, leadership, setbacks, and personal growth.
The golf analogy reflects an important reality: Careers rarely unfold exactly as planned. Sometimes the best opportunity comes from reassessing the situation and choosing a different direction.
For developers concerned about AI, employment uncertainty, or professional stagnation, Ryan's journey provides a valuable reminder that technical expertise is only one component of a sustainable career.
Learning to build relationships, recognize opportunities, and adapt to change can be just as important as learning another programming language.
Join Rob Broadhead and Michael Meloche for Part 2, where Ryan explains how he turned an industry problem into a product and why AI is changing the way developers build, test, and deliver software.
Stay Connected: Join the Developreneur Community
👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development.
Additional Resources
Career Improvement – From Better Developer To Better Career
Lifelong Learning Habit: The Career Advantage That Outlasts Talent
Security Awareness: Protect Your Code, Your Career, and Your Future
Building Better Developers Podcast Videos – With Bonus Content
Beyond Vibe Coding: Why Developers Must Become AI Team Leaders
2026/10/29
Artificial intelligence is rapidly changing what it means to be a software developer. Writing code is becoming easier, AI agents can complete increasingly complex assignments, and developers can accomplish tasks that previously required entire teams. However, the ability to generate software does not automatically mean the software is useful, secure, scalable, or even correct.
That raises an important question for developers at every stage of their careers: If AI can write much of the code, what skills will define the difference between junior, mid-level, and senior developers?
In Season 29, Episode 14 of the Develpreneur Podcast, Rob Broadhead and Michael Meloche continue their conversation about building a career beyond the code. This time, they focus on the evolution of vibe coding, the increasing importance of engineering judgment, and why developers must learn to manage AI agents like members of a development team.
Vibe Coding Is Evolving Into AI-Assisted Engineering
Vibe coding began as a way to describe building applications through natural-language instructions rather than manually writing every line of code. A developer could explain what they wanted, allow an AI tool to generate the implementation, and make adjustments through conversation.
That approach is evolving rapidly.
Developers are beginning to use specialized agents for planning, implementation, testing, documentation, and deployment. Instead of a single assistant generating snippets of code, AI can participate in much larger portions of the development process.
Rob observes that this changes how developers should think about their roles. When several AI agents can work on different assignments, the developer begins functioning more like a development team leader than an individual programmer.
The value moves from typing instructions into a source file to coordinating work, reviewing decisions, and making sure the final solution meets the intended goals.
What Separates a Junior Developer From a Senior Developer?
Traditional career progression has often been tied to experience with programming languages, frameworks, architecture, and increasingly complex technical assignments.
Junior developers learn how to implement features. Mid-level developers begin taking ownership of larger components. Senior developers understand broader systems, evaluate tradeoffs, mentor others, and take responsibility for technical outcomes.
AI complicates that progression.
If a junior developer and a senior developer both have access to tools capable of generating sophisticated code, the difference between them cannot be measured simply by how much code each person produces.
The distinction increasingly becomes the ability to evaluate what AI creates.
Can the developer identify missing requirements? Can they recognize security concerns? Do they understand why one architectural approach is better than another? Can they explain what happens when the application needs to scale? Do they know how to test and verify the result?
These skills have always mattered, but AI makes them even more visible.
Technical Knowledge Is Not the Same as Practical Experience
Michael shares an example from his experience teaching Java boot camps.
Some students could study a certification guide, memorize the material, and pass a technical examination without having much practical experience building software. Others had spent years developing applications and could solve complex problems but struggled with certification tests.
The certification demonstrated knowledge of specific material. It did not necessarily demonstrate the ability to engineer a complete solution.
AI introduces a similar challenge.
Someone who knows how to use AI tools effectively may produce impressive applications without fully understanding the underlying systems. That does not mean their work has no value, but it does mean employers and customers need better ways to evaluate their capabilities.
Developers must demonstrate that they understand what they are building, not simply that they can get AI to build it.
The Software Development Lifecycle Is Becoming More Important
One of the biggest changes AI introduces is a shift in how developers spend their time.
Historically, software implementation consumed a substantial portion of a project's schedule. Developers spent hours writing classes, creating interfaces, connecting APIs, and implementing business logic.
AI can reduce much of that implementation effort.
However, the remaining stages of the software development lifecycle still matter.
Requirements must be understood. Solutions must be designed. Systems must be tested. Applications must be deployed. Security must be evaluated. Users must confirm that the software actually meets their needs.
Rob emphasizes that developers increasingly need to understand the complete lifecycle, from initial requirements through deployment and ongoing improvement.
Michael points out that this transformation has been developing for years. Organizations have already been moving testing and DevOps responsibilities closer to development teams. AI accelerates the expectation that developers understand more than their individual specialty.
A developer who can connect the entire process becomes increasingly valuable because they can recognize problems that arise between traditionally separate responsibilities.
Quality Assurance Cannot Become an Afterthought
One of the dangers of AI-assisted development is confusing the speed of implementation with the quality of the result.
AI can generate large amounts of code, but that does not guarantee that the code is correct.
It may misunderstand requirements, introduce security weaknesses, create unnecessary dependencies, or produce a solution that technically works but fails to solve the customer's actual problem.
Michael emphasizes that quality assurance remains essential.
As implementation becomes faster, developers should spend more time verifying what has been produced. Automated tests, integration testing, user acceptance testing, and critical reviews are necessary to ensure that faster development does not produce larger collections of defects.
The opportunity AI creates is not simply to deliver more features. It is to spend more time making sure those features work correctly and provide value.
Learn to Manage AI Like a Development Team
Managing AI agents requires many of the same skills used to lead human developers.
You need to communicate expectations, establish boundaries, review progress, provide feedback, and determine whether the work meets the requirements.
Michael suggests viewing AI agents as team members that need direction and supervision. Even developers who have not held formal leadership positions can begin practicing these skills through AI-assisted development.
For example, you might assign one AI agent to design a feature, another to implement it, and another to review the result. However, someone still needs to determine whether the implementation meets the business need.
That responsibility belongs to the developer.
This process also helps developers develop better technical communication skills. If an AI agent consistently misunderstands an assignment, it may indicate that the requirements were incomplete or unclear.
Learning to provide better direction can improve your interactions with AI and your communication with human coworkers.
Business Value Matters More Than Software Output
Rob returns to a fundamental principle of successful software development: the value of software comes from the problem it solves.
Building another dashboard is not necessarily valuable. Adding another feature does not automatically improve a product. Increasing the number of lines of code does not make an application more useful.
The important question is what changes for the user.
Does a new feature eliminate unnecessary work?
Does an automation reduce mistakes?
Does a dashboard help someone make a better decision?
Does the application make a business process faster, more reliable, or easier to manage?
These are the outcomes developers should focus on.
Rob uses the simplicity of the original iPod as an example of how removing unnecessary complexity can create a better user experience. More features often introduce more testing requirements, maintenance concerns, and potential points of failure.
The best solution is not always the one that does the most.
Sometimes the most valuable engineering decision is knowing what not to build.
AI Does Not Belong in Every Solution
The increasing accessibility of AI has also created a temptation to use it everywhere.
Michael cautions against online promises that suggest building a collection of AI agents will automatically create passive income or effortless business growth. Those systems require development effort, maintenance, subscriptions, processing costs, and ongoing supervision.
Rob expands on the point by explaining the importance of deterministic software.
Some tasks benefit from AI's ability to analyze information and handle ambiguity. Others need predictable behavior and repeatable results.
For example, a system gathering specific information from a website may benefit from AI during exploration or when handling unexpected page changes. However, the actual collection of known data fields may be better handled through conventional programming.
Developers should evaluate where AI creates meaningful value and where simpler technology produces a more reliable and economical result.
AI should be a tool selected for a reason, not the automatic answer to every technical problem.
Practice Building and Managing Your
How to Stand Out as a Developer in the Age of AI: Prove Your Value Beyond the Code
2026/10/27
Artificial intelligence has changed the way developers write code, search for jobs, and present their professional experience. Resumes can be generated in seconds, proposals can be polished instantly, and technical answers are available with a simple prompt. However, all of this convenience creates a new challenge: How do you distinguish yourself when everyone has access to the same tools?
In Season 29, Episode 13 of the Develpreneur Podcast, co-hosts Rob Broadhead and Michael Meloche explore how AI is changing hiring, professional development, and the way developers communicate their value. As part of the season's theme, Build a Career Beyond the Code, they discuss why technical skills alone are becoming less effective at setting candidates apart and why critical thinking, authentic experience, and demonstrated problem-solving abilities matter more than ever.
The Problem With AI-Generated Resumes and Proposals
AI has made it easier than ever to produce professional-looking resumes and proposals. A candidate can enter a job description into an AI tool and receive a document that addresses nearly every requirement. Similarly, consultants can generate detailed proposals that appear to align perfectly with a customer's needs.
The problem is that these documents are becoming increasingly similar.
Rob compares this shift to the transition from standard-definition television to high-definition broadcasting. When everything became clearer, details that previously went unnoticed suddenly became obvious. AI is having a similar effect on professional communication. It has exposed how much of the traditional job application process relies on formulas and predictable language.
Recruiters and hiring managers are becoming familiar with AI-generated responses. A polished resume may help someone enter the hiring process, but it does not necessarily demonstrate that the candidate has the experience or judgment required to perform the job.
The real challenge is no longer simply getting someone to see your resume. It is convincing that person to have a meaningful conversation with you.
Your Technology Stack Is Not Your Entire Professional Story
Developers traditionally describe their experience through programming languages, frameworks, databases, and platforms. A resume might highlight Java, Spring Boot, AWS, React, Python, or dozens of other technologies.
While these skills remain relevant, they do not tell the complete story.
Knowing how to write code is only one part of being a successful developer. Employers and customers need people who can recognize problems, evaluate alternatives, make informed decisions, and deliver solutions that create measurable value.
Rob suggests shifting attention away from simply listing technologies and toward explaining the problems you have solved.
Consider the difference between stating that you developed a Java application and explaining that you redesigned a business process, eliminated repetitive manual work, addressed performance problems, or improved the reliability of a critical system.
The technology describes how you accomplished the work. The problem and its outcome explain why the work mattered.
Show Your Work: Critical Thinking Is the Differentiator
Michael draws an interesting comparison between software development interviews and solving math problems.
In school, students are often required to show their work rather than simply provide the final answer. The process demonstrates whether they understand the underlying concepts and can apply them to different situations.
Software development interviews should follow a similar approach.
AI can generate an answer to a coding problem almost instantly. However, that does not mean the person using AI understands the problem, recognizes potential limitations, or knows how to adapt when circumstances change.
A stronger interview focuses on the candidate's reasoning.
What problem are they trying to solve? What information do they need? How would they approach the design? What happens when their initial solution fails? How would they explain their recommendation to someone without a technical background?
These questions reveal abilities that are difficult to evaluate through memorized answers or automated coding exercises.
Michael also emphasizes the importance of communicating with nontechnical stakeholders. Developers frequently work with business owners, managers, and customers who care more about results than implementation details. Being able to explain complex technical decisions in understandable language is an increasingly valuable skill.
AI Is Changing the Hiring Conversation
Both Rob and Michael discuss how AI is introducing new complexity into the hiring process.
Michael shares experiences with candidates relying heavily on AI during interviews. Instead of responding naturally, some applicants appear to be generating answers in real time. This makes it harder for interviewers to determine whether they are evaluating the candidate's knowledge or simply the output of an AI tool.
At the same time, interviewers are becoming more sophisticated in how they evaluate applicants.
Rather than relying exclusively on technical questions, employers can ask candidates to explain previous projects, describe unexpected problems, and discuss how they adjusted their approach.
Those experiences provide a more authentic view of someone's capabilities.
A developer who can explain a difficult production issue, describe why a design decision failed, and show how the team recovered demonstrates practical experience that goes beyond a collection of keywords.
Do Not Confuse AI Assistance With AI Dependence
AI can be an excellent tool for preparing resumes, practicing interviews, researching companies, and organizing professional experience. It can help developers identify gaps in their explanations and discover better ways to communicate their accomplishments.
However, the value comes from using AI to strengthen your own knowledge rather than replace it.
Rob points out that AI-generated suggestions must be evaluated carefully. A response may sound complete while including unsupported assumptions, unnecessary details, or information that does not accurately represent your experience.
Michael adds that newer AI tools and models are not always automatically better for every workflow. Developers need to evaluate the reliability of the tools they use rather than constantly adopting the newest model simply because it is available.
The key is maintaining control over the process.
Use AI to prepare, refine, and challenge your thinking, but make sure the final result accurately represents what you know and what you have accomplished.
Just Because AI Can Do Something Does Not Mean It Should
Rob closes the discussion with an example from his own AI-assisted development work.
While working on a project, an AI assistant began identifying additional improvements in related environments. Some recommendations involved security, infrastructure, and other technical areas. Although the suggestions might have been useful in another context, they were outside the project's intended scope.
Rob had to explicitly instruct the AI not to make those changes.
This illustrates one of the most important responsibilities developers have when working with AI: determining which recommendations actually matter.
Without clear boundaries, AI can turn a relatively focused task into a much larger project. Developers must recognize when additional complexity creates value and when it creates unnecessary work or risk.
The ability to make those decisions requires experience, judgment, and a clear understanding of the intended outcome.
Building a Career Beyond the Code
The software industry is entering a period where simply producing code is becoming less distinctive. AI can assist with implementation, generate documentation, and automate repetitive tasks, but it still requires thoughtful direction and meaningful evaluation.
Developers who want to remain competitive need to strengthen the abilities that connect technical work to real-world results.
That means learning how to communicate, solve problems, evaluate tradeoffs, demonstrate experience, and explain the value of the work they perform.
The strongest professional story is not a list of technologies. It is a collection of problems solved, challenges overcome, lessons learned, and outcomes achieved.
Key Takeaways
Use AI to improve your resume and interview preparation without allowing it to misrepresent your experience.
Focus on the problems you have solved rather than relying exclusively on technical keywords.
Be prepared to explain your reasoning, decisions, challenges, and lessons learned.
Practice communicating technical solutions to nontechnical audiences.
Evaluate AI recommendations instead of accepting them automatically.
Document your accomplishments so you can provide real evidence of your professional value.
As AI continues to reshape software development, the ability to demonstrate genuine experience and sound judgment will help developers distinguish themselves from increasingly automated competition.
Your value is not simply that you know how to write code. It is that you know how to use technology to solve meaningful problems.
That is how you build a career beyond the code.
Stay Connected: Join the Developreneur Community
👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episo
Use the Right AI for the Job: Kevin Riedl on Local Models, AI Routing, and Smarter Development
2026/10/22
AI is an essential tool for many developers, but using it well takes more than picking the most powerful model. As adoption grows, developers and businesses face new questions about cost, performance, infrastructure, and matching the right technology to each task. Knowing when and how to use each option is becoming a core engineering skill.
In this episode of Develpreneur, Rob Broadhead and Michael Meloche continue their conversation with Kevin Riedl, founder of Wavect, an AI-native software agency in Austria. Building on our last discussion about AI-native development and software quality, we dig into the technical and business decisions behind efficient AI-powered systems.
Kevin shares his views on local AI models, cloud services, model routing, orchestration, token optimization, and shifting expectations for software development. We also talk about how smaller companies can compete with larger ones by using AI strategically, without piling on cost or complexity.
This episode fits Season 29, Build a Career Beyond the Code. Generating code is getting easier for everyone. Designing efficient systems, controlling costs, and delivering real business outcomes is where the value is.
About Kevin Riedl
Kevin Riedl is the founder of Wavect, an AI-native software agency based in Austria that works with clients internationally. His work covers software engineering, artificial intelligence, product development, and helping organizations build effective technology solutions.
Through Wavect, Kevin helps businesses with AI-assisted development, software modernization, and improving their engineering processes. His approach emphasizes practical results, thoughtful technology decisions, and using AI to create measurable business value. He also shares insights on emerging AI tools, software engineering practices, and technology trends through his professional content and Wavect's online resources.
Connect with Kevin Riedl:
LinkedIn: https://www.linkedin.com/in/wsdt/
Wavect: https://wavect.io/
Local AI vs. Cloud AI: Which Makes More Sense?
As developers get comfortable with AI, many start thinking about running models locally. Instead of relying on ChatGPT or Claude, they consider buying hardware and hosting their own AI infrastructure.
Michael brought this up while talking about his experiments with Apple Silicon, including Mac minis and a Mac Studio. Powerful consumer hardware gives developers more room to experiment with local models and build private AI systems.
Kevin says the decision often comes down to economics.
Local AI keeps improving, but cloud-based frontier models are still cheap compared with buying and maintaining the hardware needed to approach their capabilities. For many individuals and small businesses, running advanced models locally would cost more than a commercial AI service.
That doesn't mean local AI has no value. Running models locally gives you more control over your data, less dependence on outside providers, and a good fit for workloads that run continuously. It also lets developers see how models behave outside the interfaces the major AI companies provide.
The real question is whether the investment supports an actual business or technical need. A company sending occasional requests will likely do better with a cloud subscription. An organization running AI workloads around the clock may find dedicated hardware increasingly attractive.
Kevin recommends understanding both approaches instead of assuming one always wins.
Why Developers Should Experiment With Local Models
Even if cloud AI makes financial sense today, developers should know the alternatives.
AI providers keep changing their models, capabilities, pricing, and services. A business that depends on one provider may eventually hit limits that affect its costs or operations. Understanding local AI gives you another option.
Kevin suggests Hugging Face as a starting point for exploring available models. The platform hosts a large collection that developers can evaluate for different workloads. Tools like Ollama make it easier to run supported models on local hardware, compare capabilities, and learn the limits of smaller models.
Experiments should have a purpose. A developer might test whether a local model can summarize documents, classify information, process internal records, or handle repetitive tasks without sending data to an outside service. Those jobs don't necessarily need the most advanced model available.
Once you know which tasks a local model can handle, you can design systems that balance performance, cost, and privacy.
AI Model Routing: Choosing the Right Model for Each Task
One of the most interesting topics in our conversation was AI model routing.
Many developers pick a single AI platform and use it for nearly everything. The same advanced model summarizes emails, writes documentation, analyzes complicated architecture, and produces production code. It's convenient, but it isn't always efficient.
Kevin believes model routing will become an important part of AI development. Instead of sending every request to the same model, a routing system evaluates the task and picks a model that fits its requirements.
It works like assigning work on a development team. You wouldn't put your most experienced architect on every small documentation update or routine data-processing job. You don't need the most powerful AI model for every request either.
A model-routing strategy might look like this:
Simple classification: Use a smaller model to categorize emails, documents, or support requests.
Document summarization: Use a model that can handle the required context without extra reasoning overhead.
Code generation: Pick a model suited to the complexity and requirements of the task.
Architecture analysis: Use a more capable model when the work needs deeper reasoning and broader context.
Sensitive internal processing: Consider local models when privacy requirements rule out external services.
Complex problem-solving: Escalate difficult tasks to a more advanced model when simpler approaches fall short.
The goal isn't to pick the cheapest model. It's to find the least expensive model that can reliably do the job. A model that's too limited can cost more in the end if it produces wrong results or needs repeated attempts. Kevin stresses that routing has to balance capability and efficiency, not just price.
For developers building AI-powered applications, this is another place to apply traditional engineering principles.
AI Orchestration: Letting Models Work Together
Model routing gets even more powerful when combined with orchestration.
Instead of relying on one model to complete an entire workflow, developers can build systems where a more capable model coordinates several specialized agents or smaller models. Kevin described an approach where a higher-level AI system decides what needs to be done and delegates tasks to other models.
That mirrors how software teams divide work. A senior engineer defines the overall architecture while other team members build specific components. An AI orchestrator can take a larger objective, break it into manageable tasks, and assign each one based on the capabilities it needs.
A development workflow might use separate agents to analyze requirements, generate code, review changes, run tests, and summarize results, with the orchestration layer coordinating the work and deciding when more is needed. This can reduce how much expensive model processing goes to routine tasks.
Orchestration also adds complexity. Developers have to consider how agents communicate, how results get validated, and how the system handles failures. The goal isn't to build as many agents as possible. It's a workflow that produces reliable results with reasonable resource use.
Kevin also noted that existing AI development tools already include some orchestration features. Try those before building a complicated custom solution.
Sometimes the Best AI Solution Doesn't Use AI
Rob raised another point: what happens when an AI workflow becomes predictable enough that it no longer needs AI?
Software development has always meant finding repeatable processes and automating them. Once the rules are clear, developers can often build deterministic solutions that give consistent results. AI doesn't change that.
Kevin says that if a task requires deterministic behavior, use deterministic technology instead of adding a language model. If a system needs to validate a known data format, calculate a specific value, or apply established business rules, conventional software is usually more consistent and cheaper.
AI earns its place when a task requires interpretation, reasoning, or handling information that doesn't follow a predictable structure. Developers can get so focused on integrating AI that they overlook simpler options. A well-designed application may use AI for some tasks and conventional code for others.
The best architecture isn't the one that uses the most AI. It's the one that solves the problem efficiently and reliably.
AI Is Raising Customer Expectations for Software
AI adoption is also changing what customers expect.
Developers can build prototypes and minimum viable products faster than ever. Applications that once took weeks can become working demos in days. Kevin points out that customers know this. When software gets easier to produce, they expect more.
That adds competition. A functional application no longer gives the advantage it once did. More businesses can build software, more entrepreneurs can test ideas, and more developers can bring products to market. As the number of solutions grows, standing out takes more than the ability to generate an app.
Businesses need
AI-Native Development Without the Hype: Kevin Riedl on Building Better Software With AI
2026/10/20
Companies are racing to adopt AI. Developers are experimenting with increasingly powerful coding agents. Businesses want projects delivered faster. But faster development doesn't automatically produce better software.
In this episode of Develpreneur, Rob Broadhead and Michael Meloche talk with Kevin Riedl, founder of Wavect, an AI-native software agency in Austria. Kevin shares what he has learned building software with AI, helping organizations adopt it, and balancing automation with proven engineering practices. We cover what AI-native means, why quality assurance still matters, and how developers can use AI without sacrificing security, reliability, or maintainability.
This episode fits Season 29, Build a Career Beyond the Code. Writing code keeps getting easier. Knowing what to build, how to validate it, and whether it solves the right problem matters more every month.
About Kevin Riedl
Kevin Riedl is the founder of Wavect, an AI-native software agency based in Austria that works with clients internationally. His work covers software engineering, artificial intelligence, product development, and helping organizations build effective technology solutions.
Through Wavect, Kevin helps businesses with AI-assisted development, software modernization, and improving their engineering processes. He emphasizes practical results, established engineering principles, and reliable software over adopting technology because it's popular. He also shares insights on AI development, emerging tools, software engineering, and technology trends through his professional content and Wavect's online resources.
Connect with Kevin Riedl:
LinkedIn: https://www.linkedin.com/in/wsdt/
Wavect: https://wavect.io/
What Does It Really Mean to Be AI-Native?
Startups use the term "AI-native" to describe their business models. Established companies are restructuring around it. Software teams are working it into their development processes. Kevin thinks organizations should be careful about what the term means.
Being AI-native doesn't mean putting AI in every application or discarding decades of engineering experience. It means knowing where AI adds value and pairing it with proven development practices.
Kevin calls AI one of the most significant tools developers have received in decades, but it's still a tool. Developers still need to understand architecture, security, testing, requirements, and the business problem in front of them.
Some organizations treat AI as a replacement for their existing processes. They assume that because AI can generate code, it can also make every architectural decision, understand every requirement, and catch every problem. It can't. Good AI-native development combines what AI does well with human engineering expertise.
The goal isn't to use AI everywhere. The goal is better software, with AI used where it makes sense.
Just Because AI Can Do Something Doesn't Mean It Should
AI capabilities have expanded quickly. Modern tools can write applications, deploy infrastructure, drive browsers, analyze repositories, run tests, and help gather customer requirements. Work that once took specialized knowledge or significant time can now be partly automated.
That doesn't make automation the right call every time.
Experienced developers know the pattern. AI produces an answer that looks reasonable but misses key context. The code works, but it ignores performance concerns, security requirements, or existing architectural decisions. The model repeats approaches that already failed, or its changes break something elsewhere in the application.
The risk grows with the responsibility. Asking a model to explain a function carries little risk. Letting it modify an entire application or deploy infrastructure carries a lot more.
Kevin keeps human expertise and quality assurance at the center. Developers need to understand what the AI is doing, spot its mistakes, and set up controls that keep those mistakes out of production.
AI speeds up development. Developers still own the results.
AI Adoption Is Not the Biggest Challenge. Governance Is.
Michael asked about companies that introduce AI without preparing their people. Some buy tools, hand out licenses, and expect productivity to jump. Others build controlled environments, train employees, and phase AI into existing workflows.
Kevin says that at many companies, getting employees to use AI is no longer the hard part. They're already experimenting, sometimes without their employer knowing.
The hard part is setting rules and making sure people understand them.
Kevin described a large enterprise that had invested in its IT department, written internal policies, and provided approved AI tools. Employees still had personal smartphones. If they wanted help with a problem, they could photograph their screen and send it to a public AI service.
Locking down company computers doesn't fix that.
Organizations need to teach employees what information they can share, which tools are approved, and how to use AI responsibly. Kevin compares it to cybersecurity awareness training. Employees learned to spot phishing and suspicious emails. Now they need to learn the risks of sharing information through AI platforms.
AI governance has to be part of daily operations, not a policy people read once and forget.
Start With Simple AI Guardrails
When Michael asked what organizations should do to protect themselves, Kevin said it depends on the business. A small software agency has different needs than a large financial institution or a multinational enterprise.
His advice is to start with the basics instead of trying to solve every problem at once. Simple policies and employee education cover many of the most common risks. Start with the mistakes most likely to happen in normal AI use.
Practical guardrails to start with:
Protect confidential information. Never put sensitive business data, customer records, credentials, or proprietary information into unapproved AI services.
Establish approved tools. Tell employees which AI platforms they can use and what restrictions apply.
Provide ongoing training. Cover AI policies in onboarding and reinforce them as tools change.
Maintain human oversight. Require review before AI-generated changes reach production systems or customers.
Define quality standards. Set testing requirements, acceptance criteria, and review processes for AI-assisted work.
Adapt policies to the business. Account for industry regulations, company size, customer expectations, and how sensitive the information is.
None of this is new. These practices build on existing software development and security principles. Organizations don't need a new management philosophy to introduce AI responsibly. They need to apply established principles to a new technology.
Kevin's advice: get the fundamentals right first. Organizations that follow simple policies consistently prevent many avoidable problems and can build more sophisticated governance over time.
Managing Context in AI-Assisted Development
Rob raised another challenge: managing context.
AI tools can now work across entire repositories instead of single functions. Larger tasks need more information about the application's architecture, dependencies, requirements, and existing implementation. The question is how much the model actually needs.
Too little context leads to wrong assumptions. Too much drives up token usage, slows responses, and buries what matters.
Kevin says developers are experimenting with tools that trim unnecessary context and make information easier for AI to process. Some compress command-line output. Others organize repository information into structured knowledge representations. These techniques can cut token consumption and help AI focus on the relevant parts of a project. Kevin mentioned significant savings reported with combinations of context-management tools, though results depend on the tools and workloads.
The takeaway isn't that every developer should adopt a particular optimization framework. The technology changes too fast for any single tool to stay the obvious answer. Developers should understand how context affects AI performance and try approaches that improve efficiency.
Good Documentation Makes AI More Effective
Rob tied context management to something developers have talked about for decades: documentation.
Well-run software projects already have clear requirements, API definitions, architectural diagrams, and technical documentation. These let developers understand a system without reading every line of code. The same applies to AI.
When developers give AI accurate, structured information about an application, the AI spends less time figuring out how the system works and more time on the actual problem. Clear documentation cuts unnecessary context and makes responses more relevant.
Take an AI agent working on an API integration. It works better when the endpoints, request formats, authentication requirements, and error-handling rules sit in one place. Without that, it has to search multiple files or guess at the implementation.
That changes what documentation is for. It no longer serves only to onboard developers or maintain legacy systems. It's now part of the information infrastructure that supports AI-assisted development.
It still has to be accurate. Outdated or conflicting documentation misleads AI as easily as it confuses a human developer. The better the information we provide, the better the results.
Vibe Coding vs. AI-Assisted Software Engineering
One of the best parts of the interview covers the difference between vibe coding and professional AI-assisted development.
As AI coding tools improve, developers write less code by
Build Less, Validate More: Alane Boyd on Smarter AI Development
2026/10/15
Smarter AI development is not about using the most advanced tool or building the most complicated solution. As AI makes software development faster and more accessible, developers and business owners face a different challenge: deciding what is actually worth building. The ability to create something quickly does not eliminate the need to validate the idea, maintain the finished product, or determine where human judgment still matters.
In part two of our conversation with Alane Boyd, Co-CEO of Biggest Goal, Develpreneur: Building Better Developers explores what happens after a company moves beyond basic AI experimentation. Rob Broadhead and Michael Meloche talk with Alane about AI agents, vibe coding, custom software, minimum viable products, human oversight, and the growing temptation to build simply because AI makes building easier.
For developers building a career beyond the code, the lesson is especially relevant. AI has dramatically reduced the effort required to turn an idea into working software, but the business questions surrounding that software have not disappeared. In many cases, those questions have become even more important.
About Alane Boyd
Alane Boyd is Co-CEO of Biggest Goal and a serial entrepreneur whose background spans technology, operations, sales, marketing, automation, and business growth. She has built SaaS businesses and describes herself as a two-time SaaS founder with successful exits. Biggest Goal's current work focuses on hands-on AI training and implementation for leaders and teams, including helping organizations move from basic AI experimentation toward repeatable systems and practical business workflows.
Alane is also a published author, mentor, speaker, and podcast host. Her work increasingly focuses on practical AI fluency: helping businesses understand where AI belongs in their operations, how teams can use it consistently, and where human expertise should remain part of the process.
Learn more about Alane and her work through Biggest Goal and connect with her on LinkedIn.
Smarter AI Development Goes Beyond Chat
Many people still use AI primarily through a chat interface. They enter a prompt, receive an answer, copy the output somewhere else, and repeat the process. Alane sees organizations beginning to move beyond that model toward AI workflows, connectors, scheduled tasks, skills, and agents.
That progression can eliminate much of the manual movement between systems. Instead of repeatedly copying prompts and outputs, businesses can build processes that automatically trigger AI and move information where it needs to go.
At the same time, tools such as Claude Code have made development accessible to people who would not traditionally consider themselves developers. Alane sees value in that shift because people outside software development can finally see some of what happens behind the scenes when software is created.
However, creating an application is only one part of software development.
The excitement of building something can hide the long-term responsibility that follows. Someone still has to maintain the application, troubleshoot failures, adapt to changing requirements, manage dependencies, and determine what happens when the original creator no longer wants to spend time supporting it.
Michael sees the same issue when talking with people who have created applications using AI. They are excited because the application works, but they have not necessarily considered what comes next.
AI Makes Building Easier, Not Maintenance Optional
This creates one of the biggest challenges surrounding AI-assisted development. A founder can now describe an idea and begin creating software without fully understanding the lifecycle of the product being built.
The first version can feel almost magical. AI writes code, creates interfaces, troubleshoots problems, and helps someone move from an idea to something tangible much faster than traditional development allowed. That speed can create the impression that software has become a one-time project.
It has not.
Alane points out that maintaining what you build can become a significant burden. A founder who creates a custom platform may eventually discover that the software requires constant attention. What started as an exciting experiment can become another system the founder is personally responsible for keeping alive.
This is where smarter AI development requires thinking beyond the initial build. The important question is not simply, "Can AI build this?" It is also, "Do we want to own and maintain this after AI builds it?"
Build Versus Buy Still Matters
AI has made the traditional build-versus-buy decision even more interesting. If AI can create custom software faster and cheaper than before, building something yourself can look like the obvious choice.
Alane's experience suggests otherwise.
Before selling one of her previous companies, she merged with a competitor. Both companies had developed software, but one had built a SaaS product that customers could purchase while the other had proprietary software designed primarily for internal use.
When the combined company eventually evaluated those systems, the proprietary software was the first to be shut down.
The reason was business value. Internal proprietary software had limited marketability compared with a product customers were willing to purchase. The company had invested resources into creating and maintaining something that ultimately had little independent value during the sale process.
That experience shaped an important principle in Alane's approach: build what people want to buy.
For developers, that does not mean custom software is always the wrong decision. It means the ability to build something is not enough justification for building it. An existing platform may already solve the problem while another company absorbs the cost of maintenance, upgrades, security, and continued development.
AI changes the economics of building software, but it does not eliminate those considerations.
Validate the MVP Before You Keep Building
Developers like to build. That is one of the reasons many people become developers in the first place. Give a developer an interesting problem and enough time, and there will always be another feature worth adding.
AI can amplify that instinct.
Alane recommends returning to a familiar startup principle: the minimum viable product. Before investing heavily in development, determine the smallest version of the idea that can test whether somebody actually wants it.
That means asking practical questions early:
Will someone pay for this?
What is the smallest version we can put in front of a customer?
Which features are actually required?
Can we validate demand before investing more development time?
Are we solving a real customer problem or simply enjoying the build?
Alane acknowledges that she has fallen into the same trap herself. It is easy to believe a product needs every feature before customers can see it. The problem is that developers can spend months or even years creating something without discovering whether there is a viable market.
Time is a resource. A product that consumes a year of development without generating revenue may eventually become difficult to justify, regardless of how technically impressive it is.
Talk to Customers Before Building in a Vacuum
Alane references the early Dropbox story as an example of validating demand before completing a product. Rather than waiting until every part of the platform existed, Dropbox demonstrated the concept and gathered interest from people who wanted the solution.
The broader lesson is more important than the specific example. Developers and founders need feedback from potential customers before disappearing into build mode.
Friends and family are not necessarily enough. The useful feedback comes from people who might realistically use or purchase the product. Those conversations can expose incorrect assumptions long before they become expensive features.
AI makes this even more important because the barrier to building has dropped dramatically. When a new feature can be generated quickly, it becomes easy to keep adding functionality without stopping to ask whether anyone needs it.
Smarter AI development requires resisting that momentum. Build enough to learn, talk to users, and then decide what deserves to be built next.
Do Not Make the Solution Harder Than the Problem
Developers and founders also have a tendency to make solutions more complicated than necessary. AI gives us even more ways to do that.
A developer can open an AI coding tool, create custom logic, and continue refining an increasingly sophisticated solution. However, the same problem might be solved with a scheduled task, an AI skill, a simple automation, or an existing product.
Alane encourages teams to focus on the job that needs to get done rather than the technology they want to use. The question becomes: What is the quickest, cheapest, and easiest reliable way to accomplish the goal?
Sometimes that answer will be custom software. Sometimes it will be an AI agent. Other times, the answer may be a much simpler workflow.
That distinction matters because every custom solution creates ownership. Someone has to maintain it. Someone has to understand it when it breaks. Someone has to modify it when the business changes.
Smarter AI development includes knowing when not to develop something.
Keep Human Judgment in the Loop
One of the clearest guardrails Alane provides is that judgment should not be handed entirely to AI. AI can process information, identify patterns, generate options, and perform repetitive tasks, but Alane draws a distinction between havin
AI Is Not the Problem: Alane Boyd on Building an AI-Ready Organization
2026/10/13
Building an AI-ready organization requires more than giving employees access to ChatGPT, Claude, Copilot, or another AI platform. Without training, standards, and a clear understanding of where AI belongs, organizations can create more confusion and expense instead of improving productivity. The technology may be new, but many of the problems it exposes have been hiding inside businesses for years.
In this episode of Develpreneur: Building Better Developers, Rob Broadhead and Michael Meloche talk with Alane Boyd, Co-CEO of Biggest Goal, about what businesses are learning as they move beyond experimenting with AI. Alane has built and scaled technology companies, including two SaaS platforms and a social media agency. Today, much of her work focuses on helping organizations implement AI, train their teams, and create scalable systems that make work easier rather than simply adding another technology to the stack.
The conversation quickly reveals an important distinction. AI adoption is not really about purchasing AI tools. Building an AI-ready organization starts with understanding how work gets done and deciding where AI can genuinely improve that work.
About Alane Boyd
Alane Boyd is Co-CEO of Biggest Goal and a serial entrepreneur whose background spans technology, operations, sales, marketing, automation, and business growth. She has built SaaS businesses and describes herself as a two-time SaaS founder with successful exits. Biggest Goal's current work focuses on hands-on AI training and implementation for leaders and teams, including helping organizations move from basic AI experimentation toward repeatable systems and practical business workflows.
Alane is also a published author, mentor, speaker, and podcast host. Her work increasingly focuses on practical AI fluency: helping businesses understand where AI belongs in their operations, how teams can use it consistently, and where human expertise should remain part of the process.
Learn more about Alane and her work through Biggest Goal and connect with her on LinkedIn.
Moving Beyond AI Experimentation
For many people, the first experience with generative AI was simple experimentation. They opened a chat window, entered prompts, generated content, summarized documents, or tried whatever interesting use case appeared online. That experimentation helped people become comfortable with the technology, but organizations are now asking a more difficult question: How do we turn that experimentation into a repeatable business process?
Alane sees this transition with both individuals and organizations. Solopreneurs may want to move beyond basic prompting and learn how tools such as Claude Cowork can become part of their workflow. Larger organizations face another challenge because they need multiple employees to use AI consistently. They also need policies that prevent AI adoption from becoming what Alane describes as the "wild, wild west."
Many organizations already have employees using several different AI platforms. Those employees may be paying for separate subscriptions, developing their own prompting techniques, and solving similar problems without sharing what they have learned. Management eventually sees those subscriptions and begins asking what everyone is actually doing with them.
That is when AI stops being an individual productivity experiment and becomes an organizational challenge. It is also where the work of becoming an AI-ready organization really begins.
An AI-Ready Organization Needs Training
Michael shared an example that will probably sound familiar to many developers. One organization provided employees with AI development tools and effectively told them to use the technology to meet an aggressive deadline. There was no meaningful training, shared handbook, or established standard for how the tools should be used.
The AI helped the development team meet a deadline that likely would have been impossible otherwise. However, the lack of planning created another problem: consumption. Developers burned through available AI tokens quickly, forcing the organization to rethink how accounts and shared resources were allocated.
Alane has seen similar situations. One organization decided to skip training and purchase Claude subscriptions for its employees instead. Within days, employees exhausted their available usage and the company had to address the consequences.
The problem was not that the employees had access to AI. The problem was that nobody had taught them how to use it effectively.
Alane compares the situation to introducing any other workplace technology without establishing expectations. Give an organization Slack or Microsoft Teams without communication standards, and employees can quickly become overwhelmed with messages. AI follows the same pattern because employees naturally develop their own habits unless the organization provides guidance.
When Alane asks employees to share their screens and demonstrate how they use AI, she often discovers inefficient workflows that generate poor results while consuming unnecessary resources. Better tools do not automatically create better processes. Teams still need training.
Start with AI Champions
Organizations do not necessarily have to create an AI strategy from scratch. Alane recommends looking first at the people who are already experimenting with the technology.
Those employees can become AI champions. Instead of limiting AI adoption to the technology department, companies can create a cross-functional group of employees who already understand some of the possibilities. Representatives from sales, marketing, operations, development, and other departments can identify useful applications within their own areas while sharing what works across the organization.
This approach also helps companies address different comfort levels. Some employees naturally experiment with new technology and learn by trial and error. Others prefer structured instruction before changing how they work. Neither group represents an entire organization, so an implementation strategy needs to account for both.
Cross-department AI champions can help bridge that gap. They can demonstrate practical use cases, answer questions, and provide examples that are relevant to the work people actually perform. More importantly, they help an AI-ready organization develop shared practices instead of allowing every department to create its own isolated approach.
Not Every Task Needs AI
Another mistake is assuming that once an organization has AI, every task should involve it. Alane encourages companies to think carefully about where AI creates meaningful value.
Different teams also have different needs. Software developers may legitimately consume far more AI resources than employees performing other tasks because AI can dramatically accelerate certain areas of development. A content team, however, may not need the same allocation. In some cases, writing an email manually may actually be faster than prompting AI, reviewing its response, correcting it, and rewriting the result.
The goal is not maximum AI usage. The goal is better work. Organizations should ask where AI can handle repetitive processing, organize information, analyze transcripts, move data, or perform other behind-the-scenes tasks. They should also identify where human expertise still produces a better result.
That distinction matters because poorly implemented AI can actually increase costs. A company may purchase more subscriptions and consume more computing resources without gaining meaningful productivity. Training helps employees recognize which jobs are appropriate for AI and which jobs are better handled directly by a person.
AI Often Exposes Problems That Already Existed
One of Alane's most important observations during the conversation is that many problems blamed on AI existed long before AI arrived. Companies frequently struggle with inconsistent processes, missing documentation, scattered files, and employees completing the same task in completely different ways.
AI does not create those problems. It makes them much harder to ignore.
Alane sometimes begins working with an organization only to discover that the company does not even have a consistent shared folder structure. Before building sophisticated AI agents or automations, the organization may need to solve much more basic operational problems.
This creates an important lesson for developers and business leaders. Automation works best when the underlying process is understood. If nobody can explain how a process is supposed to work, automating it may simply make the confusion happen faster.
In that sense, AI can act as a diagnostic tool. Attempting to implement it forces organizations to ask questions they should have asked already. Where does information live? Who owns a process? What is the standard procedure? Which version of a document is authoritative? Where should a human review occur?
Those are not AI questions. They are business process questions, and answering them is an important part of creating an AI-ready organization.
AI-Ready Organization Foundations Come First
Some organizations simply are not ready for advanced AI implementation. Alane has encountered companies whose technology and processes were so outdated that Biggest Goal ultimately determined it was not the right partner for them yet.
That does not mean those companies can never use AI. It means they have foundational work to complete first.
An organization may need to establish shared storage, document its standard operating procedures, modernize parts of its technology stack, or determine how information moves between departments. Once those foundations exist, AI becomes much easier to introduce because there is a stable process to imp
Hard-Earned Business Lessons: Glenn Poulos on Selling, Scaling, and Knowing When to Change
2026/10/08
Success stories often sound much cleaner after the fact. Someone starts a company, grows it, sells it, and moves on to the next opportunity. What usually gets left out are the mistakes, difficult decisions, and moments when the business almost did not survive.
In Part 2 of our conversation with Glenn Poulos, we get into that side of entrepreneurship.
Glenn has started companies, sold companies, worked through an acquisition, nearly lost a business, rebuilt, sold again, and eventually became a buyer himself. That experience has given him a perspective you do not get from simply reading about entrepreneurship. Some of his most valuable lessons came from the deals and decisions that did not work as expected.
About Glenn Poulos
Glenn Poulos has spent more than four decades working in technical sales, entrepreneurship, and business leadership. After beginning his career in electronics, he entered technical sales in 1985 and founded his first technology distribution company in 1991. He later co-founded Gap Wireless, which grew into a major Canadian distributor serving the mobile broadband and wireless industries before being acquired in 2022.
Today, Glenn is President of ProgUSA, a U.S.-based company serving power utilities and service organizations with electrical test and measurement equipment, technical support, service, and calibration. He is also the author of Never Sit in the Lobby, which shares practical lessons from his career in sales and business.
Connect with Glenn on LinkedIn or learn more about his work through his website.
A Successful Exit That Wasn't So Successful
Glenn's first company was eventually approached by a well-known public company interested in acquiring the business. The offer looked impressive. Glenn and his partners would receive some cash, but most of the value came through millions of shares in the acquiring company. On paper, Glenn became a multimillionaire and one of the company's largest shareholders. There was one major problem. He could not immediately sell those shares.
Within roughly 18 months, the acquiring company went bankrupt, and the shares became worthless. Glenn had sold a valuable business but received nowhere near the value he expected from the transaction. That experience taught him a lesson that would influence future deals: the number written at the top of an acquisition agreement does not necessarily equal the money you will eventually receive.
It also taught him something about due diligence.
The buyer had thoroughly investigated Glenn's company, but Glenn and his partners had not done the same investigation of the buyer. Because it was a public company and a recognizable name, they assumed that was enough. It wasn't.
Due Diligence Goes Both Ways
This is an important lesson for developers, consultants, and founders because we often focus on proving ourselves. A potential employer interviews us. A client evaluates our proposal. An investor examines the company. An acquiring company reviews the books. But evaluation should work in both directions. Glenn later realized that more investigation might have uncovered warning signs within the company acquiring his first business. That experience changed how he approached future transactions.
The same principle applies outside acquisitions. Before accepting a major client, investor, partner, or even a new job, ask what you need to know about the other side of the relationship. A recognizable name does not eliminate risk.
Growth Can Take You Away From What You Do Best
Glenn's next company eventually became highly successful, but getting there was not a straight line. By 2019, the business was in serious trouble. Part of the problem was expansion. The company knew how to buy technology from manufacturers and sell it to customers. Because they were successful at that, it became easy to assume they could move into adjacent businesses. Why not install the technology too? Why not expand into another product category?
Those ideas sound reasonable until the new business requires completely different expertise, employees, equipment, inventory, and risk management. Glenn calls what happened the "reverse Midas touch." Instead of everything turning to gold, new ventures began creating problems. The company eventually found itself about $1.3 million in the hole. The solution required difficult decisions.
Glenn and his partner dramatically reduced the size of the organization, transferred a problematic service division, exited another difficult product area, and refocused on the company's core strengths. Those decisions helped turn the business around and ultimately positioned it for a successful sale. There is a valuable lesson here for technical professionals. Being good at one thing does not automatically mean you will be good at the thing next to it. Expansion needs more than opportunity. It needs the right expertise and someone capable of owning it.
Be Careful With the Money Attached to Growth
Another theme in our conversation was financing.
Glenn is careful to point out that his experience comes primarily from running traditional operating businesses rather than venture-backed startups. Within that context, he prefers avoiding outside money for as long as practical. Debt has a cost. Equity has a cost. Partners have a cost. Those costs are not always measured only in interest rates or percentages.
Taking an investor may mean giving someone influence over how the company operates. Bringing in a partner means sharing the value you eventually create. An earn-out may make an acquisition price look larger, but some of that money depends on hitting future targets after control of the company has changed.
Glenn's experience has made him particularly cautious about large earn-outs and long post-acquisition commitments.
Choose Partners for More Than Proximity
Glenn also offered a warning about business partnerships through something he jokingly calls "vice president in the room syndrome." A few friends start talking about creating a company. Someone becomes CEO. Someone else becomes VP of Technology. Another person gets sales. Someone else happens to be there, so they get a title too. The company has barely started, but ownership and leadership positions have already been distributed based on who was in the room rather than what the business actually needs.
That can become extremely expensive later.
Glenn has successfully worked with partners, so his point is not that partnerships cannot work. It is that ownership decisions made casually at the beginning become very difficult to undo once the company has real value.
Experience Is Often Learning What Not to Do
One thing I appreciated about Glenn's story is that the lessons do not come from pretending every decision was correct. Some worked. Some didn't.
His first company taught him how dangerous an acquisition can become when you fail to investigate the buyer. His second taught him how quickly expansion outside your core strengths can consume a profitable business. Selling to private equity taught him about earn-outs and what happens when you are no longer the person controlling a company you built.
Those lessons eventually influenced how he approached buying and running his current business.
For developers building a career beyond the code, that may be the most useful takeaway. Entrepreneurship is not simply about having a good idea or building a product. It requires understanding money, people, partnerships, risk, operations, and sometimes knowing when to stop doing something that is not working.
The technical problem may actually be the easy part.
Stay Connected: Join the Developreneur Community
👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development.
Additional Resources
Business Agreements – Lessons Learned
Learning From Your First Business
Strategies for a Successful Business Launch
Building Better Developers Podcast Videos – With Bonus Content
Build a Business Beyond the Code: Glenn Poulos on Buying, Building, and Using AI
2026/10/06
Building a career beyond the code does not necessarily mean leaving technology behind. Sometimes it means learning how to take technical knowledge and apply it differently. That might involve sales, leadership, consulting, or eventually building a company of your own.
In this episode of Develpreneur, we talk with Glenn Poulos, an entrepreneur who started his career as an electronic technician before moving into technical sales. That transition eventually led him to start, grow, and sell multiple technology distribution companies. More recently, Glenn took a different approach: instead of starting another company from scratch, he bought an existing business.
His experience provides an interesting lesson for developers and technical professionals considering entrepreneurship. The biggest opportunity may not always be building something new. Sometimes it is finding something that already works and figuring out how to make it better.
About Glenn Poulos
Glenn Poulos has spent more than four decades working in technical sales, entrepreneurship, and business leadership. After beginning his career in electronics, he entered technical sales in 1985 and founded his first technology distribution company in 1991. He later co-founded Gap Wireless, which grew into a major Canadian distributor serving the mobile broadband and wireless industries before being acquired in 2022.
Today, Glenn is President of ProgUSA, a U.S.-based company serving power utilities and service organizations with electrical test and measurement equipment, technical support, service, and calibration. He is also the author of Never Sit in the Lobby, which shares practical lessons from his career in sales and business.
Connect with Glenn on LinkedIn or learn more about his work through his website.
From Technical Skills to Sales and Entrepreneurship
Glenn began his career working with electronics, including repairing equipment used at Canadian weather stations. He soon discovered that the role was not what he wanted long-term, and his boss suggested that he consider sales.
That advice changed the direction of his career.
Glenn moved into technical sales in 1985, selling test and measurement equipment used by engineers. Because he understood the technology, he could speak the customer's language while learning the business side of the industry.
He eventually realized something important: sales could dramatically expand his earning potential without requiring him to abandon his technical background. A few years later, he saw another opportunity. Instead of simply selling products for someone else's company, he could build the company employing the salespeople.
In 1991, Glenn left his job and launched his first business focused on technology for the growing mobile wireless market. He would spend the next several decades building businesses around a similar model: find useful technology, understand the market, and connect those products with customers who need them.
For developers, there is an important lesson here. Your technical skills can be the foundation of your career without defining its boundaries.
Starting a Business Versus Buying One
After starting companies from scratch more than once, Glenn eventually decided he would take a different approach.
He bought an existing business.
The experience showed him how much infrastructure entrepreneurs have to recreate every time they start from zero. A new company needs banking relationships, insurance, employees, vendors, customers, processes, credit, and a reputation. An established company may already have many of those pieces.
That does not mean buying a company eliminates the work. Glenn changed much of the business he acquired, including its branding, systems, vendors, staffing, and processes. He also had to manage something founders do not encounter in quite the same way: an existing culture and employees dealing with significant change.
Still, he started with an engine that was already running.
Glenn believes there is an overlooked opportunity in smaller established businesses whose owners are ready to retire but do not have someone prepared to take over. In some cases, a new entrepreneur may be able to structure a transition in which the existing business helps finance the owner's eventual exit.
Instead of spending years creating everything from scratch, the entrepreneur can focus on improving what already exists.
AI Changes What a Small Business Can Do
The other major change Glenn has experienced is AI.
When he acquired his current company in 2024, AI was already becoming useful. In only a few years, however, it has changed how he operates the business.
Glenn described using AI across financial reporting, accounts receivable, marketing, planning, sales training, and internal tools. Rather than hiring full-time employees for every specialized role, he can combine fractional experts with AI-supported processes.
The important distinction is that AI is not running the company.
People still make decisions, review information, manage relationships, and provide judgment. AI increases what those people can accomplish.
Glenn gave a simple example with trade shows. Coordinating a trade show means tracking booth reservations, travel, hotels, equipment, marketing materials, deadlines, and dozens of other details. Instead of buying another software package, Glenn had AI help him build a tool specifically around his company's process.
He has created enough internal tools that he eventually needed another tool simply to keep track of them.
That is both funny and revealing.
AI removes many of the old barriers to creating software, automating processes, and increasing productivity. The new challenge is deciding which problems are worth solving and making sure we finish what we start.
The Opportunity Beyond the Technical Work
One thing that stood out in our conversation with Glenn is that none of these transitions required abandoning technology. His technical background remained useful throughout his career. What changed was how he applied it.
He learned sales. He learned how businesses operate. He learned how to build companies, manage people, work with vendors, and eventually evaluate an existing company as an acquisition.
Now he is adding AI to that toolkit.
That is exactly what building a career beyond the code can look like. The technical skills get you started, but the opportunities become much larger when you combine them with communication, business knowledge, sales, leadership, and the ability to recognize a problem worth solving.
You do not necessarily need to build the next startup from nothing. There may already be a good business, product, or process waiting for someone with the right technical experience to see what it could become.
Stay Connected: Join the Developreneur Community
👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development.
Additional Resources
Building Trust in the AI Era | Amit Zandberg
Can AI Help You Trust Online Course Reviews? | Amit Zandberg
The Entrepreneurial Mindset: Moving From Side Hustle to Company
Building Better Developers Podcast Videos – With Bonus Content
Developer Burnout and Work-Life Balance: Stop Bringing the Problem Home
2026/10/01
Developer work-life balance is often treated as a productivity problem. We look for better schedules, better tools, fewer meetings, or another technique for getting more done. However, our second conversation with Gaylen A. Wilson raises a different question: what happens when the problem is not how much work you have, but your inability to stop working the problem?
Developers spend their careers learning how to stay with difficult problems. We debug issues that make no sense, work through production failures, deal with changing requirements, and keep digging until we find an answer. That persistence can make us successful. It can also make it difficult to recognize when we have crossed from productive problem-solving into stress, frustration, and burnout.
The challenge becomes even greater when we carry that state away from the computer. Work may have ended, but mentally, we are still debugging. Learning to recognize that transition is an important part of developer work-life balance.
About Gaylen A. Wilson
Gaylen A. Wilson is an author, relationship coach, technology veteran, entrepreneur, farmer, former stockbroker, and heart-transplant recipient whose career has required him to reinvent himself repeatedly. Together with his wife, Heather, Gaylen developed the Monument Method, an approach they use to help couples interrupt destructive conflict patterns and strengthen their connection.
Learn more about Gaylen A. Wilson through his website http://www.monumentmethodinstitute.com/.
Developer Work-Life Balance Starts with Recognizing Your State
Michael brought the conversation back to developers by pointing out something familiar to many people in technology. We can become so accustomed to constantly working the problem that we stop recognizing what it is doing to us.
There is always another release, bug, customer issue, deadline, or technology to learn. We keep pushing because that is what has worked throughout our careers. Eventually, though, we can reach a point where we are no longer solving the problem effectively. We are simply reacting to it.
Gaylen connected that experience to what he describes as fight-or-flight thinking. He had experienced an extreme version during his health problems. As a self-described Type A personality, one of the hardest things for him was accepting that he still wanted to keep going while his body was telling him that he could not. He credited his relationship with his wife, Heather, as an important source of support during that period.
You do not need to reach that extreme before recognizing the same pattern in your career. Sometimes the warning sign is much simpler. You close the laptop, but you are still thinking about the defect. You sit down for dinner and mentally replay a conversation from work. You are supposed to be relaxing, but you feel guilty because you are not doing something productive.
The workday ended. Your brain never got the message.
The Car That Would Not Start
Gaylen shared a story that provides a surprisingly good example of what this looks like.
He had spent two months working on one of his cars and finally got it running. After driving it around the block, he and Heather prepared to leave and visit friends. He pushed the button to start the car, and nothing happened.
For someone who likes solving problems, that was frustrating enough. Gaylen also felt that he was disappointing Heather because they were supposed to leave. He grabbed a multimeter, found the battery was low, and started looking for jumper cables.
He could not find them.
They were actually nearby, underneath a blanket, but Gaylen had become so frustrated that he could not slow down enough to move the blanket and see them. By his description, he had entered full fight-or-flight mode. He found another old set of jumper cables, discovered they were badly corroded, and became even more frustrated.
Developers have our own versions of that blanket.
You have probably stared at a defect for an hour only to discover the problem was obvious once you stepped away. Maybe you rewrote code that did not need rewriting. Maybe you blamed a dependency, the network, the database, or someone else's code before discovering a simple configuration problem.
The longer we fight the problem, the narrower our thinking can become. At some point, persistence stops being an advantage.
Developer Work-Life Balance Requires an Interrupt
The most interesting part of Gaylen's story came next. Heather was sitting in the car and did not realize how frustrated he had become. Gaylen finally walked over to her and said, "I need a monument."
That phrase comes from the relationship framework Gaylen and Heather developed, which they call the Monument Method. They use "monument" as an agreed-upon signal to interrupt an escalating conflict or emotional reaction and reconnect before continuing.
Gaylen said that when Heather turned toward him, his anger quickly disappeared. He then gave her permission to use the same technique whenever she saw him beginning to spiral in the future.
Whether or not you use Gaylen's specific method, there is a useful concept here for developers: we need an interrupt.
In programming, an infinite loop does not usually fix itself because we let it run longer. Sometimes something external has to break the cycle. Our work habits can operate the same way.
Build an Interrupt into Your System
Developers love systems, so it can help to think about disconnecting from work as something we deliberately design rather than something we hope happens automatically.
Your interrupt does not have to be Gaylen's "monument." It can be something simple that signals the transition from work mode to the rest of your life.
Take a walk after shutting down your computer.
Write down the next step before leaving a difficult problem.
Create a short end-of-day routine that closes out unfinished work.
Exercise before transitioning into your evening.
Set a fixed point when you stop checking Slack, Teams, or email.
Talk with someone rather than continuing to replay the problem internally.
Step away from a frustrating problem before making another major change.
The specific ritual matters less than recognizing why you need it. If you regularly leave work in a frustrated state, simply closing the laptop does not necessarily reset that state. You may physically leave the work while mentally carrying it into everything you do afterward.
That affects more than your evening. It can affect how you communicate with the people around you and how prepared you are to return to work the next day.
You Cannot Debug Everything by Working Harder
Michael asked Gaylen an important follow-up question: what if you do not have someone there to help you reset?
Gaylen described an experience while Heather was away visiting family. He had become frustrated while working with ChatGPT and realized that Heather would normally recognize when he was becoming agitated. Without her there, he experimented with mentally recreating the calming experience they had practiced together.
He said that simply closing his eyes and imagining the familiar interaction helped him calm down. Gaylen attributed that response to repeatedly practicing their method until it had become a familiar signal for him to reset.
The larger lesson is not that developers need to reproduce Gaylen's exact technique. It is that we can become better at recognizing when our current state is no longer helping us solve the problem.
When you have been staring at the same code for three hours, are you still debugging effectively? When you are angry at a tool because it is not behaving the way you expect, are you still evaluating the problem objectively? When you are rewriting something for the third time late at night, are you improving it, or are you just unwilling to stop?
Developers spend enormous amounts of time learning how to diagnose systems. We should learn to diagnose ourselves, too.
Find Your North Star
Rob connected Gaylen's Monument Method to something we regularly discuss in software projects and businesses: having a "why."
Projects need a reason for existing. Without that reason, teams can spend enormous amounts of energy building things that do not actually move them toward their goal. A clear purpose becomes a North Star. When the project begins drifting, the team can return to the original question: what are we actually trying to accomplish?
Developers can apply that idea to our careers. Why are you working so hard? Why are you pursuing the promotion? Why are you building the business? Why are you learning another technology? Why are you putting in the extra hours?
There may be excellent answers to all of those questions. The danger comes when the work becomes its own answer.
Developer Work-Life Balance Requires Boundaries
There is a strange contradiction in successful technology careers. We work hard because we want to build a better life, but the habits that help us succeed can gradually consume the life we were trying to build.
Gaylen argued that professional success, money, and recognition lose much of their meaning if they come at the expense of the important relationships around us. Rob connected that back to the larger theme of Career Beyond the Code: career success needs a reason behind it. Simply pursuing more work, more money, or more achievement does not provide a natural stopping point.
That is why developer work-life balance cannot be solved entirely with productivity hacks. Sometimes you need to recognize that enough is enough.
The defect can wait until tomorrow. The email does not need an answer tonight. You do not have to understand every new AI tool this weekend. The side project does not have to become
Podcast reviews
Read Develpreneur: Become a Better Developer and Entrepreneur podcast reviews
SimplyShaunnaLee 2024/04/19
Such a great conversation!
Rob was a gracious host and I appreciated the change to discuss one of my favorite topics - Self Care - and how it can help make us better business ow...
We all love sudoku 2023/10/13
More than I was looking for
I originally was looking for a podcast to help me be a better developer as I'm new to the field. This podcast is so much more and has expanded how I t...
Cesarfelip3 2023/10/02
Great show!
develpreneur masterfully intersects the realms of software development and entrepreneurship. With its deep dives into both tech nuances and business ...
DonInSF 2023/04/26
Good use of my time!
Relevant topics for todays tech entrepreneur. Highly recommended!
gte164u 2023/02/14
Thought provoking podcast!
Rob asks his guests incredibly thought provoking questions that really get you thinking about all facets of your own business. I highly recommend Deve...
Label Free Podcast 2023/01/23
Very thorough!
Rob’s approach with his guest is very thorough. He makes sure he covers all bases and brings ultimate value to his audience.
jasoncercone 2022/12/07
Great Content and Conversations!
Rob does a great job featuring insightful guests and having engaging conversations from start to finish. If you’re an aspiring developer or entreprene...
ASobering 2022/11/03
Such a wealth of knowledge! 🧠
Whether you’re well established in the world of software development, or just getting started in your career, this is a must-listen podcast for you! R...
Spinner721 2022/09/19
Rob’s great!
He’s a former IT pro that understand the engineering brains we have. Great thoughtful questions.
canoeten 2021/09/07
A developer with ideas and info worth hearing about.
Rob’s got a great point of view about what it takes to be a successful developer in this age of omnipresent social media, crazy schedules and specs, a...
Podcast sponsorship advertising
Start advertising on Develpreneur: Become a Better Developer and Entrepreneur relevant audience podcasts
You may also like to advertise on these Podcasts

4.6620172000
The Dan Bongino Show
Cumulus Podcast Network | Dan Bongino

4.98711800
The Adam Mockler Show
MeidasTouch Network

4.824781904
Deck The Hallmark
Bramble Jam Podcast Network

4.916171639
The Kristian Harloff Show
Kristian Harloff

4.847132000
Pat Gray Unleashed
Blaze Podcast Network

4.713452000
The NewsWorthy
Erica Mandy

4.7368531302
Louder with Crowder
Louder with Crowder

4.84326906
The Liz Wheeler Show
Blaze Podcast Network

4.8104542000
Steve Deace Show
Blaze Podcast Network

4.813282012
The Jeff Cameron Show ~ Warchant.com
Jeff Cameron Show

