presentation information: http://www.aneventapart.com/events/2008/chicago/slides/
Eric Meyer
topic: evaluate HTML/CSS of various submitted websites
As Eric was evaluating the html behind various websites I was reminded of the history of computer science. I present my thoughts in an effort to open a community discussion about the role of knowing the details of html in order to be an effective developer and/or designer.
PRO SIDE:
The ability to see everyone’s source code (i.e. html & javascript) opens the door to some very interesting analysis of peoples’ work. It can be most humbling and is of course frought with lots of opinionated things. but overall it is a very useful way for an html coder to improve his/her writing ability. Good writers are good readers.
CON SIDE:
On the other hand, consider this - is it better to do the low level html or should your tool abstract away all the details of html. Is the exercise of reviewing someone’s html similar to reviewing the machine code of a C++ or Java programmer? Humm??? I wonder if html will go away like machine code and assembly language have “gone away”. They have dissappeared under the hood. Abstracting away by the tools. This is the history of computer science - building developer tools which abstract away the lower level details, thus helping the developer become more productive by focussing on higher level issues.
Will html go the way of assembly language like we’ve seen with compilers? Or will it always be necessary for human eyes to be able to see and modify web pages at the html level?
————————————————————————————–
speaker: Rob Weychert
topic: Design Lessons Learned in Chess
* he read several good books to improve his chess game, after 20 years of playing
* information architecture, design, build
* form a strategy based upon your client; what do they want; who do they want to reach; what is their message
* opening move = information strategy
* middle game = visual design
** strategy - overall plan
** tactics - steps you take to implement the strategy
* endgame = build
* limit the user’s options
* content is king! style (css) + behavior (javascript) ==> layout ==> content
* set expectations! (bobby fisher story from 1972)
* the web allows the receiver of the content to receive it in whatever way they want - this makes a challenge to the designer!
* don’t get too attached to your last move
* find balance in your view of validators (extreme: get rid of all validation errors extreme: who cares!)
* learn from your failures
———————————————————————————-
speaker: Dan Cederholm
topic: Implementing Design: Bulletproof A-Z
* author of simplebits.com
* “handcrafted pixels & text”
* tiny design company in vermont
* craftsmanship reflects the human touch behind the design
* flexibility in design
* case study: icedorhot.com
* need to be able to see/find/keep/improve design patterns
* we should use reset.css on all sites!
* his list of bulletproofing is excellent for developers (see http://www.aneventapart.com/events/2008/chicago/slides/)
* designers should use XScope (shareware product for macs)
———————————————————————————-
speaker: Cameron Moll
topic: The In-House Designer
* designer for LDS church - 30 designers, 100 websites
* focus on importance of relationships
———————————————————————————-
speaker: Curt Cloninger
topic: Arts & Crafts of Web Design
website: lab404.com
* William Morris - father of modern design
* this presentation seemed to be targetted @ designers and was an appeal to create places of beauty
* we need more frilly bits on our websites so this guy will die happy!
* orchestrate things so that you do what you like
* outsource/mechanize the unpleasurable, but do as much of the entire process yourself at least once
———————————————————————————-
speaker: Jeff Veen
topic: Designing the Next Generation of Web Apps
website: veen.com
* left working for google 5 months ago
* if you want to become a speaker, write a book!
* so much data - help people with all of the data in their life to be able to manage it
* gave an example of taking rainfall data - added headers, changed fonts/styles, colored the numbers, replacd the numbers with graphics of different sizes, (becareful not to go too far), redesigned google analytics over 15 months!
* looking for inspiration - history, users,