What I was learning
I was learning how Flask routes receive requests and connect them to the logic that prepares a response.
Why it matters
Routes made controller logic feel practical instead of abstract. They showed where request handling, app decisions, and response rendering meet.
Where I applied it
The idea carries into app routes, API routes, and backend handlers across the projects I am building.
What clicked
A route should coordinate the flow, not become a place where every piece of business logic gets dumped.
What I still need to improve
I still need to keep separating route handling, validation, data access, and view/response code cleanly.