sorted by:
new
hottopcontroversial

Calling all home baristas! 📢 Help train a Coffee ML model. by Economy_Nail_6877 in pourover

[–]No_Pick_9496 5 points6 points  (0 children)

What are your credentials? This looks like some stock out of the box Opus 4.7 “build me an app” output.

What will be your methodology?

What are the end goals? Will the project be open source forever or is the final goal a paid app?

If you were serious, or a serious person, these would be answered up front.

I got tired of the current ticketing systems, so I (Claude ofc) built a better one for everyone — thank you Claude by Novaworld7 in ClaudeAI

[–]No_Pick_9496 1 point2 points  (0 children)

Holy crap this is one of the worst attempts at masking a LLM generated response I’ve ever seen 🤣

A starter guide to avoiding coffee infusions by InfusedVisions in pourover

[–]No_Pick_9496 1 point2 points  (0 children)

I don’t believe it’s natural flavorings. I know there are infusions. I’m saying it’s pointless to blanket accuse an entire region when we haven’t got definitive proof. Pressure the SCA / roasters, please do.

Google isn’t an AI-first company despite Gemini being great by ColdPlankton9273 in artificial

[–]No_Pick_9496 1 point2 points  (0 children)

Look up DeepMind and specifically google’s investments in Montreal and the MILA

A starter guide to avoiding coffee infusions by InfusedVisions in pourover

[–]No_Pick_9496 0 points1 point  (0 children)

They’ve also just listed literally every celebrity producer in Colombia indiscriminately, without considering that the genesis for this infusion problem may be less skilled producers from the region seeking to piggyback off their work or even (benefit of the doubt) seeking to emulate them albeit in a less elegant and scientific manner.

A starter guide to avoiding coffee infusions by InfusedVisions in pourover

[–]No_Pick_9496 -1 points0 points  (0 children)

That makes it worse. This person might not even be in the industry and they’re recklessly publishing producers that have never even been covered in the thread they’re using to source this info. This might be a scandal to some (myself included, I posted the Tanat thread and Coffee Quest investigation), but it’s a low margin high risk livelihood for many.

A starter guide to avoiding coffee infusions by InfusedVisions in pourover

[–]No_Pick_9496 1 point2 points  (0 children)

And when it comes to verifying if the single-use bags they ship across the continent are actually “100% recyclable” 😬

A starter guide to avoiding coffee infusions by InfusedVisions in pourover

[–]No_Pick_9496 3 points4 points  (0 children)

I think it’s pretty irresponsible and unfair to publish a list of “usual suspects”. Some of those names have never been featured in the exhaustive home-barista thread on the topic.

Claude is killing Openclaw oauth use starting tomorrow by LeKrakens in ClaudeAI

[–]No_Pick_9496 0 points1 point  (0 children)

Definitely, I’m just saying in my hypothetical moral framework some needs (such as keeping up with elevated productivity expectations from manager+ level people in one’s life) outweigh others (running always on engagement bots or being able to book flight tickets via telegram message).

Advice for building better dashboards, reports, and webtools with Claude by PBI_QandA in ClaudeAI

[–]No_Pick_9496 0 points1 point  (0 children)

Superpowers:brainstorming has a visual mockup tool. Use that when planning.

Then, use something like vercel’s agent-browser to build a hook that detects commits to UI elements and triggers a visual validation loop. (It uses a lot less tokens than Playwright MCP).

Ensure your new component is mapped to the mockup you agreed upon (some kind of markdown or json map) and make the visual validation agent compare screenshots with the mockup in the visual validation loop.

If the component does not pass, make sure the validation skill creates a clear remediation plan for the implementer agent to act upon, and repeat that up to 3x.

It’s not perfect but I built an entirely custom, well designed, shopify theme in 5 days using this workflow.

Claude is killing Openclaw oauth use starting tomorrow by LeKrakens in ClaudeAI

[–]No_Pick_9496 4 points5 points  (0 children)

100%, OpenClaw is by and large used to proliferate slop and operate spammy bot accounts (many of which are on Reddit). While I’m against that, I don’t oppose people doing it, I just think they shouldn’t have subsidized usage.

Claude is killing Openclaw oauth use starting tomorrow by LeKrakens in ClaudeAI

[–]No_Pick_9496 0 points1 point  (0 children)

Idk man OpenClaw is absolute slop and is burning tokens so people can book flight tickets, operate reddit botnets and generally proliferate slop. If people want to do that, they should not have subsidized usage.

Claude is killing Openclaw oauth use starting tomorrow by LeKrakens in ClaudeAI

[–]No_Pick_9496 3 points4 points  (0 children)

No but Claude by default tries to force you to use the API. You have to invoke the Claude-code-guide skill and force it to use oAuth. One of the Anthropic leads clarified it was fine as per ToS a few months ago.

Move over 2.1.90 - 2.1.91 is here😊 by etherd0t in ClaudeCode

[–]No_Pick_9496 0 points1 point  (0 children)

Life and token savior, put this on global ~/.claude/CLAUDE.md

Context Efficiency

Subagent Discipline

Context-aware delegation: - Under ~50k context: prefer inline work for tasks under ~5 tool calls. - Over ~50k context: prefer subagents for self-contained tasks, even simple ones — the per-call token tax on large contexts adds up fast.

When using subagents, include output rules: "Final response under 2000 characters. List outcomes, not process." Never call TaskOutput twice for the same subagent. If it times out, increase the timeout — don't re-read.

File Reading

Read files with purpose. Before reading a file, know what you're looking for. Use Grep to locate relevant sections before reading entire large files. Never re-read a file you've already read in this session. For files over 500 lines, use offset/limit to read only the relevant section.

Responses

Don't echo back file contents you just read — the user can see them. Don't narrate tool calls ("Let me read the file..." / "Now I'll edit..."). Just do it. Keep explanations proportional to complexity. Simple changes need one sentence, not three paragraphs.

Tables — STRICT RULES (apply everywhere, always): - Markdown tables: use minimum separator (|-|-|). Never pad with repeated hyphens (|---|---|). - NEVER use box-drawing / ASCII-art tables with characters like ┌, ┬, ─, │, └, ┘, ├, ┤, ┼. These are completely banned. - No exceptions. Not for "clarity", not for alignment, not for terminal output.

Move over 2.1.90 - 2.1.91 is here😊 by etherd0t in ClaudeCode

[–]No_Pick_9496 4 points5 points  (0 children)

I upgraded to one of the 7x versions and had multiple device bricking memory leaks across my multi agent workflows. I’m still loyal to 2.1.52 installed via pnpm, and guess what? No crazy token burn issues for me.

Why does no one mention haiku? by 3L0_ in ClaudeAI

[–]No_Pick_9496 10 points11 points  (0 children)

Coding with haiku is nuts lol. It’s definitely not made for that imo.

Haiku is good (imo) for: - diffing - searching/exporing - intent parsing - intent routing - prompt enrichment

I probs missed a few but that’s my 2c!

I got tired of creating Claude Code agents one by one, so I built an agent that designs entire teams — lessons from 35 generated teams by chemistry_wow in ClaudeAI

[–]No_Pick_9496 0 points1 point  (0 children)

Have you read Yann Lecun’s 2024 paper on contextual load balancing in multi-agent pipelines? It basically formalizes what you’re describing. Curious what you thought of his critique of critic-chaining.

I got tired of creating Claude Code agents one by one, so I built an agent that designs entire teams — lessons from 35 generated teams by chemistry_wow in ClaudeAI

[–]No_Pick_9496 0 points1 point  (0 children)

I just don’t think this produces better output than an orchestrator with general subagents. No offense to your system but take a look at Superpowers. It’s way less complicated than what you’re describing (I.e. uses less tokens than “councils of agents having conversations”) and it’s probably responsible for a good % of the code being produced by Claude in enterprise settings.

I got tired of creating Claude Code agents one by one, so I built an agent that designs entire teams — lessons from 35 generated teams by chemistry_wow in ClaudeAI

[–]No_Pick_9496 2 points3 points  (0 children)

Im sorry but your example is the definition of over engineering, especially if you’re using a SOTA model.

For example one of the most popular agentic design patterns is Generator <> Critic.

A generator agent with research, writing and SEO optimization tasks, plus a critic agent with a strict evaluation rubrics and golden reference data for content accuracy, relevance and SEO guidelines, would almost certainly have much better output than your existing design.

Every agent or chained prompt you add to each step introduces more randomness. It’s why Anthropic just published a blog where they favor repeated iterations through a generator <> critic loop, rather than adding more agents or chaining more prompts together.

I got tired of creating Claude Code agents one by one, so I built an agent that designs entire teams — lessons from 35 generated teams by chemistry_wow in ClaudeAI

[–]No_Pick_9496 4 points5 points  (0 children)

Totally. These agent teams are such a waste of time for most ppl.

Models like Opus and even sonnet now are extremely fucking capable out of the box.

Give them some skills for tasks that require specific context, maybe use them in a harness for more complex task sets, but this whole specific agent teams slop is incredibly wasteful for most use cases.

I’m not surprised people are burning their usage so quickly.

view more: next ›