Earlier quoted context omitted.
One might argue that it’s not too too different from higher level abstractions when using libraries. You get things done faster, write less code, library handles some internal state/memory management for you. Would one be uneasy about calling a library to do stuff than manually messing around with pointers and malloc()? For some, yes. For others, it’s a bit freeing as you can do more high-level architecture without g…
I see this comparison made constantly and for me it misses the mark. When you use abstractions you are still deterministically creating something you understand in depth with individual pieces you understand. When you vibe something you understand only the prompt that started it and whether or not it spits out what you were expecting. Hence feeling lost when you suddenly lose access to frontier models and take a look…
You’re overestimating determinism. In practice most of our code is written such that it works most of the time. This is why we have bugs in the best and most critical software.
I used to think that being able to write a deterministic hello world app translates to writing deterministic larger system. It’s not true. Humans make mistakes. From an executives point of view you have humans who make mistakes and agents who make mistakes.
Self driving cars don’t need to be perfect they just need to make fewer mistakes.