[_fat_santa]

> I would love to see an anti-AI take that doesn't hinge on the idea that technology forces people to be lazy/careless/thoughtless.

Here's mine, I use Cline occasionally to help me code but more and more I find myself just coding by hand. The reason is pretty simple which is with these AI tools you for the most part replace writing code with writing a prompt.

I look at it like this, if writing the prompt, and the inference time is less than what it would take me to write the code by hand I usually go the AI route. But this is usually for refactoring tasks where I consider the main bottleneck to be the speed at which my fingers can type.

For virtually all other problems it goes something like this: I can do X task in 10 minutes if i code it manually or I can prompt AI to do it and by the time I finish crafting the prompt and execute, it takes me about 8 minutes. Yes that's a savings of 2 minutes on that task and that's all fine and good assuming that the AI didn't make a mistake, if I have to go back and re-prompt or manually fix something, then all of a sudden the time it took me to complete that task is now 10-12 minutes with AI. Here the best case scenario is I just spent some AI credits for zero time savings and worse case is I spent AI credits AND the task was slower in the end.

With all sorts of tasks I now find myself making this calculation and for the most part, I find that doing it by hand is just the "safer" option, both in terms of code output but also in terms of time spent on the task.

[didibus]

> The reason is pretty simple which is with these AI tools you for the most part replace writing code with writing a prompt

I'm convinced I spend more time typing and end up typing more letters and words when AI coding than when not.

My hands are hurting me more from the extra typing I have to do now lol.

I'm actually annoyed they haven't integrated their voice to text models inside their coding agents yet.

[fzzzy]

GitHub copilot already does have speech to text and as my sibling comment mentions, on the Mac, it is globally available. It varies according to typing and speaking speed but speaking should be about five times faster than typing.

[rapind]

On a mac you can just use a hotkey to talk to an agentic CLI. It needs to be a bit more polished still IMO, like removing the hotkey requirement, with a voice command to break the agents current task.

[didibus]

Does it use an LLM powered voice to text model ?

I find the generic ones like the ones I can use anywhere on Mac to be crap.

If you've used the ChatGPT voice to text model you know what I mean.

[rapind]

I believe it does on newer macs (m4 has neural engine). It's not perfect, but I'm using it without issue. I suspect it'll get better each generation as Apple leans more into their AI offering.

There are also third parties like Wispr that I haven't tried, but might do a better job? No idea.

[lukax]

Have you tried Soniox? It's really not expensive ($0.12/h, $200 free credits when you sign up) and really accurate.

https://soniox.com/

You can use it with Spokenly (free app, bring your own Soniox API key) on macOS and iOS (virtual voice keyboard)

https://spokenly.app/

Disclaimer: I've worked for Soniox

[hyperadvanced]

Why would I buy this if my Mac has it for free? Is it “just better”?

[wild_egg]

The mac one is pretty limited. I paid for a similar tool as above and the LLM backing makes the output so much better. All my industry specific jargon gets captured perfectly whereas the Apple dictation just made up nonsense.

[lukax]

It's really accurate and supports 60+ languages

[rapind]

I find myself often writing pseudo code (CLI) to express some ideas to the agent. Code can be a very powerful and expressive means of communication. You don't have to stop using it when it's the best / easiest tool for a specific case.

That being said, these agents may still just YOLO and ignore your instructions on occasion, which can be a time suck, so sometimes I still get my hands dirty too :)