QUEST BRIEFING — learning full-stack development by building real systems, not tutorials.
This page is a save file, not a brochure — what I've built, what's integrated, and what broke along the way.
Started with "how hard can it be" and ended up with a growing list of things I only understood after they broke. Web developer, currently building real systems — payments, auth, the parts tutorials skip.
Communication
Problem-solving
Adaptability
Flexibility
Teamwork
Meeting deadlines
ReactVite — routing & client state
Node.jsExpress (ESM) —
MongoDBMongoose
TypeScriptReactTailwind —
separate dashboard app
Firebase Admin SDK — server-side token verification
Cloudflare R2 — S3-compatible object storage
AWS — HTTPS, public domain
Top-level process.env reads can execute before
dotenv finishes loading. Fix: read env vars inside
function bodies, not module scope.
useEffect captures state at creation time. A
polling loop that needs live values needs useRef,
not useState.
A third party confirming success and my app recording it are two separate failure domains — worth tracking as its own case, not lumped in with a normal failed request.
Multi-step mutations need validate-before-commit, with a defined rollback path if a later step fails.
A slow request can still complete on the server or third-party side after the UI has stopped waiting on it.
Some real-world states — specific failure responses, edge cases — only ever show up in production. Don't assume sandbox coverage is complete.
I write the code myself first, then bring it back for review — not looking for solutions handed to me. I want the why before the what.