Building a Raycast Timer with AI: Fast Prototyping, Slow Debugging
tl;dr: Vibe coding lets you build quick prototypes, but 90% of time is spent fixing AI mistakes
Vibe coding professionally is still hard as we need to produce software that is 100% (or as close as possible) reliable.
But it's really cool that I can try new ideas or things that I would be too lazy to do if I had to code myself (with my fingers).
Then with vibe coding I can code like 30 minutes or an hour and have something working.
Today I was finally able to stop for an hour to create a Raycast extension the way that I want it to be: a timer, very simple, always in the loop, with a custom duration and with a sound when it's done.
The sound never stops playing every minute until I stop it.
So if I want to keep it running just one minute more, I don't need to do anything - it will play again in one minute.
A few observations:
- I need this to change my working position due to lower back issues
- It was not my first Raycast extension code
- 90% of the time was fixing AI vibe coding mistakes, including React mistakes and Raycast incorrect usage, for example, using a regular setInterval instead of Raycast interval, or using a Raycast interval that is not allowed
Image 1: I left it running and went to lunch (I'm in NYC so I have to enjoy)
Image 2: Raycast search
The extension is not published as I built it for my own needs, but if you want to give it a try, let me know -maybe I'll change my mind.