14 points aaronbrethorst 1 hour ago 9 comments
Kalanos 44 minutes ago | parent
orthogonal_cube 41 minutes ago | parent
t-writescode 38 minutes ago | parent
jesse_dot_id 34 minutes ago | parent
Programming as I remember it pre-AI was essentially just toil and iteration. Programming with AI is nearly zero toil and iteration. The first prompt is like installing a framework. The next 200 prompts are programming.
marcus_holmes 33 minutes ago | parent
Writing a really good skill, or a spec document, feels more like programming than Project Management.
t-writescode 40 minutes ago | parent
Though I absolutely still have to go through it robustly to protect against Claudisms, comments only Claude understands, function names that make sense only with maximum context and a dictionary of that same context, etc. and it still overlaps function responsibility.
I’m not out of a job yet! Hah.
whateveracct 39 minutes ago | parent
marcus_holmes 36 minutes ago | parent
I'll send him the article and see if a crash-course in "this is how programmers think about problems" helps.
proc0 16 minutes ago | parent
Programming entails specific instructions and a high level of control, a.k.a. specifications. Of course, there are other kinds of specs, like business specs, but here we're talking about specs in the literal sense, where you are being specific of how the machine should work in a predictive sense. We don't do this with prompts, and we expect the AI to do this for us in the same way we expect a human engineer to take ambiguous directions and turn it into the actual computer spec.
The fact that domain knowledge makes for better prompts is a shortcoming of AI instead of a feature of prompting.