Why I'm Building in Public with AI (Honestly)
I’m building AI systems in public to share genuine insights. Discover practical examples and why this transparency matters.
The term “building in public” is gaining traction among developers and entrepreneurs. It often comes with grandiose claims of success, wealth, or effortless innovation. However, my approach is different. I’m not selling you on the next big AI breakthrough; I’m simply documenting my journey of testing tools, building systems, and sharing what works—honestly.
In this piece, I’ll explore why I’ve chosen to build in public with AI, the benefits of this transparency, and some takeaways for those of you interested in a similar path.
What Does Building in Public Mean?
At its core, building in public is about sharing your development process openly, rather than hiding it behind closed doors until a finished product is ready. It involves:
Documenting your progress on social media or a blog.
Seeking feedback from peers and users at every stage.
Sharing failures and setbacks along with victories and breakthroughs.
This approach fosters a sense of community and accountability and can help refine your ideas through real-time feedback, allowing for a more organic development process. But beyond that, it can also demystify the AI development process, inviting diverse perspectives that enrich your project.
Why I Chose This Approach
1. Transparency Builds Trust: In a landscape rife with flashy marketing and exaggerated claims, being honest about my journey helps build trust. I want my audience to know that the challenges I face are real and that they’re part of the learning process. Transparency fosters a connection where followers feel more invested in my work.
2. Iteration Through Feedback: By sharing my challenges and successes, I invite constructive criticism. For example, when I recently shared a framework I created for automating data entry tasks, a fellow developer suggested a different approach that ultimately improved the system's efficiency. This feedback loop is invaluable; it transforms a solo venture into a collaborative effort, resulting in better end products.
3. Learning Out Loud: As an AI systems builder, I’m constantly learning new techniques and tools. Documenting my learning process not only helps solidify my understanding but also allows others to learn alongside me. For instance, when I experimented with various machine learning algorithms, I posted my findings on Twitter. This openness led to discussions that amplified my learning experience, introducing me to concepts and methodologies I hadn't considered before.
Real-Life Examples That Worked
Let’s dive into specific projects where this transparent approach made a difference:
Project 1: Automating Customer Support
One of my primary goals as a Laravel developer is to streamline customer support through automation. I built a simple AI chatbot using Laravel and lightweight machine learning models. Throughout the development, I shared updates on how to integrate the bot with existing workflows and tools.
Sharing the challenges of natural language processing led to a host of suggestions from my audience. For instance, incorporating an FAQ database drastically improved the chatbot’s performance, reducing the average response time from several minutes to just seconds.
Project 2: Filament CMS Enhancements
As a Laravel developer, I’ve spent considerable time tweaking Filament CMS. I documented the process of customizing its user interface and integrating third-party services. When I shared my customizations, fellow developers offered tips that saved me hours of effort and prevented common pitfalls that can arise during the configuration process.
Additionally, by discussing the methods I used to optimize load times, I received feedback that further improved my site’s performance. For example, implementing lazy loading for images was a suggestion from a follower that significantly enhanced user experience.
The Benefits of Building in Public
Building in public offers an array of rewards beyond just technical and operational improvements. Here are some of the most significant:
Networking Opportunities: Sharing your journey connects you with like-minded individuals. It can lead to collaborations, partnership opportunities, or even job offers, expanding your professional network.
Confidence Boost: Publicly committing to your projects adds accountability. It’s more challenging to abandon a project when others are following your progress, which can motivate you to persevere even when things get tough.
Skill Development: Presenting your work to an audience forces you to articulate your thoughts clearly. This can deepen your understanding of both the technology and the application processes, as teaching others is one of the best ways to learn.
Community Building: You can cultivate a community of followers who resonate with your work. They can also become your early adopters, providing valuable feedback that shapes your projects as they evolve.
Challenges I Encountered Along the Way
Of course, building in public isn’t without its challenges. I've faced criticism and skepticism. Some people are quick to dismiss ideas that haven’t yet been fully realized. I learned that resilience is key; it’s essential to remember that this process involves risk, and the reward often comes from taking these risks.
Additionally, balancing transparency with privacy can be tough. Not every detail needs to be shared, particularly if it risks exposing proprietary information or internal processes. Establishing what to share is a crucial part of this journey, and it's something I constantly refine to maintain a good balance.
Actionable Takeaways for Aspiring Builders
If you’re considering building in public, here are some practical steps to get started:
Start Small: Share your initial steps on platforms that suit your comfort level, like Twitter or a personal blog. Build your confidence over time before diving into larger projects.
Engage with Your Audience: Ask for feedback regularly. This not only helps improve your work but can establish a supportive community that encourages your growth.
Acknowledge Failures: Don’t just highlight successes. Discuss any setbacks you encounter. This authenticity fosters trust and can inspire others to embrace their failures as part of their journey.
Iterate Publicly: Use real-time feedback to improve your projects. Adapt your approach based on discussions with your audience, which can lead to innovative solutions you might not have considered.
Enjoy the Process: Building in public is as much about the journey as the end result. Celebrate small victories and keep an open mind to possibilities. Every step, no matter how small, is part of your growth as a builder.
The Future of My Journey
As I continue to explore AI and automation, I plan to maintain this transparent approach. I believe it fosters a collaborative environment and contributes to the broader developer community. While I won’t claim to have all the answers, I find that documenting this journey offers insights that benefit others and myself.
The world of AI is vast and ever-evolving. By building in public, I hope to share what really works, paving the way for a more informed community. Join me in this journey—let's learn together. Together, we can navigate the complexities of this rapidly changing landscape and uncover valuable insights that can propel our projects forward.
Want to follow along?
I share more experiments on LinkedIn and GitHub as I ship Laravel tools and test AI workflows.
Related posts

Exploring Local LLMs in Production: A Practical Approach
Discover how to effectively deploy local large language models (LLMs) in production. Learn practical workflows, case studies, and actionable insights.

Enhancing Laravel Development Efficiency with Cursor and AI
Discover how to effectively implement Cursor to enhance your Laravel and Filament development workflows, making you more efficient without the hype.