ASP.NET Core Best Practices I Actually Reach For
Pragmatic patterns from three years of shipping production .NET — DI boundaries, options, configuration hygiene, and where defaults betray you.
> whoamiSoftware Engineer II · .NET
.NET Developer building clean, scalable, and reliable software.
{
"name": "Manoj Bastola",
"role": "Software Engineer II",
"stack": [".NET", "React", "SQL Server"],
"focus": "scalable enterprise systems",
"location": "Kathmandu, NP",
"available": true
}.NET Developer with 3.5+ years of experience building enterprise systems, ERP modules, and modern web applications. Focused on clean architecture, performance, and maintainable code.

$ whoami
Manoj Bastola
I'm a Full Stack .NET Developer specializing in scalable enterprise applications, customer-screening systems, ERP platforms, and modern web solutions. Most of my production work lives in ASP.NET Core, SQL Server, and the React / Next.js ecosystem.
I like to start with the data, understand the problem, and then design clear boundaries. I focus on simple architecture, reliable systems, good performance, and documentation that helps the next developer get started quickly.
Focus areas
Each step has pushed me deeper into systems work — from ERP modules to AML platforms to enterprise-scale .NET.
Building enterprise-grade .NET applications and scalable backend systems on modern Microsoft stack.
Delivered AML and customer-screening modules for a regulated financial product.
Worked on Plus ERP — a multi-tenant school operating system.
Where I’m strongest, what I’m comfortable in, and the tools I keep close. Levels are honest signals, not vanity scores.
Where I spend most of my day. Clean services, sensible boundaries.
Pragmatic, accessible, not allergic to design.
Indexes earn their keep. Queries explain themselves.
Ship it reliably or it doesn’t count.
Cross-platform when the brief demands it.
Tools I reach for outside the day job.
From enterprise system modernization to performance work and full-stack delivery — picked based on the problem, not the trend.
End-to-end product delivery on .NET + React with a strong eye on architecture and DX.
Versioned, documented, well-tested APIs designed for the clients that consume them.
Cross-platform mobile features with React Native that talk to your existing services.
ERP, AML, and screening systems built to survive scale, audits, and team rotation.
Index audits, query tuning, and schema work that turns minutes into milliseconds.
Profiling end-to-end — from SQL to render — and fixing what actually matters.
Containerized .NET workloads with predictable build, ship, and rollback flow.
Pulling legacy ASP.NET stacks forward without burning the business down.
Short reads from production work — patterns that survived, mistakes I’d unmake, and the boring stuff that decides outcomes.
Pragmatic patterns from three years of shipping production .NET — DI boundaries, options, configuration hygiene, and where defaults betray you.
How I approach query plans, the indexes I add first, and a few patterns that consistently turn minutes into milliseconds.
Pagination, idempotency, versioning, and observability — the boring stuff that decides whether you sleep through release night.
> ready_to_collaborate.exe
Grab the resume, or just send a note. I respond within a day or two — usually with questions before commitments.
Open to engagements, collaborations, and the kind of conversations that turn into projects. Drop a note below.