Notes from building software: what this journal is for
Why I'm starting a technical journal, what I'll write about — .NET, Angular, React, SQL Server, APIs, AI-assisted development and building products — and how I'll keep it useful.
Most of what I learn about software happens in the middle of building something: a query that behaves differently under real data, an API contract that needs to change, a product decision that looks simple until a real user touches it. This journal is where I'll write those lessons down.
What I'll write about
- .NET and ASP.NET Core — building and maintaining APIs and services.
- Angular and React — interfaces for data-heavy applications.
- SQL Server and backend engineering — data access with Entity Framework Core and Dapper.
- API design, debugging and performance.
- Modernizing existing software without stopping the business that depends on it.
- AI-assisted development and the developer tools I actually use.
- Building independent products and what entrepreneurship teaches an engineer.
How I'll keep it useful
Every note should be first-hand. If I haven't built it, debugged it or decided it myself, it doesn't belong here. I'd rather publish less often and keep each piece practical: the context, the decision, the trade-off and what I'd do differently.
Strong engineering is about more than writing code. It is about understanding problems, making thoughtful decisions and continuously improving the way things work.
If something here is useful to you — or you disagree with it — I'd like to hear about it.