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.
Topics
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 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 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 10, 2026 • 5 min read
Durable AI systems win by structuring decisions, preserving evidence, and designing the workflow around the model for operators.
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.
