Days 30-37 of #100Daysofcode

Days 30-35
Designed and created a landing page
Integrated calendly and airtable for user feedback

Days 36-37
Troubleshooting for DNS issues
Connected domain for routing emails

It’s definitely been a journey, thanks for the encouragement!!! 😊

Now if something goes wrong, I can see where it starts at a glance, follow the error path and debug from there. The goal is to reuse this for multiple tools, so I still need to clean up the auth to extend later. I’m happy with the progress so far!!!

#WebDevelopment #100Daysofcode #100hours #100Devs

Logic and data flow between services is a lot easier to follow since all controllers have a similar job. Parse/validate requests, call services, and send a response. Error handling is completely separated.

I also learned node has a native module for testing called “assert”. It can be reused to verify any condition and return an error message. TypeScript recognizes this as well so type guard checks are abstracted away. Every if-else condition was replaced with one line of code.

The express middleware catches any errors thrown within the app. And instead of try-catch blocks in every controller, a higher order utility function is used to wrap the controllers for each endpoint. It takes two arguments, an async controller and a string to identify the error location.

Let’s goo!! 🔥🔥🔥

Definitely trying this!! What are you making with the shredded chicken?

Happy that it’s early enough to refactor quickly. Next task, learn a better implementation. Definitely need to work on my debugging/error handling skills!!!

#WebDevelopment #100Devs #100hours

Day 19
- Fixed alignment issues for my portfolio page
- Adjusted feature requirements for my next project

Day 15-19 of #100Daysofcode

Day 15-16
- Added banner and hero sections to freelancing page
- Updated call to action links

Day 17-18
- Full redesign for freelancing page (themes, page sections, animations, & buttons)