For my Frontend JS Project, I chose to make a platform called AdSize, where designers and advertising professionals can access ad-dimensions for popular ad platforms in one, consolidated platform.
After completing my Sinatra project and moving on to Rails, I began to see why people fall in love with it. ‘Convention over configuration’, an adage often repeated in the Rails ecosystem, began to become more clear as I have learned more and more about the framework and its benefits.
In the Flatiron curriculum, I view this project as a major milestone in my journey to becoming a full-stack web developer. This is the first time I have had the pleasure of see a functioning website that I built! Not to say that all the lessons and the CLI project leading up to this were not fun and challenging; they were the building blocks that I most certainly need, but it can be difficult to see the ‘big picture’ when starting out. I’m proud to say that I’m finally catching my first glimpses of that ‘big picture’.
For the CLI Data Gem Project, I have chosen to go with the API route over scraping.
As budding web developers, just getting to the point where you can code even the most modest of websites can often seem like an insurmountable task. But as we grow and learn, and real, operational websites begin to seem more and more possible, I’ve found myself asking: what about user authentication? How does it work? Where are usernames and passwords stored? How could I keep them safe?