Dev Blog
Essays on HubSpot architecture, AI workflow design, and engineering delivery for teams that care about what happens after launch, when operators, edge cases, and changing requirements put the real system on display.
Aug 28, 2026 • 7 min read
Games make software feedback immediate. Building five of them sharpened how I think about iteration, device realities, content quality, and the difference between correct and genuinely enjoyable.
Aug 27, 2026 • 6 min read
Five party games can share a platform without becoming the same game. The useful architecture keeps sessions, delivery, and operations common while leaving each rule system explicit.
Aug 14, 2026 • 5 min read
Two new public recommendations describe the same kind of delivery I value: listen carefully, take ownership, translate ambiguity, improve the underlying system, and leave a team with something maintainable.
Aug 12, 2026 • 6 min read
Synchronized lyrics look simple in a player, but trustworthy line timing depends on identity, source text, alignment, validation, export, and a local QA gate.
Aug 8, 2026 • 5 min read
A television app has different input, distance, attention, and release constraints than a web page. Designing for it means treating the device as its own computing environment.
Aug 1, 2026 • 6 min read
If an AI feature can change a customer decision, an operator workflow, or a safety boundary, its evaluation plan is part of the product requirement.
Jul 28, 2026 • 6 min read
Feature flags are not just a way to hide unfinished UI. They are operational controls that need owners, evidence, rollback rules, and cleanup dates.
Jul 24, 2026 • 5 min read
Good technical discovery reduces delivery risk by turning uncertainty into explicit decisions, owners, constraints, and acceptance criteria instead of producing a large document that nobody operates from.
Jul 13, 2026 • 5 min read
Enterprise migrations succeed when teams treat them as coordinated changes to traffic, data, integrations, ownership, and operations rather than as a bulk transfer between platforms.
Jul 9, 2026 • 5 min read
Forward Deployed Engineers sit close to customers, but the role is more than technical consulting. They own the difficult path from an ambiguous business problem to a working production system.
Jun 7, 2026 • 5 min read
Internal systems work better when teams design the queue itself as a product surface instead of focusing only on the single-record happy path.
Jun 4, 2026 • 5 min read
Prompt edits can change routing, escalation, and decision quality in production, so they deserve versioning, evaluation, and rollback.
May 22, 2026 • 4 min read
Workflow quality depends on whether each state has a clear owner, a clear next action, and a clear escalation path.
May 21, 2026 • 5 min read
Useful documentation reduces coordination drag by making state, ownership, and recovery legible without extra meetings.
May 20, 2026 • 4 min read
Operational simplicity lets teams publish, recover, and change systems without constant escalation or hidden process drag.
May 18, 2026 • 4 min read
Internal tools succeed when they reduce operator friction in real queue work, not just when they look polished in demos.
May 16, 2026 • 4 min read
Boring integrations stay reliable because their contracts, ownership, and failure handling are explicit from the start.
May 6, 2026 • 4 min read
Launches go better when teams instrument critical workflow states, delays, failures, and human intervention before go-live.
May 4, 2026 • 4 min read
Fast delivery only lasts when teams keep change cheap and refuse to let temporary shortcuts harden into architecture.
May 1, 2026 • 5 min read
This dev blog is where I write about the architectural, operational, and delivery decisions that determine whether systems keep working after launch.
