|
|
|
|
|
by solatic
323 days ago
|
|
It's not so much typing that is valuable for vibecoding, but being able to give the agent hooks into tooling that provides negative feedback for errors. The easiest is typing, sure, because it's built into the compiler. But you can also add in static analysis linters and automated testing, including - notably - testing for performance. Of course, you have to tell the agent to set up static analysis linters first, and tell the agent to write tests. But then it'll obey them. The reason why large enterprises could hire armies of juniors in the past, safely, was because they set up all manner of guardrails that juniors could bounce off of. Why would you "hire" a "junior" agent without the same guardrails in place? |
|