3 ms·
It takes some practice to get good using them. I use it as a sophisticated autocomplete. For example, if I'm building an api client layer in a web frontend, I m
by nosefurhairdo 2y ago
It takes some practice to get good using them. I use it as a sophisticated autocomplete. For example, if I'm building an api client layer in a web frontend, I might have `fooApi.ts`, `mockFooApi.ts`, and `barApi.ts`. instead of writing `mockBarApi.ts`, something that might take 5 - 15 minutes, I can feed those 3 existing files into context, and a few seconds and pennies later I have a nearly perfect file ready for review.
For any semi novel development I want to write it myself to establish the patterns I like and get an understanding of what I'm building. It's the boring stuff I hand over to Claude.
- toprerules 2y agoThat's just it, I try not to write the boring parts at all. That's what libraries and design pattern are for - avoiding writing boilerplate. I certainly can see it being useful for writing additional tests, although I am very worried based on what I've seen that it will introduce more bugs than it's worth, which is why it's still a tool I use for hobby projects and not for real work.
- guappa 2y ago> I certainly can see it being useful for writing additional tests If your metric is number of tests, sure. If your metric is number of useful tests… eh