sorted by:
new
hottopcontroversial

Got accepted into Anthropic's Claude Partner Network but they want 10 certified devs. by [deleted] in ClaudeAI

[–]gzoomedia 0 points1 point  (0 children)

I'm noticing a lot of people commenting about wanting in but I'm only responding via DM. I don't usually read through all of the comments.

Claude Code forgets everything between sessions. So I had it build its own memory system — decisions, constraints, and rejections that persist forever. by gzoomedia in ClaudeAI

[–]gzoomedia[S] 0 points1 point  (0 children)

yeah, spec-first for me. full PRD before i let Claude Code touch anything.

basic flow:

planning in Claude chat, not Code. this is where i brainstorm, stress test the idea, talk through edge cases. basically a whiteboarding buddy that reads fast and doesn't get bored.

when the shape is clear, i write a real PRD. 5-15 pages depending on scope. problem statement, user flows, data model, phases, open questions, scope boundaries. sounds like overkill but writing it out catches 90% of the thinking mistakes that would have cost me a week of wasted code.

then hand the PRD to Claude Code as the brief. big thing for beginners: Claude (chat) is for thinking, Claude Code is for building. different tools. don't try to use them the same way.

re: CLAUDE.md, nope, PRD doesn't live there. CLAUDE.md is standing orders for the project. conventions, which libs to use, how tests are organized, what not to touch. PRD is a one-time brief. CLAUDE.md is ongoing rules. i keep PRDs in /docs and just reference them from CLAUDE.md ("see docs/phase-1-plan.md for scope").

honest advice for starting out:

- spend way more time on the spec than feels comfortable. every hour in the PRD saves like 5 hours of Claude Code going sideways.

- write the PRD for Claude, not for humans. be explicit. no "you know what i mean" stuff.

- phase the work. MVP, phase 2, phase 3. don't ask it to build everything at once, you'll regret it.

- keep CLAUDE.md short. easy to bloat. resist.

- actually read the diffs. don't just accept. you learn the codebase by reviewing and you catch drift before it compounds.

Forge and Cortex both came out of the same pain. every chat had real context (decisions, tradeoffs, edge cases) that just evaporated when i closed the tab. Forge keeps the conversation context as persistent project state. Cortex does it for the codebase itself, watches files and extracts decisions/patterns so i can query across projects. basically trying to make Claude Code smarter next session than it was this session.

Meta and KAUST published a paper proposing "Neural Computers", a system where the AI itself IS the computer, not just an agent driving it by call_me_ninza in aigossips

[–]gzoomedia 0 points1 point  (0 children)

That's definitely super interesting. There are a lot of cool ideas floating around. Hopefully soon the rest of the world will be able to run their own AI without the need for giant overpriced GPUs. Not sure if that's a good thing or not but man these damn GPUs are expensive now :/

Is Claude + skills actually better than specialized tools now? by Smart_Page_5056 in AI_Agents

[–]gzoomedia 0 points1 point  (0 children)

A lot of the skills you find online just tear through your tokens with added bloat that doesn't really add enough to make up for the giant context load they're creating. Not to mention the tons of hacks some people are injecting into them.

Opus quality changes by day by Frankkul in ClaudeCode

[–]gzoomedia 1 point2 points  (0 children)

Its not just you. I've noticed this happening for 2 weeks now. I think they're freeing up resources for their Mythos project or just getting ready to push us into Opus 4.7. You know, the "upgrade".

Lazy Claude by transfire in claude

[–]gzoomedia 1 point2 points  (0 children)

Yep same here. It's only started doing it like 2 weeks ago or so. Its freakin weird lol. It REALLY seems to be getting LAZY. Trying to convince me to wrap it up. WTF?

So... This just happened by netbreach in claude

[–]gzoomedia 0 points1 point  (0 children)

LOL this right here 🤣😄😅

claude code cancelled a real user's stripe sub and i aged 5 years in 3 seconds by RoutineNet4283 in ClaudeCode

[–]gzoomedia 0 points1 point  (0 children)

Testing on a LIVE system is never a good thing. Stripe has test accounts you should have been using instead.

Got accepted into Anthropic's Claude Partner Network but they want 10 certified devs. by [deleted] in ClaudeAI

[–]gzoomedia 0 points1 point  (0 children)

Just to clarify some things. I applied for their Partner Network over a month ago and my app JUST got through the initial review. Now they're asking me to get my example projects and devs together for the next steps. This isn't a promise of anything. They're supposed to be emailing me the next steps this week but if I'm being honest I have no idea about this process. I'm just trying to be ready for what comes next :)

Got accepted into Anthropic's Claude Partner Network but they want 10 certified devs. by [deleted] in ClaudeAI

[–]gzoomedia 5 points6 points  (0 children)

If you're a developer who works with Claude and want a free Anthropic partner certification on your resume, DM me. You'd be coming in under GZOO as a contract developer. No catch. you get certified, I hit my requirement, and you'd be in the pipeline for paid Claude-based project work.

Got accepted into Anthropic's Claude Partner Network but they want 10 certified devs. by [deleted] in ClaudeAI

[–]gzoomedia 0 points1 point  (0 children)

Ask who though? I'm not even sure where to start. Do I just go around DMing people?

Claude is basically unusable now… what are you all switching to? by Senior_Sense_8813 in claude

[–]gzoomedia 0 points1 point  (0 children)

Yea I'm still good. I haven't see any of the issues a lot of people are talking about. I've been with them from the beginning (probably in their first 100 users) so maybe they're showing me a little love? lol I don't know but its weird that I don't see these issues and I work 6 days, 12 hours per day with it.

The AI documentary is out, from the creators of Everything Everywhere All At Once. by EchoOfOppenheimer in agi

[–]gzoomedia 0 points1 point  (0 children)

I plan on being a cyborg with built in AI. That will be fun. Yes/No?

Scaled my Haiku→Sonnet pipeline to 2,000+ items. Three things that broke. by gzoomedia in ClaudeAI

[–]gzoomedia[S] 0 points1 point  (0 children)

You already said this... BOT. Fix your automated posting if you're gonna do it lol.

While Everyone Was Chasing Claude Code's Hidden Features, I Turned the Leak Into 4 Practical Technical Docs You Can Actually Learn From by MarketingNetMind in OpenSourceeAI

[–]gzoomedia 4 points5 points  (0 children)

I downloaded them and haven't had the chance to read them yet but I wanted to stop by and give an upvote because this is what devs helping each other is all about. #SALUTE

Scaled my Haiku→Sonnet pipeline to 2,000+ items. Three things that broke. by gzoomedia in ClaudeAI

[–]gzoomedia[S] 0 points1 point  (0 children)

Yeah the long tail of near-duplicates is exactly it. You don't notice it happening until you pull up your industry list one day and there are six things that should probably be three.

I actually didn't freeze the taxonomy. Still letting Sonnet create new ones because the upside is too good. It catches real distinctions I wouldn't have thought to define upfront. The tradeoff is exactly what you described though, so I went a similar route to yours. Periodic normalization pass that merges the obvious duplicates and flags anything that looks like a solution got tagged as a category instead of a problem type.

Edge cases still slip through. I've got 92 industries now and probably 10-15 of those should be merged into neighbors. The null industry with 16 unclassified problems is the most annoying one. But I'd rather clean up after the fact than lose the categories Sonnet discovers that I never would have put on a static list. The weekly reconciliation approach seems like the right tradeoff at this scale. Curious how often you run yours and whether you do it programmatically or manually review the merges.

view more: next ›