←back to thread

280 points zachwills | 1 comments | | HN request time: 0.001s | source
Show context
Frannky ◴[] No.45229341[source]
Is it a good idea to generate more code faster to solve problems? Can I solve problems without generating code?

If code is a liability and the best part is no part, what about leveraging Markdown files only?

The last programs I created were just CLI agents with Markdown files and MCP servers(some code here but very little).

The feedback loop is much faster, allowing me to understand what I want after experiencing it, and self-correction is super fast. Plus, you don't get lost in the implementation noise.

replies(2): >>45229554 #>>45229778 #
ehnto ◴[] No.45229554[source]
Code you didn't write is an even bigger liability, because if the AI gets off track and you can't guide it back, you may have to spend the time to learn it's code and fix the bugs.

It's no different to inheriting a legacy application though. As well, from the perspective of a product owner, it's not a new risk.

replies(2): >>45229731 #>>45229830 #
zarzavat ◴[] No.45229731[source]
Claude is a junior. The more you work with it, the more you get a feel for which tasks it will ace unsupervised (some subset of grunt work) and which tasks to not even bother using it for.

I don't trust Claude to write reams of code that I can't maintain except when that code is embarrassingly testable, i.e it has an external source of truth.

replies(1): >>45231943 #
1. shaisjsh ◴[] No.45231943{3}[source]
> some subset of grunt work

What tasks are these? I don’t doubt they’re out there, but if I know the exact code that needs to be generated typing speed is not a bottle neck.

For me the slow part is determining what to write. And while AI helps with that (search, brainstorm, etc) by the time I know what to write trying to get the AI to enter those lines is often just a slow down. Much like writing up a ticket for a junior, I could write the code faster than I could write the English language rules describing how to write that code.