JyB

While that is true, the overarching point is that it fundamentally still is, just a story. You're just describing real world consequences, precisely because humans/societies believe in that story and enforce it.

What credentials related to software engineering? Please expand and do not post nebulous comments like these.

Courage is not the appropriate word

This specifically is super annoying.

Restrictions don’t have to be confusing, they can be clear. You are missing the whole point.

modern MCP clients do smart tool search that obviates the entire "I am sending the full list of tools back and forth" mode of operation

This has always surprised me as this always comes up in MCP discussions. To me, it just seem like a matter of updating the protocol to not have that context hungry behaviour. Doesn't seem like an insurmountable problem technically.

Glad you say it has already been addressed. Was the protocol itself updated to reflect that? Or are you just referring to off-spec implementations?

I don’t know if you’re being serious but that’s laughable

How is that specific to antigravity? Seem like it could happen with a bunch of tools

That’s exactly what it is in essence. The MCP protocol simply doesn’t have any mechanism specifications (yet) for not loading tools completely in the context. There’s nothing really strange about it. It’s just a protocol update issue.

The MCP standard will and has to evolve to address this context issue. It’s a no brainer and this is a perfect example of the direction mcp is going / will go. There’s fundamentally nothing wrong, it’s just protocols updates that have to occur.

In also interested in n8n. From what I gathered it’s a everything baked in app, not a lib. Meaning that unless you re doing upstream contributions you don’t actually code anything. Just manage big configs. How are you planning to use this toolkit with it?

Concurrency. Unless you’re happy stopping the world on llm io… Go excels at handling network calls and the like. It’s basically what agents are.

I think you are right.

Claude Skills just seem to be the same as MCP prompts: https://modelcontextprotocol.io/specification/2025-06-18/ser...

I don't really see why they had to create a different concept. Maybe makes sense "marketing-wise" for their chat UI, but in Claude Code? Especially when CLAUDE.md is a thing?

I'm super confused as well. This seems like exactly that, just some default prompt injections to chose from. I guess I kinda understand them in the context of their claude chat UI product.

By I don't understand why it's a thing in Claude Code tho when we already have Claude.md? Could also just point to any .md file in the prompt as preamble but not even needed. https://www.anthropic.com/engineering/claude-code-best-pract...

That concept is also already perfectly specd in the MCP standard right? (Although not super used I think?) https://modelcontextprotocol.io/specification/2025-06-18/ser...

I never understand why there's always one of the top comment on every Go post being derogatory and mentioning Rust. It never fails. It starts to feel like a weird mix of defensiveness and superiority complex.

No one think any form of "prompt engineering" "guardrails" are serious security measures right?

Assuming you're using GitHub or similar, make pushing branches and creating PRs part of their prompts, and review on the GitHub app or equivalent? Seem like an orthogonal problem to those LLMs tools.

I can start a Claude Code session and if I need to leave my laptop, I can respond from my phone anywhere

I've been looking for this for some time now. This is amazing if it delivers.

That's a funny response I have to admit. No 100% serious, I don't see the advantage.

That's exactly how you should do it. You can also plug in an MCP for your CI or mention cli.github.com in your prompt to also make it iterate on CI failures.

Next you use claude code instead and you make several work on their own clone on their own workspace and branches in the background; So you can still iterate yourself on some other topic on your personal clone.

Then you check out its tab from time to time and optionally checkout its branch if you'd rather do some updates yourself. It's so ingrained in my day-to-day flow now it's been super impressive.

I’m really wondering what internally causes this. No one likes it when they have outages, but it keeps happening. Is this a culture thing? Like pressure to ship features fast? Some under staffed teams or lack of ownership on some crucial components?

Because iterating multiple sessions through multiple terminals is obviously more efficient and seamless than interacting thought a scuffed IDE side panel ui.

Better prompts?

Same question. I don’t understand what they mean by that. It obviously seem pretty central to how Claude Code is so effective.

How can it not be exactly what’s happening?

I thought Claude code was pay as you go!?

There is something much deeper going on when you force yourself to actually write things down. This is especially relevant in engineering. That is why "RFCs" are so prevalent in many tech companies. They are often just as useful to the writer as they are to the reviewers.

There is the Claude Code cli, now Gemini CLI. Where is ChatGPT CLI?

"LLMs are one of the technologies that exist, like autocorrection and CAD"

Pretending it's on par with these. No need for more. Seem inevitable enough.