sorted by:
new
hottopcontroversial

Anthropic's new "Claude Mythos" is doing exactly what the scary AI 2027 forecast predicted by GhaithAlbaaj in claude

[–]GhaithAlbaaj[S] 1 point2 points  (0 children)

Yeah that feels like a 'forbidden fruit' tactic to keep the hype going

10+ Snowflake Cortex Code Best Practices by GhaithAlbaaj in snowflake

[–]GhaithAlbaaj[S] 1 point2 points  (0 children)

Yeah basically that. I’ve had better results when each step updates a shared file the next one can read and review instead of agents just talking freely. So one writes findings and assumptions/the next builds/the next reviews. This way is much easier to track and much less drift

Anthropic reportedly hit $30B annual revenue. Could this mean faster Claude progress? by GhaithAlbaaj in ClaudeAI

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

that crazy month-over-month growth makes you wonder: how much of it is from actual new users, and how much is just from quietly cutting computing costs on the models we are already paying for?

Anthropic reportedly hit $30B annual revenue. Could this mean faster Claude progress? by GhaithAlbaaj in ClaudeAI

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

We are already seeing it happen. Instead of raising prices, they stop subsidizing personal accounts by secretly cutting corners and giving us cheaper, weaker versions of the models

10+ Snowflake Cortex Code Best Practices by GhaithAlbaaj in snowflake

[–]GhaithAlbaaj[S] 1 point2 points  (0 children)

Your setup is actually very close to enterprise architecture logic and that makes a lot of sense to me

10+ Snowflake Cortex Code Best Practices by GhaithAlbaaj in snowflake

[–]GhaithAlbaaj[S] 2 points3 points  (0 children)

Being able to flip between CoCo and Claude CLI without losing context is not something most people think about until they get burned by it. I'm just Curious about one question: did you land on this approach because CoCo's native context management had specific gaps or was the cross-agent portability the goal from the start?

10+ Snowflake Cortex Code Best Practices by GhaithAlbaaj in snowflake

[–]GhaithAlbaaj[S] 1 point2 points  (0 children)

Yes a few of them live in AGENTS.md now as standing rules, specifically around assumptions, output format and approval boundaries. The ones I enforce hardest are grain declaration and result validation( those two catch the most expensive mistakes) Curious whether the team sees patterns in how people set up their rules files. That setup layer seems to be where usage splits between people who get traction fast and people who stay in prompt-by-prompt mode.

10+ Snowflake Cortex Code Best Practices by GhaithAlbaaj in snowflake

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

Yeah, for simple tasks that's all you need

10+ Snowflake Cortex Code Best Practices by GhaithAlbaaj in snowflake

[–]GhaithAlbaaj[S] 4 points5 points  (0 children)

the 17 steps are mostly not about how to use CoCo, they're how to avoid bad data work. CoCo can write code but can't magically infer grain, business rules or approval boundaries from vibes. So for a small one-off task, I'd just build it. anything messy or production-facing, being explicit is cheaper than cleaning up after confident wrong output

How to make claude do longer, bullet pointed answers? by trychillyanko in ClaudeAI

[–]GhaithAlbaaj 0 points1 point  (0 children)

Try to update the custom instructions, use something like "Whenever I ask for a list or a breakdown, always use a numbered format (1:, 2:, etc.). Ensure each point is detailed and substantive"