←back to thread

Andrej Karpathy: Software in the era of AI [video]

(www.youtube.com)
1479 points sandslash | 1 comments | 19 Jun 25 00:33 UTC | HN request time: 0.285s | source
Show context
jes5199 ◴[19 Jun 25 16:06 UTC] No.44319936[source]▶
okay I’m practicing my new spiel:

this focus on coding is the wrong level of abstraction

coding is no longer the problem. the problem is getting the right context to the coding agent. this is much, much harder

“vibe coding” is the new “horseless carriage”

the job of the human engineer is “context wrangling”

replies(3): >>44320141 #>>44320829 #>>44323742 #
1. throw234234234 ◴[20 Jun 25 00:21 UTC] No.44323742[source]▶
I will counter this with the fact that sometimes, and depending on the abstraction level that you are trying to solve/work at code or some other determinstic language is the right and easier way language to describe the context. This doesn't just apply to SWE, but all forms of engineering (electrical, civil, mechanical, etc).

We have math notation for maths, diagrams for circuits, plans for houses, etc etc. Would hate to have to give long paragraphs of "English" to my house builder and watch what the result could be. Feels like being a lawyer at this point. English can be appropriate and now we also have that in our toolbox.

Describing context at the abstraction level and accuracy you care about has always been the issue. The context of what matters though as you grow and the same system has to deal with more requirements at once together IMV is always the challenge in ANY engineering discipline.