Oct 5, 2026 • 5 min read
Technical Debt Needs a Repayment Trigger
A technical shortcut becomes manageable when its record includes the consequence, the affected work, and a clear trigger for paying it back.
ArchitectureDeliveryOperations
Dev Blog
Building systems that survive real use.
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.
Explore the blog
Find your next read.
20 articles in Architecture
Clear filtersSep 10, 2026 • 5 min read
Build or Buy Starts With the Cost of Leaving
A build-versus-buy decision should account for data portability, customization, operating effort, and the cost of changing direction later.
ArchitectureProductClient Work
Aug 27, 2026 • 6 min read
Building Five Party Games on One Platform
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.
Game DevelopmentArchitectureDelivery
Jul 28, 2026 • 6 min read
Feature Flags Are Operational Controls
Feature flags are not just a way to hide unfinished UI. They are operational controls that need owners, evidence, rollback rules, and cleanup dates.
DeliveryOperationsArchitecture
Jul 19, 2026 • 5 min read
When a Website Becomes an Enterprise Application
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.
ArchitectureProductSystems
Jul 13, 2026 • 5 min read
Large Enterprise Migrations Are More Than Moving Content
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.
ArchitectureOperationsDelivery
Jun 19, 2026 • 3 min read
Retrieval Quality Is Product Quality
Retrieval is not plumbing in an AI product. It directly shapes whether the answer feels relevant, grounded, current, and useful.
AIDataArchitecture
Jun 10, 2026 • 5 min read
Permissions Are Part of the Operating Model
Permission design shapes how safely teams can self-serve, recover, and change a system without constant specialist involvement.
OperationsGovernanceArchitecture
Jun 5, 2026 • 5 min read
Source of Truth Is a Workflow Decision
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.
ArchitectureDataSystems
May 31, 2026 • 4 min read
Naming Is Part of the Architecture
State names, field labels, and object vocabulary shape how quickly teams can understand, operate, and safely change a system after launch.
ArchitectureOperationsGovernance
May 29, 2026 • 4 min read
Data Contracts Make Integrations Easier to Change
Integrations stay safer and cheaper to evolve when teams define field meaning, ownership, and failure behavior before the first sync goes live.
IntegrationsDataArchitecture
May 26, 2026 • 8 min read
Most AI Product Problems Are Context Problems
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.
AISystemsArchitecture
May 24, 2026 • 5 min read
Recovery Paths Are Part of the Product
Systems feel reliable when retry, rollback, reprocessing, and operator recovery paths are designed before failure forces them into existence.
OperationsArchitectureSystems
May 22, 2026 • 4 min read
Good Workflows Make Ownership Obvious
Workflow quality depends on whether each state has a clear owner, a clear next action, and a clear escalation path.
SystemsDeliveryArchitecture
May 16, 2026 • 4 min read
The Case for Boring Integrations
Boring integrations stay reliable because their contracts, ownership, and failure handling are explicit from the start.
ArchitectureSystemsDelivery
May 14, 2026 • 4 min read
The Real HubSpot Architecture Work Starts After Launch
HubSpot architecture proves itself after launch, when editors, marketers, and ops teams start stretching the portal in production.
HubSpotArchitectureOperations
May 12, 2026 • 4 min read
Content Models Outlast Page Templates
Content models matter more than page templates once campaigns, channels, and teams need the system to reuse content cleanly.
HubSpotArchitectureSystems
May 6, 2026 • 4 min read
What to Instrument Before a New System Goes Live
Launches go better when teams instrument critical workflow states, delays, failures, and human intervention before go-live.
DeliveryOperationsArchitecture
May 4, 2026 • 4 min read
Shipping Fast Without Building Fragile Systems
Fast delivery only lasts when teams keep change cheap and refuse to let temporary shortcuts harden into architecture.
DeliveryArchitectureSystems
May 1, 2026 • 5 min read
Why This Dev Blog Exists
This dev blog is where I write about the architectural, operational, and delivery decisions that determine whether systems keep working after launch.
ArchitectureDeliverySystems