TDD
I’ve been playing around with various vibe-coding tools. While working on building this blog using Astro, I asked Claude Code to use a test-driven development (TDD) approach.
Bingo! It just built a whole test bed and followed the TDD approach for every new feature that’s built.
I liked Bolt.dev, but since I started using Claude Code, it’s a completely different experience. Bolt can still provide compelling prototypes. That, along with Claude Code, takes it to the next level with its much more intelligent implementation.
I’ve also asked it to make it a practice without me reminding it of TDD every time. For that, Claude inserted the following into its config file:
Eventually, I ended up with 90 tests and Claude executing them as I work on improving the functionality.
Be careful with overfitting
Apart from this, I had issues with rendering images on the homepage. It took me a couple of iterations to get it right with Claude. Sometimes, you see the model overfitting to your precise rules. Even to an extent, it hardcodes certain logic, in this case, the image file name. Being with it, nudging, and providing additional context usually fixes the issues.
So far, so good! I can clearly see where we are heading … a world of exponential efficiencies from where we are.