There wasn't much skill involved, but if there's credit to be had for giving Claude a few screenshots, API docs and iterating on the design while doing human product testing, then I guess I'll take it!
I haven't shared it because it's rough (you know what vibe code looks like underneath!) and I only implemented the features I needed. So there's no external IFTTT-like hooks, it probably doesn't internationalize well, and I didn't need collaboration features. I also don't want to be on the hook for supporting a codebase that isn't the core of what I do. My real goal was to see if I could implement a replacement for myself in less than the cost of one annual seat, even at API pricing.
But I'm surprised to see Harvest is still in the news about this... so, maybe! Thanks for the encouragement!
alt Hacker News
There wasn't much skill involved, but if there's credit to be had for giving Claude a few screenshots, API docs and iterating on the design while doing human product testing, then I guess I'll take it!
I haven't shared it because it's rough (you know what vibe code looks like underneath!) and I only implemented the features I needed. So there's no external IFTTT-like hooks, it probably doesn't internationalize well, and I didn't need collaboration features. I also don't want to be on the hook for supporting a codebase that isn't the core of what I do. My real goal was to see if I could implement a replacement for myself in less than the cost of one annual seat, even at API pricing.
But I'm surprised to see Harvest is still in the news about this... so, maybe! Thanks for the encouragement!