Built login/signup for my notes app just to learn auth properly. Biggest takeaway: never roll your own session handling when NextAuth exists. I did it the hard way so you don't have to.
Cart state in my bookstore lives in React context, not a state library. For a single-user cart it was the right call — no Redux boilerplate for state that never leaves one tab. Use the simplest tool that survives your actual requirements.
One middleware.js file protects every checkout route in my bookstore. Took me embarrassingly long to realize auth doesn't belong in 12 different page components — it belongs in one gate. Centralize your auth checks.
My bookstore's MongoDB schemas went through 4 rewrites. Lesson: model for how you READ the data, not how it looks in your head. Embedding vs referencing in Mongoose is a design decision, not a syntax one.
Type in the ingredients you have, get recipes with instructions. Built this when I was tired of staring at a half-empty fridge. JS, no framework bloat.
https://t.co/5AMMp03Xc3
Built my own notes app with login/signup and personal todo lists because I didn't trust random note apps with my stuff. Simple stack, does exactly one job.
https://t.co/3EnOSxi82H
Hardest part of my bookstore app wasn't the cart — it was auth. NextAuth + MongoDB sessions, middleware protecting checkout routes. Took 3 rewrites to stop leaking session state. Happy to share what I learned if anyone's fighting NextAuth right now.
Built a full-stack bookstore with Next.js 13, MongoDB + Mongoose, NextAuth, and Tailwind. Cart, wishlist, search — 112 commits in. Code's public, roast it:
https://t.co/KdwEznBoBE
Frontend dev (React, Next.js, TypeScript) sharing what I build and what breaks. Currently: polishing a full-stack bookstore and job hunting for remote roles. Follow along if that's your thing.
You’ll receive 50000000000
50000000000 $PEPE (2.15 ETH) each to the first 4900 people who follows and retweets pinned 📌 post
Drop your wallet address 👇