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.
43 articles
Sep 28, 2026 • 5 min read
AI Features Need Unit Economics
The useful cost of an AI feature includes retries, retrieval, review, and support—not just the price of one successful model response.
AIProductOperations
Sep 19, 2026 • 4 min read
Performance Budgets Should Follow User Journeys
Web performance work becomes more useful when budgets track the journeys people complete, including repeat navigation, search, and submission.
PerformanceProductDelivery
Sep 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
Sep 4, 2026 • 4 min read
Accessibility Is a Workflow Requirement
Accessibility becomes practical when teams define how people complete real tasks, including keyboard navigation, validation, and confirmation.
AccessibilityProductDelivery
Aug 28, 2026 • 7 min read
What Game Development Taught Me About Shipping Software
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.
Game DevelopmentProductDelivery
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
Aug 14, 2026 • 5 min read
The Work Behind Two New Client Recommendations
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.
Client WorkCareersDelivery
Aug 12, 2026 • 6 min read
Timed Lyrics Are a Data Engineering Problem
Synchronized lyrics look simple in a player, but trustworthy line timing depends on identity, source text, alignment, validation, export, and a local QA gate.
DataAudioDelivery
Aug 8, 2026 • 5 min read
The Living Room Is a Different Computing Environment
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.
ProductRokuDelivery
Aug 4, 2026 • 5 min read
Desktop AI Needs a Hardware Budget
A useful desktop AI product treats memory, model formats, fallbacks, and degraded states as product decisions—not surprises for the person using it.
AIDesktopPerformance
Aug 1, 2026 • 6 min read
AI Evaluations Are Product Requirements
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.
AIProductDelivery
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 24, 2026 • 5 min read
Technical Discovery Should Produce Decisions, Not Documents
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.
DeliveryOperationsGovernance
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
Jul 9, 2026 • 5 min read
What a Forward Deployed Engineer Actually Does
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.
DeliverySystemsCareers
Jul 1, 2026 • 3 min read
The Model Is Only One Part of the Interface
AI product quality depends on the full interface around the model: inputs, controls, evidence, state, review paths, and recovery behavior.
AIProductSystems
Jun 28, 2026 • 2 min read
Good AI Tools Preserve the Decision Trail
AI tools are easier to trust and improve when they preserve inputs, evidence, decisions, approvals, and corrections instead of only storing the final output.
AIGovernanceOperations
Jun 22, 2026 • 3 min read
When AI Should Ask Before Acting
The best AI workflows know when to pause for clarification, approval, or missing context instead of forcing a confident action from uncertain inputs.
AIOperationsProduct
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 14, 2026 • 3 min read
AI Agents Need Operating Boundaries
AI agents become more useful when their authority, inputs, tools, and escalation paths are defined before they start acting inside real workflows.
AIAutomationGovernance
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 7, 2026 • 5 min read
Queues Are a Product Surface
Internal systems work better when teams design the queue itself as a product surface instead of focusing only on the single-record happy path.
OperationsSystemsDelivery
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
Jun 4, 2026 • 5 min read
Prompt Changes Are Production Changes
Prompt edits can change routing, escalation, and decision quality in production, so they deserve versioning, evaluation, and rollback.
AIDeliveryOperations
Jun 1, 2026 • 6 min read
Documentation Is Part of the AI Stack
AI systems get more reliable when documentation defines the terms, states, tool behavior, and exception handling the workflow depends on.
AIDocumentationSystems
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 21, 2026 • 5 min read
Documentation Should Lower Coordination Cost
Useful documentation reduces coordination drag by making state, ownership, and recovery legible without extra meetings.
DocumentationDeliveryOperations
May 20, 2026 • 4 min read
Operational Simplicity Is a Product Feature
Operational simplicity lets teams publish, recover, and change systems without constant escalation or hidden process drag.
OperationsDeliverySystems
May 18, 2026 • 4 min read
Why Internal Tools Fail After the Demo
Internal tools succeed when they reduce operator friction in real queue work, not just when they look polished in demos.
OperationsSystemsDelivery
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 10, 2026 • 5 min read
AI Workflows That Survive Contact With Reality
Durable AI systems win by structuring decisions, preserving evidence, and designing the workflow around the model for operators.
AIAutomationSystems
May 8, 2026 • 4 min read
Automation Needs a Human Exit Ramp
Good automation removes routine work but still gives people a clear, informed way to take over exceptions.
AutomationAIOperations
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