1. The Ticket Farming Model
Frontend engineers get stuck churning out features and components, preventing them from exploring web performance, design systems, state management, and monorepo architecture.
Hear it at 0:00 →Engineering video
1:04 · 29 September 2026
Stop Farming Tickets - Become a Better Frontend Engineer
Key concepts in this video:
2. Moving Beyond Component Coding
Instead of coding hundreds of components, engineers should look into tooling, code quality measures, and defining overall application architecture to meet modern interview expectations.
Hear it at 0:36 →Transcript
A lot of developers, a lot of front and devs were focusing a lot on building components. But when you build components, you don't have time to touch things around your components, like web performance or building a design system or getting deeper into the architecture of the whole app when it comes to state management, not just component state, or front end architecture like monorepos or micro front end architectures.
So, because you're doing a lot, you had to ship things and you had to push out turn out features, there was no time to get into this. So when I ask a lot of front end engineers that we work with, what were your responsibility, most of them get stuck into the ticket farming model where you're just churning out features. And the problem is nowadays, you go to interviews, most companies will require you to be able to build the whole thing, to be able to define the architecture.
And so you want to get deeper in the front end. Okay? Now, instead of doing, instead of coding the fifth component or the component number 115, you actually want to look around building components. Like tooling, code quality measures, all that.