After the data update I did last month, the next step – obviously – was refactoring code, right? Right.
In seriousness, this was pretty old code for me and I’ve learned a lot in the last year, so it was a good project to refactor. I wrote it, but I also knew I could write it better today. Continue reading Cider Tasting refactor
Just a quick update to my Cider Tasting page – I’ve been a little behind but I just added 26 new ciders, bringing the list from 97 to 123.
I’ve got some improvements to the page that I’m also working on – cleaning up and refactoring code, maybe adding some new features without compromising the core function. Still, it’s nice to get the list up to date!
I first learned about Flexbox Froggy quite a while ago – it’s a wonderful resource for both learning what flex can do and as a resource for remembering a specific flex property. Sure, a site like CSS-Tricks has a great flexbox article which I refer to just about every time I work with flex, but sometimes you just need to put some frogs on lilypads. I saw it in my bookmarks earlier today and ran through some of the exercises again. #24 is still pretty intense for how it works – and works without class-specific order rules, which is incredibly impressive in my book. Continue reading Flexbox Froggy
The final week of Code 201 was essentially a small hackathon: Taking everything you’ve learned (and anything you’re willing to learn quickly), make a project concept, model the domain, and then, as a team, build it. I worked on a team building a Welcome to Seattle web app, answering the first question any potential resident would ask themselves. Where should I live?
In week 3 of Code 201, our project was BusMall – think Sky Mall for people trapped on a long bus commute. Something of a familiar issue to Seattle commuters! From the programming end, it was an exercise in tracking and storing data persistently, then using Chart.js to render results. Object constructors, event listeners, randomizing functions, and more… Continue reading BusMall: And you thought SkyMall was bad…
As a one-day lab in 201, we were given an image of a website and told to go make a design comp in teams of two; basically a day of pair programming. It made me think our instructor really has a pizza thing considering after pizza 3001 we went right into a chocolate pizza design comp. Our task was to replicate an image of a website as best we could. That turned out to be “pretty well” in my opinion! Continue reading One-day design comp
Our second 201 project was to create a pizza shop. Not just any pizza shop, but Pizza 3001 – A cheese odyssey from the future. I’m not making that up.
At the start of the week, this was an introduction to javascript object literals – lots of them. Copy and paste, change a value, copy and paste, change a value, rinse, repeat. But in just a few days, we went from object literals to constructors and working on the prototype – and from static, predefined data to user-provided dynamic data. Hundreds of lines of manually defined javascript became, well, a lot fewer lines and a whole lot more functionality. It’s almost like they wanted us to learn exactly how valuable constructors are. Answer: Very. Continue reading Pizza 3001: Our Last, Best Hope
Earlier this month, I took and completed Code Fellows Code 201 – I’m about to start 301 so you know what that means: retrospective post time!
When I told some of my peers my plans to move on from my previous job as a front end developer for a small nonprofit and take some code classes, one of the first questions was “but you have the job, why?” Well, a few reasons. Continue reading Code Fellows Code 201
More for my own benefit than anyone else but the extremely niche project I discussed in Agile in the Unlikeliest of Places is now on Github.
If you’re thinking “you just wrote this post as an excuse to post that image,” you would be correct, yes. I expect it to be more true than not in the near future, though.
At least for my organization, four minutes.
Several weeks ago, I was reading an article about iPhone 6+ display scaling and the author prefaced the main body of the content by saying “And, I’ve reduced this article from 14-min reading into less than 6-min reading. My target was 3-min reading.”
I thought to myself – I wonder how many minutes my company’s blog posts take to read? How many does our audience want to give to a particular post? Is my organization meeting their needs by producing articles that can be read in the time they’re willing to give us? I set out to find out – if I could. Continue reading How many minutes for a blog post?