Remix.run Logo
▲ nzach an hour ago

AI only can improve velocity if it mostly works unsupervised. But most people don't trust their agents to run alone.

And to build that trust will take some time, people will need to learn how to use AI effectively.

I think the PS3 hardware could be a good analogy. It was really powerful, but nobody really knew how to use it. After a few years people got really good at it . And you can view this evolution by the improvement of graphical fidelity we got over the years.

▲malfist an hour ago | parent | next [-]

I'm not sure how you can claim it takes time to build trust with AI as if AI isn't actively demonstrating every day why it can't be trusted. Just this morning I had it review clinical notes from a procedure I had done and it mathed things wrong (declaring an injection was 2.5ml when it was 2ml of one thing plus 1ml of another).

I ask it to fix one bug and it introduces three more. I ask it to add a feature and it adds four features.

It has very little common sense. I asked it to build a feature that required api calls to openai, and it decided the best approach was to hand roll the interface code with some bonkers defaults (explicitly zero retries, explicit 1 second timeouts to non steaming api) and wrote the most fragile code that didn't generally work. Even when directed to use the published library by openai it still tried to apply its insane invited requirements to make even that fragile.

I don't think it's nobody knows how to use it, its just not that reliable.

▲dagss 34 minutes ago | parent [-]

What model are you using/complaining about? Just seems so very removed from my work day where I am more usually impressed about the amount of common sense displayed by the AI..

▲IsTom 9 minutes ago | parent [-]

I find it to be very random. Sometimes it'll do something very reasonable on its own that solves a problem I haven't considered and then give up and say it's very hard when prompted to do the same in another project. Or it'll start adding some static HTTP headers somewhere deep in sever code instead of one line in apache config. And I'm mostly using Opus 5.5 on medium.

▲aDyslecticCrow an hour ago | parent | prev [-]

> can improve velocity if it mostly works unsupervised.

I would refute that a bit. I've found quite a nice workflow using a small dumb model (haiku mostly), and basically use it as editor tooling. Change function signature here, split out section into a function and update all similar usage locations there, add a new file and update the make system over there. Trivial tasks that just takes longer to write myself; things i would trust are mostly correct because it still compiles.

It's not a 10x workflow, but keeps me enjoying the coding without loosing track or stagnating my own learning. "commit this" is probably my most used prompt at this point. (with a few strict commit hooks to make it behave and keep brevity).

Mabie a 50% velocity bump to the coding itself on a good day.