Over the years, I’ve tried writing software myself. Ambitious ideas, grand plans, and inevitably, abandoned projects when the going got too harsh. Then came AI coding assistants, and with them, a new path: vibecoding.
Vibecoding is what I call the intuitive, chat-driven way of working with tools like GitHub Copilot, Cursor AI, and ChatGPT. Instead of starting with a blank file, I start with a feeling, a vibe, and a conversation. With natural language as the new programming language, it is my new superpower!
My journey went from asking ChatGPT for quick Python snippets to fumbling together semi-functional ensembles of scripts. Then came GitHub Copilot, which felt like autocomplete with ambition. And finally, Cursor.com, which turned out to be more like a pair-programming partner with opinions.
My first real interaction with Cursor was a turning point. I asked it for bold architectural changes and told it to push back if I was making bad decisions. And boy, did it deliver. Cursor replied with a thoughtful, structured rebuttal:
🚨 I would ADVISE AGAINST this change
The plugin enablement system isn’t broken. In fact, we just fixed an integration bug and it’s now working well. You’re proposing to remove something that’s serving important purposes, like safely handling experimental features and allowing configuration for different environments.
Cursor wasn’t just going along for the ride-it was asking the hard questions. And when I clarified my goals, it flipped:
🎉 This is EXCELLENT design thinking!
Your plan to default-enable plugins, provide user-friendly configuration, and add a sequencer for orchestrating plugin execution is professional-grade. You’re solving real problems with a scalable, maintainable solution.
What followed was a thrilling back-and-forth. Cursor outlined a four-phase implementation plan, encouraged starting with a detailed design document, and even coached me on software development workflows:
📋 Phase 0: Project Design Document
Include user stories, plugin metadata schema, JSON configuration format, CLI interface, and migration strategy.
This will set us up for success and help us avoid rework.
It was like getting a crash course in systems architecture, project planning, and developer ergonomics-all in one.
So here I am: a technical writer turned vibecoder. I’m still learning. Still fumbling. But now, I’m doing it with a sparring partner who helps me write better software and think more clearly.
If you’re a fellow tech writer curious about coding, AI tools like Cursor can open doors, not by dumbing things down, but by treating you like a collaborator with potential. Ask good questions. Stay humble. And vibe on.
This post was made possible with the help of generative AI tools, including ChatGPT and Cursor. They’re not just assistants—they’re collaborators in this process of learning, building, and reflecting.
Next up: writing that sequencer design doc. Wish me luck.
Rolfe Dlugy-Hegwer 