Leave room for the unknown.
A direction can be clear without pretending the whole route is known.
Start with a complete path.
A wide list of features can hide a missing connection. A small workflow that reaches from the interface to the database makes the connections visible.
For Care IQ, patients and appointments form that first path. For this portfolio, the first path is a visitor understanding the work, inspecting a decision, and finding a way to start a conversation.
Keep the expensive parts deliberate.
A separate API is useful when a clear boundary earns its cost. It also adds deployment and contract work. A database is useful when information needs to change and persist. A static page does not need one simply because the rest of the stack supports it.
This portfolio keeps the Next.js frontend and Express API foundation in one workspace. The reading experience is statically generated; it does not wait on an API to explain the work.
Write down the turn you took.
An architecture decision record does not need to be a thesis. State the context, name the decision, describe the cost, and say what would make it worth revisiting.
That leaves the next person with something more useful than a rule: a reason.
Keep enough room to notice.
Hiking, sailing, and photography each reward paying attention. That is the quality I want this field guide to carry: a clear direction, curiosity about the conditions, and enough space to look again.
The next step should be informed by what the current one reveals.