###Week 6 It’s amazing to look back over all we’ve learned and were able to accomplish by the end of week 05. Trial by fire some may call it, the Iron Yard’s Hackathon holds a spot in the student’s hearts. The standard week-in week-out of an immersive coding and design school is already compressed and forces you through a range of emotions while constantly out of your comfort zone. The Hackothon compresses that further.
3.5 days — from noon Thursday to 1am Monday - you work with your team to spring an idea, plan the process, and build a functioning app working with a database. And you do this with 5 or so weeks of experience! My team was awesome, working long and hard, and with great companionship — I couldn’t have asked for more. After the dust settled, my initial reaction is, “Wow, that was a hell of a lot of work, but equally as rewarding.” It could possibly be one of the highlights of my Iron Yard experience. Needless to say, a little bit of a break was in order.
###Jekyll & Markdown
If you weren’t aware, this site is built off of Jekyll, a “blog-aware” framework designed to help build efficient blogs using the Markdown language.
Markdown is a nifty language that is easy and quick to type and can be converted to html. These blog posts are written in Markdown and allow me to effortlessly write posts without having to muck about with html tags and elements.
From Daring Fireball > Markdown is a text-to-HTML conversion tool for web writers. Markdown allows you to write using an easy-to-read, easy-to-write plain text format, then convert it to structurally valid XHTML (or HTML).
I highly recommend reading that post as Daring Fireball’s author, John Gruber, is one of the creators. It will give you a thorough overview of the syntax and features.
###Paper & prototyping
We’ve begun to study rapid prototyping techniques and how to effectively use them to help product design. A quick exercise involving teams of two was set up to paper prototype a user action on an airline website. The process myself and parter selected was choosing a flight with US Airways. While we found a small number of ways we believe the site could be improved, we learned a lesson that prototyping should make extensive use of data and a hypothesis which may require more time than we were allowed.
Through a couple of quick tests, we were able to find that our hypothesis of removing additional choices in the flight filter options, and moving the price to a more prominent location, resonated with our test demographic (my classmates).
I think the power of paper prototyping is real, but I am more excited to get into prototyping tools like InVision. Continuing with my goal of working on a native product, I want to become familiar with these tools and the experience of using them in the workplace.