I made a TON of progress on my project last week, and I was really excited about it. I also learned two important lessons:
- If you’re designing something that you want to look good on a smartphone screen, it’s probably a good idea to test that design on an actual phone, and not just by resizing the browser on your laptop.
- Reading the documentation and instructions for using a framework (or really, anything) before you start using it can prevent a lot of stress.
Want to know how I learned those lessons? Keep reading.
Continue reading “Lesson learned: Always read the instructions first”
The items in the title of this post are in reverse order, but it’s my blog and I can do what I want, so let’s get to the big stuff first, shall we?
Last Friday was my last day as associate editor at TechRepublic, which was bittersweet. I’d been there for almost three years, I had a great group of coworkers, and I learned so much and gained a lot of professional self-confidence during that time. But moving on so I could focus more on learning and getting experience in web development and UX was what I felt like I needed to do.
At the beginning of this year, I was in a mediation class (I’m going to get all new age-y on you for a second.) and two words came to me: listen and honor. I decided to adopt those as sort of a mantra for this year, as much as I can. So a few weeks ago, when I thought about leaving my job, something just felt right, and I decided to listen to and honor that inner voice.
So anyway, my plan is to spend the next few months working on my Code Louisville project, doing online classes, and looking for and learning from any other resources I can find. Then I’ll be looking for opportunities to get my new career off the ground.
In other news, I’ve had quite a bit of time to work on my Louisville Triple Crown of Running project version 2.0 over the past couple days, so I’ve gotten it to a pretty good place. Not perfect, by any means, but good. (It’s hosted here, if you want to check it out.)
This seems like a good time to go item-by-item through all the changes I’ve made. If you’re into that kind of thing, stick around.
Continue reading “Week 9: Project progress and a career leap of faith”
This post is going to be a short one. I wanted to stick to my goal of posting at least once a week, though.
It’s probably good that I learned how to do basic front end layout things the hard way first, but Bootstrap has made it a lot easier to accomplish the design I have in my head.
Continue reading “Week 7: Dear Bootstrap, you’re amazing…”
Continue reading “Week 6: jQuery and Flexbox layouts”
But mainly I wanted to share what I’ve been working on project-wise. In a previous post, I talked about making the Louisville Triple Crown of Running website more user-friendly, so I’ve come up with a basic layout that solves the issues I was having.
One of the first bits of advice I got from mentors in the program was to put my ideas on paper before writing any code. My idea went through several iterations, but here’s the one I ended up with:
Continue reading “Project update: Creating the basic layout for my Louisville Triple Crown of Running site”
Not gonna lie, this week was tough!
But instead of turning this post into one big rant, let’s focus on the things that did go right this week:
One of the big requirements for the Code Louisville program is designing and building the front end of a website or app from scratch. For this project, I wanted to solve an issue that’s bugged me for years.
I’ve run the Louisville Triple Crown of Running several times, so every year, I’ve visited the website looking for race dates. And every year, I have the same frustrating experience. Here’s a screenshot of what you first see:
Continue reading “Project: Making the Louisville Triple Crown of Running website more user-friendly”