fresh off the keyboard
Notes from the workbench.
Things I've learned, broken, and fixed.
Writing about building for the web, leading a team, and the lessons that only show up after something breaks in production.
5
posts
5,374
words
Oct 2026
latest
§ 01Latestpinned.md
Pinned to the wall
§ 02Indexall-posts.md
Every note, in order
- 005How to Structure a Large Next.js App (App Router, 2026)The feature-based folder structure I use for large Next.js App Router projects, with the rules that keep it clean as the team and codebase grow.6 min27 Oct 26
- 004The Code Review Checklist I Use With My TeamThe checklist my team uses for every pull request: author prep, correctness, React specifics, security, accessibility, and how we write review comments.5 min27 Oct 26
- 003How I Estimate Web Projects as a Team LeadThe estimation process I use for client web projects, with a worked example: task breakdown, three-point estimates, overhead, risk buffers and quoting a range.5 min27 Oct 26
- 002From Senior Developer to Team Lead: What Actually ChangesWhat really changed when I moved from senior developer to team lead: how success is measured, delegation, reviews, communication, and protecting focus time.5 min27 Oct 26
- 001From Beginner to Full-Stack DeveloperA detailed look at my growth from learning the basics of web development to becoming a full-stack developer, sharing key milestones, challenges, and lessons learned along the way.3 min14 Dec 25
§ 03Topicstopics.md
What I write about
Building for the web
Practical notes on React and Next.js: how to structure a large App Router project, where server actions belong, and what to look for when reviewing code.
Leading a development team
What changes when you go from senior developer to team lead, how to delegate without becoming a bottleneck, and how to estimate web projects honestly.
Growing as a developer
The longer view: learning web development from the basics, moving from front end to full stack, and the lessons that came with each step of the career.
§ 04Questionsfaq.md
Questions these posts answer
What is the best folder structure for a large Next.js App Router project?
Keep the app directory thin and use it only for routing, then group everything else by feature: each feature folder holds its components, server actions, queries, validation schemas and types. Shared UI goes in components/ui and infrastructure such as the database client and auth goes in lib.
Read the full postWhat should a code review checklist include?
Cover five areas: whether the change does what the ticket asks, whether it is readable and consistent with the codebase, framework-specific pitfalls such as React effects and keys, security and access control, and accessibility. Leave formatting and linting to automated tools so humans focus on logic.
Read the full postHow do you estimate a web development project?
Break the project into tasks no bigger than two or three days, estimate each with an optimistic, likely and pessimistic number, combine them with the PERT formula, then add overhead for reviews, testing, meetings and deployment, plus a risk buffer. Quote the result as a range, not a single date.
Read the full postWhat is the difference between a senior developer and a team lead?
A senior developer is measured mostly by the quality of their own work. A team lead is measured by what the whole team delivers. The lead still writes and reviews code, but also plans work, makes and explains technical decisions, unblocks people, and communicates with clients and management.
Read the full post
To
Hardik Gohil
Surat, Gujarat, India
Write the message here, it lands in my inbox.