Welcome
This is my personal documentation space, where I capture my learnings, hands-on experience, and practical insights across the stack I actually work in.
The content here is a mix of notes, guides, patterns and real-world lessons picked up while building projects and preparing for interviews. It's built to be clear, fast and markdown-first, so it's easy to evolve as I keep learning.
Why This Exists
This documentation is intended to:
- Serve as my personal learning archive
- Capture practical implementation details, not just theory
- Hold interview answers written the way they should sound out loud — the short version first, the detail if the follow-up comes
- Document the tools, patterns and trade-offs I have actually used
- Act as a quick reference for future projects and real-world problem solving
What's Inside
Frontend
| Topic | What's inside |
|---|---|
 JavaScript | Closures, the event loop, prototypes, async patterns, ES6+ and coding questions |
 TypeScript | Types, narrowing, generics, utility types, and TS with React and Node |
 React | Hooks, reconciliation, state management and performance — through React 19 |
 Next.js | App Router, Server Components and the Next.js 16 caching model |
Backend
| Topic | What's inside |
|---|---|
 Node.js & Express | The event loop, REST APIs, middleware, authentication, databases, error handling |
 .NET | Planned — not written yet |
Cloud & DevOps
| Topic | What's inside |
|---|---|
 CI/CD Fundamentals | Pipelines, GitHub Actions, secrets, deployment strategies, rollback |
 Vercel | Serverless, cold starts, DNS, custom domains, environment variables |
| Render | Always-on containers, health checks, workers, zero-downtime deploys |
 AWS & Azure | Planned — not written yet |
How It's Organized
Each topic follows the same shape:
- Overview — a roadmap, and what interviewers actually test
- Concept pages — the fundamentals, with runnable examples
- Interview Questions — grouped Basic → Intermediate → Advanced
If you are preparing for an interview, start at a topic's overview and finish on its questions page. If you are looking something up mid-task, use search (Ctrl K).
Where a framework changed between versions — React 18 vs 19, Next.js 15 vs 16, Express 4 vs 5 — both are documented, because interviewers still ask about the older one.
Keep This in Mind
These are personal notes, not official documentation. They are written against specific versions and the ecosystem moves quickly — the Next.js pages in particular are pinned to version 16 behaviour.
Always check the official docs before relying on something in production:
Who's Writing This
I'm Dipak Mourya, a Full-Stack & AI Engineer based in India.
I build web applications and AI-powered products — LLM integrations, conversational assistants, AI agents and workflow automation — alongside the usual full-stack work of shipping and scaling real applications.
Stack I work in: React, Next.js, TypeScript, Node.js, Tailwind CSS, PostgreSQL, MongoDB, Socket.IO, Redux, Docker, AWS.
Background: Computer Science Engineering, plus an MBA in Business Analytics from Symbiosis International University — which is why a fair amount of these notes care about trade-offs and cost, not just syntax.
Find me
- dipakdev.in — portfolio
- GitHub
- LeetCode
Ready to dive in? Start with JavaScript — everything else builds on it.