The Janitor Pattern

There is a role that does not appear in any job description but exists on almost every frontend team. You know it when you are living it. You spend more time navigating someone else's decisions than making your own. Every new feature requires archaeology. Every bug fix risks destabilizing something three layers removed. You are not building anymore. You are maintaining the illusion that the codebase is still under control. This is the Janitor Pattern. And it is not caused by bad developers. It is caused by a structural assumption that gets made early, often before the first line of code is written, and almost never gets questioned: that the frontend is a UI layer. A skin over the real system. Something you bolt on at the end, staff with whoever is available, and optimize last if at all. That assumption is wrong. And the codebase you inherit six months later is the proof. How the Assumption Takes Hold It rarely starts as a conscious decision. It starts as a staffing model. The backend e