HackerTrans
TopNewTrendsCommentsPastAskShowJobs

subomi

no profile record

Submissions

Steering the Ship

keygen.sh
3 points·by subomi·5 mesi fa·0 comments

Forward Compatible Unions in TypeScript

speakeasy.com
2 points·by subomi·6 mesi fa·0 comments

Building a High-Performance OpenAPI Parser in Go

speakeasy.com
39 points·by subomi·7 mesi fa·9 comments

Preparing your repo for AI development

speakeasy.com
4 points·by subomi·7 mesi fa·0 comments

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

speakeasy.com
1 points·by subomi·8 mesi fa·0 comments

Open Source Your Product

tommoor.com
2 points·by subomi·9 mesi fa·0 comments

I was wrong about AI Coding

arslan.io
3 points·by subomi·10 mesi fa·0 comments

MCP Evals

huggingface.co
1 points·by subomi·10 mesi fa·0 comments

comments

subomi
·6 mesi fa·discuss
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 mesi fa·discuss
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.