New Feature: Weekly Progress Report (for November 13-19)

I’ve been narrowing my focus over the past few months and will continue to do so. The biggest change I’ve made is that I’ve decided to stop working on the #100DaysOfCode challenge just past the halfway point, at day 54.

I started making changes to have the rules fit me and how I was going to do it, and it was really getting pretty far from the initial challenge. And it's not like I need inspiration to keep going – if I have time to work on things, I do.

I was learning a lot, but felt obligated to code each day to get the challenge done. This was coming at the expense of learning why I was doing the things I was or how it actually worked.  That's not what I want.  Although I still have a certain amount of time scheduled each day for projects/development, I’m no longer worried about coding. Some days I’ve been able to code the entire time and others I’ve not written a single line while I learn how something new works. I'll be writing a separate post about why I think #100DaysOfCode is a great idea, but it’s just not for me.

I had written a weekly post in the past as an experiment, but I’m going to try that again with a little different format. Every week I’m going to write about the following items:

  • Projects: I have a number of projects I want to work on, including changing the “Howdy” text to a Hawaiian greeting, something to track my workouts (mostly running) for our Navy Reserve fitness test, a custom review post type for this site, a plugin to track my coffee consumption, and a restructuring of this site to launch January 1st (if not before). Every week I’ll share my progress and link to the code on GitHub, or other applicable location.
  • Learning: I’m a lifelong learner and I won’t ever have enough time to learn everything I would like. With that being said, I generally do some each week, if not every day. I have a premium subscription to Lynda.com and am always working on something there. I’ve also done some work on freeCodeCamp’s Front End Development Certification.
  • Gotchas: Sometimes you hit a wall when you’re working on something. Any time I run into issues I’ll share what happened and how I got around it.
  • Podcast Pick(s) of the Week: I listen to a lot of podcasts on a wide range of topics including WordPress, general development, organization, and productivity. I kept track of how many I listened to a couple weeks ago and it was almost 80. Although I feel many of them are beneficial, I’ll only be sharing my top picks each week.
  • Article Pick(s) of the Week: As with podcasts, I read a lot of articles – mostly about WordPress. I’m going to find the ones I think are interesting.
  • Goals for the next week: This is pretty straightforward; this is what I want to accomplish the following week.

Learning

I've done a lot of learning the past few months.  It's tough because I want to learn so many things.  The biggest thing I've learned recently is to slow down.  I was coding just to code as I worked through #100DaysOfCode even if I wasn't fully understanding what I was doing.  From here on out I'm setting out a learning path that is just as important as the number of lines of code I write.  For now, I'm going to include what Lynda.com courses I'm taking, but I may remove that in the future and just have some key takeaways for the week.

WordPress/PHP

[Learning: Lynda.com] Finished WordPress: Custom Post Types and Taxonomies

[Learning: Lynda.com] Working On:  JavaScript for Web Designers

General/Tools

  • Atom Shortcut
    CTRL+/ comments a block of code
  • I came across Automattic's Git Workflow and I really like their branch naming scheme.  This is the scheme I will be using going forward.
    add/{something} — When you are adding a completely new feature update/{something} — When you are iterating on an existing feature fix/{something} — When you are fixing something broken in a feature try/{something} — When you are trying out an idea and want feedback

Projects

[Plugin] Hawaiian Howdy

Purpose:  Hawaiian Howdy is a simple plugin that changes the "Howdy" text in the admin area to a Hawaiian greeting based on time of day.  It can also wish you a Happy Aloha Friday.  Both of these are options that can be turned on or off independently.
Progress:  I have to finish up the plugin internationalization, change the default information in the readme file, and make sure the rest of the WordPress coding standards are followed.  After that, Hawaiian Howdy should be done.  I already use it on my site and I love the extra touch of Hawai'i it adds.
GitHub Repo:  https://github.com/geoffreyshilling/hawaiian-howdy

[Website] GeoffreyShilling.com

Purpose:  This is an obvious one – it's my website!  I'm going to share weekly updates, reviews, plugins/themes I write, code snippets, and information that I think would help others on the same path as me.  I won't be doing a complete redesign right now, but I am changing how things are laid out.  The changes are planned to go live on January 1st, 2018. 
Progress:  I have a good portion of the work done.  The reviews are going to have their own custom post type and I am working on building that.  The biggest thing I have left is to write the actual content for some of the pages.  I also have to decide if I want to add in things beyond code, such as recipes and fitness tracking.  It would make it a lot easier for me to maintain one site, but that also dilutes the focus of the site.  We'll see.


Podcast Pick(s) of the Week

I’m going to start sharing my top pick(s) next week.


Goals for This Week

  • [Plugin] Hawaiian Howdy:   I should have no problem finishing the Hawaiian Howdy rebuild this week.
  • [PHP] IZ Ipsum:  The code on IZ Ipsum needs cleaned up.  Although this is a non-WordPress project, I also want to rewrite the code so it conforms to the WordPress PHP standards.
  • [Plugin] PRT Tracker:  If I get done with the other projects, I would like to get back into my PRT Tracker.  This is what I'm going to use for tracking my workouts (running, curl-ups, and push-ups) to improve my score on the Navy Reserve fitness test we have every six months.
  • [Learning] Lynda.com:  This week I'll finish up JavaScript for Web Designers and then I'm going to work on the Become a PHP Developer learning path.  I've already taken a couple courses, but will probably take them again as a refresher.

That's all for now.  Aloha until next week!

Note:  This post was written using Gutenberg.

Leave a Reply

Your email address will not be published. Required fields are marked *