HackerTrans
トップ新着トレンドコメント過去質問紹介求人

stitched2gethr

no profile record

投稿

[untitled]

1 ポイント·投稿者 stitched2gethr·3 か月前·0 コメント

[untitled]

1 ポイント·投稿者 stitched2gethr·3 か月前·0 コメント

[untitled]

1 ポイント·投稿者 stitched2gethr·4 か月前·0 コメント

Gartner: Market Guide for API and MCP Testing Tools

gartner.com
4 ポイント·投稿者 stitched2gethr·4 か月前·0 コメント

[untitled]

1 ポイント·投稿者 stitched2gethr·4 か月前·0 コメント

コメント

stitched2gethr
·先月·議論
Without saying that I think LLMs are alive, I do think it matters. I have personally been cruel to an LLM in ways that would make me ashamed if I suddenly understand that it had feelings.
stitched2gethr
·3 か月前·議論
Try this: `claude --model claude-opus-4-6`
stitched2gethr
·3 か月前·議論
> Anthropic already has a tool for it Yes, but Anthropic built this tool after OpenClaw, because of OpenClaw.
stitched2gethr
·3 か月前·議論
A question asking how your project compares to x so I don't have to do the research for myself.
stitched2gethr
·3 か月前·議論
This is intriguing.

On another note, I do not understand how posts make it to the top of the front page with essentially no comments.
stitched2gethr
·4 か月前·議論
https://www.linkedin.com/posts/nicolaschaillan_there-you-hav...
stitched2gethr
·4 か月前·議論
Try proxymock. It's not open source but it is free to use.
stitched2gethr
·4 か月前·議論
It's not ready to make important decisions. But that's not the same as making important contributions.
stitched2gethr
·4 か月前·議論
We're way past that.
stitched2gethr
·4 か月前·議論
Insane. I'm terrified and I can't wait.
stitched2gethr
·4 か月前·議論
It all depends on the model and how much you use it of course. We're running Opus 4.6 and on a light day it spends a dollar or two. This is just a few simple operations like "create a ticket for ..." and it's regular heartbeat checks. The heaviest day I see is $110 and on that day we were basically talking to it and having it implement features all day long.
stitched2gethr
·5 か月前·議論
We did the same and I wrote (admittedly had AI write) about it.

https://speedscale.com/blog/building-speedy-autonomous-ai-de...
stitched2gethr
·5 か月前·議論
I had to scroll too far to find this take. 100%.

This is like saying the CLAUDE.md or AGENTS.md is irrelevant because the LLM generated it.
stitched2gethr
·5 か月前·議論
It's all about how full the context is, right? For a task that can be completed in 20% of the context it doesn't matter, but you don't want to fill your context with exploration before you do the hard part.

I have actually found something close to the opposite. I work on a large codebase and I often use the LLM to generate artifacts before performing the task (for complex tasks). I use a prompt to say "go explore this area if the code and write about it". It documents concepts and has pointers to specific code. Then a fresh session can use that without reading the stuff that doesn't matter. It uses more tokens overall, but includes important details that can get totally missed when you just let it go.
stitched2gethr
·5 か月前·議論
I think that's partly the point. This is the tool that everyone wanted but couldn't quite describe. Not saying he's a genius, but he was the first to will it into existence.
stitched2gethr
·5 か月前·議論
Try running `/insights` with Claude Code.
stitched2gethr
·5 か月前·議論
I think the rationale is that with the right tools you can move much faster, and not burn everything to the ground, than just rawdogging Claude. If you haven't bothered setting up extra tools you may still be faster / better than old you, but not better than the you that could be. I'm not preaching, that's just the idea.

> That is not software engineering or development, it's brogrammer trash.

Yes, but it's working. I'm still reading the code and calling out specific issues to Claude, but it's less and less.
stitched2gethr
·5 か月前·議論
I think it also presumes that the skills of today won't be helpful in making you better, faster, stronger at knowing what to learn tomorrow. Skateboarding ain't snowboarding but I guarantee the experience helps.
stitched2gethr
·5 か月前·議論
And how are you using it now? Have you seen real value weeks or months on?
stitched2gethr
·5 か月前·議論
This is what we're working on at Speedscale. Our methods use traffic capture and replay to validate what worked before still works today.