I recently picked up Cracking the Coding Interview 6thEd. to help me prepare for technical interviews. Although the book is based in Java, I will be working my way through the problems using Ruby and blogging some of my solutions along the way.
Flatiron School has been a great match for me and I have taken a lot out of the experience. The full-time program was a good combination of structure and flexibility. It gave me daily and weekly goals while still allowing me to balance life and sharing a work-from-home office in the midst of quarantine. The pace of a bootcamp can be very intimidating for some. There were times when I would start to feel like the information was coming on very quickly and as soon as I began to fully grasp something it was on to something new, but every time I looked back on my progress I would find the building blocks have piled on top of each other and I had a really well-rounded understanding of what I was doing. The projects and bigger labs were always really gratifying. It was a chance to put everything together, reflect on what you’ve learned and be creative. One of my only wishes was there was a few more of these touchstones along the way. I would enjoy weekly mini-projects that gave you a chance to test your understanding that was between the labs and portfolio projects in scope.
This React/Redux project has taught me a lot about the benefits and challenges of working with React components, especially when managing fetch requests. Let me walk you through some troubleshooting I had to do when working on this project.
My Single-Page-Javascript-Application project is a team-builder tool for a mobile game called Marvel Strike Force. I approached this project with the full intent of writing Object Oriented Javascript code but that quickly fell by the way-side for me. I began to hammer features out and tackle problems one by one and this was a bit more “fly by the seat of my pants” programming that, for me, lent itself to functional programming. I kept on soldiering through until Friday at 10am I was finished and happy with the finished app.
I just completed my Rails app, which is a Spa booking app, and wanted to give some insights into the way I chose to manage my routes. First I should talk a little bit about the models involved. The main model is Spa which has has_many associations with Technicians and Treatments (that work and are offered there). I also have a User model. When booking an Appointment a User can select a Treatment and Technician, so the Appointment model has a belongs_to relationship and foreign keys for those classes. So let’s talk specifically for the seven RESTful routes for Appointments.