Engineering video
1:12 · 25 September 2026
An engineer's ability to guide AI successfully depends on their core skills, enabling them to specify requirements and verify results—such as frontend engineers handling performance and bundle sizes better when vibe coding than backend engineers.
Hear it at 0:00 →Code is not going away; instead, coding is transforming into low-level design where humans focus on how components and custom hooks work while AI handles the repetitive generation of code, effectively scaling the engineer's judgment.
Hear it at 0:41 →The paradox is to guide the your ability to guide the AI is proportional to your skills. So even when in vibe coding, you'll see front end engineers getting much better results today than a back end engineer. So a lot of people are saying that it's about creativity. I dare to disagree. I think if you understand the code and you understand how components are built together, how state management works, your first version of everything will be much better than the 10th version of somebody else.
A a civilian, let's say, a back end engineer, let's say they want a vibe code some front end. They will realize they need to take care of performance, web performance, right the bundle size, way deep into the product. Whereas a good engineer in the front end has already solved all those because they can specify that and verify. So I don't think code is going away, but I think code is transforming and coding into what we call low-level design.
Well you go into a component or a custom hook and you just look at the design of how it works, and then you zoom out. But then you don't have to write that component 50,000 times. It's going to be the AI that does it. So in the best way you can use the AI as a way to scale your judgment. In context engineering and skills, it's just your ability to really scale yourself using an LLM.
