Consistent Data Flow from Persisted Models to the Frontend
Why I care about keeping names consistent from Entity Framework models to Razor Pages forms and Cotomy, and how that reduces mistakes in long-lived business systems.
Why I care about keeping names consistent from Entity Framework models to Razor Pages forms and Cotomy, and how that reduces mistakes in long-lived business systems.
Why I stopped placing shared TypeScript infrastructure at the solution root and moved it into Core so Razor Pages and Cotomy could form one coherent application foundation.
How I place page-level TypeScript next to Razor Pages files and build a small shared foundation so Cotomy can stay aligned with endpoint boundaries.
How I use solution and project boundaries in Razor Pages systems to keep business functions understandable, extensible, and manageable in solo development.
How code-first modeling in Entity Framework reduced the historical gap between database schema and application logic.
How global CSS collapsed under scale, and how scoped CSS in Razor Pages reshaped my architectural thinking.
Why I continue using C# for daily business system development, and why solution/project boundaries matter more than language syntax.