After going through what seemed like thousands of free themes, I ended up choosing a WordPress theme that was already featured(go figure). Choosing my theme and getting a visual idea of what my site will look like really made me feel like we just matured from newborn to toddler. I was extremely excited, and then I started going into the files of my theme. In these files were loads of code, some that I understood immediately and others that I have a strong feeling will take me a while to figure out. I am still just as excited to get the ball rolling on this project, but we went from like 30 lines max in Codecademy to, in my case, 573 lines of CSS and that’s just one folder. Looking at all of the files was a little overwhelming and I must say, thank you Greg for NOT making us do this from scratch. I remember asking in the beginning of the semester why in the world other coders would share their codes for free. I look back now and wholeheartedly understand the reasoning. They do it for people like me and I’m extremely grateful these people exist!

What I found most interesting is that I thought I’d have more difficulty understanding the codes but I actually had more problems understanding the comments explaining the codes. Everything has an official/proper name that I’m sure all veteran coders know. For example, in Codecademy when we’d practice, I often found myself commenting like “change box thingy” or “moves grid thing to the left”. That kind of language won’t get me very far in the real world of code and also won’t aid in my understanding of what others are trying to pass along to me.

I meant to ask this in class but when we are in GitHub and preparing to update and sync things, I remember we have to write a note saying what that change does. I’m finding that I may know what something does, but I may not know exactly how to say it. I’m sure the solution to this is just practice, but I probably need to figure that out sooner than later.