Engineering video
0:46 · 10 October 2026
The speaker explains: engineers guarantee the quality of their applications and must be able to defend specific technical choices like state management or CSS styling, or risk having their skills invalidated.
Hear it at 0:10 →The speaker explains: with text and code generation widely available from large language models, speed and quantity are no longer scarce, making quality the primary focus.
Hear it at 0:36 →So the problem here is that at the end of the day, you're not a product person, you're not a vibe coder, you're a software engineer. So you'll be always evaluated on your technical knowledge. Now, nobody cares if you will build the application with AI or not, you're the one guaranteeing for the quality. And and I see a lot of interviews moving towards that direction where they'll make you build something.
And then they'll go in and be like, okay, what state management philosophy you chose? Why are we writing CSS in this way? And if you cannot defend that, then they will completely unvalidate all your skills because they assume that you are not in a position where you can make technical decision. So, again, the scarcity after we have large language models and text generation at the scale we're doing it in code generation, is not anymore quantity or speed. It's always quality.
