Develpreneur: Become a Better Developer and Entrepreneur

In Part 2 of our interview with Dusty Gulleson, CEO of eResources, we explore how value-driven project discovery helps teams make better decisions, prevent waste, and build software that actually supports the business. Dusty goes deep into prioritization, budgeting, revenue-generating processes, and why discovery is essential for steering both startups and large enterprises toward meaningful outcomes. About Dust Gulleson Dusty Gulleson is a founder who never set out to build a large company—he simply followed the work, served people well, and let loyalty drive the growth. After leaving a COO role that didn't fit, he waited tables, picked up freelance web projects, and gradually built what is now eResources, a 100+ person organization spanning strategy, branding, IT services, cybersecurity, SaaS automation, and offshore teams. Born in Indonesia and now leading four thriving divisions, Dusty has grown the company without hype or outside funding, relying instead on relationships, trust, and consistent delivery. With five acquisitions under his belt and recurring revenue across industries like housing, higher education, and public health, his leadership philosophy centers on people, clarity, and service. Whether in a boardroom or a bourbon tasting room, Dusty approaches every conversation with the same question: "Where do you want to go, and how can we help?" Why Value-Driven Project Discovery Matters Many organizations want to move fast, but not necessarily in the right direction. Dusty explains that teams often fixate on long feature lists instead of business value. Value-driven project discovery flips that conversation by asking: What outcome are you trying to achieve? This shift helps clients focus on what matters most instead of chasing nice-to-have ideas. "Everyone's looking at the finish line, but no one is asking what the starting line really looks like." Using Value-Driven Project Discovery to Find True Priorities Dusty combines the 80/20 rule with the MoSCoW method to identify what the project truly needs at launch. Clients frequently bring big ideas, but through value-driven project discovery, his team uncovers the 20% that delivers 80% of the impact. The Must-Haves rise to the top naturally when tied back to real outcomes. Cutting Through Data Bloat One recurring obstacle is data collection bloat—requests to capture everything "just in case." Dusty highlights how the value-driven approach clears away unnecessary data points so teams can focus on action-driving information. This reduces complexity, speeds delivery, and saves money. Budget Reality Checks Dusty emphasizes that constraints are real and useful. Budgets shape scope, timelines, and phases. Instead of forcing everything into a fixed number, focusing on value helps teams see what is truly feasible. Often, clients don't understand how misaligned their vision and budget are until the story is mapped out clearly. Identifying Golden Processes Using Value-Driven Project Discovery Golden processes—the steps that generate revenue or sustain the business—are central to prioritization. During value-driven project discovery, Dusty helps clients identify the processes that keep the company moving. Once those are defined, secondary ideas naturally fall into later phases. "Your golden processes determine where the first dollars must go." Value-Driven Project Discovery and the Chapter-One Mindset Big visions don't require big bang releases. Dusty encourages a chapter-one approach: start small, deliver one valuable win, and build momentum. A $100 improvement today may pave the way for a $1,000 investment tomorrow. This phased approach reduces risk and increases adoption. Applying Value-Driven Project Discovery to Grow Without VC Funding Dusty's entrepreneurial journey is a testimony to value-driven thinking. He grew his company to 100+...

In this episode of the Building Better Developers Podcast, we sit down with Dusty Gulleson, CEO of eResources, to explore why story-driven discovery is the foundation of every successful software project. Dusty shares how understanding a customer's journey, motivations, and real-world frustrations leads to better outcomes than any technical requirement alone. Instead of focusing on platforms and features first, he explains why great projects begin with people and the stories behind their needs. About Dust Gulleson Dusty Gulleson is a founder who never set out to build a large company—he simply followed the work, served people well, and let loyalty drive the growth. After leaving a COO role that didn't fit, he waited tables, picked up freelance web projects, and gradually built what is now eResources, a 100+ person organization spanning strategy, branding, IT services, cybersecurity, SaaS automation, and offshore teams. Born in Indonesia and now leading four thriving divisions, Dusty has grown the company without hype or outside funding, relying instead on relationships, trust, and consistent delivery. With five acquisitions under his belt and recurring revenue across industries like housing, higher education, and public health, his leadership philosophy centers on people, clarity, and service. Whether in a boardroom or a bourbon tasting room, Dusty approaches every conversation with the same question: "Where do you want to go, and how can we help?" Why Story-Driven Discovery Matters More Than Requirements Most clients initially express their needs in bullet points, task lists, or feature requests. But as Dusty explains, those surface-level items rarely reflect the full picture. Story-driven discovery goes deeper by uncovering the context behind the request: the business pressures, the users involved, and the real outcome the client is trying to achieve. "We're customer service people first — we just happen to do technology," Dusty shared. This mindset ensures teams build solutions that support real workflows rather than assumptions. How Story-Driven Discovery Reveals Real Problems As Dusty shifted from a bullet-point mindset to a more narrative-focused approach, he began asking open-ended questions such as: Stories expose problems that requirements often hide. Rob Broadhead offered a relatable example: someone saying "the printer isn't working" may actually mean "I need this document before my meeting." Story-driven discovery uncovers the urgency, not just the symptom. Using Story-Driven Discovery Before Delivery Begins Dusty breaks every project into two essential steps: Discovery Delivery Skipping step one is where most projects fail. Without story-driven discovery, teams risk scope creep, mismatched expectations, unrealistic budgets, and frustration on both sides. "If a company won't invest in discovery, they're not serious about solving the problem." A proper discovery process creates alignment long before development begins. Avoiding AI RFP Pitfalls with Story-Driven Discovery Dusty highlighted a growing issue: AI-generated RFPs that look polished but lack practical context. These documents often include: They list features — but no story. Story-driven discovery corrects this by grounding requirements in real organizational challenges and goals. Prioritizing Needs with Story-Driven Discovery During discovery, Dusty uses two powerful prioritization methods: MoSCoW Method Must-Have Should-Have Could-Have Won't-Have (for now) The 80-15-5 Rule 80% 15% 5% These frameworks help keep projects realistic and focused on value. How Story-Driven Discovery Builds Trust At its core, story-driven discovery builds stronger relationships. Clients feel heard. Developers gain clarity. Executives stay aligned. Teams avoid...

In part 2 of our Building Better Developers conversation with Mark Struczewski (Mister Productivity), we shift from foundational habits to the modern reality of our digital world. With smartphones, notifications, social media, and AI competing for every second of our attention, managing digital distractions has become one of the most important productivity skills of our time. Mark pulls back the curtain on how our devices keep us hooked—and offers practical, simple steps to regain control of our attention before the noise takes over. About Mark Struczewski Today, we're joined by Mark Struczewski—pronounced STRU-CHESS-KEY—better known as Mister Productivity. This Houston-based coach and host of the Mister Productivity™ Podcast, with over 1,340 episodes and thousands of downloads, equips busy professionals to crush overwhelm and reclaim focus. Drawing on his corporate grit and daily running discipline, Mark shares his proven 'Distraction Detox' framework to turn digital chaos into high-impact action. Please welcome Mark! Twitter/X, YouTube, Instagram, LinkedIn, TikTok, SnapChat Turning Off the Noise: First Steps in Managing Digital Distractions Mark starts with a surprisingly bold recommendation: turn off vibration mode—permanently. Even if your phone is "muted," vibration keeps your brain on high alert. Removing it creates true silence and removes the physical stimulus that pulls you out of focus. He also stresses the importance of auditing every app notification you have. Most people tap "Allow" without thinking, and developers take full advantage of that. Mark insists you go through each app and ask: Does this notification serve me? Or is it another distraction stealing my focus? In most cases, you'll turn off 90% of them. A Notification Is a Demand for Your Attention: If your phone decides what you do next, you're not in control—your apps are. Advanced Techniques for Managing Digital Distractions Beyond simple notification hygiene, we explore more powerful ways to reinforce boundaries. 1. Use Focus Modes Intentionally Newer smartphones allow you to block almost everything while allowing a short list of apps or people through. It turns your phone into a calmer, quieter version of itself—ideal for deep work. 2. Block Websites at the Router Level Michael shares how he blocks entire sites like Facebook or news apps from his entire home network. This prevents drifting into distraction, no matter which device he picks up. 3. Silence Individual Contacts If someone sends constant memes or random texts, you can mute their message sounds without blocking them. Messages still arrive, but they don't interrupt your work. These tools aren't "nanny features"—they're modern essentials for managing digital distractions in a tech-saturated world. Social Media Boundaries: Build the Muscle, Not the Habit One area where many people struggle is social media consumption. Mark shares that he only spends 3–4 intentional minutes on platforms like X or Instagram before moving on. How? He uses scheduling tools—Meta Business Suite, Buffer, TikTok Studio—to create content in batches and avoid the endless scroll. His rule is simple: And if he's with people in person? The phone goes away—no exceptions. If someone picks up their phone mid-conversation, he stops talking or walks away. For Mark, presence is respect. True Focus Requires Presence: Being fully present strengthens your attention—even when you're not working. The AI Overload Problem We also explore a growing concern: the overuse of AI tools as substitutes for real thinking. Mark notes that people are starting to treat AI chatbots like best friends, therapists, or decision-makers. The risks include: Studies show that too much AI reliance leads to dramatically lower cognitive activity, essentially putting the...

In this episode of the Building Better Developers podcast, part of our Building Better Foundations season, Rob Broadhead and Michael Meloche sit down with Mark Struczewski, better known as Mr. Productivity. His passion is helping people get unstuck—whether through time management, clarity, or intentional focus. And in today's always-on environment, staying focused is one of the biggest challenges professionals face. The first half of our interview explores distraction awareness, practical habits, and foundational techniques for staying focused in a world full of interruptions. About Mark Struczewski Today, we're joined by Mark Struczewski—pronounced STRU-CHESS-KEY—better known as Mister Productivity. This Houston-based coach and host of the Mister Productivity™ Podcast, with over 1,340 episodes and thousands of downloads, equips busy professionals to crush overwhelm and reclaim focus. Drawing on his corporate grit and daily running discipline, Mark shares his proven 'Distraction Detox' framework to turn digital chaos into high-impact action. Please welcome Mark! Twitter/X, YouTube, Instagram, LinkedIn, TikTok, SnapChat How Mr. Productivity Built His Approach to Staying Focused Mark didn't begin his career expecting to teach productivity. After being fired from his corporate job in 2005, he tried entrepreneurship through wedding photography—an attempt he freely admits "bombed." But that failure revealed something more important: he loved teaching, coaching, and speaking. A mentor eventually encouraged him to lean into his natural strengths. Mark hadn't realized his productivity habits were unusual until someone pointed them out. Over the years, he connected those habits back to the discipline his parents instilled—do your work, do it right, and do it on time. Productivity Starts with Foundations: Many of the skills required for staying focused begin with simple, consistent discipline—not complicated tools. The Distraction Detox: A Practical Path Toward Staying Focused Mark's "Distraction Detox" is one of his simplest yet most powerful techniques. It starts with awareness—because most people don't realize how often they're pulled off track. The exercise: every single distraction Within minutes, people typically discover just how fragmented their attention has become. We're not just distracted—we're constantly distracted, and often subconsciously. You Can't Improve What You Don't See: Awareness is the first step in staying focused. What You Can Control When Staying Focused Once you have captured your distractions, the next step is to separate what you can influence from what you can't. Outside your control: Within your control: Even small adjustments can dramatically improve your ability to stay focused. The goal isn't perfection—it's reducing friction. Why Analog Tools Can Help With Staying Focused Mark strongly recommends using analog tools during focus sessions. Phones and computers invite distraction, even when you "just need to write something down." An analog notepad avoids all the digital temptations. During deep work: After the session and after taking a break, revisit the list. You'll often find that many of the items no longer matter. Most Thoughts Lose Importance After a Break: Analog tools keep you focused without triggering digital distractions. A Simple Self-Check for Staying Focused Not every distraction is obvious. Sometimes you drift into another task without realizing it. Mark offers a quick self-check that prevents accidental derailment: "Is this what I'm supposed to be doing right now?" This three-second pause helps reset your attention and prevents you from going too far down an unintended path. Start Small: The Easiest Way to Support Staying Focused Mark believes that simplicity beats complexity....

In this special holiday episode of the Building Better Foundations season of the Building Better Developers Podcast, hosts Rob Broadhead and Michael Meloche pause their usual deep-dive discussions to share meaningful Thanksgiving reflections for developers. This annual tradition goes beyond technology and process—it centers on gratitude, growth, and the people who shape our journeys. Why Thanksgiving Reflections for Developers Matter Even though the recording takes place before the holiday, the episode releases just as listeners gather for Thanksgiving. Rob's signature "gobble gobble" sound kicks things off, marking another year of stepping back to appreciate the wins, the lessons, and the relationships that make the development life meaningful. Thanksgiving reflections for developers remind us that progress isn't just code—it's community, resilience, and perspective. Two Sides of the Year: Thanksgiving Reflections for Developers Rob begins with a candid look at a year of downsizing, simplifying, and major life changes. The process has been exhausting but also freeing—removing clutter, shifting priorities, and making room for what matters most. Michael shares his own version of growth: completing a massive project, evolving his consulting business into a full-fledged software company, and learning hard lessons through the transition. The challenges brought long hours and stress, but they also delivered clarity and direction for the future. These Thanksgiving reflections for developers capture a familiar truth: every challenge is a stepping stone. Gratitude for People: Core Thanksgiving Reflections for Developers Both hosts highlight the importance of people above all else. Rob's Reflections Michael's Reflections The strongest Thanksgiving reflections for developers are always about people—not projects. Technology and Connection: Modern Thanksgiving Reflections for Developers Rob notes how technology has made it possible to work from almost anywhere—thanks to wireless tools, remote access, and communication platforms like Zoom and FaceTime. Michael adds that technology is powerful when used for real connection—not just scrolling or posting, but collaborating, calling, and being present with others. These Thanksgiving reflections for developers highlight a key truth: tech connects us, but only if we use it intentionally. Traditions and Joy: Lighthearted Thanksgiving Reflections for Developers The episode also brings fun holiday traditions into the conversation: Stranger Things These lighthearted moments remind us that gratitude isn't just serious—it's joy, nostalgia, and shared experiences. Community Appreciation: Final Thanksgiving Reflections for Developers The hosts close with heartfelt thanks to the podcast community. Listener stories, project successes, and feedback fuel the show's mission to help developers grow, improve, and thrive. "Go out into the world and be thankful." — Building Better Developers Podcast Thanksgiving Reflections for Developers: Build Better Foundations This Thanksgiving episode delivers a warm reminder that building better developers begins with building better foundations of gratitude—for people, for opportunities, for growth, and for technology that keeps us connected. From Rob and Michael: Happy Thanksgiving—and stay thankful. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Gratitude and Growth: A Thanksgiving...

Thanksgiving week is here, and with it comes the perfect opportunity for developers to slow down, unwind, and refocus. In this special pre-holiday episode of the Building Better Developers podcast, Rob and Michael step away from the regular Building Better Foundations theme to talk about travel mishaps, gaming plans, personal downtime, AI experiments, and practical Thanksgiving tips for developers who want to rest and still grow. Whether you're staying home, traveling, or juggling family plans, this episode delivers simple and meaningful insights to help you make the most of the holiday season. Why Thanksgiving Matters for Developers For nearly a decade, the podcast has featured Thanksgiving episodes as a fun tradition—lighter, more personal, and focused on gratitude. As Rob and Michael reflect on the year, they share stories and ideas every listener can relate to. It's also a moment to pause and consider meaningful Thanksgiving tips for developers who are used to fast-paced schedules and tight deadlines. Holiday Chaos Happens—Laugh and Keep Moving The episode kicks off with Rob's comedy-level travel disaster involving early check-ins, confusing airline mishaps, and even a sushi order gone terribly wrong. Despite the chaos, he reminds us that embracing humor is one of the most underrated Thanksgiving tips for developers dealing with holiday stress. Embrace the unexpected. Use holiday disruptions as forced downtime to reset. Gaming, Rest, and Making Time for Fun Developers love learning—but they also love games. Rob talks through his Steam Deck frustrations while trying to play Blood Bowl 3, and Michael shares his goal to finally play his untouched birthday gift, Pokémon ZA. Gaming becomes more than entertainment—it's one of the best Thanksgiving tips for developers who need a mental break. The message is simple: Make room for joy. Let yourself play. Exploring AI, Creative Coding, and One-Day Projects Instead of doom-scrolling, Rob suggests exploring AI tools—both for fun and learning. Michael adds that Thanksgiving is a perfect time for a bite-sized coding experiment or "kitchen sink app" to explore new Java, Spring, or Python updates. This is where holiday downtime becomes a strategic advantage. You can recharge while sharpening skills. Try a no-pressure mini-project. One day of playful coding can spark major creativity. Disconnecting to Reconnect: The Heart of the Season Thanksgiving isn't just time off—it's time together. Michael encourages listeners to unplug, enjoy family time, watch holiday specials, and take a real break from screens. Spending quality time with loved ones is one of the most important Thanksgiving tips for developers who often live in digital worlds. Even for those working through the holiday week, a quieter office can provide opportunities to reconnect with coworkers or simply enjoy a more relaxed pace. Black Friday Deals and Leveling Up Your Toolkit Rob and Michael wrap up with practical advice: use holiday sales wisely. From software subscriptions to hardware upgrades, tech deals can help developers invest in their craft. They even recommend tools like CamelCamelCamel for smarter price tracking—another useful Thanksgiving tip for developers planning their 2026 goals. Final Thoughts: Rest Today, Grow Tomorrow Thanksgiving is a rare chance to step back, breathe, and appreciate what matters most. Whether you're experimenting with tech, catching up on games, visiting family, or indulging in post-turkey naps, embrace the pause. Because the work—and the opportunities—will be waiting after the holiday glow fades. For now, apply these Thanksgiving tips for developers, enjoy the season, and recharge for the journey ahead. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether...

Choosing the right pricing model can make or break a project, and understanding fixed bid vs time and materials is essential for developers, consultants, and business owners alike. In Part 2 of our Building Better Foundations interview with Charly Leetham, we explore the complexities behind scoping work, managing expectations, and balancing fairness with sustainability. This conversation dives into real experiences—both successful and painful—that highlight how important clarity is when building custom software or digital solutions. About Charly Leetham Charly Leetham brings more than 40 years of hands-on experience in building practical, reliable systems for small businesses. She earned her amateur radio license at 13, became an electronic engineer by 21, and completed her MBA while working full-time and raising two young children. Her career has spanned technical support, sales, project management, and client services, giving her a deep understanding of both technology and people. After running multiple franchises and overcoming a major business setback, she founded Ask Charly Leetham—now a long-standing digital services company supporting clients across Australia, the U.S., and beyond. Known for her clear, no-nonsense approach, Charly specializes in turning complex tech into simple, workable solutions. She also hosts Rise and Shine – Your Business Tech Boost, offering practical guidance to business owners who want answers they can trust. Facebook, Twitter / X, YouTube, Instagram, LinkedIn, Website Fixed Bid vs Time and Materials: When Fixed Pricing Works Charly begins by explaining that fixed bid pricing only works when the scope is tight, clear, and measurable. If she can define every deliverable—content length, number of pages, number of images, required effort—then fixed pricing is a win for both sides. Everyone knows what will be delivered and at what cost. "Fixed bid requires fixed scope. If you can't list every deliverable, you shouldn't fix the price." – Charly Leetham But when the work involves unknowns, research, or variable technical challenges, time and materials become the safer, more honest approach. When ambiguity is present, Charly often starts with a one-hour or two-hour discovery block before offering a detailed estimate. Fixed Bid vs Time and Materials: Owning the Estimate One powerful theme from Charly's perspective is ownership. If she commits to a fixed price and the work takes longer than expected—yet stays within the original requirements—she believes it's her responsibility, not the client's problem. She compares it to car maintenance: if a mechanic quotes you a fixed price for an oil change, you don't pay extra because it took them longer internally. "If I overestimated my abilities, that's on me—not the client." Michael shares a similar story from his own experience: a large fixed-bid software project that went significantly over budget due to missed requirements and "muscle memory" business processes the client never mentioned. Even after months of discovery, unseen complexity still appeared late in development—forcing a learning experience the hard way. Hidden Requirements: The Biggest Threat to Fixed Bid Work One of the biggest takeaways from the episode is how hidden systems and unspoken workflows can wreck a fixed price project. Rob and Charly both describe situations where: These are the real reasons fixed bids go off the rails. Not because developers fail—but because the truth of the workflow is often hidden beneath assumptions. If you don't see the real workflow, your scope is incomplete. Good requirements gathering means observing actual work—not just interviewing leadership. Learning vs Billing: Handling Complexity Fairly Another powerful point from Charly is knowing when to charge for expertise and when to absorb learning time. She tells a story about...

Building a strong company starts with strategic foundations for business growth. In Part 1 of our interview with Charly Leetham, we explore how clarity, customer understanding, and simple systems help businesses grow with confidence. Her insights show how the right strategic groundwork leads to long-term success. About Charly Leetham Charly Leetham brings more than 40 years of hands-on experience in building practical, reliable systems for small businesses. She earned her amateur radio license at 13, became an electronic engineer by 21, and completed her MBA while working full-time and raising two young children. Her career has spanned technical support, sales, project management, and client services, giving her a deep understanding of both technology and people. After running multiple franchises and overcoming a major business setback, she founded Ask Charly Leetham—now a long-standing digital services company supporting clients across Australia, the U.S., and beyond. Known for her clear, no-nonsense approach, Charly specializes in turning complex tech into simple, workable solutions. She also hosts Rise and Shine – Your Business Tech Boost, offering practical guidance to business owners who want answers they can trust. Facebook, Twitter / X, YouTube, Instagram, LinkedIn, Website Strategic Business Foundations Start With the Right Questions Charly opened the conversation with a key insight: you cannot build a strong business without asking strong questions. These questions shape your strategic business foundations and guide the decisions that follow. "Before you build, you must know what you're building and why." – Charly Leetham Too many business owners rush into action without defining their audience or validating the problem they're trying to solve. Charly recommends asking: These questions are simple, yet they prevent misalignment and wasted effort. Understanding Your Customer Is Key to Strategic Business Foundations Charly highlighted that meaningful customer insight is essential. Many entrepreneurs claim to understand their customers, but they rely on assumptions rather than evidence. This weakens their strategic business foundations and often leads to products that miss the mark. She encourages leaders to: "Your customers will tell you what they need—if you give them space to speak." This approach ensures your solution fits the customer's world—not just your idea of it. Simplicity Strengthens Strategic Business Foundations One of Charly's most powerful insights is the importance of simplicity. Many founders believe complexity signals value, but Charly argues that clarity creates far stronger strategic business foundations. She recommends: "If your customer can't understand what you do, they won't buy from you." Simplicity improves messaging, operations, and customer experience. Systems and Processes Anchor Your Strategic Business Foundations According to Charly, strong systems are not optional—they're essential. Businesses often wait too long to document processes or create workflows. This delay weakens their strategic business foundations and makes growth harder. Systems help businesses: Templates, automations, and repeatable processes transform chaos into structure. Final Thoughts: Building Strategic Business Foundations That Last Part 1 of our interview with Charly Leetham offers a powerful reminder: success begins with strategic business foundations. When you ask the right questions, understand your customers, simplify your offerings, and build systems early, you create a business that can grow with confidence and purpose. Stay tuned for Part 2, where we explore how automation, alignment, and intentional tools help businesses expand on these foundations and operate more efficiently. Stay Connected: Join the Developreneur...

In this Building Better Foundations episode, hosts Rob Broadhead and Michael Meloche continue their conversation with Greg Lind, founder of Buildly and OpenBuild. They explore how automating quality in software development changes the way teams build and test software. Greg explains that AI and automation can improve collaboration and prevent errors before they happen. As a result, teams can deliver code faster, maintain consistency, and build stronger foundations for long-term success. Greg's experience across startups and open-source projects has shown him one simple truth: quality can't be bolted on at the end—it must be built into the process from the start. "QA often gets left until the end. But it has to start from the developer." — Greg Lind About the Guest — Greg Lind Gregory Lind is an American software developer, author, and entrepreneur with over 20 years of experience in open-source innovation, software efficiency, and team transparency. He's the founder of Buildly in Brooklyn and co-founder of Humanitec in Berlin, helping organizations modernize systems through collaboration and automation. A frequent speaker at Open Gov and Open Source conferences, Greg advocates for open, scalable solutions and smarter software processes. His upcoming book, "Radical Therapy for Software Teams" (Apress, 2024), explores how transparency and AI can transform how teams build software. Automating Quality Starts with Developers Greg explains that every developer should think like a QA engineer. Testing isn't something done after code is written—it's something built into how code is written. He stresses that developers should write unit tests early and often, focusing on verifying object-level functionality rather than simply checking UI forms or user flows. QA should then expand from there, building additional layers of testing as complexity grows. "I learned that I need to think like a QA person from the very beginning." — Greg Lind By shifting QA upstream, teams reduce rework, accelerate release cycles, and improve code confidence. Automating Quality in Software Development Across the Pipeline At Buildly, Greg and his team integrate testing automation into every stage of the development pipeline. Tools like Robot Framework and Selenium handle both front-end and API-level testing, while Git pre-commit hooks ensure tests are written before code even reaches the repository. "You have to make sure those tests have already been written. If there isn't a test, it pulls it back and says, 'make sure that you have your test in before you check it in.'" — Greg Lind This system ensures that developers can't skip testing—and that QA has visibility into every build. It's a workflow that blends accountability with automation, reinforcing a culture where quality is everyone's job. AI's Role in Continuous Improvement Greg sees AI as a critical ally in maintaining software quality at scale. Rather than replacing QA engineers, AI helps automate the tedious parts of the process—like generating basic test cases, reviewing commits, or spotting missing standards in pull requests. "I don't mean to put that out there as a replacement for QA in any way. Developers need to be in the process, and QA are developers as well." — Greg Lind AI's ability to analyze large volumes of commit history and testing data helps teams identify trends, recurring issues, and areas for improvement. This frees human testers to focus on strategic validation, exploratory testing, and creative problem-solving. Transparency, Collaboration, and Learning Another major theme Greg highlights is transparency. Buildly's AI-driven summaries and automated reports make quality metrics visible to everyone on the team—developers, product managers, and QA alike. "It's not about who wrote the bad test—it's a learning process. Every pull request is an...

In part one of this Building Better Foundations interview, hosts Rob Broadhead and Michael Meloche talk with Greg Lind, founder of Buildly and OpenBuild, about bridging the gap in software development through AI, automation, and collaboration. Greg shares how modern teams can overcome silos, strengthen communication, and build transparency into their workflows — creating stronger, more adaptive foundations for success in today's fast-paced, AI-driven world. "We wanted to bring developers and product managers into one tool—so they could build together rather than as two separate teams." — Greg Lind About the Guest — Greg Lind Gregory Lind is an American software developer, author, and entrepreneur with over 20 years of experience in open-source innovation, software efficiency, and team transparency. He's the founder of Buildly in Brooklyn and co-founder of Humanitec in Berlin, helping organizations modernize systems through collaboration and automation. A frequent speaker at Open Gov and Open Source conferences, Greg advocates for open, scalable solutions and smarter software processes. His upcoming book, "Radical Therapy for Software Teams" (Apress, 2024), explores how transparency and AI can transform how teams build software. Bridging the Gap Between Teams and Tools Greg's journey toward bridging the gap started years ago while working with Humanitech in Berlin, where he saw firsthand how poorly connected processes caused frustration and inefficiency. Traditional Agile frameworks, while once revolutionary, began to buckle under the pressure of multi-repo, multi-cloud, and AI-driven development. "Agile started to break under the pressure—especially when we introduced AI-driven tools and CI/CD pipelines. The cycles just weren't fast enough." — Greg Lind To solve this, Buildly introduced a Rapid AI Development (RAD) process — a modern evolution of Agile that supports faster, release-based cycles rather than rigid sprints. It's an approach designed to keep pace with today's distributed teams and complex workflows. Bridging the Gap Through Automated Communication At the heart of Buildly's philosophy is a belief that communication shouldn't slow developers down — it should empower them. By integrating tools like Trello and GitHub, Buildly connects product and sprint backlogs into one transparent view. Developers' commits, issues, and updates automatically feed into team dashboards, reducing the need for endless meetings and manual updates. "You shouldn't have to explain what you did yesterday. Your commits already tell that story." — Greg Lind This approach allows teams to focus on outcomes rather than overhead — building trust, visibility, and true alignment across departments. It's automation as a bridge, not a barrier. Using AI to Bridge the Gap Between People and Process While Greg embraces AI's potential, he warns against depending on it too heavily. AI is great at identifying tasks and patterns, but humans still bring creativity, empathy, and strategic thinking to the table. "AI can tell you what's urgent, but it can't understand what's important." — Greg Lind In Greg's view, AI should be a co-pilot — helping teams filter information, automate repetitive work, and focus on higher-value decisions. By balancing automation with human insight, teams can bridge the gap between efficiency and innovation. Empowering Developers to Bridge the Gap Themselves Greg encourages developers not to wait for leadership to fix broken processes — but to take initiative. Automate your own workflows, visualize your backlog, and demonstrate how better systems can look in practice. "Even if you have to automate your own backlog—do it. Show your team what better looks like." — Greg Lind This proactive mindset transforms teams from reactive to adaptive, ensuring that everyone contributes to bridging the gap between...

In this follow-up episode of Building Better Developers, Wes Towers returns to share his hands-on approach to WordPress SEO for developers. From choosing lean tools like Kadence and Rank Math to using AI for faster content creation, Wes explains how developers can simplify design, speed up performance, and stay visible in an AI-driven search world. Key Idea: Smart WordPress SEO for developers isn't about more plugins—it's about clarity, speed, and content that stands out across search and AI platforms. About the Guest — Wes Towers Wes Towers is the founder of Uplift 360, a Melbourne-based digital agency that helps builders and trades turn websites into trusted, lead-generating tools. With over 20 years of hands-on experience, Wes focuses on authenticity, clear strategy, and measurable growth — no fluff, just results. Through his work and podcast appearances, he shares practical insights on niching for developers, SEO, and building trust in an AI-driven world. 🔗 Learn more: uplift360.com.au 💼 Connect: LinkedIn | Instagram | Facebook| X WordPress SEO for Developers: One Concept, Less Confusion Early in his career, Wes pitched three designs for everything. Results? Slower decisions and muddier direction. Today, he presents one, well-researched concept informed by a quick sitemap, a handful of reference sites, and the client's style preferences. It shortens cycles and raises satisfaction—because clarity beats choice overload. Client Script: "We'll align on a single, focused concept so you spend less time deciding and more time winning work." WordPress SEO for Developers in the LLM Era Traffic patterns are shifting as answers surface inside platforms like Google's AI Overviews, ChatGPT, and Perplexity. Clicks may drop even when visibility rises. Wes's response: publish high-quality, experience-rich content that LLMs want to cite. only you If content is generic, LLMs will ignore it. Specificity is the new SEO. WordPress SEO for Developers: AI Drafts + Human Stories Wes drafts with AI, then has clients weave in real stories—field photos, client quotes, job constraints, and outcomes. That blend delivers speed and originality. Quick Win: Create a "First-Draft Prompt" template and a "Brand Voice Prompt" you reuse across pages. WordPress SEO for Developers: Performance & CDN Reality Caching and CDNs confuse non-technical clients—and sometimes even teams. Wes's guidance: Start with good hosting. Cache carefully. Use a firewall/CDN Optimize images Caution: Don't "optimize" yourself into a support spiral. Fewer, reliable plugins beat a kitchen-sink stack. WordPress SEO for Developers: A Lean, Fast Stack Wes's current go-to recipe favors Gutenberg blocks and keep-it-simple plugins: Theme/Builder:Kadence SEO:Rank Math Security:WordfenceSucuri Forms:Gravity Forms Avoid: Stack to Copy: Kadence + Rank Math + Gravity Forms + Wordfence/Sucuri + a single cache plugin on quality hosting. WordPress SEO for Developers: Getting Started (or Leveling Up) For newcomers and refreshers alike, Wes recommends: Map a one-page sitemap Present one concept Draft with AI, finish with proof: Harden and speed up: Measure what matters: Publish consistently: Bottom Line: WordPress SEO for developers isn't about clever hacks—it's about repeatable execution, authentic content, and a lean stack that stays fast after handoff. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional...

In this Building Better Foundations episode, Rob Broadhead and Michael Meloche talk with Wes Towers of Uplift360, a Melbourne-based digital agency serving the construction and trades industry. The discussion centers on niching for developers—how focusing on a specific audience helps software teams and agencies communicate better, deliver faster, and build lasting client trust. Key Idea: Niching for developers isn't about limiting opportunities — it's about amplifying your expertise and clarity in the markets that need you most. About the Guest — Wes Towers Wes Towers is the founder of Uplift 360, a Melbourne-based digital agency that helps builders and trades turn websites into trusted, lead-generating tools. With over 20 years of hands-on experience, Wes focuses on authenticity, clear strategy, and measurable growth — no fluff, just results. Through his work and podcast appearances, he shares practical insights on niching for developers, SEO, and building trust in an AI-driven world. 🔗 Learn more: uplift360.com.au 💼 Connect: LinkedIn | Instagram | Facebook| X From Process Talk to Outcomes That Win Wes highlights that clients, especially those in the trades, don't care about the tech stack or your process — they care about outcomes. Developers who focus on solving the real business problem instead of selling the "how" stand out immediately. Clients want: Pro Tip: Translate every technical feature into a tangible outcome. Instead of "faster hosting," say "Your pages load instantly, turning more visitors into paying customers." Niching for Developers Through Customer Venting and Differentiation Wes's secret? The "venting session." He asks clients to privately vent about competitors and what frustrates them about the industry. The complaints reveal what not to be — and the positive opposites become the brand's differentiators. Try This: Let clients rant. Capture their pain points, flip them into value statements, and turn those into marketing headlines for your site or proposal. AI and Niching for Developers: Staying Competitive and Streamlined A wake-up call came when Wes's company valuation dropped because of AI disruption. Instead of resisting, he integrated AI into his processes — automating repetitive SEO tasks and improving build speed without losing quality. How AI supports niching for developers: Callout: AI can't replace niche expertise. It just multiplies it — when used strategically. Trust First: Niching for Developers in Crowded Markets With privacy concerns on the rise, trust is the new lead magnet. Customers won't even trade an email for a free download unless they trust the brand. Developers and agencies must show reliability through transparency, proof, and consistent communication. Trust builders that work: Pro Insight: When you niche deeply, your audience feels understood — and trust grows faster. Maintenance Cadence: Niching for Developers Includes Ongoing Care Wes warns that many clients still see websites as "set it and forget it." With WordPress, especially, updates and security patches are constant. Maintenance is a vital part of niching for developers — protecting clients' investments and your reputation. Client Script: "We don't just build your site — we maintain it so it stays fast, secure, and effective." Action Steps: Niching for Developers This Week Apply these takeaways now: Bottom Line: Niching for developers builds clarity, focus, and trust. It's not about doing less — it's about doing what matters most, better than anyone else. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at...

In this episode of Building Better Developers, hosts Rob Broadhead and Michael Meloche revisit one of the most essential pillars of software development — requirements gathering. As part of the Building Better Foundations season, this discussion dives deep into why strong requirements are not just documentation — they're the blueprint of success for every software project. From Classroom Rules to Real-World Clarity Rob opens the discussion by highlighting a gap many developers face: they're trained to solve problems, but not to define them. In classrooms and coding bootcamps, students are handed requirements. But in the real world, success depends on a developer's ability to uncover and validate them. Early-career developers often transition from following fixed assignments to navigating vague project goals. Rob emphasizes that the most important skill they can develop is asking smart, clarifying questions — turning fuzzy instructions into actionable tasks. For example, if a task says, "Add two numbers," the experienced developer asks: "Strong requirements start with strong questions. Don't just do the task — define it." – Rob Broadhead The Recipe Analogy: How Cooking Teaches Strong Requirements Michael brings the discussion home with a relatable metaphor — cooking. Every recipe is a set of instructions, ingredients, and steps. If you change them — like adding raisins to chocolate chip cookies — you get the wrong result. The same goes for software. Weak requirements lead to unpredictable results. Strong requirements lead to consistent, repeatable success. Each requirement should be clear, testable, and unambiguous — something that can be verified as true or false. Ambiguous statements like "allow users to enter data" need refinement: What kind of data? Is it numeric, text, or secure input? Without that clarity, developers risk misunderstanding the goal. The "And Then What?" Approach to Strong Requirements Rob introduces his favorite tool for strengthening requirements: the "And then what?" method. After each answer, ask what happens next. And then what? And then what happens if it fails? Each "and then" uncovers gaps, edge cases, and overlooked scenarios. Great developers think like curious toddlers — always asking "why" and "what next" until every path is clear. Speaking the Same Language Another foundation of strong requirements is communication. Many clients express what they want, but not what they need. Developers must bridge that gap, asking why to understand the purpose behind each request. Michael reminds us that non-technical stakeholders often assume things are apparent — but what's evident to them might be missing from the documentation. Practical requirements gathering bridges those blind spots before development begins. Building for the Future with Strong Requirements Finally, both hosts stress scalability. Systems designed without future growth in mind will quickly collapse under success. Strong requirements anticipate change — considering performance, user volume, and integrations from day one. "If your system can't scale, your foundation wasn't strong enough." – Michael Meloche Key Takeaway Strong requirements aren't just a step in the process — they are the process. They transform ideas into actionable blueprints, prevent scope creep, and ensure teams deliver software that lasts. To build better software, start by building better foundations — with strong requirements. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting...

In this episode of Building Better Foundations on the Building Better Developers podcast, hosts Rob Broadhead and Michael Meloche explore one of today’s fastest-growing software trends—vibe coding. Vibe coding blends human creativity with artificial intelligence, allowing developers to describe what they need and let AI generate code in real time. It’s a revolutionary idea that promises speed, flexibility, and innovation—but it also raises new questions about structure, consistency, and long-term maintainability. What Exactly Is Vibe Coding? At its core, vibe coding means coding collaboratively with AI. Developers outline the functionality, design, and structure they want, while AI produces the initial code and suggestions. This makes it ideal for rapid prototyping and minimum viable products (MVPs)—helping teams turn ideas into functioning apps in record time. “You’re using AI to generate some code and basically allowing AI to code as you go,” Rob explains. The catch? Without solid foundations and thoughtful architecture, the speed of AI-generated code can create technical debt—making long-term projects harder to maintain or scale. Using AI as a Junior Developer Rob compares vibe coding to collaborating with a junior or mid-level developer: capable and fast, but in need of clear direction. “If you define your architecture, style, and structure clearly,” he says, “AI can build pages and components that fit your system.” The best results come from specific, incremental prompts. Instead of asking for an entire app, start small—perhaps a single navigation bar or form layout—and refine from there. Each small win compounds into a solid, scalable solution. From User Stories to Smart Code Michael takes the discussion further, explaining how test-driven development (TDD) and user stories make vibe coding more reliable and efficient. “If you walk AI through the user story—‘as a user, I need to log in’—you’ll get a better, more useful result,” he says. Start by asking AI to write a test case for your feature. Once that test passes, ask it to generate the code. This simple adjustment keeps AI aligned with real-world behavior and helps non-coders understand how requirements become working software. 5 Pro Tips for Smarter Vibe Coding Be Specific: Start Small: Iterate Often: Think in Tests: Validate Needs: Avoiding the Trap of Confirmation Bias Michael also warns against confirmation bias—believing AI’s output simply because it sounds right. “AI can tell you what you think you need, not what you actually need,” he cautions. To stay grounded, developers should regularly check with clients or end users to confirm that AI-generated solutions align with real requirements. AI is a tool, not a truth engine. From Prototype to Production While vibe coding is perfect for prototypes, Rob reminds listeners that production-ready systems still need human craftsmanship. Clean architecture, maintainable code, and performance tuning remain crucial for success. AI can accelerate development—but it’s still the developer’s job to ensure that the final product is secure, scalable, and sustainable. Final Thoughts on Vibe Coding Vibe coding represents a major shift in how developers think about building software. Used wisely, it enhances creativity, speeds up delivery, and reduces repetitive tasks. Used carelessly, it can create chaos and confusion. As Rob and Michael emphasize, the secret lies in balance: human insight plus AI efficiency. Together, they form the foundation for faster, smarter, and better software. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you’re a seasoned developer or just starting, there’s always room to learn and grow together. Contact us at info@develpreneur.com with...

In this episode of Building Better Developers, hosts Rob Broadhead and Michael Meloche continue their conversation with Agustin Morrone, CEO and co-founder of Vintti, a company improving the remote hiring process for U.S. and Canadian businesses across Latin America. From his base in Barcelona, Agustin explains how Vintti combines AI, automation, and cultural alignment to build remote teams faster while keeping people at the center. Vintti’s mission remains clear: help companies hire top Latin American talent in under 21 days, saving up to 60 percent on payroll while maintaining quality and trust. In Part 2, we explore how Vintti’s evolving systems make the remote hiring process smarter and more scalable. Using AI to Strengthen the Remote Hiring Process Vintti’s young, tech-driven team approaches work with an “AI-first mindset.” Rather than replacing people, AI removes repetitive tasks that slow down the remote hiring process. Originally, every interview was manual. Now, AI manages more than half of all first-round interviews, rating English proficiency and technical expertise. Recruiters then step in to evaluate communication style and cultural fit. “AI helps us focus on what matters most,” Agustin says. “It saves time and allows our recruiters to build stronger relationships.” Automation Tools That Simplify Remote Recruitment Vintti automates much of its communication and reporting to improve efficiency. Instead of sending raw resumes, it builds custom, client-ready CVs using AI. Each profile merges data from interviews, LinkedIn, and client discussions into a consistent, easy-to-read document. Automated follow-ups and feedback loops help recruiters stay engaged throughout the remote hiring process, keeping clients informed without losing the human connection. Automation drives consistency, but empathy drives connection. Human Insight: The Key to Remote Hiring Success AI helps identify top candidates, yet it can’t replace intuition. Recruiters still assess tone, enthusiasm, and motivation—critical elements of cultural fit. Similarly, Vintti maintains personal conversations with each client to understand company culture before sourcing talent. This ensures every step of the hiring process reflects both human judgment and data-driven insight. Testing, Learning, and Improving the Remote Hiring Process Experimentation fuels progress at Vintti. Recruiters rely heavily on LinkedIn but constantly test new tools to expand reach and reduce friction. “We test, compare, and adapt,” Agustin explains. “If a tool adds value, we scale it. If not, we move on.” This culture of experimentation keeps the hiring process innovative and resilient. Cultural Patterns in Global Recruiting Regional patterns help Vintti understand candidate strengths. Colombian professionals often shine in customer support, Argentines excel in sales, and Mexican talent frequently leads in finance. However, Agustin cautions against stereotyping. “Patterns are helpful, but people are unique,” he says. That perspective ensures fairness and flexibility in every hiring process decision. Supporting Global Teams After Placement Once hired, contractors integrate fully into client organizations. Vintti provides behind-the-scenes support—helping with taxes, communication skills, and professional development—while avoiding cultural interference. Support Principle: Empower independence and provide structure. This hands-off guidance strengthens relationships and keeps the hiring process transparent from start to finish. Discipline and Growth in the Hiring Journey Internally, Agustin looks for self-motivated people who take ownership. He values discipline over motivation, believing that commitment leads to better long-term outcomes. “Motivation fades, but discipline lasts,” he...

In this episode of Building Better Developers, hosts Rob Broadhead and Michael Meloche speak with Agustin Morrone, CEO and co-founder of Vintti. The company helps U.S. and Canadian businesses master remote hiring across Latin America. From Barcelona, Morrone shares how his bootstrapped startup is growing fast while staying true to its people-first culture. Vintti’s mission is simple yet bold. The team helps companies build remote Latin American teams in less than 21 days. They often save clients up to 60% on payroll costs. More importantly, they deliver strong talent that fits culturally and professionally. Morrone’s vision redefines remote hiring as a human-centered process built on trust and shared goals. From Argentina to Barcelona: Building a Remote Hiring Vision Agustin Morrone was born in Argentina and now lives in Spain. After earning an MBA, he joined a startup that automated financial planning for global firms. There, he discovered a major problem. Many companies could automate their systems, yet they struggled to find qualified remote professionals. “There was a shortage of skilled professionals who understood the U.S. market and could deliver real value,” Morrone explains. That insight inspired him to launch Vintti, a company dedicated to remote hiring for North American clients. The focus on Latin America made sense. The region shares time zones, values, and strong English skills. This approach ensures clients receive not only technical expertise but also a cultural match. Building Trust Through Secure Remote Hiring When companies hire for finance or accounting roles, data security becomes critical. Morrone explains how Vintti protects both sides of the partnership. “We never access client data. Clients install their own software and security measures,” he says. The company runs detailed background and reference checks. It verifies professional histories and technical skills. As a result, every candidate meets strict ethical and professional standards. This attention to detail makes remote hiring safe and reliable for both clients and talent. Culture and Fit: The Heart of Remote Hiring Success About 85% of Vintti’s workforce operates as contractors. However, the company goes far beyond quick placements. Morrone believes the hardest part of remote hiring is not skill—it’s culture. “The toughest thing to find is cultural alignment,” he says. “Technical skills matter, but culture determines success.” Rather than keeping a bench of idle candidates, Vintti searches for the perfect match each time. Every placement aligns with a client’s values, work style, and long-term goals. As a result, teams perform better and relationships last longer. Scaling Remote Hiring Through Relationships and Community Growth at Vintti has come through real relationships, not ads. Paid campaigns have been challenging. However, outreach-driven marketing has delivered great results. “We focus on relationships—LinkedIn engagement, conferences, and meeting clients face-to-face,” says Morrone. This people-first approach gives Vintti a clear advantage in today’s remote hiring market. After the pandemic, many leaders wanted personal connection again. Therefore, Vintti’s direct and genuine approach builds credibility and long-term trust. Leadership Lessons in Remote Hiring Interestingly, one of Vintti’s biggest challenges is its own remote hiring. Morrone personally interviews each finalist to protect company culture. “As CEO, I see myself as the guardian of our culture,” he explains. “I hire people with ambition, alignment, and attitude.” To support growth, Vintti invests heavily in processes and standard procedures. These systems ensure consistent onboarding and operations. “When you grow fast, it’s hard to document everything,” Morrone admits. “But once you find what works, you have to capture it...

In this continuation of the Building Better Developers interview series, Kevin Adelsberger—owner of Adelsberger Marketing—returns to explore how businesses can refine their identity and message once the foundation is set. This episode focuses on branding and marketing fundamentals, uncovering what really drives connection, credibility, and growth. “Thinking about your brand and overall messaging is more important than color or font,” Kevin explains. “If your brand feels disconnected, no color will fix that.” The conversation moves beyond logos and design to the deeper work of communicating who you are and what you stand for—authentically and consistently. Branding: More Than Color and Fonts While many companies spend hours perfecting color palettes, Kevin challenges that mindset. He believes color psychology is largely a myth, with few industries where color directly affects success. Instead, businesses should focus on how their messaging and visuals align. Fonts, he adds, do have power. The right typeface can instantly signal tone—formal, playful, or high-tech—but only when used intentionally. “If you want to be a fun, crazy brand and your visuals feel stiff, no amount of color will fix the disconnect.” A strong brand reflects alignment: visuals, tone, and message working together to create trust and recognition. Keep Your Message Steady, but Your Website Fresh Kevin offers a balanced approach to maintaining your digital presence. Instead of obsessing over analytics or daily edits, he recommends structured consistency: monthly or quarterly inbound marketingoutbound efforts “Most people never look at their website after it launches—that’s a bigger problem than over-tweaking it.” Once your brand identity and message are established, spend more time sharing your expertise rather than endlessly adjusting pixels. Marketing Fundamentals for Beginners For entrepreneurs and small business owners who feel lost, Kevin recommends a few key resources to master branding and marketing fundamentals: Building a StoryBrand by Donald Miller EntreLeadership by Dave Ramsey The Four Conversations by Blair Enns Kevin also emphasizes simple, actionable steps: competitive advantages one-liner Learn from Competitors—Ethically Healthy competition can inspire innovation. Kevin encourages learning from peers and even collaborating with them. He participates in groups like the Bureau of Digital, a network of agency owners who share ideas without direct competition. “Artists steal,” Kevin jokes, “but the goal is to make other people’s ideas better, not to copy them.” For those in established industries, he suggests finding professional or ownership groups—places where you can share, learn, and grow together. AI’s Impact on Marketing and Creativity The conversation inevitably turns to artificial intelligence. Kevin views AI as both a tool and a threat—a resource that democratizes creativity while also reshaping industries. He points out the uncertainty around copyright, authenticity, and ethics, but admits that ignoring AI isn’t an option. His team meets weekly to test new tools and evaluate where they can help. “We use AI to assist us, not replace us,” Kevin says. “It helps us work faster, but not everything it creates is ready for prime time.” From generating first-draft website content to creating AI voiceovers when budgets are tight, Kevin shows how these tools can fill gaps—without losing the human touch. Staying Grounded in a Changing Landscape Despite new technologies and shifting trends, Kevin’s message remains timeless: strong branding is built on clarity, consistency, and authenticity. As the conversation wraps up, he reminds listeners that tools may evolve, but trust remains the core of every successful brand. “Stay human, stay honest, and keep...

In this episode of Building Better Developers, hosts Rob Broadhead and Michael Meloche sit down with Kevin Adelsberger, owner of Adelsberger Marketing, to explore how small businesses can build success through branding basics. The discussion ties into the season’s theme — Building Better Foundations — and shows how a thoughtful marketing strategy helps transform side hustles into thriving companies. Listen now to the full episode on Building Better Developers, available on Spotify, Apple Podcasts, and Develpreneur.com — and stay tuned for Part 2 of the conversation with Kevin Adelsberger. Starting Small: Branding Basics from Burritos to Business Kevin’s marketing journey started with burritos — literally. While working at a nonprofit, he began helping a local restaurant with its marketing in exchange for food. That early “say yes to everything” mindset helped him gain experience and connections. “When you’re starting out, the answer is often yes to everything,” Kevin says. “But that can spread you too thin.” This early phase taught him one of the first branding basics: you must start broad to learn, but eventually narrow your focus to your strengths. Developers, freelancers, and small business owners can take this same approach — experiment early, then specialize as your reputation and client base grow. Knowing When to Rebrand As side hustles evolve into established businesses, many entrepreneurs ask: Should I rebrand? Kevin’s advice is clear — it depends on your audience. “If your new focus serves a completely different audience, rebranding makes sense. But if there’s overlap, changing your name or logo might cost you valuable recognition.” One of the key branding basics is understanding brand equity — the value built over time through consistent visuals, messaging, and reputation. A name people know is worth protecting. The Four Branding Basics Every Business Needs Kevin shares his firm’s framework for defining a complete brand identity — four elements that every company should eventually refine: Visual Identity Positioning Identity Messaging He notes that new businesses don’t need all of these perfected on day one. Start with visual identity and positioning, then evolve the rest as your business matures. “You don’t have to get everything perfect on day one. Start simple, then refine as you grow.” Avoiding Common Marketing Mistakes When asked about bad marketing, Kevin emphasizes that missteps often come from ignoring your audience. “If you’re doing something just to brag and not to provide value,” he warns, “you’re going to have a bad time.” A big part of branding basics is keeping your customers at the center. Test your messages, get outside feedback, and consider how different people might interpret your marketing. Kevin also highlights the danger of having too few perspectives — especially when creating ads or visuals. Diversity in feedback helps prevent tone-deaf campaigns and strengthens connections. Investing in the Right Visual Identity The conversation wraps with a discussion on logos — a key topic in branding basics. While giant brands like Nike or Amazon have iconic designs, Kevin explains that small businesses don’t need to overthink it. “A good logo used well adds professionalism,” he says. “A bad one gets you confused with everyone else.” He recommends investing in a professional brand kit that includes proper logo formats, colors, and fonts. Consistency builds recognition — and recognition builds trust. Branding Basics for Long-Term Success The first part of the interview with Kevin Adelsberger reminds us that branding isn’t about fancy design or big budgets. It’s about clarity, consistency, and connection. Whether you’re launching your first side hustle or re-shaping a growing business, mastering branding basics helps you build a foundation that...

In this episode of Building Better Developers, hosts Rob Broadhead and Michael Meloche continue their insightful conversation with Adam Malone, exploring how trust and reliability drive stronger teams and foster more robust customer relationships. We pick up with Adam, who opens by emphasizing that reliability begins with consistency. Teams should revisit their guiding principles every couple of weeks—not just at the start of a project. These regular check-ins foster alignment, identify minor missteps early, and maintain clear priorities. “Even if it feels repetitive, that one time someone speaks up can save weeks of rework,” Adam explains. He adds, It’s not about being flawless. It’s about being consistent, accountable, and transparent—values that transform principles from words into action. Reinforcing Reliability Through Shared Principles Reliable teams share a standard compass. Adam recommends boiling down guiding principles to one or two clear slides so everyone can easily reference them during meetings. When conflict arises, those principles provide the framework for productive discussions. Rather than asking who’s right, teams can ask: Does this decision align with our values? “That constant reinforcement builds reliability,” Adam says. “It keeps everyone anchored, no matter who’s leading the conversation.” This shared structure enables teams to make consistent, principle-driven decisions—an essential component of long-term reliability. Extending Reliability to the Customer Experience Michael then turns the discussion outward: how does this translate to the customer experience? Adam explains that reliability for customers begins with a clear definition. Many organizations claim to deliver “great service,” but few define what that means in concrete, repeatable terms. Is it speed? Fairness? Empathy? When teams clearly define those expectations—how to handle complaints, returns, or exceptional cases—they make it a measurable concept. “We all own the customer experience,” Adam emphasizes. “It’s not one department’s job—it’s everyone’s responsibility.” By conducting after-action reviews and evaluating whether customer interactions align with agreed principles, businesses ensure that it becomes a company-wide culture rather than a customer-service function. The Three Elements of Reliability Adam breaks reliability into three key elements that inspire trust: empathy, authenticity, and performance. Empathy Authenticity Performance “Reliability is the visible form of trust,” Adam says. “It’s how people know we’ll do what we say.” These principles work equally well for internal teams, turning accountability into culture. Aligning Internal and External Reliability Adam also shares how teams can connect internal with external outcomes. In his “out-of-the-box” sessions, team members from every department—engineering, operations, and customer service—gather to experience a product exactly as a customer would. “Every process has a supplier and a receiver,” Adam explains. “Bringing them together helps everyone understand how reliability feels from start to finish.” This hands-on approach highlights where it breaks down and how teams can collaboratively improve it. It bridges gaps between departments and strengthens the company's overall dependability. Reliability Through Early, Honest Conversations Adam closes with one of the episode’s most memorable points: reliability thrives on honesty. Avoiding tough conversations damages trust. “The argument’s going to happen eventually,” he says. “Like bad fish, it doesn’t get better with age.” By addressing conflicts early, teams preserve transparency, reduce frustration, and maintain consistent reliability across every relationship—internal or external. Final Thoughts In this powerful continuation of their...

In the first half of our conversation with Adam Malone, founder of The Tenacious Operator, we explore the Power of Trust — how it drives leadership, strengthens teams, and turns potential project failure into growth. From large-scale ERP rollouts to everyday collaboration, Adam shows that the Power of Trust is what truly separates good teams from great ones. Why the Power of Trust Matters Adam begins with a story familiar to many project leaders: a major ERP implementation where everything looked perfect on paper. All dashboards were green, metrics were solid, and executives were confident. Yet almost overnight, the project unraveled. The root cause? A loss of trust. Team members stayed silent about risks. Operations fixed issues without communicating them. The requirements were “complete,” but in reality, they were incomplete. When trust fails, clarity disappears — and even the best teams lose momentum. When everyone claims “we’re on track,” but no one feels safe to speak up, the Power of Trust has already broken down. The Power of Trust in Psychological Safety One of the key insights Adam shares is how psychological safety amplifies the Power of Trust. Proper safety allows people to say, “I’m concerned,” or “This might fail,” without fear of backlash. He recommends creating space for negative feedback through deliberate questions: Conducting a reverse post-mortem helps uncover weak points before they become disasters. This proactive honesty fuels progress and strengthens the Power of Trust across the entire team. Seeing Work Clearly: The Power of Trust in Transparency Drawing from Toyota’s famous Gemba concept — “go to the actual place” — Adam urges teams to physically and mentally visit where value is created. In manufacturing, that’s the factory floor. In software, it’s the analyst’s spreadsheet, the developer’s codebase, or the tester’s environment. When teams observe each other’s real work, they develop empathy and shared understanding. That transparency reinforces the Power of Trust — helping communication thrive where silos once stood. Disagree and Commit: The Power of Trust in Alignment Conflict doesn’t destroy trust; it refines it. Adam calls this the disagree and commit principle — a hallmark of mature teams. Healthy disagreement surfaces risks, values, and differing priorities. Once discussed openly, the team commits to the final decision together. No finger-pointing, no second-guessing. This habit embodies the Power of Trust by turning friction into forward motion. The Power of Trust isn’t about avoiding conflict — it’s about using it to align around shared goals. Guiding Principles: Building Systems Around the Power of Trust Before a project begins, Adam recommends defining guiding principles — the rules of engagement that sustain the Power of Trust. Examples include: When these principles are written down, decisions become consistent and fair. Trust grows because everyone understands how success will be measured and maintained. Leading Through the Power of Trust For leaders, the Trust means striking a balance between empathy and accountability. Adam suggests two types of sponsors for every major initiative: executive sponsor operational sponsor Add in a skilled project manager who encourages honest conversation, and the Power of Trust becomes the foundation of performance — not just a talking point. Key Takeaways from Part 1 Power of Trust Psychological safety Transparencyfosters empathy, and empathy in turn Healthy conflict Guiding principles Connect with Adam Malone If you enjoyed this conversation and want to learn more from Adam, he’s always open to sharing insights and connecting with like-minded professionals. LinkedIn:Adam Malone on LinkedIn http://thetenaciousoperator.com/ Visit him on LinkedIn and...