Discover
Develpreneur: Become a Better Developer and Entrepreneur
Develpreneur: Become a Better Developer and Entrepreneur
Author: Rob Broadhead
Subscribed: 121Played: 9,675Subscribe
Share
© 2017-2025 - Rob Broadhead, All Rights Reserved
Description
This podcast is for aspiring entrepreneurs and technologists as well as those that want to become a designer and implementors of great software solutions. That includes solving problems through technology. We look at the whole skill set that makes a great developer. This includes tech skills, business and entrepreneurial skills, and life-hacking, so you have the time to get the job done while still enjoying life.
1027 Episodes
Reverse
Building a successful business requires more than developing a great product. As companies grow, they face new challenges involving customer expectations, operational efficiency, financial decisions, and the constant pressure to innovate. Artificial intelligence has made it easier to build software and experiment with ideas, but knowing which opportunities are worth pursuing remains an important skill. In this episode of Building Better Developers, hosts Rob Broadhead and Michael Meloche continue their conversation with Ari Kimmelfeld, founder of Commonplace, a nationwide marketplace specializing in large secondhand items. After exploring how Commonplace grew from a simple Peloton resale website into a full-service marketplace, the discussion turns toward AI, experimentation, financing, customer acquisition, and the challenges of scaling a technology-driven business. Ari shares how his team uses AI to accelerate development, why some promising business ideas fail, and how Commonplace continues to find opportunities in markets where traditional online platforms leave customers with complicated problems to solve. About Ari Kimmelfeld Ari Kimmelfeld is the founder and CEO of Commonplace, a U.S.-based marketplace that makes buying and selling large secondhand items easier by coordinating inspections, payments, pickup, delivery, and installation. The business evolved from TradeMySpin, an online service originally focused on used Peloton equipment. Ari and his wife, Naomi, expanded the concept into Commonplace to address the difficulties associated with purchasing and transporting expensive secondhand products. Ari is a graduate of Macaulay Honors College at the City University of New York. His entrepreneurial approach combines customer-focused experimentation, logistics innovation, and practical software development to simplify transactions that traditional online marketplaces often leave customers to manage themselves. Connect with Ari and Commonplace: Website: https://trycommonplace.com LinkedIn: https://www.linkedin.com/in/arikimmelfeld Using AI to Build Faster Without Losing Control Artificial intelligence is changing how developers build applications and how businesses approach software development. Tasks that once required significant time and resources can now be completed much faster, allowing smaller teams to experiment with capabilities that previously seemed unrealistic. For Commonplace, AI has become an important part of maintaining and expanding the systems supporting its operations. Ari explains that the company develops much of its application functionality internally, including dispatch management, customer workflows, payment integrations, and logistics coordination. Rather than depending entirely on third-party marketplace platforms, Commonplace builds the specialized functionality necessary to support its business model. However, this does not mean reinventing every technology component. The company uses established services such as Stripe for payment processing while developing its own integrations and workflows around those services. This distinction is important for developers and entrepreneurs. Building custom software does not require creating every component from scratch. The goal is to maintain control over the processes that distinguish your business while using reliable existing technology where it makes sense. AI helps Commonplace move faster, but the real advantage comes from understanding what needs to be built and how it fits into the larger operation. Turning an Idea Into a Working Solution One example Ari shares involves a program to help people donate unused fitness equipment to New York City fire stations. According to Ari, Commonplace worked with the New York City Fire Department to create a way for individuals to donate exercise equipment rather than sell it. Because the company already had systems for listings, pickup, and delivery, its team could adapt those capabilities to support donations. Ari explains that the new functionality was implemented in approximately 24 hours. He estimates that a comparable effort might previously have required several developers working for weeks. While those estimates reflect Ari's experience rather than a universal development benchmark, they illustrate how AI can change the economics of building software. For developers, the opportunity is not simply generating code faster. It is being able to test worthwhile ideas that might previously have been postponed because of cost or limited development resources. However, faster development also introduces another challenge: deciding which ideas deserve attention. Experimentation: Why Not Every Good Idea Works One of the most valuable lessons from Ari's experience is that even promising business ideas do not always succeed. During the interview, Michael asks about changes Commonplace has tested and ultimately abandoned. Ari explains that the company regularly experiments with new concepts, but only a small percentage become meaningful successes. One example involved offering customers the ability to rent products such as ATVs on a daily, weekly, or monthly basis. On the surface, this seemed like a reasonable opportunity. Customers might want access to expensive equipment without committing to ownership. However, the results revealed something different. Because the secondhand products were already available at significant discounts, customers often preferred purchasing them instead of renting them. Rather than abandoning the broader concept of making products more affordable, Commonplace explored financing. Ari explains that offering financing options extending up to 48 months generated considerably stronger customer demand. What initially looked like an unsuccessful rental experiment helped the business discover a more valuable purchasing option. This is a useful reminder that experimentation should not be measured solely by whether the original idea succeeds. An unsuccessful test can still provide valuable information when it helps identify what customers actually want. AI Creates More Opportunities, but Focus Still Matters Developers have always struggled with deciding what to build next. There are usually more ideas than available resources, and priorities must be established around business value, customer needs, and technical complexity. AI changes the equation by making it possible to implement more ideas with fewer resources. However, increased development capacity does not automatically create better products. Ari discusses how quickly his team can now experiment with new functionality, but he also acknowledges that many ideas never produce meaningful results. Even when technology makes development easier, companies must still determine which changes are worth maintaining and supporting. This connects directly to the broader theme of Season 29, Career Beyond the Code. Developers who want to advance their careers need to understand how technology decisions affect the business. Writing code efficiently is valuable, but recognizing when something should not be built can be just as important. Before committing to a feature, consider whether it solves a demonstrated customer problem, whether the expected benefit justifies the effort, and whether it supports the company's larger objectives. Scaling a Marketplace Through Real Customer Demand As Commonplace grows, Ari sees opportunities in additional product categories, particularly those involving expensive, bulky items that are difficult to purchase through traditional peer-to-peer marketplaces. However, expanding a marketplace introduces challenges beyond increasing the number of listings. Each category may require different inspection procedures, delivery equipment, installation capabilities, and customer expectations. The business must also attract buyers and sellers who may approach secondhand shopping differently. Ari explains that Commonplace initially reached customers through Facebook groups focused on Pelotons, Tonals, and other exercise equipment. Rather than attempting to convince everyone to change their shopping habits, the company focused on people who were already buying and selling those products. That strategy continues as Commonplace promotes listings across other marketplaces where potential customers are already searching. The company also faced a branding challenge when it expanded beyond fitness equipment. The original TradeMySpin name clearly communicated its initial purpose, but it became limiting as the business introduced appliances, furniture, saunas, and other categories. Rebranding as Commonplace allowed the business to represent a broader market, but it also required explaining its value to new customer groups. For entrepreneurs, this demonstrates why growth requires balancing specialization with flexibility. A narrow focus can help establish a business, but eventually, the company must decide how to expand without losing the value that made it successful. Using Data to Improve Marketplace Pricing Another important challenge in secondhand marketplaces is helping sellers understand what their products are worth. Individual sellers often base asking prices on what they originally paid rather than what buyers are willing to spend. This can create unrealistic expectations and prevent transactions. Commonplace addresses the problem with a pricing system that considers factors such as product brand, model, age, condition, and geographic location. When sellers create listings, the platform can provide suggested prices based on market data. Sellers are not required to accept those recommendations, but the information helps them make more informed decisions. Ari explains that prices can vary considerably between locations, reflecting differences in regional supply and demand. For developers, this illustrates how
Building a successful business does not always begin with a revolutionary technology or a complicated application. Sometimes, it starts with identifying one frustrating problem and creating a simple way to solve it. For developers and entrepreneurs, the challenge is often resisting the temptation to build everything at once and instead focusing on what customers actually need. In this episode of Building Better Developers, hosts Rob Broadhead and Michael Meloche welcome Ari Kimmelfeld, founder of Commonplace, a marketplace designed to make buying and selling large secondhand items easier. From fitness equipment and appliances to furniture, saunas, and hot tubs, Commonplace handles much of what makes these transactions difficult, including inspections, pickup, delivery, and payments. Ari shares how a website with just two buttons evolved into a nationwide business, the unexpected complications of combining software with physical logistics, and why understanding customer problems matters more than building another feature. About Ari Kimmelfeld Ari Kimmelfeld is the founder and CEO of Commonplace, a U.S.-based marketplace specializing in large secondhand products, including fitness equipment, furniture, appliances, hot tubs, saunas, and other difficult-to-transport items. Ari and his wife, Naomi, built the business around making secondhand shopping more accessible by addressing challenges such as inspections, logistics, secure payments, and delivery. The company evolved from TradeMySpin, a narrowly focused service for buying and selling used Peloton equipment, into a broader marketplace serving customers nationwide. A graduate of Macaulay Honors College at the City University of New York, Ari brings an entrepreneurial approach that emphasizes identifying customer pain points, testing simple solutions, and improving operations through real-world experience. Through Commonplace, he continues to explore how technology and hands-on service can work together to make complicated transactions easier. Connect with Ari and Commonplace: Website: https://trycommonplace.com LinkedIn: https://www.linkedin.com/in/arikimmelfeld Starting Small: The Two-Button Business Model Ari's entrepreneurial journey began with a problem he had experienced personally. Having bought and sold secondhand products since childhood, he understood the opportunities available through platforms like Craigslist and Facebook Marketplace. However, he also recognized a major limitation: purchasing something large, expensive, or difficult to transport was rarely convenient. During the COVID-19 pandemic, many people purchased Peloton exercise bikes for home workouts. As gyms reopened, some of those expensive machines sat unused. Ari saw an opportunity to connect people who wanted to sell their equipment with buyers looking for a bargain. Instead of developing an elaborate marketplace, he launched a basic Shopify website called TradeMySpin. It featured two simple options: buy a Peloton or sell a Peloton. That simplicity made the concept immediately understandable. Customers knew what the website offered, and search engines could recognize its purpose. According to Ari, the business attracted significant organic interest as people discovered an easier way to buy and sell used exercise equipment. For developers, this is an important reminder that a minimum viable product does not need to demonstrate everything your technology can do. It needs to demonstrate that your solution solves a real problem. Building a Marketplace That Solves More Than the Transaction Traditional marketplaces do a good job of connecting buyers and sellers, but the transaction itself can still become a frustrating experience. Buyers may need to negotiate prices, inspect products, arrange transportation, and coordinate with sellers who sometimes stop responding. These problems become considerably more complicated when purchasing a refrigerator, treadmill, or hot tub. Ari realized that Commonplace needed to provide more than a place to post listings. The real opportunity was to remove the obstacles that prevented secondhand transactions from happening. Commonplace developed a service model that includes inspections, delivery coordination, payment processing, and installation where appropriate. The company also introduced a pay-on-delivery approach, allowing buyers to reserve an item for one dollar and complete payment after inspecting it. This was not simply a feature Ari assumed customers wanted. He explains that the team experimented with different purchasing processes before discovering that even a small financial commitment produced better results than allowing buyers to reserve products entirely for free. The lesson extends well beyond online marketplaces. The best software solutions often emerge from understanding customer behavior rather than making assumptions about how people should use an application. When Every Order Requires a Truck As Commonplace expanded beyond Pelotons, its greatest challenge was not necessarily building additional website functionality. It was creating the operational infrastructure necessary to deliver different types of products safely and consistently. A refrigerator requires different handling than a treadmill, and moving a hot tub may involve plumbing, electrical connections, specialized equipment, or even a crane. Each product category introduces requirements that must be reflected in the business processes and the software supporting them. Ari explains that Commonplace developed a nationwide network of more than 3,000 trained, vetted, and rated delivery professionals. Its systems coordinate drivers based on location, qualifications, product categories, and job requirements. Scaling this operation required more than assigning additional deliveries. The company had to develop dispatch processes, driver training, qualification checks, and specialized workflows for individual product categories. This illustrates a challenge developers frequently encounter when working with real businesses: the software is only one component of a much larger operational system. Building an application that technically functions is different from creating one that consistently supports the people doing the work. Learning From the Problems That Go Wrong One of the most valuable parts of Ari's conversation is his explanation of how Commonplace improves its processes through experience. The company uses inspection checklists containing approximately 30 to 50 points for individual products. Those checklists can vary based on the manufacturer, model, and category. When something goes wrong during a pickup, inspection, or delivery, that experience becomes an opportunity to improve the next transaction. A problem discovered while moving a particular hot tub in Texas, for example, can lead to updated inspections and training that help prevent the same issue during a future delivery in Maryland. Ari describes these lessons as the price of learning. Rather than treating every operational problem as an isolated failure, Commonplace uses those experiences to strengthen the entire network. For developers, this approach closely resembles continuous improvement in software development. Bugs, failed deployments, unexpected user behavior, and process breakdowns provide valuable information when teams take the time to investigate their causes. The goal should not simply be to fix a problem once. It should be to improve the system so that the same problem becomes less likely to happen again. Trust Is Part of the Product Buying an expensive secondhand item online requires confidence. Customers need assurance that the product is in the expected condition, that delivery will happen, and that someone will help when something goes wrong. Commonplace addresses these concerns with multiple inspection checkpoints, photographs, videos, delivery coordination, and a parts warranty. Customers can even communicate with delivery crews during pickup to ask questions about an item before completing the transaction. These additional services create a level of trust that a traditional listing alone cannot provide. For developers and entrepreneurs, the larger lesson is that customer experience includes everything surrounding the software. A polished interface cannot compensate for unreliable fulfillment, poor communication, or unclear expectations. Technology becomes more valuable when it supports a dependable service rather than simply adding more functionality. Building Better Developers: Solve the Problem Before Expanding the Product Ari's journey from TradeMySpin to Commonplace demonstrates how a focused solution can grow into something much larger. What began as a straightforward way to buy and sell Pelotons eventually required sophisticated logistics, specialized inspections, payment workflows, and a nationwide delivery network. The growth did not come from attempting to build an entire marketplace on day one. It came from identifying a meaningful customer problem, building something simple enough to test, and expanding the solution as new requirements emerged. As developers, we sometimes measure progress by how many features we deliver or how quickly we can write code. However, the real measure of success is whether our work removes obstacles, improves operations, and creates value for the people using it. Before starting your next project, consider what your version of those original two buttons might look like. Find the smallest useful solution, validate it with real customers, and let the lessons from actual usage guide what you build next. That is how we move beyond simply writing code and start building better solutions. Stay Connected: Join the Developreneur Community 👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seas
Artificial intelligence has dramatically reduced the time and effort required to develop software, but building a successful product still demands more than generating code. Developers must understand customer problems, evaluate technical decisions, maintain quality, and create solutions that people actually want to use. In Part 2 of their conversation with Ryan Drumheller, Building Better Developers hosts Rob Broadhead and Michael Meloche explore how AI is reshaping product development and what that means for developers looking to build a career beyond the code. About Ryan Drumheller Ryan Drumheller is a technology leader, entrepreneur, author, and co-founder of Dogleg Digital. With more than two decades of experience spanning IT operations, infrastructure, development, technical leadership, and business strategy, Ryan has focused much of his career on connecting technology with the people and organizations it serves. He graduated from Western Governors University and advocates for professional education, mentorship, and continuous learning. His book, From Firewalls to Fairways: How a Career in IT Led Me to Golf, shares lessons from his career and explores how setbacks and unexpected opportunities can lead to personal and professional reinvention. Connect with Ryan and learn more about his work: LinkedIn: https://www.linkedin.com/in/ryan-drumheller/ Personal website and book: https://ryandrumheller.com/ Dogleg Digital: https://doglegdigital.com/ Stop Selling Yourself and Start Solving Problems Rob begins the second part of the interview by exploring an interesting observation from Ryan's career. Despite years of technical expertise and leadership experience, Ryan found it difficult to confidently sell his consulting services. However, when he began developing a product designed to solve a specific problem, that hesitation largely disappeared. The difference was not simply confidence in his technical abilities. It was confidence in the solution. Rather than asking potential customers to believe in his experience, Ryan could demonstrate a product shaped by their needs. His team had spoken with people in the golf industry, identified operational challenges, and incorporated that feedback into its development decisions. This shifted the conversation away from selling technical expertise toward explaining how a solution could improve a customer's business. For developers considering entrepreneurship or consulting, the lesson is significant. Customers are generally less concerned with the technologies used to build something than they are with whether it solves a problem that matters to them. Finding Customers Through Genuine Conversations Michael followed Ryan's comments by asking how he identified and connected with his target audience, particularly when traditional networking and face-to-face business relationships can be difficult to establish. Ryan explained that his interest in golf initially developed as an escape from professional burnout. After spending years immersed in technology, getting outside and playing golf provided an opportunity to disconnect from work. However, his technical curiosity eventually followed him onto the course. As Ryan visited different golf facilities, he began observing their operations, software, booking processes, and business challenges. What started as a recreational activity became an opportunity to understand an industry from the customer's perspective. He began asking questions, connecting with golf professionals on LinkedIn, publishing observations, and participating in industry discussions. Those conversations eventually helped shape Dogleg Digital's product direction. Rather than building something first and searching for customers afterward, Ryan and his team used customer relationships to identify which problems deserved attention. The approach provided valuable feedback while also establishing connections with potential future customers. AI Makes Experimentation Easier, but Quality Still Matters Rob then shifted the conversation toward AI and its ability to reduce the cost of experimenting with new software ideas. Ryan acknowledged that modern AI tools make it possible to build products that would have required significantly more time and resources only a few years earlier. His original idea for Dogleg Digital had existed for approximately three years, but the economics of traditional development made the project more difficult to pursue. AI changed what his team could realistically accomplish. However, Ryan cautioned against confusing development speed with product readiness. Generating functional code is only part of the challenge. Developers still need to consider security, usability, reliability, and the experience delivered to the customer. He specifically distinguished AI-assisted development from simply accepting whatever code an AI tool produces. Developers with strong technical foundations can use AI to accelerate implementation while recognizing weaknesses, correcting mistakes, and making informed architectural decisions. Without that expertise, organizations risk releasing products that appear complete but lack the quality required for real-world use. For Ryan, speed to market is important, but it cannot come at the expense of proper testing and quality assurance. The Human Advantage in an AI-Driven Industry Michael expanded the discussion by asking whether faster AI-powered development could reduce demand for traditional services as businesses increasingly build solutions themselves. Ryan acknowledged that some industries are already experiencing this pressure, particularly creative and marketing-related professions. Organizations may view AI as an opportunity to reduce costs, even when doing so sacrifices valuable human experience. However, he argued that experienced professionals remain essential because they understand how to use technology effectively. An AI tool can produce an output, but an experienced developer or business specialist can evaluate whether that output makes sense, identify missing requirements, and recognize problems that automated systems overlook. Ryan recalled that his approach to AI consulting involved identifying the employees who provided an organization with its greatest competitive advantages. Those were the people he wanted involved in AI adoption because their expertise could make the technology more effective. The same principle applies to software development. AI should enhance the capabilities of knowledgeable professionals rather than become an excuse to eliminate critical thinking. Leading Development Teams Beyond Vibe Coding Rob connected Ryan's perspective to the responsibilities of effective leadership. A strong technical leader does not simply assign tasks and disappear. Leaders provide direction, participate in problem-solving, mentor their teams, and help ensure that the final work meets expectations. Ryan described how Dogleg Digital combines traditional development expertise with AI-assisted processes. His business partner creates detailed product requirements documents that outline functionality, interface expectations, and visual examples. These specifications provide developers with a clearer understanding of what needs to be built before implementation begins. AI can then help accelerate the development process, allowing team members to spend more time refining functionality, improving security, and reducing defects rather than repeatedly interpreting incomplete requirements. Ryan explained that this approach makes it easier for the entire team to understand development progress. It also allows a relatively small group to pursue an ambitious product roadmap that would have been substantially more difficult using traditional methods alone. The result is not development without developers. It is a process where developers spend more of their time applying judgment and improving the finished product. Building Better Developers Means Understanding the Entire Process Ryan's experiences reinforce a recurring theme throughout this season of Building Better Developers: Technical ability alone is no longer enough to define a successful development career. AI may change how code is written, but it does not eliminate the need to understand customers, establish clear requirements, manage risk, or evaluate whether a product delivers meaningful value. The developers who thrive in this environment will be those who can connect technical capabilities with business outcomes. They will know when to use AI, when to challenge its recommendations, and when human experience must guide the final decision. Ryan's journey from corporate technology leadership to building Dogleg Digital demonstrates how those skills can create opportunities beyond traditional employment. The future of software development is not simply about writing code faster. It is about understanding the problem, building the right solution, and using AI to make the entire process better. Follow Building Better Developers for more conversations with technology leaders, entrepreneurs, and professionals who are creating opportunities beyond the code. Stay Connected: Join the Developreneur Community 👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources AI-Native Development Without the Hype: Kevin Riedl on Building Better Software With AI Build Less, Validate More: Alane Boyd on Smarter AI Development AI Workflow Automation: Start With the Problem, Not the AI Building Better Developers Podcast Vi
Artificial intelligence has dramatically accelerated software development, allowing developers to generate applications, build infrastructure, and automate repetitive tasks in a fraction of the time previously required. However, writing code faster does not necessarily mean delivering better software. Without clear requirements, thoughtful architecture, comprehensive testing, and proper documentation, AI-generated applications can introduce problems just as quickly as they solve them. In this episode of Building Better Developers, Michael Meloche and Rob Broadhead continue their discussion about building a career beyond the code by examining how AI is transforming the software development lifecycle (SDLC). Their conversation focuses on why developers must take ownership of the entire process rather than relying on AI to generate working code. Beyond Vibe Coding: Building Software With Purpose Vibe coding has become an increasingly popular approach to developing applications with AI. Developers describe what they want, allow AI to generate the implementation, and refine the results until something appears to work. While this approach can produce rapid prototypes, it may also create applications with missing requirements, security weaknesses, or architectural problems. Michael compares some AI-generated minimum viable products to structures held together with toothpicks. They may function initially, but their underlying design can lack the stability needed for production environments. The solution is not to abandon AI-generated code. Instead, developers should use AI throughout the development process while maintaining responsibility for the quality and reliability of the result. Start the AI Software Development Lifecycle With Requirements Before generating code, developers must understand the problem being solved. Requirements define what the application should accomplish, how users will interact with it, and what conditions determine whether it works correctly. Michael emphasizes the importance of requirements traceability, particularly as AI makes it easier to generate substantial amounts of code without fully understanding the intended behavior. A requirements traceability matrix connects requirements to implementation and testing, helping developers verify that important functionality has not been overlooked. AI can assist with requirements analysis by identifying missing information, organizing acceptance criteria, and developing implementation plans. However, developers must review those outputs to ensure they reflect actual business needs. Build Testing Into Development From the Beginning Testing should no longer be something developers postpone until the end of a project. AI makes it possible to generate test scripts, configure development environments, and create automated testing infrastructure early in the lifecycle. Rob recommends establishing development and QA environments alongside the initial application setup. Tools such as Docker can help developers create repeatable environments, while continuous integration and continuous delivery (CI/CD) pipelines can automatically execute tests and quality checks. Michael also recommends simplifying repetitive processes through automation. If running the complete test suite requires several commands or tools, developers can create scripts that execute those steps consistently. The goal is to make testing easier to perform and harder to overlook. Prevent AI From Overengineering Your Application Although AI can generate sophisticated architectures, more complexity does not necessarily produce a better solution. Rob describes situations where AI expanded relatively simple projects into unnecessarily elaborate environments, introducing additional components, testing steps, and infrastructure that offered little practical value. This creates a different form of development risk. Instead of failing to implement enough functionality, AI may implement far more than the project requires. Developers must review proposed architectures and question unnecessary complexity. AI should support project objectives rather than continually expanding them. Clear requirements, defined boundaries, and regular progress reviews help prevent scope creep and keep development focused on the intended outcome. Use Markdown Documentation to Maintain Context One of Michael's practical recommendations is using Markdown files to maintain project context throughout AI-assisted development. Large AI conversations can become difficult to manage, particularly when multiple tasks, implementation decisions, and revisions occur over time. A structured Markdown document can capture the problem being solved, requirements, implementation steps, completed tasks, outstanding questions, and decisions made during development. Developers can instruct AI to update this documentation as work progresses, creating a record that supports code reviews, handoffs, and future maintenance. This approach also helps prevent AI from losing focus. Instead of relying entirely on conversational history, the model can reference an approved project document that describes the current task and its boundaries. Make AI Part of Your Quality Assurance Process AI should not be limited to writing code. Developers can use it to review implementations, evaluate test coverage, inspect infrastructure, and identify weaknesses before submitting changes for peer review. Rob recommends giving AI explicit review checklists rather than relying on broad requests such as asking it to find problems. A structured checklist can direct attention toward error handling, security, missing requirements, coding standards, and potential runtime failures. Michael also describes using AI to understand undocumented legacy applications. By analyzing existing code and infrastructure, AI can help generate preliminary documentation that developers can verify and improve. These capabilities make AI valuable for both new development and maintaining established systems. Focus on Solving Problems Instead of Using AI Everywhere Rob raises an important consideration: developers should not adopt AI simply because it is available. The starting point should always be the problem that needs to be solved. Some tasks benefit significantly from AI-assisted analysis and development. Others are better handled with straightforward automation or conventional programming. AI can help developers determine the appropriate solution, but human judgment remains essential when evaluating cost, complexity, reliability, and long-term maintainability. The objective is not to maximize AI usage. It is to improve the effectiveness of software development. Own the Entire Development Process AI is changing how developers work, but it does not eliminate the need for strong software engineering practices. Requirements, architecture, quality assurance, documentation, security, and deployment remain essential components of successful applications. As AI takes on more implementation work, developers have an opportunity to devote additional attention to these responsibilities. Instead of measuring productivity only by the amount of code produced, teams can focus on delivering reliable solutions that solve meaningful problems. Stay Connected: Join the Developreneur Community 👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources The Power of Clickable Demos in the Software Development Lifecycle Software Development Requirements: Staying True to Specifications AI Governance Framework: Why Guardrails Help AI Move Faster Building Better Developers Podcast Videos – With Bonus Content
Artificial intelligence is changing how developers build software, but it is also changing how we think about security. AI can generate applications, analyze complex systems, and identify vulnerabilities much faster than traditional development processes. While these advancements provide tremendous opportunities, they also introduce new risks for developers, businesses, and anyone responsible for protecting sensitive information. In this episode of Building Better Developers, co-hosts Michael Meloche and Rob Broadhead explore AI security for developers and the challenges of protecting code, data, and intellectual property in an increasingly connected world. As part of Season 29, Building a Career Beyond the Code, their discussion examines why developers must expand their skills beyond writing code and begin taking greater responsibility for the systems they create. Why AI Changes Software Security For years, developers relied partly on the complexity of software systems to discourage unauthorized access. Although security by obscurity was never a reliable security strategy, understanding or exploiting certain vulnerabilities often required significant time and technical knowledge. AI is changing that equation by making it easier to analyze code, automate tests, and explore potential weaknesses. Rob explains that developers can no longer assume a system is secure simply because finding its vulnerabilities would take too much effort. AI-assisted tools allow someone to investigate far more possibilities than traditional manual testing, increasing the importance of deliberate security practices. However, these capabilities are not limited to attackers. Developers can use AI to improve their own testing processes, examine unusual scenarios, and identify potential weaknesses before software reaches production. The same technology that creates new security concerns can become an important part of the solution. Protecting Intellectual Property in the AI Era Michael raises another significant concern: protecting proprietary software and business information when developers increasingly rely on external AI services. Many organizations have invested years in developing specialized applications, internal processes, and unique business logic that provide competitive advantages. While common software components and established programming patterns are widely available, certain implementations and combinations of business rules may represent valuable intellectual property. Sharing that information with an external AI service requires careful consideration of the provider's data-handling policies and the permissions granted to the tool. The concern extends beyond source code. Technical documentation, customer records, internal processes, and business strategies may contain information that organizations cannot afford to expose. Developers must understand what information they are sharing and why an AI system needs access to it. AI Security Starts With Data Protection One of the central lessons from the conversation is that protecting information begins with limiting unnecessary access. Rob compares this approach to established security practices in regulated industries, where sensitive information must be handled according to specific requirements. Developers should apply those same principles when working with AI. An application may need access to a database credential to perform a task, but the AI model helping build that application generally does not need to see the credential itself. Likewise, customer information can often be replaced with representative test data when debugging software. Practical safeguards include: Keep passwords, API keys, and other secrets out of AI prompts. Limit AI access to the specific files and information required. Separate sensitive business data from application code. Review AI providers' privacy, retention, and training policies. Use appropriate access controls for repositories and internal systems. Test applications for vulnerabilities before deploying them. These practices reduce unnecessary exposure while allowing development teams to benefit from AI-assisted tools. Local AI Versus Cloud-Based AI Michael and Rob also discuss whether running AI locally provides additional protection. Local AI systems can offer greater control over where information is stored and processed, making them attractive for businesses handling proprietary or sensitive material. However, building a private AI environment introduces additional considerations, including hardware expenses, maintenance, access controls, and network security. A locally hosted model is not automatically secure simply because it operates on internal hardware. For many developers, a hybrid approach may offer a practical balance. Sensitive information can remain in controlled environments while less sensitive tasks use external AI services. The important decision is not whether every organization needs private AI, but whether developers understand the risks associated with each approach. Use AI to Strengthen Your Security Practices Rather than viewing AI exclusively as a potential threat, developers should consider how it can improve software quality and security. AI can assist with generating unit tests, reviewing code, examining authentication logic, and identifying scenarios that might otherwise be overlooked. For example, instead of asking whether an application works under normal conditions, developers can ask AI to identify unusual inputs, possible permission failures, and unexpected interactions between components. These questions encourage a more comprehensive approach to development and testing. AI-generated findings still require verification, but they can help developers investigate problems more efficiently and focus attention on areas that deserve closer examination. Building a Career Beyond the Code The changing security landscape reinforces the broader message of Season 29. Developers increasingly need the ability to evaluate systems, understand business requirements, recognize risks, and make informed technical decisions. AI can accelerate programming, but it cannot remove the developer's responsibility for the resulting product. Understanding what information should remain private, how components interact, and where vulnerabilities may exist becomes essential as software development grows more automated. The future of development is not simply about generating applications faster. It is about building software responsibly, protecting the information that matters, and using AI as a tool to strengthen the entire development process. Stay Connected: Join the Developreneur Community 👉 Subscribe to Building Better Developers for more conversations on momentum, leadership, and growth. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources AI Governance Framework: Why Guardrails Help AI Move Faster AI Governance Implementation: Turning AI Policies into Everyday Practice AI Governance Framework: Why Every Business Needs Guardrails Before AI Building Better Developers Podcast Videos – With Bonus Content



