A few first thoughts. tidewave
is working extremely well with vscode and github copilot
. It is unimaginable productivity growth. I have used tidewave
with cursor
, claude code
, cline
and vscode copilot
. For tasks which are generally moderate ( involving atleast generating 30-100 lines - 2-3 files). For whatever reason vscode copilot
gave the best results. cline
gave the worst results. A few more observations:
- in
cline
the token usage has increased exponentially - not sure iftidewave
in any way responsible for that. Possibly, the huge context built up bycline
is causing the problem. - I have observed that
vscode copilot
made the maximum usage of tools fromtidewave
. It was much lesser in all other tools. - The amount of halucination has come down drastically once
tidewave
is running. Earlier, these agents would get into endless loops with reference to new heex syntax etc. - and they used to repeatedly make the same mistakes. It has come down significantly.
A few personal notes: - Vibe coding a big project is a myth. For attention seeking on social media, people claim a lot of things. But, we will not be there for sometime - my guess.
- If you can work with a few fellow engineers - you already can work well with these AI tools. There is no brilliance here. In fact, oversmartness results in a lot of productivity and money loss.
- Oneshotting is a term token sellers want to sell like the snakeoil. Do not believe it. Split the application/feature into moderate level - clearly definable task. Just iterate through and you will be there. Any reasonable application would need multiple iterations, small adjustments, lot of handholding the agent etc.
- I would dare say - the developers who will be successful in this domain will be the same developers who are successful elsewhere. Ship quick - ship small - iterate small - iterate clear - these are the success mantras.
Hope this is useful for someone.