{"id":1350,"date":"2016-12-26T21:34:16","date_gmt":"2016-12-26T12:34:16","guid":{"rendered":"https:\/\/n8finch2024.local\/?p=1350"},"modified":"2019-06-30T07:01:17","modified_gmt":"2019-06-29T22:01:17","slug":"looking-backwards-2016-review","status":"publish","type":"post","link":"https:\/\/n8finch2024.local\/looking-backwards-2016-review\/","title":{"rendered":"Looking Backwards: 2016 in Review"},"content":{"rendered":"
It’s that time of the year, reviewing what has been done, assessing what was good, discarding what was not, and moving forward in a better\u00a0situation than I was before.<\/p>\n
After my theme and goal setting at the end of 2015<\/a>, I moved into the new year with hope and optimism. This year was very interesting to say the least. I’ve experienced the lowest lows and the highest highs.<\/p>\n However, I think 2016 will go down as the most significant year for me since marriage.<\/p>\n Read on to find out why…<\/p>\n <\/p>\n This year did not start off well.<\/p>\n A bright spot was that I had developed my first WordPress theme from scratch at the beginning of the year using the _s starter<\/a> theme. It went pretty well, was very intuitive, and I built it starting with Sass, and used masonry.js and backstretch.js as well, my first venture\u00a0into JavaScript for the new year. I was pretty pumped, learned a lot, and felt ready to throw my hat into the ring and apply for work with a company. But first…<\/p>\n After losing almost 30 pounds at the end of the year, my back went out the second or third week of January. Actually, it did not completely go out like it has in the past, so I wasn’t doubled over in pain while walking. I was frustrated, especially after losing all that weight, I felt great, was playing basketball twice a week, and by all accounts was very healthy.<\/p>\n But, I kept going. In an attempt to “go pro<\/em><\/strong>“, I had applied to several jobs, and was accepted to one on a trial basis. I was elated, and the company seemed great. They gave me the task of developing a theme from scratch for one of their clients, and gave me about a week to do it. Due to my inexperience and not understanding the scope completely, I did not pass the trial period. While I got some good feedback, I felt like an idiot.<\/p>\n After applying to another company and getting turned down due to my coding ability, I asked for some feedback and a code review. I wanted to grow as much as I could and show this company that I was able quick learn and adapt.\u00a0The suggestion was to work on my JavaScript skills if I wanted to be a better front-end developer. I asked for recommendations, and they recommended Udacity.<\/p>\n <\/a>Udacity:\u00a0<\/strong>I gave it about a week, and enrolled in the Front End Nano Degree program. It was actually really great! I learned a ton about JavaScript, building single page applications, and even using Jasmine to run tests. I got a lot of great feedback and was able to finish the program in about four months. The major\u00a0takeaway from this program was working with APIs and reading documentation. I finished the nanodegree in June, just in time for summer vacation! 😎<\/p>\n Udacity wasn’t my only stop for education this year.<\/p>\n <\/a>KnowTheCode:\u00a0<\/strong>I had reached out to Tonya the year before, and had joined up with the WPDC as an apprentice. However, when she launched KTC, my learning in WordPress, and especially\u00a0Genesis, skyrocketed. I finally understood <\/a>JSforWP:\u00a0<\/strong>Towards the end of the year, I decided to enroll in Zach’s course for using JavaScript with WordPress. So far, the course has been mostly review, which is nice. I know more will be added to the course in the future, and I’m especially looking forward to the framework and WP REST API discussion.<\/p>\n All of this learning really takes me to the end of October. While I’m still freelancing, I’m really not taking on too many clients, instead working a lot to develop my skills personally, and begin to see how I can read documentation and tutorial to impelment some plugins and themes.<\/p>\n During this time, I also began to experiment with Angular on Genesis<\/strong><\/a>, and wrote a three part series which got picked up by Genesis Weekly<\/strong><\/a>.<\/p>\n With all this fun and learning, it was time to dive back into\u00a0going pro<\/em><\/strong>…<\/p>\n <\/a><\/p>\n Over the course of the previous months, I had submitted my first theme<\/strong><\/a> to the WordPress.org theme repo, as well as a few plugins<\/strong><\/a>. By the end of October, I had the theme approved, and three plugins in the repo. Theme and Plugins in the repo. I also had the chance to translate some of a plugin into Spanish. It felt incredibly good to be able to give back to the community that has been so helpful in my formation and learning.<\/p>\n <\/a>\u00a0 \u00a0\u00a0<\/a><\/p>\n Around the middle of October, after no luck applying to companies, I decided to apply to two freelancing “guilds”, and see if I could get accepted. Low an behold, I passed all the tests and joined up with toptal<\/strong><\/a> in October, and Codeable<\/strong><\/a> at the beginning of\u00a0December. Both of these companies are great for finding top-tier developers, and I feel very fortunate and blessed to be a part of them. They are a great community of freelancers.<\/p>\n There will be plenty to keep me busy this year. Looking back, even though the year got off to a rough start, I can say that I finally\u00a0went pro<\/em><\/strong>.<\/p>\n I wrote more on this blog than I have any year previously. I averaged\u00a0two to 3 posts a month about different topics like web development, cooking and growing professionally.<\/p>\nInstant Failure<\/h2>\n
Get Educated and a Little Connected<\/h2>\n
filters<\/code> and
action<\/code>\u00a0hooks, Genesis markup, and started digging a lot more into the PHP manual to get answers and\u00a0move toward custom code, functions, and\u00a0plugins.<\/p>\n
Went Pro<\/h2>\n
Wrote More<\/h2>\n