Since most of the endpoints will need some kind of error handling, our goal should be to reduce boilerplate when adding new features. Even more importantly, this will reduce the risk that someone forgets to handle validation errors. The pattern that I want to have is handling errors behind the scenes:
The concept is simple, scrape a website for the top teams of all time and let the user pick a team to read more about.
Today I want to go over how to create a feature in the search box that allows you to show you matches of the letters you are typing.
I was recently on a call with a developer, flatiron alumni, that talked to me about the clearly definied paths one can take as a developer. He told me that even though he chose the front end route, we are trained as full stack developer at flatiron. He also said that when he first started he had talked to senior front end developer that was not aware of the MVC design pattern and that he felt he had something to contribute to the team because of it. That has prompted me to do a small review on writting to make sure I am keeping up with patterns I learned even though I am not actively using them at the moment.
This week I wanna talk about flexbox. I worked on a small item this week that was heavy on css and learned a lot there. Flexbox is a css layout model, and it will allow elements to rearrange depending on screen size.