omg brb roflmao

Attention all three subscribers to this, my personal/professional blog:


Seriously though, I cannot even begin to express in words the wave of relief that washed over me as I pressed enter and pushed those final changes to Github.

I finally have something of value that showcases my skills. Not only that, but I’m pretty darn proud of how it turned out. Check it out!

check out the rest of my portfolio here:

For some reason, this project really stumped me. I started and stopped and restarted about fifty different times, and never really felt like I was getting anywhere with it. I’d work on it for a day or two, and come back a few weeks later hating all of the changes I had previously made. I redesigned the entire site no less than six times, and don’t even get me started on how much time it took to choose a font…

After three months of waffling it is finally live, and so I decided to take some time to really think about why this site was so daunting in the first place. Here’s what I came up with:

1. What the h*ll do you even put on a portfolio anyways?

For me, as a new developer, the most terrifying part of creating my portfolio was feeling like I didn’t have any “real” work-experience type projects to showcase.

I went through a code school where I learned all the things necessary to be a successful developer but only one project out of the entire course was really portfolio-worthy in my opinion (maybe I’m a little picky…?).

So, to combat that feeling of dread and embarrassment anytime someone asked to see my portfolio, I started looking for free-lance and open-source coding opportunities to spice up my bare-bones work history. I joined sites like Upwork, Voly, and Catchafire. I even hit my local developer’s Slack channel and attended some meetups.

Basically, I networked my butt off to find projects I could contribute to, and it worked! I found some projects that I started right away and even got paid to do a couple of them.

2. Blank canvas syndrome

I’m very much a right brain kind of person. But the thought of a blank canvas is terrifying to me. So, I did what I always do when I can’t seem to find that ‘Aha!’ spark of momentum: research.

I spent countless hours researching portfolio sites, making notes, comparing and contrasting different styles, testing out fonts, looking at color schemes etc. I probably spent more time looking at other people’s sites than I did actually building my own. It turns out the actual building of the site is not really all that difficult (a little HTML, some CSS, a sprinkle of javascript), it’s making and sticking to your decisions that’s hard.

After many, many (so many) scrapped designs, I Frankenstein-ed (not sure if that’s a real word…) a bunch of really awesome ideas together and finally started to feel the flow of my portfolio.

3. Ain’t nobody got time for that

Trying to work full time, do side projects, actively search for jobs, build yourself a portfolio, and remember to breathe is real hard. But, it’s not impossible.

I think being excited or passionate about something really allows you to over come great obstacles, and for me, that has really worked in my favor. I love coding and I have loved every minute of this journey so far, even the stressful parts.

Check out all my hard work here.