Live data from Hacker News

Setting up your spare Mac for Claude Code to control, a step-by-step guide

ykdojo.github.io

131–140 of 213 posts

Re: Setting up your spare Mac for Claude Code to control, a step-by-step guide

#131
post #118

Earlier quoted context omitted.

Running tests and optimize?

Running tests that the agent created for its own hallucinations? Optimize using another hallucinating agent? Which tests and optimizations do you propose to run after a night of supervised work when one of main things that all agents keep doing is "load all records from db , and filter them in memory"? It's now become so bad, I had to literally vibecode a separate linter for this. And that's just one of the problems.

If this is your problem, I hate to say it, but it’s a skill issue on your side. I didnt even start developing software until LLMs even though I know all the primitives quite well and have a strong grasp of architecture. ADHD, perfection, and focus got in the way. I’m writing a pretty complex application and I don’t have the problems you’re running into. I regularly have my code reviewed by professional devs to ensure I’m not just vibecoding into slop. I’m not. I also read my code regularly and do a lot of exercises and courses to keep learning as well.

So I dunno what to say, except it’s possible to write really solid code with LLMs.

Re: Setting up your spare Mac for Claude Code to control, a step-by-step guide

#132
post #101
post #69

Earlier quoted context omitted.

No sarcasm, I am completely serious. I don’t have time for much leisure coding these days. I do have time to kick off a few tasks in the morning to progress my many side projects. Nothing public / oss, just code that I find useful/interesting like home automation, content pipelines, games, etc. There are a bunch of cases where remote control from iOS onto a Mac Mini is simply nicer than using iOS Claude Code sandboxe…

On all projects I've run any of the models they: - infinitely duplicate any and all code, helpers and components - infinitely duplicate CSS (because they duplicate components) - continuously write code like "read the entire db into memory and run a filter function on retrieved data" - continuously write code like "call db with multiple queries for each element in a list" - etc. etc. Why the hell would I ever want to…

[flagged]

Re: Setting up your spare Mac for Claude Code to control, a step-by-step guide

#133
post #84

Earlier quoted context omitted.

You want your team spending their time fixing these simple errors? The secret sauce is in the triage. We've adopted solutions alot like this, and now our team spends its time on much more meaningful work.

Why are the errors occurring, though? That's what boring analyse-and-fix addresses, through familiarity, recognition of patterns and "hang onnn..." moments. It's like your AI agent is just plugging the leaks in the dyke each time, instead of fixing the architecture of the dam.

There are many sources of boring predictable errors which nonetheless are easy to miss and easy to fix. API validation errors for example.

Re: Setting up your spare Mac for Claude Code to control, a step-by-step guide

#134
post #99
post #12

Earlier quoted context omitted.

I think you need to open your mind to the possibilities? For example: - scanning logs for errors and - opening issues which are then auto-triaged and - PRs are opened for them and auto-reviewed and - merged (and deployed). This workflow alone is immensely powerful, and takes alot of burden off the team.

> scanning logs for errors famously a good job for a tool that takes 10-50k logs to run out of context and forget what it's doing.

Not really? Imagine for example looking for http status code 500 in an api log over the past hour. The nice thing here is it doesn’t matter if you get them all because it’s reoccur (or not).

Re: Setting up your spare Mac for Claude Code to control, a step-by-step guide

#135
post #84
post #61

Earlier quoted context omitted.

None of these are things I want or need in the product I maintain with a team, there's really no point to any of this unless you run a vibe coded SaaS (?)

You want your team spending their time fixing these simple errors? The secret sauce is in the triage. We've adopted solutions alot like this, and now our team spends its time on much more meaningful work.

Yes, I want my team to be deeply familiar with the codebase and every single little bug that needs fixing both trains them and let's them learn a little bit more about the codebase.

They can use agents. Like, team members don't need to be replaced, they can simply use agents when they deem it useful. If they see a trivial bug,they can put their agent on it and go work on something else meanwhile.

Re: Setting up your spare Mac for Claude Code to control, a step-by-step guide

#136
I've done this before as a free replacement for my OpenClaw bot. It loses its connection sometimes and you need to redo the handoff with your phone. But otherwise, nice to have a use for my old Mac. It's also running my Home Bridge, which Claude can interact with. Pretty cool.

Re: Setting up your spare Mac for Claude Code to control, a step-by-step guide

#137
post #97
post #51

Earlier quoted context omitted.

I run a lot of data science-type analyses that can take up to hours at a time to run, so Claude is « monitoring » tasks most of the time. I have it on remote-control so I get notified when a task is done or need clarification, but most importantly whenever I have a new idea, I can just ask Claude to queue it up. Most of the time my hardware is the bottleneck, not the subscription quotas.

> take up to hours at a time to run, so Claude is « monitoring » tasks most of the tim How is Claude monitoring them for hours? Claude runs out of context and extremely long sessions are prohibitively expensive even according to Anthropic (after they dispense with the marketing bullshit of long running tasks)?

It launches these tasks in the background. It became really good at it a couple of months ago, now it sets monitors on timer (not something I instructed, so I assumed it’s part of the system prompt for this kind of tasks) and then just wait for the next prompt, for the background process to be done, or for a monitor to trigger a checkup.

Re: Setting up your spare Mac for Claude Code to control, a step-by-step guide

#138
It's so strange to me that tech crowd uses macs for use cases that spend all their time idle or serve some light http request.

It's a glorified API gateway...it could run on a medium sized potato

Almost like an entire generation just grew up coding on macbooks as the obvious choice for coders and just can't conceptualize hardware outside of that walled garden

Re: Setting up your spare Mac for Claude Code to control, a step-by-step guide

#139

Earlier quoted context omitted.

Yeah good luck being employed in 3 years once this bubble popped when all you do is type some natural language into a phone screen. People being proud of not using an IDE anymore is such a foreign concept to me, who enjoys coding and got into the profession because of the love of that.

If you got into the industry due to enjoying the typing of code the future is looking pretty bleak.

[dead]

Re: Setting up your spare Mac for Claude Code to control, a step-by-step guide

#140
post #118

Earlier quoted context omitted.

Running tests and optimize?

Running tests that the agent created for its own hallucinations? Optimize using another hallucinating agent? Which tests and optimizations do you propose to run after a night of supervised work when one of main things that all agents keep doing is "load all records from db , and filter them in memory"? It's now become so bad, I had to literally vibecode a separate linter for this. And that's just one of the problems.

>It's now become so bad, I had to literally vibecode a separate linter for this.

You see, there's your problem right there. You're vibe coding, which by definition literally means you're unwilling to look at the generated code. That's not what successful ai assisted software developers are doing. YOU HAVE TO READ THE CODE. Refusing to do that means you're not a serious programmer, you're outsourcing your thought and design and implementation, trying to get something for nothing by taking the easy way out, and you're going to get terrible results no matter what prompts you "engineer". There ain't no such thing as a free lunch (yet).

And while we're at it, to elaborate on what serf said: people mindlessly parroting terms like "stochastic parrot" to criticize llms without having read the actual paper that coined the term and understanding what it really claimed and how other papers responded to it means you're just a human stochastic parrot no better than what you're criticizing -- at least the llm has read all those papers and understands what "stochastic parrot" actually means in context. Ask it, it will be glad to explain!

Emily M. Bender, Timnit Gebru, Angelina McMillan-Major, and Margaret Mitchell. On the Dangers of Stochastic Parrots: Can Language Models Be Too Big? (FAccT 2021)

https://dl.acm.org/doi/10.1145/3442188.3445922

Post reply on HN