Develpreneur: Become a Better Developer and Entrepreneur

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

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 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 another full-time job. The people around you should not always receive whatever energy remains after work takes the best of you. Those are not failures of ambition. They are boundaries that can make a long career possible. Quality Includes the Life Around the Product At EnvisionQA, we talk about finding problems before customers do. That mindset usually applies to software quality, requirements, integrations, processes, and the technology supporting a business. However, quality is also about sustainability. A development process that only succeeds because someone works eighty hours is not a healthy process. A release that depends on heroics every time has a system problem. A developer who cannot disconnect from work indefinitely will eventually pay for that somewhere. Building better developers should mean more than producing developers who can write better code. It should mean developing people who can solve difficult problems without allowing every difficult problem to consume them. That is part of building a career beyond the code. Developer Work-Life Balance Means Knowing When to Stop One of Gaylen's final reflections brought both parts of our conversation together. Looking back over a life filled with career changes, financial setbacks, addiction, serious illness, and a heart transplant, he asked himself why those experiences had not left him bitter. His answer was gratitude. Gaylen said he realized that he had generally been more grateful for what he still had than bitter about what he had lost. Today, he practices that gratitude more intentionally. For developers, perhaps there is another lesson in that perspective. We are trained to see what is broken. It is literally part of the job. We find the missing requirement, failed test, security vulnerability, performance bottleneck, integration problem, or defect that everyone else missed. That skill makes us valuable, but we cannot spend our entire lives looking only for the next thing that needs fixing. Sometimes building a career beyond the code means recognizing what is already working, protecting the things that matter, and knowing when to walk away from the keyboard. The problem will still be there tomorrow. You will probably solve it better after the reset. About Gaylen A. Wilson Gaylen A. Wilson is an author, relationship coach, technology veteran, entrepreneur, former farmer and stockbroker, and heart-transplant recipient. His professional life has included multiple reinventions, from agriculture and finance to PeopleSoft consulting, computer repair, nationwide technical field work, writing, and relationship coaching. Together with his wife, Heather, Gaylen developed the Monument Method, a relationship framework centered on interrupting destructive conflict patterns and protecting the connection between partners. Their work grew from their own relationship, Gaylen's health journey, his involvement in large online communities discussing intimacy and relationship challenges, and their subsequent relationship-coaching education. Gaylen described his broader philosophy during our conversation as intentionally protecting what matters most rather than allowing the pressures of work and the outside world to damage it. You can learn more about Gaylen, his books, and his work through his PodMatch profile and the Monument Method Institute. 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 Constructive Communication in Software Development That Drives Results Facilitative Leadership: Why Modern Teams Need Guides Instead of Heroes Software Communication Gaps: The Hidden Foundation Problem Slowing Your Team Building Better Developers Podcast Videos – With Bonus Content

Career reinvention for developers is usually discussed in terms of learning a new language, moving into leadership, adapting to AI, or finding a new job. Our conversation with Gaylen A. Wilson takes that idea much further. His story shows what happens when careers, businesses, health, and even our assumptions about the future stop following the plan. Season 29 of Building Better Developers is about building a career beyond the code. Usually, that leads us into conversations about leadership, communication, business value, quality, or the skills developers need as they move beyond completing technical tasks. This episode is different. We did not spend much of the first half talking about software development or QA. Instead, Gaylen told us his story, and the longer he talked, the clearer the connection to developers became. Gaylen's career repeatedly forced him to confront something most developers eventually discover for themselves: you can master the tools, solve complicated problems, and work incredibly hard, but none of that guarantees life will follow the architecture you designed. His story is ultimately about rebuilding when the plan fails, which makes it an unexpected but valuable example of career reinvention for developers. 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/. Your Career Is Not a Straight Line Gaylen started his professional life far away from software. He became a farmer in his twenties and built a life around agriculture. Then drought and crop failures destroyed the business, eventually forcing him into farm bankruptcy. He had to reinvent himself. His next chapter took him into finance as a stockbroker. He succeeded there until a company whose investment he had recommended collapsed after, according to Gaylen, misrepresenting its financial condition. He described that experience as another devastating setback. Without healthy ways to process what had happened, his personal life also began to unravel. Eventually, Gaylen rebuilt again. In 2001, he found work as a traveling PeopleSoft computer consultant. He was earning more than he ever had before and thought he had finally reached a stable point in his career. Then September 11 changed the economy and consulting industry around him. By December, he had lost that job. After months of searching and hundreds of mailed résumés, he eventually took a job as a Walmart cashier because he needed to work. For developers, there is an important lesson in that progression. We often build our identity around what we do. We become the Java developer, QA engineer, architect, DevOps specialist, technical lead, or whatever role currently defines our career. Then the technology changes, the company restructures, a project ends, AI changes part of the workflow, or the market simply decides that yesterday's valuable skill is commonplace today. The ability to rebuild can matter more than the title you are trying to protect. Career Reinvention for Developers Starts with Transferable Skills One interesting part of Gaylen's story is how often skills from one chapter became useful in the next. Farming did not look anything like stockbroking, and stockbroking did not look much like technology consulting. Yet farming had already taught him far more about running a business than people might assume. When the consulting market disappeared, Gaylen eventually returned to his hometown and put a small advertisement in the newspaper offering computer repair. He had never worked professionally as a computer repair technician. He had simply been interested in computers for years. Within six months, that small side business was outperforming his Walmart job. Then the market changed again. As Windows became more reliable and malware-related repair work declined, the computer repair business that had supported Gaylen and his wife, Heather, began drying up. Instead of assuming the old business would somehow return, he adapted. He found platforms connecting technicians with companies needing field work and began traveling throughout rural America installing and servicing technology. Eventually, that work took Gaylen and Heather through all 48 contiguous states. That is where this story starts to sound much more familiar to a developer. Technologies disappear. Frameworks fall out of favor. Companies reorganize. Entire categories of work become automated. A skill that was valuable five years ago can become commonplace today. Career reinvention for developers becomes easier when we stop defining ourselves by a particular technology and start recognizing the skills that survive those changes. Those transferable skills include: Problem-solving and troubleshooting Learning unfamiliar systems quickly Breaking complicated problems into manageable pieces Communicating with customers and stakeholders Testing assumptions instead of blindly following them Adapting when the original solution no longer works Understanding the business problem behind the technology Those are skills that remain valuable even when the code changes. Developers Are Professional Problem Solvers There is another reason Gaylen's story belongs in a developer-focused season. Developers tend to be fixers. Give us a broken system, and we immediately start looking for the defect. We gather information, isolate variables, test assumptions, and keep working until we understand the problem. That mindset is incredibly valuable. It can also become dangerous when we start treating every problem as something we can overcome simply by working harder. Michael touched on this at the beginning of the episode while discussing the difficulty of slowing down after a period of long releases and extreme work hours. Even after the immediate pressure disappeared, there was still that feeling that he should be doing something. Rob connected that experience to the larger conversation about how quickly technology is moving and how easily careers can consume the rest of our lives. Many developers know that feeling. There is always another ticket, certification, framework, side project, production issue, release, or AI tool to learn. We tell ourselves things will calm down after the current deadline. Then another deadline appears. Gaylen eventually encountered a problem he could not outwork. When Working Harder Stops Being the Solution In 2014, after years of traveling for technical work, Gaylen became seriously ill. He initially believed he had pneumonia and continued working. During another extended trip, his condition worsened until a clinic in Corpus Christi sent him for a chest X-ray. He was told he had congestive heart failure and needed to return to Colorado. His first reaction is revealing. The jobs were paying well. They already had weeks of work scheduled. Gaylen initially thought they should finish the trip before dealing with his heart. It took two more jobs before the seriousness of the situation finally broke through his drive to keep working. That moment is an extreme example of a pattern many developers experience in smaller ways. We know we need sleep, but the release needs to go out. We know we need a weekend away from the computer, but production has a problem. We know we have not spent enough time with the people around us, but there is one more thing we need to finish. The problem-solving mindset becomes a trap when the answer to every problem is simply more effort. There are times when the correct solution is to stop. What Are You Actually Building? Gaylen eventually received a heart transplant in 2018. He described being near the point where he and Heather were preparing for the possibility that he would die when they received the call that a donor heart was available. By the next morning, Gaylen had received a new heart. He viewed the transplant as an opportunity to have more years with the person who had stayed beside him throughout his illness. That experience changed what success meant to him. It also gives developers a useful question to ask about our own careers: What are we actually building? We spend our days building systems for other people. We think about architecture, scalability, reliability, technical debt, requirements, and defects. Yet we do not always apply the same intentional thinking to the systems surrounding our careers. A successful career should support a life rather than consume it. That does not mean ambition is wrong. It does not mean developers should stop working hard or stop pursuing difficult goals. It means the career itself should serve something larger. Otherwise, we can become incredibly efficient at building a future we eventually discover we did not want. Quality Applies Beyond Software At EnvisionQA, we spend a lot of time thinking about quality and finding problems before customers encounter them. One lesson from this conversation is that the same mindset can extend beyond software. In software, we do not wait for catastrophic failure if we can avoid it. We monitor systems. We test assumptions. We look for warning signs. We examine recurring defects because they often point toward deeper problems. Our careers deserve similar attention. If every release requires heroics, something may be wrong with the process. If every week requires sixty or eighty hours, the workload may not be sustainable. If you cannot stop thinking about work when you leave the computer, that is information worth examining. If professional success consistently comes at the expense of health or important relationships, simply becoming more productive may not solve the underlying problem. Sometimes the system itself needs redesigning. Career Reinvention for Developers Is About More Than Technology Gaylen's journey moved from farming to finance, technology consulting, computer repair, nationwide field service, serious illness, a heart transplant, and eventually relationship coaching. That is hardly a traditional developer career path, but that is precisely why this conversation fits our season. Careers rarely follow the architecture diagram we created when we started them. Technologies change. Businesses disappear. Markets collapse. Health changes. Priorities change. Sometimes we make mistakes, and sometimes circumstances outside our control rewrite the requirements completely. The developers who build lasting careers are not necessarily the ones who perfectly predict what comes next. They are the ones who learn, adapt, rebuild, and carry lessons from one chapter into the next. That is ultimately what career reinvention for developers is about. Most importantly, the career is not the final product. The life you are building around it is. In Part Two of our conversation with Gaylen A. Wilson, we bring his experiences more directly back to developers, burnout, fight-or-flight thinking, relationships, and the challenge of leaving work at work. We also explore what happens when the same problem-solving mindset that makes us effective developers follows us home. 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 Customer Feedback for Developers: How to Listen Without Losing Your Vision Developer Career Growth: Breaking Through Stagnation Building Better Developers Podcast Videos – With Bonus Content

AI communication skills are becoming increasingly important as developers and leaders rely on artificial intelligence to summarize meetings, draft emails, organize ideas, and prepare for conversations. These tools can save time, but Salvatore Manzi warns that using AI to improve your communication is different from letting AI do your communicating for you. In Part 2 of our Develpreneur conversation with leadership communication coach Salvatore Manzi, Rob Broadhead and Michael Meloche explore how communication changes as developers move into leadership roles and AI becomes part of everyday work. The discussion covers better meetings, keeping remote teams engaged, using AI without weakening your skills, and communicating technical ideas to people outside your technical world. About Salvatore Manzi Salvatore Manzi is a leadership communication coach whose work sits at the intersection of leadership, communication, and collaboration. He works with teams and analytical professionals to improve how they communicate so they can collaborate more effectively and move their ideas forward. Salvatore is also the author of Clear and Compelling: Communication Strategies for Big Thinkers. During the Develpreneur interview, he explained that the book draws on twenty years of communication strategies and is aimed particularly at analytical, technology, and data-driven professionals with bold ideas. His work fits closely with the theme of this season of Develpreneur: building a career beyond the code. Technical knowledge can help you develop the idea, but leadership communication helps you explain it, build support for it, and bring other people along with you. Social: Facebook / YouTube / Instagram / LinkedIn Website: Salvatore Manzi's Website AI Communication Skills Need Structure Without Becoming Rigid Developers tend to appreciate systems, but nobody wants every conversation governed by a complicated set of rules. That creates an interesting challenge for leaders: How much structure does a team actually need? Salvatore describes communication as an art rather than something with a perfect formula. However, he also points out that people need parameters. We need to understand the limits before we know how much freedom we have within them. In a meeting, those limits might involve time, the topic being discussed, or how long each person should speak. The key is keeping those parameters flexible. Telling someone they can speak exactly seven words creates a new problem because everyone becomes focused on satisfying the rule. Asking people to keep their responses to one or two sentences establishes a useful boundary without turning the meeting into an exercise in compliance. This same principle applies throughout leadership. Structure should help people communicate rather than becoming another obstacle they have to navigate. Better Communication Starts With the Purpose of the Meeting Many developers have experienced days where one meeting runs into another until there is almost no time left to do the work discussed in those meetings. The problem is not necessarily whether a meeting lasts fifteen minutes, thirty minutes, or an hour. Salvatore recommends starting with a more fundamental question: What is this meeting supposed to accomplish? Without a clear objective, a meeting can continue indefinitely without producing a useful result. When people understand the goal and receive the information they need beforehand, however, some discussions can be resolved in five or fifteen minutes. That changes the way we think about meeting efficiency. Instead of automatically scheduling an hour and trying to fill it, define the outcome first. Then determine how much time the team actually needs to achieve it. AI Communication Skills Require Human Engagement AI has added another dimension to the meeting problem. We can now record conversations, generate transcripts, create summaries, identify action items, and return to the information later. Those capabilities are useful, but they can also create an excuse to disengage. Michael raised a scenario that is becoming increasingly familiar: people attend a meeting with their cameras off, barely participate, and depend on an AI-generated transcript or summary to tell them what happened afterward. Salvatore argues that leaders have a responsibility to create engagement. His recommendation is the 3-5 rule: every three to five minutes, introduce some type of pattern disruption that brings people's attention back into the conversation. That disruption does not need to be dramatic. A leader can: Ask a question. Poll the group. Ask someone for their perspective. Introduce an interactive visual. Connect the discussion directly to someone's current work. Change the way information is being presented. One of the most effective approaches is relevance. If you connect a discussion directly to a project someone is working on, that person's attention naturally increases. Instead of simply delivering information to a group, you are showing people why that information matters to them. That may become even more important as AI makes passive participation easier. Communication Skills Matter Even Without a Leadership Title What happens when you recognize that a meeting is failing but you are not the person running it? That is a common situation for developers. You may be sitting in a retrospective, refinement, stand-up, or project meeting where two or three people dominate the conversation while everyone else remains silent. Salvatore suggests that participants can help create engagement without taking over the meeting. One approach is to respond directly to something another person shared. You might briefly explain what you appreciated about their contribution and how it connects to the work. If the meeting consistently prevents important voices from being heard, that can also become a conversation with the facilitator before the next meeting. Explain what you need from the discussion and why hearing from more of the team matters to your ability to move forward. This approach changes the interaction from criticism to a request. You are not simply saying that the meeting is bad. You are explaining what would make it more useful and why that change matters. Better Team Communication Permits People to Challenge Ideas Another problem appears when people have concerns but do not want to become known as the person who is always negative. Salvatore described working with a startup that deliberately assigned roles such as the critic, negator, or contrarian during meetings. The roles rotated between people, which gave someone explicit permission to challenge an idea without being personally labeled as difficult. Over time, something interesting happened. Team members reported feeling safer raising uncomfortable issues even when they were not officially assigned one of those roles. For software teams, this concept has obvious applications. Projects need people willing to ask what happens when something fails. Testers need to challenge assumptions. Developers need to question architecture. Business analysts need to identify missing requirements. Security teams need to think about how a system could be abused. The goal is not negativity. The goal is making constructive disagreement part of the process instead of treating disagreement as a personality problem. Communication Skills Help Make Complex Ideas Easier to Process Technical experts often struggle with another communication problem: we know too much. When someone asks about a system we have spent months or years building, it is tempting to provide all the history, context, data, dependencies, and edge cases necessary to prove that we understand the problem. The listener probably does not need all of it. Salvatore recommends narrowing information into a small number of meaningful chunks. The underlying data still matters, but effective communication requires deciding which pieces another person needs to understand before moving forward. That skill becomes increasingly important as developers move into leadership. Executives, customers, operations, marketing, legal, and other departments usually do not need the same technical depth that another developer needs. The challenge is not knowing the information. It is knowing which information matters to the person in front of you. Do Not Let AI Communication Replace Your Own Voice This is where AI communication skills become particularly important. AI can summarize a long email chain, draft a response, prepare meeting notes, and transform rough ideas into polished language. Salvatore sees value in those capabilities, but he also sees a risk when AI begins communicating back and forth while the people involved stop thinking for themselves. Eventually, an email conversation becomes a real conversation. At that point, you have to explain the ideas that supposedly came from you. You have to answer questions in real time, adapt to new information, defend decisions, and respond to a dynamic situation. If AI has been doing all of the thinking and communicating for you, you may discover that you are not prepared for that conversation. Salvatore's recommendation is straightforward: use AI, train it toward your voice, and take advantage of what it can do, but always read before you send. Edit the output. Make sure it sounds like you. More importantly, make sure you understand and can stand behind what is being communicated. AI should reduce unnecessary work. It should not remove you from your own communication. Build AI Communication Skills One Problem at a Time Avoiding AI entirely is not the answer either. The challenge is maintaining your own cognitive and communication abilities while taking advantage of increasingly capable tools. Salvatore offers a simple exercise: one a day. Once each day, take one problem and work through it yourself before asking AI for help. Think through the problem, develop your answer, and write out your reasoning. Then give it to AI and compare what it produces with your approach. That creates a very different relationship with the technology. Instead of asking AI to think so you do not have to, you are using it as another perspective against which you can test your thinking. You continue exercising the skill while also learning where AI can improve your work. For developers, this should feel familiar. We do not become better programmers by copying code we do not understand. We improve by solving problems, reviewing alternatives, testing assumptions, and learning from the differences. AI communication skills should develop the same way. Communication Skills Help You Speak Outside the Technical Room Technical professionals face another challenge as their careers progress. Eventually, the audience changes. You may spend years discussing systems with developers who understand your terminology, assumptions, and data. Then you walk into a room with operations, HR, legal, sales, marketing, executives, or customers. The same communication approach no longer works. Salvatore recommends practicing metaphors because they force technical professionals to translate an idea into something another audience can visualize. He compares this to giving someone the blueprint for a house versus showing them a rendering of the finished house. The blueprint may contain more precise technical information, but the rendering makes the result easier to understand. Developers can practice this before they ever enter the boardroom. Pick something familiar—a hobby, sport, cup of coffee, or everyday activity—and explain how your current project is similar to it. The metaphor does not need to be perfect. The exercise teaches you to look at the same technical idea through a different lens. That ability to switch communication styles is part of moving beyond the code. The more responsibility you gain, the more likely you are to communicate with people who do not share your technical background. AI Communication Skills Are Career Skills AI will continue getting better at writing, summarizing, organizing, and preparing information. That makes learning how to use these tools important, but it also increases the value of the skills that remain human. Can you read the room? Can you recognize when someone has disengaged? Can you explain a technical problem to a nontechnical stakeholder? Can you challenge an idea without attacking the person who proposed it? Can you answer an unexpected question without waiting for an AI-generated response? Those are communication skills, but they are also career skills. Salvatore's advice is not to reject AI. Use it for interview preparation. Use it to evaluate your communication. Use it to help generate new ways to explain an idea. Train it to better understand your voice. Just do not stop developing your own. 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 Communication – Critical For Success Gain Wisdom Through Better Listening Skills Constructive Communication in Software Development That Drives Results Building Better Developers Podcast Videos – With Bonus Content

Leadership communication becomes increasingly important as developers move beyond writing code and begin leading people, projects, and technical decisions. Being the smartest person in the room does not automatically make you the most effective leader. In fact, technical expertise can sometimes work against a team when the people with the strongest opinions dominate the conversation while everyone else quietly checks out. In this episode of Develpreneur, Rob Broadhead and Michael Meloche talk with leadership communication coach Salvatore Manzi about what happens when developers and technical experts move beyond writing code and begin leading people. The conversation focuses on learning how to make sure people understand one another, contribute their ideas, and work together instead of simply talking past each other. About Salvatore Manzi Salvatore Manzi is a leadership communication coach whose work sits at the intersection of leadership, communication, and collaboration. He works with teams and analytical professionals to improve how they communicate so they can collaborate more effectively and move their ideas forward. Salvatore is also the author of Clear and Compelling: Communication Strategies for Big Thinkers. During the Develpreneur interview, he explained that the book draws on twenty years of communication strategies and is aimed particularly at analytical, technology, and data-driven professionals with bold ideas. His work fits closely with the theme of this season of Develpreneur: building a career beyond the code. Technical knowledge can help you develop the idea, but leadership communication helps you explain it, build support for it, and bring other people along with you. Social: Facebook / YouTube / Instagram / LinkedIn Website: Salvatore Manzi's Website Leadership Communication Starts With Understanding Technical professionals are trained to process information quickly. Someone explains a problem; our brains immediately start analyzing it. This happens even before the other person has finished speaking; we may already be constructing a solution. That speed can be useful when solving technical problems. It can also create problems when working with people. Salvatore recommends starting disagreements with shared understanding. Before offering your own response, rephrase what you believe the other person said and confirm that you understood it correctly. The purpose is not to repeat their words back to them. It is to demonstrate that you understood the idea behind those words before adding your own perspective. For developers, this can initially feel inefficient. If everyone in the room understands the technology, why repeat something that was just said? Salvatore argues that this small investment in leadership communication can prevent much larger problems later. Rephrasing establishes a common starting point, particularly when people are working together for the first time or discussing an important decision. A simple way to develop the habit is to practice it once each day. Find one conversation where, instead of immediately responding, you rephrase what you heard and ask whether you understood correctly. Over time, that intentional pause becomes part of how you communicate. Get Your Voice Into the Meeting Early The opposite communication problem happens when someone has something useful to contribute but waits too long to speak. This is common on technical teams. When one or two people are viewed as the experts, everyone else may wait for them to speak first. Once those people begin driving the conversation, it becomes increasingly difficult for quieter team members to enter it. Salvatore recommends getting your voice into the meeting within the first five minutes. You do not need to make a profound statement or immediately solve the problem. Ask a question, acknowledge someone else's contribution, or invite another person into the discussion. The goal is simply to become an active participant instead of a passive observer. That advice applies especially well to developers who prefer to process information before speaking. Waiting until you have the perfect answer can mean never entering the conversation at all. Leadership can make that problem easier or harder. Leadership Communication Means Creating Space for Everyone A leader's responsibility is not simply to provide the best answer. Effective leadership communication also means creating an environment where the team can produce better answers together. Salvatore suggests several practical techniques for getting more people involved. One is a quick round-the-room check-in where everyone provides something that is going well and something that could be going better. The important part is establishing limits, such as one sentence for each answer, so the exercise does not turn into a series of monologues. Another technique is the 10-second rule. Ask the team a question, but tell everyone that nobody should answer for ten seconds. That short silence gives analytical team members time to process the question. Instead of rewarding whoever can speak fastest, the meeting gives everyone a chance to formulate a useful response. These techniques are simple, but that is part of their value. Improving team communication does not necessarily require a new platform, complicated process, or another meeting. Sometimes it requires changing the way an existing conversation is structured. Stop Putting People on the Spot There is also a significant difference between inviting someone into a conversation and suddenly calling on them. Anyone who remembers being unexpectedly called on in school knows the feeling. Instead of thinking about the question, your brain suddenly starts thinking about the fact that everyone is looking at you. Salvatore demonstrated a better approach during the conversation: give the person advance notice that you are coming to them, tell them the subject you want them to address, briefly move the group's attention elsewhere, and then return to them. That small handoff gives the person time to prepare mentally. Instead of creating a performance test, the leader creates an opportunity for the person to contribute. This is particularly useful for technical teams where some members may need a few moments to organize a complex answer. The goal is not to eliminate spontaneity. It is to stop confusing fast responses with valuable responses. Breaking Down Technical Silos Through Better Communication Technical organizations naturally create specialists. One person understands the database. Another understands infrastructure. Someone else knows the business rules, testing process, user interface, or deployment pipeline. Specialization helps teams solve difficult problems, but it can also create silos. Salvatore described working with a team whose individual groups functioned effectively but struggled when they came together. They were essentially speaking different languages. During a half-day session, the team worked through what they needed from one another and what they believed they were hearing from each other. They also formed smaller cross-functional groups. One surprisingly effective part of the exercise was asking people to begin by identifying something they appreciated about another person's work. That forced team members to think about what their colleagues actually contributed rather than seeing only their own piece of the system. That lesson matters in software development because it is easy to judge another role by how it affects your own work. Developers can become frustrated with QA. QA can become frustrated with developers. Technical teams can become frustrated with business stakeholders, while business stakeholders wonder why seemingly simple requests take so long. Good leadership communication helps people understand those different perspectives. Understanding what another person contributes does not eliminate disagreement, but it gives that disagreement context. What About the Person Who Never Stops Talking? Creating space for quieter voices introduces another challenge: the person who takes too much of that space. Most teams have experienced the meeting where someone gets the microphone and never seems to give it back. Salvatore recommends addressing this before it becomes a problem by establishing communication agreements for the team. Those agreements might include: Make sure every voice has an opportunity to contribute. Keep individual contributions short. Lead with the bottom line. Provide additional detail when the group needs it. Once those expectations are established, a phrase such as "bottom line" can become a shared reminder rather than a personal criticism. Everyone already understands what it means and why the team uses it. That distinction is important. Good meeting facilitation is not about silencing people. It is about managing the limited amount of attention and time available so the entire team can participate. Leadership Communication and the Move From Expert to Leader One of the biggest career transitions for developers is moving from being responsible for your own technical output to helping other people produce results. The skills that made you a strong developer do not disappear when you become a technical lead, architect, manager, or executive. However, they are no longer enough by themselves. You have to listen differently. You have to recognize when someone has stopped participating. You have to create room for people who need time to think while keeping stronger personalities from consuming the entire conversation. Most importantly, you have to stop measuring leadership communication by whether you successfully said something and start asking whether the other person actually understood it. Salvatore's advice throughout this conversation comes back to small, repeatable behaviors. Rephrase someone's idea once a day. Speak within the first five minutes of a meeting. Give people ten seconds to think. Prepare someone before handing them the conversation. Establish expectations before someone starts monopolizing the room. None of those techniques requires a major organizational transformation. They require practice. That is also what makes them valuable for developers working to build a career beyond the code. Leadership does not suddenly begin when someone gives you a management title. It develops through the way you communicate, listen, facilitate, and help the people around you contribute their best ideas. 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 Constructive Communication in Software Development That Drives Results Facilitative Leadership: Why Modern Teams Need Guides Instead of Heroes Software Communication Gaps: The Hidden Foundation Problem Slowing Your Team Building Better Developers Podcast Videos – With Bonus Content

AI can produce code faster, automate repetitive work, analyze enormous amounts of information, and move development tickets at a pace that would have seemed impossible only a few years ago. Yet faster execution does not automatically create better software delivery systems. In fact, speed can expose weaknesses that organizations previously managed to hide. That distinction becomes central in the second part of Dana Hetté's conversation with Rob Broadhead and Michael Meloche on Building Better Developers. The first part explored the organizational cracks that form between roles and how developers can use systems thinking to recognize them. Part two moves from recognition to action: What happens when delivery is already struggling? Where should an organization start? And what role should AI play when the underlying system is not healthy? Hetté's answer challenges a common technology reflex: tools do not define the solution. They enable a solution that has already been defined. About Dana Hetté Dana Hetté, also known as Blondie Geek, is a fractional operator who works with founders and leadership teams at startups and small product organizations. After earning a degree in computer science, Dana spent roughly seven to eight years as a software engineer before moving toward roles centered on product, operations, and the connection between business strategy and execution. Dana describes her work as occupying the operator seat: the connective role between what leadership intends and what teams ultimately deliver. Her approach combines the systems-thinking foundation of software engineering with product discovery, organizational operations, and cross-functional communication. Rather than focusing only on what individual teams are doing, she looks for the cracks between roles where context, ownership, and business intent can disappear. You can learn more about Dana at BlondieGeek.com, connect with Dana Hetté on LinkedIn, or subscribe to her newsletter, Closing the Loop. Software Delivery Systems Need Diagnosis Before Automation Consider an organization where code is still shipping, deadlines are still being met occasionally, and every department appears busy. Underneath that activity, however, pipelines are breaking, quality is deteriorating, bugs are increasing, and teams are getting closer to the red line. Leadership sees the symptoms and understandably wants a solution. Maybe another project-management platform will help. Perhaps a new AI development tool can increase productivity. Maybe another automation will remove the bottleneck. Hetté argues that this is precisely where organizations need to resist the urge to start with technology. "Tools are not the solution, they enable a solution that you've already defined." — Dana Hetté When an organization does not understand why its delivery system is breaking, automating that system can simply make the dysfunction operate faster. Instead, Hetté returns to something far less glamorous: discovery. She describes getting into the organization, talking to people, observing stand-ups, examining project-management tools, reviewing tickets, and investigating what is actually happening. AI can assist with that process by analyzing meeting transcripts, tickets, sprint information, and other organizational data, but human judgment remains necessary to understand what those signals mean. The objective is not immediately to fix everything. It is first to define what is actually broken. Software Delivery Systems Improve When You Find the Real Problem Hetté points to the classic Five Whys technique as an example of how straightforward the diagnostic process can be. Something is broken. Why? Then ask why again. Continue until the team moves past symptoms and reaches the underlying cause. This sounds elementary, particularly to developers accustomed to sophisticated debugging tools, observability platforms, AI assistants, and complex architectures. Yet the underlying principle is remarkably similar to debugging software. A developer encountering an exception does not permanently solve the problem by hiding the error message. The exception is evidence. You trace the execution path until you understand the condition producing it. Organizational problems deserve the same discipline. Hetté describes the balance as spending much of the effort defining the problem. Once the actual problem is understood, the solution often becomes surprisingly straightforward. Complicated symptoms do not necessarily require complicated solutions. The complexity may come from not knowing which problem you are actually solving. This is also why firefighting becomes dangerous when it turns into a permanent operating model. There are legitimate emergencies where a team has to use what Hetté calls "duct tape and chewing gum" to cross the finish line. Production needs to be restored. A deadline cannot move. A customer needs an immediate resolution. The distinction is whether the organization recognizes that temporary stabilization is not the same as solving the underlying problem. Align Software Delivery Systems Around Trade-Offs Even after identifying a problem, teams can struggle because leadership and engineering are optimizing for different outcomes. Engineering may want time to improve quality. Leadership may be focused on speed to market. Finance may be focused on cost. Product may be trying to protect scope. None of those priorities automatically makes one group wrong. The organization needs to decide what matters most. Hetté uses what she calls project sliders during discovery. The idea involves familiar project constraints such as speed, quality, and cost. Leadership needs to determine where those sliders sit rather than pretending every priority can simultaneously be maximized. A company may say it needs to reach the market tomorrow while spending as little as possible. The next question becomes unavoidable: What is the organization willing to compromise—quality, scope, consistency, or time? Many disagreements that appear technical are actually disagreements about priorities that were never explicitly decided. Those decisions provide developers with something extremely valuable: guardrails. Hetté shares an example involving an engineer who wanted an increasingly agentic workflow. Instead of manually associating work, the engineer wanted one agent to determine what another agent was doing. Hetté suggested a dramatically simpler solution: put the ticket number in the pull request. The engineer could even have an agent perform that step. The exchange highlights an important distinction between technological possibility and operational value. An organization does not need to automate something merely because it can. Once leadership has established its priorities, those principles can become the North Star for deciding which practices are worthwhile. AI Needs Human Inspection Points The role of human judgment becomes particularly important when AI enters development workflows. In Part One, Hetté described developers using AI agents to move rapidly through tickets only to discover during user acceptance testing that the output did not match what was actually needed. Part Two reinforces why those failures matter. AI dramatically increases the amount of work a developer can produce. However, increasing output also increases the consequences of an incorrect assumption. A misunderstanding that once produced one incorrect implementation might now propagate across specifications, tickets, code, tests, and documentation before anyone notices. The answer is not necessarily a large new governance process. Sometimes it is simply a sanity check. An AI agent turns raw requirements into a specification. Before the next agent begins producing code, someone reads the specification and asks: Is this actually what we need? That lightweight inspection can prevent an incorrect assumption from accelerating through the entire delivery pipeline. Find one AI-assisted handoff in your development process and introduce a deliberate verification point. Do not merely ask whether the AI completed the task. Ask whether its output still matches the original intent. Human-in-the-loop development should not mean manually redoing everything AI produces. That would eliminate much of AI's value. Instead, human judgment should be strategically positioned where errors become increasingly expensive if they continue downstream. Software Delivery Systems Need Ownership There is another problem that neither AI nor better tooling automatically resolves: ownership. As organizations grow, a single operator cannot personally inspect every handoff. If that person attempts to do so, the individual who was supposed to eliminate bottlenecks becomes one. Hetté discusses solving this through mentorship and delegation. In one engagement, she entered knowing from the beginning that part of her responsibility would be finding and developing her eventual replacement. Rather than building an organization permanently dependent upon her, she worked with a more junior person and transferred the systems-thinking and operational mindset needed to continue the work. That approach provides an important lesson for technical leaders: good systems should reduce dependency on specific individuals. This is familiar territory for developers. We know the danger of a critical application understood by only one engineer. We recognize the bus-factor problem in software. Yet organizations can accidentally create exactly the same dependency in operations. The answer is to transfer judgment, context, and ownership. Hetté argues that systems thinking, product-oriented thinking, and operational judgment can be taught. Instead of requiring one senior person to own every organizational seam, leaders can develop others who learn how to recognize gaps and take responsibility for them. AI Changes What Makes Developers Valuable The conversation ultimately moves from organizational systems back to the developer's career. Michael Meloche raises a significant concern: If AI increasingly performs junior-level coding work, how do junior developers acquire the experience necessary to become senior developers? Hetté compares the current transition to earlier abstractions in programming. Developers who worked closer to the machine once worried about newer generations who did not understand the same low-level concerns. She uses the transition from languages such as C++ to Java as an example. Developers could work at a higher abstraction level because the language handled concerns that previously required more direct attention. AI may represent another, significantly larger abstraction. Future developers may write less code manually while becoming increasingly skilled at managing AI systems that produce it. Hetté sees the possibility of an AI product builder role that blends characteristics traditionally associated with engineering and product management. The valuable capability then becomes judgment. Can you determine whether the generated solution makes sense? Can you understand what the business is trying to accomplish? Can you recognize when an agent has produced something technically plausible but strategically wrong? These questions point directly back to systems thinking. Knowing syntax matters less when a machine can generate syntax. Understanding consequences becomes more important when a machine can generate enormous amounts of implementation. Start With One Seam Hetté closes the extended conversation with a particularly useful challenge for developers who want to move beyond their existing role. First, adopt an ownership mindset. Many employees naturally stay within their lane. They complete their assigned responsibilities and leave adjacent problems to whoever supposedly owns them. That approach can be perfectly functional, but it does not develop the perspective required for an operator or broader leadership role. Hetté describes the alternative as approaching the work with a sense that "the buck stops with me and I own this thing." That does not mean becoming controlling or assuming responsibility for the entire company. It means becoming interested in whether the overall outcome succeeds rather than only whether your assigned portion is complete. Then make the exercise manageable. "Pick one handoff point, pick one seam." — Dana Hetté Perhaps it is the transition from requirements to specifications. Maybe it is specifications to tickets, tickets to pull requests, or pull requests to testing. If AI generates code, compare what was produced against the original specification. Do not attempt to redesign the entire organization. Investigate one boundary. As Rob Broadhead notes during the discussion, unclear ownership is frequently where the cracks appear. Ask who owns a particular handoff. If everyone starts looking around the room waiting for someone else to answer, you may have found the gap. Conclusion: Better Tools Require Better Systems The future of software development will almost certainly involve more AI, more agents, and greater automation. That makes strong software delivery systems more important, not less. When execution becomes cheap and fast, mistakes can become cheap and fast too. The organizations that benefit most from AI will therefore not necessarily be those using the largest number of agents or adopting every new development tool. They will be the organizations that understand what they are trying to accomplish, define ownership clearly, establish meaningful guardrails, and know where human judgment creates the most value. For developers, this creates an opportunity that goes well beyond learning another AI tool. Learn to diagnose systems. Learn to recognize trade-offs. Learn to see the seams between people, processes, software, and strategy. When you want to start, follow Hetté's advice: pick one handoff and find out whether it actually works. 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 Handling Software Delivery Panic: Strategies for Developers Software Delivery Clarity: Why Visibility Beats More Process Hero Culture Risks: Why AI Is Exposing the Cracks in Software Delivery Building Better Developers Podcast Videos – With Bonus Content

Software development careers have traditionally been measured by technical ability: the languages you know, the systems you can architect, the bugs you can solve, and the quality of the code you produce. But developer systems thinking expands that definition. As developers advance in their careers, their value increasingly comes from understanding not only how software works, but how people, processes, business goals, and technical decisions work together. That distinction sits at the center of Dana Hetté's conversation with Rob Broadhead and Michael Meloche on Building Better Developers. Hetté, also known as Blondie Geek, began her career in software engineering before moving into what she describes as the "operator seat." Her work now focuses on a problem that many startups and product organizations encounter: teams may be busy building, leadership may have a clear vision, and every individual may appear to be doing their job, yet what ultimately ships does not match what the business actually needs. The problem is often not inside any one role. It exists in the space between those roles. About Dana Hetté Dana Hetté, also known as Blondie Geek, is a fractional operator who works with founders and leadership teams at startups and small product organizations. After earning a degree in computer science, Dana spent roughly seven to eight years as a software engineer before moving toward roles centered on product, operations, and the connection between business strategy and execution. Dana describes her work as occupying the operator seat: the connective role between what leadership intends and what teams ultimately deliver. Her approach combines the systems-thinking foundation of software engineering with product discovery, organizational operations, and cross-functional communication. Rather than focusing only on what individual teams are doing, she looks for the cracks between roles where context, ownership, and business intent can disappear. You can learn more about Dana at BlondieGeek.com, connect with Dana Hetté on LinkedIn, or subscribe to her newsletter, Closing the Loop. Developer Systems Thinking Starts With the Gaps Hetté describes herself as the cohesive layer between strategy and execution. In smaller organizations, founders often carry an enormous amount of context in their heads. They understand the company strategy, board expectations, customer demands, product direction, and countless decisions that have accumulated over time. Engineering, meanwhile, is responsible for turning some version of that vision into working software. The trouble begins during the transfer. A founder may tell a technical lead what needs to be built. The technical lead interprets that request through an engineering lens and passes work to developers. The developers execute against the information they have. Everyone can perform their individual job correctly while the organization still produces the wrong outcome. Hetté calls attention to the "cracks" between roles. Those cracks are where assumptions go unchallenged, context disappears, ownership becomes unclear, and seemingly small communication problems become delivery problems. A team can execute every assigned task successfully and still fail to accomplish the business objective. Local success does not guarantee system-wide success. One example from Hetté's work involved a feature-intake process at a larger organization. The company already had automations built into its project-management platform. On paper, the system appeared complete. Requests entered the system, automations processed them, and work moved through the expected steps. Then Hetté started asking questions. What business rule determined a particular assignment? Why did an item move from one place to another? Who owned the decision at a particular handoff? The answers were missing. The automation existed, but the underlying operational logic had gaps. As Hetté explains, people tend to operate within the boundaries of their defined roles. Consequently, "the gaps form between the roles." That observation is important for developers because those gaps are fundamentally systems problems. Why Developer Systems Thinking Goes Beyond Architecture Developers already learn to think in systems. We reason about dependencies, inputs and outputs, interfaces, failure states, data flows, and interactions among components. When one component behaves incorrectly, experienced developers do not automatically assume that component itself is the root cause. They trace what entered it, what left it, and how it interacts with everything around it. Hetté argues that this same ability can be applied to an organization. Instead of looking only at software architecture, look at the architecture of the business producing the software. Where does a requirement originate? Who translates it? What information is lost before it reaches engineering? What happens when engineering finishes? Who determines whether the result actually fulfills the original business objective? This represents an important shift for developers interested in careers beyond coding. Hetté spent roughly seven or eight years as a software engineer after earning her computer science degree. Over time, she realized she was becoming more interested in what the team was building and why than in every technical detail of how it was built. That did not make her engineering background irrelevant. It gave her a different place to apply it. She specifically identifies systems thinking as one of the strengths engineers can carry into product, program management, and operator roles. The mental model remains useful; the boundaries of the system simply become larger. Developer Systems Thinking Connects Code to the Customer One danger of remaining exclusively focused on implementation is that developers can unknowingly optimize for the wrong definition of success. Engineering naturally views a product through an engineering lens. Users do not. Hetté references Alan Cooper's The Inmates Are Running the Asylum when discussing this distinction. One of the ideas she draws from the book is that engineers and the people using their software frequently operate with very different mental models. What seems intuitive to someone who understands the internal mechanics of a system may be confusing or ineffective for the person the product was actually designed to serve. That principle extends beyond user interfaces. A technically elegant implementation can still solve the wrong problem. A completed ticket can still fail to deliver the expected business outcome. A feature can satisfy its technical acceptance criteria and still disappoint the customer. Moving beyond code does not mean abandoning technical thinking. It means expanding the system you are thinking about until the user, business objective, and organization become part of it. Hetté encourages developers to ask larger questions while they work. What is the company trying to accomplish? What is the product supposed to achieve? Does the current work support that strategy? What does the end user actually care about? Holding that context changes technical decisions because developers are no longer treating a ticket as an isolated unit of work. They are seeing where that ticket fits into the larger machine. The Operator Vacuum Between Founders and Engineering This becomes particularly important in startups. A founder or CEO in a six-person organization cannot spend the entire day translating product ideas for engineering. The founder may also need to work with investors, communicate with the board, develop partnerships, pursue business development, and determine company strategy. Yet that same founder may be the person carrying the clearest picture of the product. The result is what Hetté calls an "operator vacuum." The founder needs to leave the weeds, but the organization still needs someone capable of translating strategy into execution. Hiring a project manager or product manager may address portions of the problem, but Hetté notes that those people also have defined roles. The missing function may be broader: someone who can extract the founder's context, understand stakeholder demands and strategy, and work across project managers, technical leads, and the execution team. Hetté compares the position to being a first officer to the captain. The operator is not there to replace engineering, product management, or leadership. The operator connects them. For developers considering how to broaden their careers, this presents an interesting opportunity. You do not necessarily need the word "operator" in your title to begin thinking this way. Look for Symptoms Instead of Assuming the Problem An important part of systems thinking is resisting the temptation to diagnose a problem from its most visible symptom. A founder may say, "My team isn't shipping on time." Another may say that the team is shipping, but what arrives is not what was envisioned. A leader may feel trapped in day-to-day decisions because leaving the team alone seems likely to send development in the wrong direction. Those are symptoms. Hetté approaches them similarly to product discovery. She begins with probing questions for leadership and then talks with the people performing the work. Comparing those perspectives exposes where expectations, processes, and reality diverge. One useful signal appears when all the formal indicators say a project is healthy while downstream results say otherwise. A project board can be green. Stand-ups can report that everything is on track. Developers can close their tickets. Then the product reaches user acceptance testing and gets rejected. Something happened between "everything is green" and "this isn't what we wanted." That seam deserves investigation. Metrics that measure activity inside individual roles can hide failures at the handoffs between them. A green dashboard is not proof that the entire delivery system is healthy. This matters even more as AI accelerates individual parts of software development. Hetté describes a project where developers used agents to move rapidly through tickets. From a productivity perspective, it looked impressive. Code was being produced quickly, and boxes were being checked. But when the results reached UAT, the output was not aligned with what was actually needed. Some of it was effectively unusable. The AI had accelerated execution without repairing the underlying handoff. Developer Systems Thinking Requires Collaborative Ownership Seeing a broken system is one thing. Raising the issue inside an organization is another. Hetté acknowledges that developers do not always feel comfortable telling leadership that a process is broken. Even when managers explicitly invite candid feedback, employees may remain quiet. Her recommendation is to frame the conversation around improving the system rather than blaming an individual. The objective is not to prove that leadership, product, or another developer made a mistake. The objective is to make what Hetté calls the organizational "machine" work as effectively as possible. That distinction changes the conversation. Instead of saying, "This person is doing this wrong," a developer can identify a disconnect between what the organization intends to accomplish and what its current process produces. Developers are particularly well suited to these conversations because systems thinking already encourages us to look at relationships rather than isolated components. Action: Identify one recurring handoff in your current work. Compare what the person on one side believes they are providing with what the person on the other side believes they are receiving. The difference may reveal more than another process meeting ever will. The goal is not to take control of everyone else's job. It is to recognize that meaningful ownership sometimes requires looking beyond the boundaries of your assigned ticket. Moving From Code Builder to Problem Solver The transition Hetté describes does not require developers to stop being technical. Instead, it asks them to redefine what they consider the system. Early in a career, the system might be a function, service, application, or architecture. As responsibility grows, the system can include requirements, customers, teams, handoffs, leadership decisions, and business strategy. That broader perspective is where developers can begin creating value that is difficult to measure in lines of code. The developer who notices that two teams are individually performing well but consistently losing information during a handoff is solving a technical organization problem. The engineer who asks whether a feature actually supports the company strategy is contributing beyond implementation. The technical lead who recognizes that a founder's abstract vision needs another translation step before reaching developers is preventing expensive rework. Those behaviors represent a career beyond the code without requiring someone to abandon the skills that got them there. In fact, the engineering mindset may be precisely what makes the transition possible. Conclusion: Expand the System You Are Building Developer systems thinking begins when developers stop viewing their responsibility as ending where the code ends. The lesson from Dana Hetté's experience is not that every developer should become an operator. It is that the skills developers already possess can be applied to larger and more consequential systems. Organizations have inputs, outputs, dependencies, bottlenecks, interfaces, and failure states just as software does. The hardest problems frequently emerge not inside the individual components, but at their boundaries. Learning to see those boundaries is a powerful step toward becoming more than the person who implements the solution. It positions a developer to understand which problem should be solved, why it matters, and how the pieces must connect for the solution to actually work. 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 Forward Momentum as a Developer Entrepreneur Growth Ceiling Systems: Why You're Not Actually Stuck Private AI Systems: Why Smart Developers Build for Themselves First Building Better Developers Podcast Videos – With Bonus Content

Software development is changing quickly. AI can generate code, build prototypes, test ideas, and turn concepts into working software faster than most of us would have imagined just a few years ago. That raises an important question for developers: If writing the code is becoming easier, what makes you valuable? Welcome to Season 29 of the Develpreneur Podcast. This season, we're returning to an idea that has been at the heart of the show from the beginning. Becoming a better developer means developing more than your ability to write code. Our theme for Season 29 is Build a Career Beyond the Code, and throughout the season, we'll explore what that means for developers navigating an industry being reshaped by AI. More Than a Coder We've always made a distinction between being a coder and being a developer. A coder can take a requirement and turn it into code, while a developer needs to understand the problem behind that requirement. Developers have to determine whether the proposed solution makes sense, identify potential risks, and ultimately help deliver something useful. That distinction matters more now than ever. AI is becoming remarkably good at generating code. Give today's tools enough context, and they can produce in hours what might previously have taken a developer days or weeks. That doesn't eliminate the need for developers, but it does change where developers provide value. The valuable skills increasingly involve asking better questions, understanding the business problem, evaluating possible solutions, communicating with stakeholders, testing assumptions, and recognizing risks. We also have to determine whether what we're building actually solves the original problem. In other words, the future developer isn't simply someone who knows how to code. The future developer knows how to solve problems. AI Changes the Speed, Not the Responsibility One of the most exciting things about AI is how quickly we can experiment. An idea that might once have sat in a notebook for years can now become a prototype over a weekend. We can pressure-test concepts, generate alternatives, experiment with architectures, and throw away approaches that don't work without investing months of development effort. Instead of having one opportunity to build something correctly, we may be able to test dozens of approaches before committing to one. That's an incredible advantage, but it also creates a new problem: just because AI can build something doesn't mean we should build it. We can generate a prototype overnight and then immediately add another feature. That leads to another feature, another integration, and another idea that suddenly seems easy to implement. Before long, the simple application we originally wanted to build starts looking like we're trying to recreate Salesforce. Knowing when to stop is becoming an important development skill. So is knowing which features actually matter and whether the application still solves the problem we started with. AI can dramatically increase our development speed, but speed without direction simply allows us to make mistakes faster. The MVP Is Changing For years, building a minimum viable product required meaningful investment. Even a relatively simple prototype could require developers, designers, infrastructure, and weeks or months of work. AI has changed that equation. Today, creating something that looks impressive is relatively easy. You can quickly build an application with polished screens, dashboards, workflows, integrations, and features that would have required a significant development team not long ago. That means the existence of a prototype doesn't tell us nearly as much as it once did. We have to ask deeper questions about what we've created. Does it actually work? Is the architecture sustainable? Can it handle real users and real data? Is it secure and maintainable? Does anyone actually need it, and does it create real value? Those are not primarily coding questions. They're development questions, and answering them requires experience, critical thinking, testing, and an understanding of the people and businesses using the software. Developers Still Need to Think AI tools are powerful, but they still require direction, context, validation, and oversight. Working with AI agents can sometimes feel a lot like leading a development team. You assign work, review the results, discover something wasn't done the way you expected, refine the requirements, and try again. The difference is that AI lets you repeat that cycle incredibly quickly. That makes critical thinking even more important. Developers need to learn how to communicate what they want, provide the right context, establish boundaries, review results, test assumptions, and recognize when an answer that looks convincing is actually wrong. This also changes the questions developers should be asking. Instead of focusing entirely on whether AI can generate a particular application or feature, we need to ask whether we should build it in the first place. Then we need to determine how we'll know whether we built the right thing. That's where experience becomes leverage. Your Career Isn't Disappearing. It's Evolving. There's understandable concern about what AI means for software development careers, particularly for developers entering the industry. Some traditional career paths are already changing. Work that once gave junior developers opportunities to learn may increasingly be handled by AI, teams may become smaller, and individual developers may become capable of producing dramatically more than before. However, that doesn't mean there is nowhere left to go. The career ladder hasn't disappeared. The angle has changed. Developers who combine technical knowledge with problem-solving, communication, business understanding, critical thinking, leadership, and testing have an opportunity to become far more capable. AI can amplify those skills by helping developers move from an idea to something they can evaluate much faster. The goal isn't to compete with AI over who can type code faster. The opportunity is to become the person who understands what needs to be built, why it needs to be built, how to validate it, and how technology can solve the underlying problem. Building the Skills Beyond the Code Season 29 brings Develpreneur back to its roots while building on everything we've explored during the last several seasons. We're going to continue talking about AI because it is now part of the development landscape, but AI itself isn't the destination. We're interested in what developers can accomplish with it and which skills become more valuable as these tools improve. That means exploring technical skills alongside communication, critical thinking, problem-solving, requirements, testing, leadership, business value, decision-making, and project ownership. We'll look at how developers can pressure-test ideas before investing too much time in them, manage AI-generated solutions, and recognize the difference between a flashy prototype and production-ready software. Quality becomes particularly important when software can be generated so quickly. Producing code faster doesn't automatically mean we're producing better software. Every additional feature introduces complexity, potential failure points, testing requirements, and long-term maintenance. If the foundation isn't solid, AI can help us create a complicated mess much faster than we could have created one ourselves. That's why testing, validation, and asking the right questions become even more important. Generating more code isn't necessarily progress. Generating the right solution is. A New Career Path for Developers The changes we're seeing aren't limited to the tools developers use. They affect how people build careers. Developers need to become comfortable moving between technology, business problems, communication, testing, and decision-making rather than defining themselves by a programming language or framework. AI may even accelerate that career progression. Developers can experiment with ideas that previously required an entire team. They can work with AI agents in ways that resemble managing junior developers, explore unfamiliar technologies, and rapidly test different approaches to a problem. However, getting the most from those capabilities still requires knowing enough to recognize when something is wrong. Experience matters because AI doesn't remove responsibility from the developer. If anything, it increases the number of decisions we can make in a shorter period. The better we become at making those decisions, the more valuable the technology becomes. Welcome to Season 29 We're now well beyond 1,000 episodes of the Develpreneur Podcast, but the mission remains remarkably similar to where we started: helping developers become better developers. The tools have changed, the industry has changed, and AI has accelerated what individuals and teams can accomplish. The path developers take through their careers is changing along with it. That's exactly why this is the right time to return to the fundamentals. We need to learn how to think through problems, communicate effectively, evaluate what we're building, test our assumptions, and understand the value behind the technology. We also need to learn how to use AI without allowing the speed of AI to replace good judgment. Season 29 is about taking everything we've learned about software development, careers, business, quality, and AI and asking where developers go from here. The answer isn't to abandon technical skills or stop writing code. It's to recognize that code is only one part of what makes someone a valuable developer. The developers who thrive in this next stage of our industry will be the ones who can look beyond the code, understand the problem, use the tools available to them, and consistently turn ideas into solutions that provide real value. Welcome to Season 29 of the Develpreneur Podcast: 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 episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Destined For A Career In Software – A William A. Adams Interview Enterprise AI Reality: What Software Teams Are Learning Beyond the Hype Developer Career Growth: Breaking Through Stagnation Building Better Developers Podcast Videos – With Bonus Content

Laura Chattington, CEO of Rebalance Network and an AI strategy adviser, explores how AI is reshaping software development. Entrepreneurs can now build prototypes and workflows without coding expertise, but engineering boundaries remain vital. They discuss quality assurance, risk, business outcomes, measurable KPIs, and finding AI opportunities that reduce pain or create revenue.