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 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.
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 19, 2026 • 5 min read
A website becomes an enterprise application when it starts owning operational state, sensitive submissions, permissions, integrations, and workflows the business cannot afford to treat like ordinary pages.
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.
Jun 19, 2026 • 3 min read
Retrieval is not plumbing in an AI product. It directly shapes whether the answer feels relevant, grounded, current, and useful.
Jun 10, 2026 • 5 min read
Permission design shapes how safely teams can self-serve, recover, and change a system without constant specialist involvement.
Jun 5, 2026 • 5 min read
Systems stay easier to operate when teams decide source of truth by workflow state and correction path instead of letting multiple tools feel authoritative at once.
May 31, 2026 • 4 min read
State names, field labels, and object vocabulary shape how quickly teams can understand, operate, and safely change a system after launch.
May 29, 2026 • 4 min read
Integrations stay safer and cheaper to evolve when teams define field meaning, ownership, and failure behavior before the first sync goes live.
May 26, 2026 • 8 min read
AI features improve when teams treat context assembly as product and systems design work instead of assuming the model can infer its way past noisy, stale, or incomplete inputs.
May 24, 2026 • 5 min read
Systems feel reliable when retry, rollback, reprocessing, and operator recovery paths are designed before failure forces them into existence.
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 16, 2026 • 4 min read
Boring integrations stay reliable because their contracts, ownership, and failure handling are explicit from the start.
May 14, 2026 • 4 min read
HubSpot architecture proves itself after launch, when editors, marketers, and ops teams start stretching the portal in production.
May 12, 2026 • 4 min read
Content models matter more than page templates once campaigns, channels, and teams need the system to reuse content cleanly.
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.
