Backend & Systems
APIs. Data. Workflows.
Built to stay clear as
complexity grows.
EngineerBuilderProblem solver
Hanoi, Vietnam · Open to Fresher / Junior Software Developer roles
NguyenQuang Ha
Software Developer
I turn learning into software
people can actually use.
Full-stackAPIsSQLDockerProduction
Ship Software
Build. Integrate.
Deploy with care.
Keep it operable.
Project Stories
Real projects.
Thoughtful design.
Meaningful impact.
Production deploymentFull-stack deliverySecurity handoverAI-assisted, human-owned
01 / Selected build stories
Projects are more useful when the decisions are visible.
Each story connects a technical build to its context, constraints, evidence, honest limitations, and the next thing I need to learn.
01 / .NET product rebuild
Taskie
How a university MVC project became a containerized ASP.NET Core application.
C#ASP.NET CoreEF CoreSQL ServerReactTypeScript
Read the story 02 / Production internal tooling
CreateStory
The first system I shipped had to keep working after I left.
ReactTypeScriptFastAPIPostgreSQLDockerGoogle Drive API
Read the story 03 / First C# game
Skeleton Survivors
My first C# project, built before I started working with AI.
C#UnityGame logicObject-oriented programming
Read the story 04 / Product discovery
BedReads SEO Reader
Building the bridge between a search result, a free preview, and the mobile app.
ReactTypeScriptVitePrerendering
Read the story 02 / The journey
The projects are chapters, not isolated cards.
01
First year
Learning C# through game development
I built Skeleton Survivors, a small Unity game, before AI became part of my workflow. It was my first complete loop of classes, behavior, collision, scoring, and persistence.
02
Third year
Building the first version of Taskie
An academic ASP.NET MVC project introduced me to server-rendered applications, Entity Framework, SQL Server, authentication, and relational product data.
03
2026
Shipping software in a real company workflow
At Nova, I helped build, deploy, maintain, and hand over internal content-automation software used on a company-controlled production host.
04
Now
Returning to .NET with better context
I am using Taskie to strengthen C#, OOP, SQL, EF Core, authentication, authorization, and my ability to explain every important decision.
03 / What production taught me
Shipping widened the problem.
My internship gave me something tutorials could not: responsibility for software whose state, credentials, users, and next maintainer existed outside my laptop.
Operations change the definition of done
A safe update depends on running jobs, backups, configuration, rollback, and the person operating the system—not only whether the build passes.
Data safety is product behavior
Persistent jobs, migrations, backups, credential boundaries, and non-destructive update commands are part of the application contract.
Handover is a final engineering feature
A system is healthier when another developer can run it, diagnose it, recover it, and continue without the original author present.
04 / About the developer
I want a steeper learning curve—and the foundations to handle it.
I am a final-year Information Technology student at Hanoi Open University, focused on becoming a dependable software developer who can explain what he builds, debug it when it breaks, and keep learning from stronger engineers.
Production experience clarified what I want next: more consistent engineering challenges, stronger review and mentorship, and the chance to deepen backend engineering, C#, ASP.NET Core, SQL, EF Core, and software design.
How I work with AI
AI is a major accelerator in my recent work. I do not treat generated code as automatic mastery. I review behavior, test important flows, clean up security and configuration, document decisions, and make each project material I must be able to defend.
05 / Currently sharpening
Backend foundations. SQL reasoning. Production context.
Object-oriented designLINQ + async workflowsRelational modeling + queriesEF Core behaviorAuthentication + authorizationReading and defending Taskie