1. Fixing the Factory Over Components
Focusing on improving the building quality pipeline and overall system context rather than just repairing individual components or endpoints.
Hear it at 0:00 →Engineering video
0:47 · 15 October 2026
stop fixing the code fix the factory
Key concepts in this video:
2. Evaluating Systemic Consequences
Considering the broader, long-term impacts of coding patterns across the codebase, such as potential increases in bug density and testing efforts.
Hear it at 0:15 →Transcript
So a lot of what I do these days is kind of looking at our end results, are going to the source code and I got the components, I'm like, okay, what do I need to implement in the building quality pipeline or the context to make this better. So I'm not fixing a component, I'm fixing again the factory. That's a big mindset shift you need to take. And you always think in second or third world consequences.
It's not about if we change this and we make this a custom hook, how would the component change, but rather, if the agents were started writing custom hooks all over the code base, what will be the end consequences? Is that going to increase the bug density? Is that going to increase our testing efforts? So that's how you think as opposed to back in the days where I had to do all the ground works, I would spend a lot of time just building a specific end point or component or view, and then when I finish that, then I put on my architect hat and then I look at the overall kind of system.