Hi, I'm Binita Sapkota, a junior .NET developer.
Mostly C#, ASP.NET Core, and SQL. I like to understand a problem properly before I write any code, and I'm learning React so I can take a feature all the way from the database to the screen.
$ ls ./projects
Frontend Developer, 2025
A calm horoscope app that finds your sign from your birthday, shows what the sky is doing right now, and tells you how well two signs get along.
$ git log --career
Backend services first, with full-stack work along the way
// what I'm learning now
Getting better at system design, and at building services that stay calm under real load.
On the side, I'm getting comfortable with React so I can own a feature from end to end.
$ cat ./blog/*.md | head -3
Mar 12, 2026
AI now drafts code, reviews it, and explains it. Here's what that changes about the work, and what it doesn't.
Read the postFeb 24, 2026
It's not the .NET some people remember. Here's why I think it's still one of the most practical choices for backend work.
Read the postJan 18, 2026
Practical habits that keep an API fast and easy to maintain, long before you need anything exotic.
Read the post$ whoami
I'm a .NET developer with a year of professional experience, mostly on backend systems and APIs, with some full-stack work along the way. I like taking a loosely defined problem and turning it into software people can depend on, and I enjoy the small details that make something feel solid.
When something is new to me, I read the docs, try it on a small scale, and ask questions early instead of guessing. I try to leave code a little clearer than I found it, and I'm still learning something every week.
{
"backend": [
"C#",
".NET Core",
"ASP.NET Web API",
"Entity Framework",
"REST APIs",
"JWT"
],
"data": ["SQL Server", "PostgreSQL"],
"frontend": ["React (learning)"],
"tools": ["Git"]
}How I use AI
AI helps me move faster on the parts that don't need deep focus, like boilerplate or exploring an unfamiliar API. The thinking, the decisions, and the responsibility for what ships stay with me.
AI takes on the repetitive work, like boilerplate and first drafts of tests, so I can spend my time on design, edge cases, and the parts that actually matter.
Every suggestion gets read, tested, and questioned before I use it. It's a quick helper, not something I trust blindly.
Secrets, customer data, and company code never go into public AI tools. I follow company policy, remove sensitive details, and stick to approved assistants.
I keep prompts narrow, strip out personal data, and keep experiments clearly separate from production code.
$ ./contact.sh
Or maybe you just want to talk about .NET and APIs. Either way, I'd be glad to hear from you.