leon

[leon @leonxxxxxxxxxtp]

Section 42 showed me that error handling means controlling error flow, reducing repetition, distinguishing error types, and returning useful responses without exposing sensitive details in production.

#webdevelopmentjourney #techjourney #learninginpublic #TellerOne

[leon @leonxxxxxxxxxtp]

Section 42 of my YelpCamp journey focused on “Handling Errors in Express Apps.” I learned how Express moves errors through its middleware pipeline, from the point where an error occurs to the handler that turns it into an HTTP response.

[leon @leonxxxxxxxxxtp]

I also compared the course’s Express 4 approach with Express 5. Express 5 automatically forwards rejected promises from route handlers, so `wrapAsync` is mainly necessary here because the supplied project targets Express 4.17.1.

[leon @leonxxxxxxxxxtp]

I’m continuing to build and understand each part rather than simply copying the final code. If you have questions, corrections, or insights, feel free to share them.

#webdevelopmentjourney #techjourney #learninginpublic #TellerOne

[leon @leonxxxxxxxxxtp]

Section 41 of my web journey focused on YelpCamp:“Adding Basic Styles” with EJS-Mate and Bootstrap. The biggest lesson was moving from repeated standalone EJS pages to a reusable layout, shared partials, and responsive styling.

[leon @leonxxxxxxxxxtp]

Section 41 showed me that styling is more than appearance. It connects reusable architecture, responsive design, accessibility, correct HTML, and the relationship between Express, EJS, Bootstrap, and the database.