Okay, so my “pitfall” of starting new projects while already working on projects I mentioned in my last post didn’t turn out as bad as I though. I can’t say I’m a Scrum Master; but I use it enough at work with my team that I feel comfortable enough at giving it a go on my own. Also figured out it wasn’t all to hard to find one sufficient for my own personal projects, Azure DevOps Services. Considering I already have an account and it is free, figured why not.
I now have an official project setup for my Dev Journal site with my own Scrum board and a Story to cover my sites initial setup. First task, cleanup the CSS! Got the stylesheet copied off of the server, created notes on the custom CSS I was using, and pulled some styles from the original WordPress.com version of this site.
I’ve already started looking through; but realized it wouldn’t hurt to setup some version control for the stylesheet considering it is over 3300 lines of code. Knowing me, way too easy to completely screw this one up. Now to get even more familiar with GIT and start branching!
So my last update mentions I need to work on my CSS. Problem is, I still need to pull my style sheets off the server to start scrubbing through them. This has to be my biggest personal pitfall. Fortunately, I don’t have this problem at work. However, by the time I’m done with work, I can’t say I’m always that eager to jump straight into another project. Typically, I hop on my computer with the intention of being productive, then I open Steam.
The unfortunate part about this is that I really want to work on this. Thinking I need to start setting up blocks of time to just start chipping away at this. Setup my own Agile workflow. Oh crap, another pitfall as I’m typing. Thinking of a new project while still needing to work on my current one. Focus, need to focus.
Okay, so using something like WordPress to build out my blog was easy. Moving over to my own AWS instance and setting up my own WordPress server is a whole different story. Especially when the WordPress Theme doesn’t migrate as expected.
I’ve been doing what I can in the WordPress admin page to add custom CSS styles to tweek the look; but realizing this doesn’t cut it so well when I’m trying to override the existing CSS styles that are part of the theme. Then I remembered this is my own server. I don’t have to use the custom CSS feature in WordPress itself, I can edit the actual CSS files on the server itself.
Still new to HTML/CSS, so why not just dive into the deep end with tweeking a website far more complex then anything I’ve actually created. Just need to figure out my plan of attack, create backups of the files (not my first rodeo), and start to dig through some CSS.
So I created this blog with the idea of documenting things that I’m working on from a developer standpoint. Now I just need to start documenting things. Between this blog being on my own server in AWS, what I’m doing at work, and what I would like to start doing in my free time, there are definitely things I can start with. I just need to get past my mental block of “maybe I should start with this, or maybe I should start with that”.
Doesn’t do me any good to have ideas if I don’t start working on them.