Here is another summer I find myself in the same position like last time. I'm trying to job search but to no avail with no results. Last summer, I was starting off with a blank slate trying to obtain a job in IT and I accomplished that. That was grueling process to go through in waiting to be called back. Now with my career change, I find myself in the same position again in going through this process. As much as I want to make it in this field, I feel that like it is getting farther than my reach. The longer I wait for an opportunity to be given to me, the more I feel discouraged. I feel like the effort I put in is not putting a dent in the distance between me and obtaining my dream career.
Only until I had this epiphany. After talking with my family, I remembered why am I doing this for. Besides my passion for web development, I also want to be the person to improve the way my family lives and take the load off of my parent's shoulders. I'm tired of seeing my father work long hours to provide for us. Instead of letting this fire within me dim, I will add more tinder to the flame and reignite my passion to its peak. Before I lost the scope in my focus but now I will be zeroing in and staying locked and engaged. Instead of waiting for someone to give me a chance, I am going to go out there and take it. I will be putting even more applications per day like I have today. I will scour the web and exhaust every option in my job search until someone answers my knock on the door to let my foot in. I will be participating in more projects. I will dedicate myself to mastering more languages such as ReactJS, Django, Node.js . I will be going to more networking events, and messaging and learning from my connections on LinkedIn.
Today, I write this as my statement of action and for others to hold me by my goal and my raised expectations.
Thanks for reading.
Look forward to this blog being updated with my latest progress in my projects as well as posting my experience with my previous projects that I created so far in Udacity Full Stack Web Developer Nanodegree.
Saturday, July 1, 2017
Saturday, January 7, 2017
Project 3 Multi User Blog
I know this long due as I've already completed this project as well as the fore-mentioned Tournament project but I figure I'd post my thoughts I wrote down of working on it at the time. Enjoy
------------------------------------------------------------------------------------------------------------------------
I'm at the half way point of the Udacity Full Stack Nanodegree. I am currently working on the tournament project. I expect to finish the nanodegree close to the end of this month.
I will go over my overall impressions of the nanodegree as well as my progression. So far I've faced a lot of difficulties within the previous project, the Multi-User blog. This project consumed most time thus far. This was probably due to my introduction to back-end programming. I had little to no experience to working with back-end programming with the exception of the small copious amount dealing with CouchDB (All back-end programming done with couch was done locally and I focused more on the front end aspect so this will be the first time dealing with live online persistent data). When taking on this project, I definitely felt the difficulty curve with learning and understanding the complexities of Google App Engine and its version of SQL language called GQL (Google Query Language). While learning, I relied heavily on forums of Udacity Full Stack and Google App Engine documentation (I suggest you do the same to understand GQL). This was a big step for me jumping into back-end development from front-end developement. With back-end programming, I was not able to see the action/code executing in front of eyes like front-end programming. What took up the majority of my time during this project was the troubleshooting. When working the back-end, the errors are not so obvious and can even sometimes point to a piece of code not even in the python file I created. Through some googling and reading the Google App engine documentation, I solved some errors which I believe really cemented my understanding of the way code works in Google App Engine.
After completing this project, I definitely feel accomplished. The learning curve was steep but I was able to climb it and understand the material. This project truly humbled me and really brought me back to how it was learning a programming language for the first time and the frustration that comes with it. But now, I can confidently say that I understand GQL language and back-end programming.
Here are some snapshots of the Multi-User Blog app in action:
You can actually view the live version of this site at the following link below:
http://multi-userblog.appspot.com/blog
------------------------------------------------------------------------------------------------------------------------
I'm at the half way point of the Udacity Full Stack Nanodegree. I am currently working on the tournament project. I expect to finish the nanodegree close to the end of this month.
I will go over my overall impressions of the nanodegree as well as my progression. So far I've faced a lot of difficulties within the previous project, the Multi-User blog. This project consumed most time thus far. This was probably due to my introduction to back-end programming. I had little to no experience to working with back-end programming with the exception of the small copious amount dealing with CouchDB (All back-end programming done with couch was done locally and I focused more on the front end aspect so this will be the first time dealing with live online persistent data). When taking on this project, I definitely felt the difficulty curve with learning and understanding the complexities of Google App Engine and its version of SQL language called GQL (Google Query Language). While learning, I relied heavily on forums of Udacity Full Stack and Google App Engine documentation (I suggest you do the same to understand GQL). This was a big step for me jumping into back-end development from front-end developement. With back-end programming, I was not able to see the action/code executing in front of eyes like front-end programming. What took up the majority of my time during this project was the troubleshooting. When working the back-end, the errors are not so obvious and can even sometimes point to a piece of code not even in the python file I created. Through some googling and reading the Google App engine documentation, I solved some errors which I believe really cemented my understanding of the way code works in Google App Engine.
After completing this project, I definitely feel accomplished. The learning curve was steep but I was able to climb it and understand the material. This project truly humbled me and really brought me back to how it was learning a programming language for the first time and the frustration that comes with it. But now, I can confidently say that I understand GQL language and back-end programming.
Here are some snapshots of the Multi-User Blog app in action:
You can actually view the live version of this site at the following link below:
http://multi-userblog.appspot.com/blog
Subscribe to:
Comments (Atom)