Responsive Desighn Workflow – My work flow

Every project starts in the same spot, getting or being given an idea (or project). Every time I immediately record the concept as soon as possible. I also am careful to not record ideas or any concepts that will give me a bias when I reach a real development stage; something I do too much and have ruined projects with. Then I mull the idea around thinking about how it should be approached, I also get input from others to help find some direction or unique approaches… this is something I am constantly doing. Then I finally sit down to create my first written ideas, starting with documenting the bare-bones structure needed and then playing with how those can be best presented. This stage involves a lot of getting ideas and input from others as-well as looking to see what others did in similar situations. After a seriously large bit of thinking and trial and error I settle on how everything should be tackled. Finally I start coding at this point and making a wireframe, this involves just as much if not more of seeing what works and what does not and getting ideas and input from others; I am also referencing my notes from before. After a the roller coaster that is settling on a layout is finished I start populating the website and fine tuning everything to work. I have come to really love being a part of this process, and I am so excited for further my skills and try new things. On that note and given that this is my last post for this class I would really like to say thank you fer everything this quarter… changing over to web dev for school was a scary thing to do and I’m so happy to have taken the leap! I’m excited to go to school and too see what this all becomes. I look at the whole world differently and have skills I would have never dreamed of, and I’m just getting started! Thanks



Responsive Design Workflow – Chapter 4,5,6

Chapter 4, introduction of the “tool rule”! I’m sure glad the author did that, otherwise I could never see past his command line work and simulations. He luckily has the thought to realize that our industry is constantly changing and there are many angles to work it from. Ill tell you what, the command line is cool, converting to html was cool, but its not my thing.

I really like how the author keeps giving attention to working with the client. The author gives good input regarding problems he has had and ways to communicate in understandable terms. Furthermore this translates to the attention given to documentation in wire frames.

This last week I didn’t get to the reading until Thursday, so most of it was review. I’m going to try and read far ahead this week. It will help in class and I’ll have less to carry biking to school!


Responsive Design Workflow – Chapters 1,2,3

I love how the author jumps right off sharing his background the development of how web sites are developed and then goes straight to poking holes at the entire process, making a mockery of it, arguably even throwing a wrench into the whole concept. Beautiful. Furthermore, necessary. I have been thinking to my self very much recently, whats so different between what I want to and others in my classes with similar but different interests and fields want to do? I suppose the real difference is personal interest/focus, the author goes to make a good point that if your touching front-end work then it means… well you touched the front-end. It seems like a moot point and isn’t the soul focus of this chapter but its a great point to look at none the less. It takes no thought and comes with no regret to follow the author as he “jumps from the waterfall” and take a step forward into designing in the browser.

Websites should not be built like automobiles in an assembly line.

What a great idea! Its kinda a statement that deserves a response to the nature of, “duh”. I have my sites set more on doing freelance and more individualistic work, but I was disturbed to learn how teams building websites interacted.  Even from a stand point that is involved I have remained upset with such a illogical method of completing a task, let alone a task of this type. Just as I largely dislike poor-efficiency I value true efficiency greatly and the manner in which the author proposes one should start designing a website is spectacular. Its simple, fast, realistic, and growth oriented.

The authors stance that wireframes are over complicated, it makes me uneasy. I understand how he has come to feel such a way but I myself from a rather unbiased point of view slightly concur. I believe that basic sketched wireframes would be a perfect step added between gathering a content inventory and jumping into markup. It gives a simple and non time consuming moment to figure our what the client does and does not want, even if its a vague it of direction, but I digress the author shows humility in his stance and I may feel different as I continue on. As a final side note, I feel like mobile first is genius; its simple and very growth oriented.