Remix.run Logo
▲ sroerick 20 hours ago

I make 55k working at a dental office and a restaurant and I'm paying 200$ a month on open source models because I'm having an absolute blast with them.

Plenty of jobs have expenses built into them. Maybe a subscription is more than it used to be, I had great jobs on a used 200$ thinkpad, but it's still cheaper than being a photographer. And 100k is more than most jobs.

Software dev, even if it's all agents now, is still pretty dang economical

▲julianeon 6 hours ago | parent | next [-]

Have you tried OpenRouter and the DeepSeek-like models? If you try to optimize a little you could probably slash those costs.

I send a ton of requests and even reaching $10 for the month would take more calls than I have capacity to review and use. And as I said, that's for a ton of requests.

▲sroerick 2 hours ago | parent [-]

I use Synthetic, Neuralwatt, and Opencode. My usage is fairly high, I'm at 1.5B tokens in the last 7 days. ;)

▲sam345 19 hours ago | parent | prev | next [-]

I'm paying $20 a month using opus 5.5 and having a blast.

▲stuaxo 13 hours ago | parent [-]

20 a month and using sonnet mostly for random fun stuff.

At work, it seems a bit different - I'm certainly having to declaudify things it can be hard starting there's a lot to dig into - you can see it's overwritten but need to understand every detail to sort it out.

▲rglullis 18 hours ago | parent | prev | next [-]

It's easier to enjoy it if you don't see how the sausage is made.

I am definitely not having a blast at work with LLMs. Everyone in the team has become simple rubber-stampers for whatever the AI puts out. There are mountains of documentation which gives a false sense of understanding of how things work, but the code repository itself could have been written in Brainfuck and it would make almost no difference. And we keep getting told by management that this is fine. We've become simple janitors in the slop hall.

▲booty 5 hours ago | parent | next [-]

    Everyone in the team has become simple 
    rubber-stampers for whatever the AI puts out.
Whoever figures out better ways to:

1. Present a big AI PR to a fellow human for review 2. Understand a big AI PR, as a human reviewer

...is going to be a hero. This is one of the biggest unsolved problems of this new era.

I've been experimenting with this, but it's early days. My efforts are mostly along the lines of having AI generate artifacts that guide the reviewer through the PR in execution flow order, explaining the reason for changes along the way.

▲mattm 3 hours ago | parent [-]

I don't think that's the way forward. We don't accept mega-PRs from people, why accept them from machines? The best practice of small, focused commits - whether it be from a person or a LLM - will win out in time once we're past this manic phase.

▲sroerick 18 hours ago | parent | prev [-]

Yeah, I'm sorry to hear that. I'm very glad I am not dealing with anything even remotely corporate during this time, because I'd absolutely hate it

▲ 19 hours ago | parent | prev [-]
[deleted]