Working Surfacelink · 29 Sep · 08
08
A figure seen from behind, the back of the head showing, stands at a tall wooden board of hooks where one key hangs for each door along a corridor, while two small robots carry parcels down the corridor and each door opens only where its matching key hangs, the whole scene drawn with wide empty margins on every side.
Accidentally in Code

Good Architecture Is a Function of Time

Cate Huston · 29 September 2026

How-to · decisions · design systems · Agent context files

Read the original
Takeaway

Cate Huston, who led the rebuild of Twill, a recruiting platform, says a design system and a strict permissions model paid off once her team built with AI agents.

Summary

Cate Huston is the part-time chief technology officer of Twill, a platform where members, candidates and recruiters each see the same data in different ways. Her team rebuilt Twill in four months with tight scope, but she paid for a design system and a central model of who may see what. She writes that neither would have been worth it before AI agents wrote code, and that both caused far fewer problems than expected.

Key points
  • Huston argues that architecture makes good decisions easier over a period a team can reason about. A start-up can rarely see that far ahead, so good architecture is often too expensive for it to justify.
  • Her permissions model makes it easy to add a new type of user, and granting a permission takes one line in a table. She chose it because Twill's roles kept changing and because security depends on who can see what.
  • When she noticed architectural problems emerging elsewhere, she added more work of the same kind, such as replacing hand-written database queries with generated ones.
  • She argues that AI agents talk about time without experiencing it, so judging what is likely to change remains a human responsibility.
Implication

An engineering team that builds with AI agents may find that shared structure it once could not justify now pays for itself. Huston gives no numbers, and the application beyond Twill is an inference and is not the author's claim.

Suggested actions
Engineering

Keep every rule about who may see what in one central permissions table, so that adding a type of user or granting a permission is a one-line change.

Engineering

When AI agents write much of the code, invest in shared structure for the parts that change most, such as a design system or generated database queries.

Derived by Working Surface from the article. Source line: Neither of these choices would have been justifiable in a pre-agentic-development world.

Source issue

29 September 2026: when AI tools do the making, a team has to keep some of the old steps on purpose.