Insights
Engineering writing, not marketing copy
Notes from the work: how we evaluate AI features, choose tenancy models, migrate legacy systems and keep performance from regressing.
These articles are in editorial review
Everything here is written in-house and currently marked as draft while it goes through technical and editorial review. The reasoning is ours and we stand behind it; the draft label simply means it has not yet been through final review.
Featured article
Build the evaluation set before you write the prompt
Most AI features stall because nobody can tell whether a change made things better. A small, honest test set fixes that faster than any prompt technique.
Xalicon Engineering7 min read
Read the articleGet new articles by email
Roughly monthly. Engineering writing only, unsubscribe in one click.
All articles
Browse by category
Showing 5 of 5 articles
- ArchitectureDraft
Three multi-tenancy models, and how to choose between them
Shared schema, schema per tenant, or database per tenant. The right answer depends on isolation requirements and operational cost — and it is expensive to change later.
9 min read
- ModernizationDraft
The strangler pattern in practice: migrating without a cutover
How to move a business-critical system to new foundations one capability at a time, keeping rollback available at every step.
8 min read
- FrontendDraft
Performance budgets that actually hold
Core Web Vitals improve when regressions fail the build. Here is how to set budgets teams do not route around.
6 min read
- AI EngineeringDraft
Guardrails for AI agents that take real actions
An agent that can only read is a search feature. One that can write needs permission boundaries, approval gates and an audit trail.
8 min read
- Engineering ManagementDraft
Dedicated developers, team extension or a delivery pod?
The right engagement model depends less on budget than on how much engineering management capacity you actually have.
5 min read
Start a conversation
Want to talk about any of this?
These articles describe how we work. If something here matches a problem you have, we are happy to go deeper.
Prefer email? contact@xalicon.co