←back to thread

Nobody knows how to build with AI yet

(worksonmymachine.substack.com)
526 points Stwerner | 1 comments | | HN request time: 0.215s | source
Show context
fizx ◴[] No.44616685[source]
The "time dialation" is real. I mostly manage these days, yet my fun projects progress faster than they ever have, because I can prompt in the 2 minutes between meetings, and come back to significant progress.
replies(1): >>44616741 #
jvanderbot ◴[] No.44616741[source]
Yes, it's not faster to develop with AI if you watch it work. It's faster to develop with AI if you parallelize. Typing was never the bottleneck, but is is a now-parallelizeable part of the pipeline.
replies(2): >>44616810 #>>44616828 #
nojs ◴[] No.44616828[source]
> Yes, it's not faster to develop with AI if you watch it work.

It’s actually a lot faster. You read the diffs as soon as they start coming in, and immediately course correct or re-prompt when you see bad mistakes.

replies(3): >>44616886 #>>44616897 #>>44621822 #
1. wrs ◴[] No.44616897[source]
Indeed, I hit the stop button quite a bit when Claude goes off course. Then make a note of the right choice so maybe it won't do that again, revert and proceed. I have the feeling there is an optimal size of project proportional to the context size, where you can fit the critical design points into the context and/or there are enough examples in the code of how things should be done.