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

subomi

no profile record

投稿

Steering the Ship

keygen.sh
3 ポイント·投稿者 subomi·5 か月前·0 コメント

Forward Compatible Unions in TypeScript

speakeasy.com
2 ポイント·投稿者 subomi·6 か月前·0 コメント

Building a High-Performance OpenAPI Parser in Go

speakeasy.com
39 ポイント·投稿者 subomi·7 か月前·9 コメント

Preparing your repo for AI development

speakeasy.com
4 ポイント·投稿者 subomi·7 か月前·0 コメント

Reducing MCP token usage by 100x – you don't need code mode

speakeasy.com
1 ポイント·投稿者 subomi·8 か月前·0 コメント

Open Source Your Product

tommoor.com
2 ポイント·投稿者 subomi·9 か月前·0 コメント

I was wrong about AI Coding

arslan.io
3 ポイント·投稿者 subomi·10 か月前·0 コメント

MCP Evals

huggingface.co
1 ポイント·投稿者 subomi·10 か月前·0 コメント

コメント

subomi
·6 か月前·議論
I was here a few weeks ago, but I'm now on the CC train. The challenge is that the terminal is quite counterintuitive. But if you put on the Linux terminal lens from a few years ago, and you start using it. It starts to make sense. The form factor of the terminal isn't intuitive for programming, but it's the ultimate.

FYI, I still use cursor for small edits and reviews.
subomi
·6 か月前·議論
Why do we all of a sudden hold these agents to some unrealistic high bar? Engineers write bugs all the time and write incorrect validations. But we iterate. We read the stacktrace in Sentry and realise what the hell I was thinking when I wrote that, and we fix things. If you're going to benefit from these agents, you'd need to be a bit more patient and point them correctly to your codebase.

My rule of thumb is that if you can clearly describe exactly what you want to another engineer, then you can instruct the agent to do it too.