The Melbourne practice
Listener Vertex Grid exists because event listener activity is easy to feel and hard to name. A double submit, a page that grows heavier the longer someone stays, a modal that ignores the close control — these arrive as complaints. They are, in the applications we see, usually a matter of what attached, what fired, and what failed to detach.
The practice sits at Level 7, 84 William Street, Melbourne VIC 3000. The name is literal. A vertex is the meeting point of listeners on a single event. The grid is the list we draw before anyone argues about a cause. We borrowed the newspaper habit of putting the map on paper so the walkthrough has something to point at.
We take work from teams in Melbourne first, and from elsewhere in Australia when the traces travel. We decline sittings that would require us to become a standing monitor, and we decline applications we cannot be shown. Credentials in this field are the reports and the walkthroughs; we do not print a wall of badges.
The relationship we want with a client is short and specific. You bring an application and a question about its listeners. We read, we write, we sit with you, and we stop. If a later release attaches new handlers, that is a new brief, not an unspoken continuation.
Rhys Calder
Rhys spent years in Melbourne application support being called when a page “just froze.” The cause, more often than a bad server, was a listener that attached on every visit and never left. He opened this practice to do that reading in the open, on paper, with the owning team in the room.
Anika Voss
Anika builds the catalogue of attach points when a surface count is too large for one sitting. She prefers a printed grid to a wall of screenshots, and she will send you back to gather a missing build rather than invent a handler she has not seen.