Office planner
- Users
- Office managers
- Before
- Seating plans on paper
- After
- A native SVG map: people and equipment at desks across six offices
The project support team ran projects in Google Sheets with VBA macros, accounting lived in Excel, and office managers planned seating on paper. Over eighteen months I built them five modules of one Nuxt system as the team’s only frontend developer.
I worked on the ERP alongside everything else from day one. The other modules I built one at a time, in the order shown.
My favourite module
This is where I first thought hard about rendering a lot of data. With all five levels open, the table grows to 25,000 rows and 20 columns. A browser can’t handle that many DOM nodes, so I render only the rows in view and load nested levels when someone opens them.
Users came from Google Sheets and expected it to behave the same way. The table supports arrow keys, block copy and paste, drag-to-fill and in-cell editing. TanStack Query caches the data. An edit shows up at once and rolls back if the server rejects it.
The project also had exemplary code hygiene: strict ESLint, pre-commit hooks and a clear module structure.
Expand everything and watch the counter. Move around with the arrow keys, drag a value by the cell corner, copy a block and paste it elsewhere. Switch the network to “Flaky” and edit a cell.
A story
The funniest bug in the project schedule. The server sent a tree where every row had a children array holding the next level. Sometimes the query cache drifted from what the backend had, the store crashed, and nested rows vanished from the table. Hence the name.
We changed the transport. The server started pushing changes over WebSocket, and I patched them into the query cache one by one. The client showed its own edits optimistically and rolled them back on error.
The hardest module
Management planned quarters and years in this module and spent a long time deciding how they wanted to see the data. It started as a plain Gantt chart. Then came the idea of pairing it with a table, and that version finally stuck.
To avoid rewriting the module a fifth time, I changed how I worked. I built each new idea as a quick prototype from open-source components and showed it in a meeting. Proper development, to spec and in the company style, started only after sign-off.
In the final version the table and the Gantt chart scroll in sync, colleagues’ edits arrive over WebSocket, and a snapshot freezes the plan on a date so you can compare it with the current one later.
Drag a bar to another month or stretch it by its right edge. A colleague is editing the plan too, and her changes arrive on their own. Press “Take snapshot”, change a couple of rows and see where the plan drifted from it.
The first module
This is where I started. Office managers tracked equipment and seated people on paper, and at the peak the company had six offices with 2–3 floors and 50–100 desks each.
I wrote the map in native SVG with my own logic: you assign a person or equipment to a desk, and the office manager sees right away what is free.
Pick a person and click a free desk, or drag them onto it. Click a taken desk to see what is on it.
Accounting kept project documents in Excel. The register grew to 2,500 of them. Acts and invoices come from a template or by hand, PDF and DOCX files upload straight into the record, and amounts are edited in cells like in a familiar spreadsheet.
The company first looked at off-the-shelf ERPs, but any of them would need long customisation for its processes. Our module grew with all the others from day one: timesheets, tasks as Kanban, table and Gantt, leave requests with approval. On peak days up to 500 people used it at once.
All five modules live in one Nuxt application and share a common layer: the query cache, the WebSocket channel and a Naive UI theme I adapted to the company style. Linters, pre-commit hooks and Nuxt deployments were on me too.
For the first six months I worked under a lead developer, then on my own with team lead review, and I reviewed my colleagues’ code.
Often there was no spec. I sat in review meetings with management and clients and gathered requirements straight from the people who would use the system. Their feedback was positive across the board.
The company’s interfaces are private, so the demos on this page are my own reconstructions with fictional data. No product code, data or design made it here.