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.
I do not follow development methodologies rigidly. Some environments break them entirely. What actually moves projects forward is adapting to the real constraints in front of you, not applying theory.
Solo development does not fail because of design alone. It fails when the shared understanding of what to build drifts. Use cases are the simplest and most effective tool to prevent that.
Why inheritance is rarely used when designing entities in business systems.
How debugging is handled in Cotomy, from browser debugging to localStorage-based runtime log categories.
AI coding agents are useful, but they work from narrow context rather than stable architectural intent. That makes software design and compact feature boundaries more important, not less.
A practical reflection on how I use ChatGPT, Codex, and Copilot to design first, code second, and reduce the risk of AI-driven development.