Lessons from The Complete Software Developer's Career Guide - Part 1
When I started reading “The Complete Software Developer’s Career Guide” by John Sonmez, I was overwhelmed when I found that would be 796 pages. Now I have read novels longer than this such as “A Storm of Swords”, but it’s difficult to compare reading fiction and non-fiction. Sonmez’s writing style eliminates any fear of this being a tiresome read and the way it’s structured has a remarkeable impact. It’s not only an incredibly conversational and comedic perspective on the tech industry, but also one of the most resourceful books that I’ve encountered.
The Job Search
One of the most important things that I’ve learned from my job search is that there are always opportunities to expand your resume. Rejection can generate many different reactions, but it should never mean that it’s the end of the road. Having thoughts of “I don’t have as much experience as other candidates” or “this was not the right career path” will not help you move forward. If you spend too much time focusing on that, it will derail the train and prevent you from reaching your goals. I’ve encountered a handful of roadblocks as a programming student, some of which I never thought I would make it past, but I did. Going into an industry that is constantly evolving, you need to be open-minded, but also patient with yourself and the process.
Restful Routes and Nested Resources
Having spent the past few months building in React, I wanted to travel back to my Ruby on Rails applications to modify and add features that I had sketches for, but never implemented. I think that it’s important to continue building and innovating your earlier projects as you gain a greater understanding of each programming language and their functionality. It was interesting to explore Restful Routes and Nested Resources, something that I had overcomplicated myself with while originally creating Renecades Gameroom.
An Overview of State in React
State is a Javascript Object that stores dynamic data in a React class component. The state is initialized in the class constructor and is inserted into the component after super(props). One of the many reasons that programmers use state is so you can create components that are both dynamic and interactive. Properties or keys can be added to the component’s state with values. For example, in a signup component, a username and password could be the state keys as seen below.