Dwellworks

Twenty independent bundles inside a Razor monolith rather than one single-page app. That is an inherited constraint rather than my decision, and it is the right one for this platform: each page ships on its own and a broken build cannot take the rest down with it, which matters on an application running live relocations. The cost is duplicated vendor weight in every bundle and no shared client-side router.

Error boundaries per cell rather than per page. A page-level boundary is less code and gives a cleaner failure, but it blanks a consultant's screen in the middle of a move. Containing the failure to the cell that caused it means a grid degrades instead of disappearing, and the stack trace still reaches the logger.

When a company moves an employee to another city or country, someone has to run that move: find the family a home and a school, handle the lease and the visa paperwork, and track it through to move-out. This is the platform that manages it.

It is a long-running modernization rather than a greenfield build — an established .NET application with React carved into it page by page over years. That is a more interesting engineering problem than a clean slate, because every change has to work with decisions made by people who have moved on.