HN user

uduni

12 karma
Posts0
Comments12
View on HN
No posts found.

It's a skill set just like coding. You can embrace an elevated workflow where you can forget about the specific syntax and focus on the architecture and integration. It takes time to intuit what exactly the models are bad at, so you can forsee hallucinations and prevent them from happening in the first place. Yes you can write 1 line faster than Claude, but what about 10 lines? 100? 1000?

Cursor 3 4 months ago

I guess they are assuming LLMs will just get better and better until youn don't look at code at all.

Ignoring the fact that software will just keep getting more and more complex and interconnected... There will always be a new frontier or code and UX

I've been running a custom harness in production for months (code gen on cloud boxes), it's quite simple (<500 LOC). The model can use sed or other nice bash tricks to efficiently read. U really don't need any tool besides bash plus a good system prompt. Subagents are the same as the main agent (end with a summary). U can just remove tool results (oldest first) to save context, the model can read again if it needs to. High quality memory is the only difficult part. But that can also be solved with high quality documentation

" The real value in the AI ecosystem isn’t the model or the harness — it’s the integration of both working seamlessly together. "

Wut? The value in the ecosystem is the model. Harnesses are simple. Great models work nearly identically in every harness

Slop becomes impossible to maintain, and eventually product velocity slows down. Maybe it's ok for an ultra simple todo app, but for most apps code quality absolutely matters... Users expect snappy UX and all the new bells and whistles.

Why did Whatsapp grow so big while thousands of previous chat apps didn't code quality (scalability)

How is this different from previous layers of abstraction? React/JS dev don't have to think about memory management or a million other things that C++ application devs did. Instead that cognitive load is unbundled onto the framework maintainers, and frontend devs can be much more productive.

Obviously react/js didn't cause job apocalypse... Quite the opposite. It's just another abstraction layer making it possible to build a full application with less text. Prompts are the same pattern again IMO