About
The Geometry of the Grid: Engineering Discipline Since Deva Victrix
Devafusion is a personal technical laboratory for exploring software engineering, cloud architecture, modern web technologies and the practices that bring them together.
The Origin of Devafusion
The name traces back to Chester, United Kingdom - once Deva Victrix, the fortress city of the Roman Legion XX Valeria Victrix. Its engineers didn't build temporary camps; they built permanent infrastructure designed to outlast centuries of pressure. That same bias toward durable foundations shapes this practice's own engineering choices, without treating any one stack or decision as permanent - the tooling and technologies used here keep evolving.
The name is a deliberate, four-layer fusion:
- Deva - the foundation. A direct homage to Chester and the legion's engineering legacy: discipline, precision, structures built to last.
- Dev - the discipline. The daily reality of software craftsmanship, systems architecture, and engineering rigor.
- Fusion - the method. "Develop a Fusion" - synthesizing disparate technologies into one coherent, unified system.
- .net - the architectural nod. A salute to the type-safe, high-performance framework anchoring backend engineering discipline.
Colour is not decoration - it's archival. Roman Madder Red is a direct nod to the organic crimson dye extracted from Rubia tinctorum, the plant the legions actually used to colour cloth and standards. Paired with Legionary Gold and Gladius Steel, the palette is historically accurate, not merely "Roman-themed." The geometry mirrors the Cardo and Decumanus - the cross-axis grid at the center of every Roman fortress city - framed by the outline of Chester's own Roman Wall, and carries specific shield heraldry lifted from the XX Legion: white horizontal arrows (momentum, directed force), vertical gold lines (structural load, integrity), and the central boss (the point where distinct systems converge into one).
See the engineering log entry documenting how this mark was actually built.
Engineering Principles
Discipline here is enforced by tooling, not memory - and it sits alongside an agile, evolving practice: work ships in small vertical slices, and the toolchain keeps being re-examined against newer approaches rather than fixed in place.
- Test-Driven & Behaviour-Driven Development. Code is written to a failing test first. Behaviour is specified before implementation exists, not retrofitted after.
- CI/CD automation & DevOps culture. Every change ships through an automated pipeline - lint, typecheck, unit, E2E, visual regression - before a human ever reviews it. See it running in the engineering log, documenting real incidents as they happened.
- Clean Code & SOLID principles. Single-responsibility components, explicit boundaries between server and client rendering, no speculative abstraction.
- Scalable system architecture. Infrastructure as code (Terraform), separated deployment pipelines for application vs. infrastructure, explicit resource-address migration discipline - decisions documented, not assumed.
- Continuous learning. The engineering log is a public, timestamped record of real decisions and real incidents - not a curated highlight reel.
Open Source & Proof of Work
Claims are cheap. A public commit history is not. Devafusion's own build is public on GitHub. Every commit follows Conventional Commits, every PR is validated by CI before merge, and the engineering log narrates the reasoning - including the mistakes, such as a DNS recordset conflict, as candidly as the wins. See the Devafusion project entry for how this site itself is built and operated.
Questions or feedback? See the Contact page.