3 posts tagged with "development"

AI coding assistants can be incredibly helpful — until they aren't.

Recently, I asked my AI assistant to help rebase my local main branch onto an upstream repository. What followed was a seemingly helpful but quietly destructive sequence of Git operations, carried out without sufficient warning or consent. The AI confidently moved forward, using commands like git reset and git push --force-with-lease — powerful tools that should never be used lightly.

I've been experimenting with "vibe coding" tools like Cursor and Claude Code (3.5)—the kind of AI pair programmers that promise to understand your code, suggest fixes, and help you fly through bugs without touching the keyboard too much. In theory, it's magical.

In practice? Well... let me tell you a story.

Context​

Recently, I dove into creating a blog site dedicated to my new passion: vibe coding. I've previously built projects using Docusaurus, a React-based framework optimized for documentation and blogs, making it a natural choice for this project. Initially, I considered using Hashnode for hosting based on Deepseek's recommendation. At first glance, Hashnode appeared to be a great fit—it's easy to set up, visually appealing, and community-oriented. However, a deeper dive revealed serious SEO issues, specifically broken sitemaps and landing pages that couldn't be indexed by Google. Given the importance of SEO for visibility, this was a significant drawback. With that, I quickly decided to migrate my content from Hashnode to a more reliable solution—Docusaurus.