Against all given advice (due to the complexity that arises through our project scope), I decided to use some form of authentication in my app. I worked through this issue with a friend in the cohort and here is what we learned: “It can be a little tricky”.
If you’re reading this, I’m either nearing the end of my Flatiron experience or I’ve managed to find a job and move on with my career. Either way, I primarily wanted to just reflect on some thoughts and my interactions I’ve had along the way. This has not been easy, but engaging in conversations with others in the same spot makes a world of difference.
Javascript, very similar to most other programming languages, has a way to define, create, and operate on an instance through what we refer to as a Class. This really helps to focus the scope of the functions we use to modify data, images, or just about any content within a single page of an application. I would also consider the ability to organize our data like this adds the benefit of mimicking the style of Ruby for example. We’ll go over just a few ways by using some examples from my own project.
Project building has always been my favorite part about the Flatiron curriculum. It’s exciting to take an idea and shape it into whatever you’d like it to be using newly acquired knowledge. Building in Rails, however, has been the hardest task to date. It’s a powerful environment but even a new and empty project comes with so many files and folders compared to previous projects, so it’s easy to get a little lost in the madness. Nevertheless, I set off to build a simple IT Ticketing system to meet my requirements. I won’t explain the entire project, but I do want to break down 3 of my models that helped me realize just how easy it is to break your environment.
I like to be prepared. It’s nice to know what to expect so you aren’t ever caught off guard, so with the Sinatra Project, I was eager to take a look at the requirements and get started a little early on the planning portion. I really didn’t need a ton of time to come up with an idea once I began reading through all of the instructions since a previous job of mine gave me a pretty good idea of what I could work with. We used to have this website which our company hosted internally. Employees could log in, share messages, and view basic information about other employees or the company itself. It wasn’t incredibly impressive, but it seemed to be a good place to start and that’s what I decided to build.