I haven’t blogged for years, since it was kind of old and I was using X (Twitter) to share my thoughts. But now I’m starting this blog as a genuine space to document and share my journey with AI-assisted development (or vibe-coding). This isn’t just another tech blog but it’s a personal chronicle of how these tools are reshaping my work and creativity. I wanted to create an authentic place to share both the breakthroughs and the stumbling blocks I encounter along the way.
Why did I start a blog?
After taking a GitHub Star Award and collecting the work I’ve done so far, I noticed that I’m lacking in blogging. I’ve been building projects, contributing to open source, and exploring new technologies, but I haven’t been documenting or sharing these experiences in a structured way. This realization made me see how much valuable knowledge I’ve accumulated without creating a way to share it with others or even reference it myself later.
The award was a reminder that people find value in what I create, but I wasn’t providing context, explanations, or the thought processes behind my work. I was missing the opportunity to turn isolated code contributions into comprehensive learning resources. Lately, I’ve found myself constantly experimenting with AI development tools, discovering new workflows, and solving interesting problems. These experiences feel too valuable to keep to myself.
The desire to share our stories is what makes us human, even as we navigate this new AI-driven world.
I need a place where I can document these discoveries in detail; something beyond what social media platforms allow. I want to share my real, unfiltered experiences with the tools I use, and connect with others on similar journeys.
Social media has become increasingly difficult for meaningful technical discussions. Character limits, algorithm-driven feeds, and the constant noise make it nearly impossible to have thoughtful conversations about the nuanced realities of AI-assisted development.
When spaces become too noisy, we must create our own quiet corners for reflection and genuine connection.
This blog is that quiet corner: a space where I can share comprehensive guides, detailed observations, and honest reflections without the constraints of other platforms.
What will I write about?
I’ll be focusing primarily on AI-assisted development tools and techniques that have transformed my workflow:
- My experiences with Windsurf and Cursor and its best practices I’ve discovered through daily use
- How GitHub Copilot has changed my approach to coding and the honest limitations I’ve encountered
- The concept of vibe-coding, finding the flow state where AI and human creativity work in harmony
- Practical prompt engineering techniques that have made these tools significantly more useful
- Real-world projects where these tools have both helped and hindered
Beyond tech, I’ll also share about my hobbies outside of coding that keep me balanced and provide perspective. The parallels between pursuing creative interests and navigating the rapidly changing AI landscape have been surprisingly insightful.
What I hope to do here
My goals for this blog are straightforward: I want to document my genuine experiences with AI tools in a way that’s accessible to everyone. I’ll share the actual prompts that worked, the approaches that failed, and the unexpected discoveries along the way.
We’re all figuring out this AI revolution together—what works, what doesn’t, and how to integrate these tools without losing our creative voice.
This won’t be a highlight reel of perfect results. I’ll share the frustrations, the limitations, and the ethical questions I wrestle with as these tools become increasingly central to my work.
My journey so far
My exploration of AI-assisted development began with simple Copilot suggestions and has evolved into crafting complex workflows in both Cursor and Windsurf that significantly enhance my productivity. It hasn’t been a straight path—I’ve spent hours fine-tuning prompts that ultimately saved me days of work, and I’ve also gone down rabbit holes that yielded little value.
What I’ve learned is that these tools shine brightest when approached with both curiosity and healthy skepticism. They’re incredible partners in the development process, but understanding their limitations is just as important as leveraging their strengths.
The most valuable part of this journey isn’t achieving perfect AI outputs. It’s developing the judgment to know when and how to use these tools effectively.
Looking ahead
I’m genuinely excited to share detailed workflows, prompt templates, and real examples from my development process. I’ll document my experiments with integrating Cursor, Windsurf, and Copilot into different aspects of development, from ideation to debugging to refactoring.
I’d love to hear about your own experiences too—the prompts that worked for you, the workflows you’ve developed, and how you balance AI assistance with maintaining your developer intuition.
This blog will be an honest record of navigating development in the age of AI assistants—both the “wow” moments and the “wait, that’s not right” ones. I hope my experiences, whether successful or instructive failures, will be valuable as you explore these tools in your own work.
This article was proofread and enhanced with AI assistance.