TypeCulture Academic Resource - a directory, archive and educational aid for design students, educators and professionals who are seeking information about type; its history, manufacture, use and artistic significance.

Information architecture, communication, graphic design and presentation, Mr. Tufte is the man. Whether your a Graphic Designer, or a Project Manager his knowledge will help you. Check out the Ask E.T. section to learn more.

on Squidoo

When and Where
Monsanto on Friday, November 10, 2006 from 8:00a.m. - 5:00p.m. The conference is filling up fast. Only 100 participants allowed to register.

How Much
$30 before July 31st and $45 after August 1st. All proceeds from registration fees are used to fund conference logistics. The conference continues to be maintained by a "grassroots" organization -- all planning, coordination, presentations, etc. are done by user experience practitioners for user experience practitioners.

Keynote Speaker
Dirk Knemeyer. Dirk will be presenting "The Future of Digital Product Design."

Interactive Poster Session
New this year -- a poster that will be created by participants during the conference. We'll provide a space for you to share your favorite research, technique, and tool sites and we'll publish it after the conference for all attendees.

Click for Agenda

Registration
When you register for this year's conference, you'll be asked to complete a section with your personal information. You'll then be asked to pre-select the sessions you would like to attend. This allows UX06 to ensure that they have the proper facility arrangements for each presentation. Spaces will fill up fast, so register as early as possible to ensure you get to attend the sessions of your choice.

After you complete registration, you'll see a link to PayPal. A special thanks to Gateway CHI for kindly offering their PayPal account as a way for us to collect registration fees. Your registration payment is a separate step and can only be completed by using a PayPal account that is either linked to your bank account or by using your credit card to pay your registration fee.

All proceeds from registration fees are used to fund conference logistics, meals, etc. If you cancel your registration, your fee WILL NOT be refunded. Registration for STLUX06 is open now through November 1st. Register by July 31st to receive the Early Registration discount. For security reasons, no on-site registration will be allowed; if you want to attend, you must register by the November 1 deadline. Register using the link below: (a big thank you to Maritz for the very generous donation of their registration tool)

https://www.meetinghq.com/group/101005647?wslid=attendee

Questions?
Jennifer Ruffino
jennifer.ruffino@monsanto.com
314-694-4649

I’ve been a member of LinkedIn for over a year. Although the idea of an exclusive way to make business connections seems great, I have some reservations about the idea of exclusivity and accuracy. The concept of endorsing someone, a mini testimonial, is totally self-serving. How can that lend credibility to one’s self-described professional abilities?

The social fabric created in LinkedIn - the ability to see who is linked to whom and the degrees of separation - is interesting, but what real purpose does it have? I guess it allows one to use someone to gain access to someone else - a connection pimp. I haven’t really connected with anyone via an existing connection and I view this site and my participation as an experiment and don’t have any expectations. Only time will tell if this virtual network has validity.

If you are a member, contact (mail at jamesbielefeldt dot com) me, let’s get connected.

When working with vendors there’s always the risk they will jeopardize the outcome of a project, hurt your relationship with the client and cost you a lot of money. It’s best to try to minimize this risk and the best way is with a service level agreement. This contract should require a signature, be a binding, legal document and contain clauses that specifically address potential problems.

Some general recommendations:

• Clearly state your expectations on quality.
• Establish the fact you are their client and they work for you, not your client.
• Define communication channels and the proper protocol. This is essential in maintaining control.
• If possible, keep ownership of all deliverables.
• Outline responsibilities for all phases of the project.
• Require they follow best practices and deliver good work. Have a clause that states you can audit their work at defined intervals, or when the project is suspected to be affected.
• State any loss due to missed deadlines or unacceptable deliverables is their liability.
• Require detailed plans and necessary documentation demonstrating they know what they are doing.
• Determine lead and tag times, turn around times and expected response times.
• Have a change control process that details how changes are approved and incorporated into the project’s scope.
• List the consequences for failure to meet requirements and the escalation/arbitration process.

These are just some basics requirements any good service level agreement should have. Remember this is an agreement so it is important to review this with your vendor, discuss each requirement and customize it so both parties can really agree to follow it.

Truer words were never spoken. Great post by Seth Godin.

There have always been good resources for JavaScript online. But recently there’s been some robust libraries created and made available that do everything from animation to AJAX. These libraries are ways for novice developers to quickly implement complex JavaScript functionality into sites while adhering to good programming rules.

One problem with some of these libraries, if used in their entirety, is the file size they can add to a web page. Often it is best to just incorporate the code that does what you need and delete the rest – if you know how to do that. Here are a few of the most popular.

Script.aculo.us   

“script.aculo.us provides you with easy-to-use, compatible and, ultimately, totally cool JavaScript libraries to make your web sites and web applications fly, Web 2.0 style.”

jQuery  

“jQuery is a new type of Javascript library. It is not a huge, bloated, framework promising the best in AJAX - nor is just a set of needlessly complex enhancements - jQuery is designed to change the way that you write Javascript.”

Yahoo! User Interface Library 

“The Yahoo! User Interface (YUI) Library is a set of utilities and controls, written in JavaScript, for building richly interactive web applications using techniques such as DOM scripting, DHTML and AJAX. The YUI Library also includes several core CSS resources.”

Interesting online viewing from Flash In The Can.

GMunk | Joshua Davis & Stephan Sagmeister | Ben Fry

Forms on the web are vulnerable and subject to malicious behavior. With the explosion of forums, wikis and blog comments, programs having been created to spam these useful communication mechanisms. Often these forms do not require any authentication. Users can simply complete the form and submit it to post their comments.

A newly popular technique for prohibiting malicious applications from submitting forms are CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart) Security Images. These are images created at runtime that have a random sequence of numbers and letters that are distorted so only humans can interpret them.

CAPTCHA image
 

There are several code examples and small libraries online that illustrate how to implement this feature, just Google. Here are a few:

ASP
http://www.tipstricks.org/

PHP
http://phpsec.org/articles/2005/text-captcha.html
http://www.evolt.org/securing_forms_random_image

ASP.NET
http://www.hotscripts.com/Detailed/43986.html
http://www.lanapsoft.com/products.html

While this is great for forms exposed to the public, many developers are also using them on login forms. I don’t understand this practice. One would think a properly implemented password would be sufficient. The image just complicates matters and some are barely legible by humans. I know Yahoo! displays them for subsequent attempts to submit an authorization form, but not on the first try. I guess that’s a compromise for usability’s sake.

The two most common ways to price interactive work are Fixed Price and Time & Materials. Each method has its pros and cons that greatly affect the buyer and seller of the services.

Fixed Price

Fixed Price is popular with ad agencies and communications firms doing interactive work. It’s how they have traditionally priced their services and is client friendly, because with Fixed Price the risk to produce the job, at the quoted price, lies with the seller. When pricing a project this way it is imperative that the project’s requirements are determined and the scope is tightly controlled. Any complications, rework, or excessive man-hours because of underestimating required time, unseen issues, or inexperience are the cost of the seller. The only time the price is usually renegotiated is when the requirements change, or the buyer requests a change of scope.

When calculating a Fixed Price estimate is it important to figure in contingencies for the unknowns and potential problems, in addition to a profit margin. Counting just man-hours usually means an unprofitable situation. There are several ways to include these cushions: applying a multiplier, padding hours, and adding a risk contingency cost based on project requirements are a few.

Time & Materials

Because of the difficulty of gathering requirements and establishing a detailed project scope, Time & Materials is how most IT companies price their services. This method puts the risk on the buyer to get the project completed within their budget and can be unfavorable in competitive environments, or unacceptable in RFPs. An estimate with a price range is usually proffered with the proposal/contract. Initial estimates can range in excess of +/- 25%. Most buyers like the price to be accurately estimated, but this arrangement is more flexible than Fixed Price. Additional estimates are often given as requirements become available, or as work is completed. Any changes are simply billed when they are incurred.

Do not mix the two methods. Real problems arise when a solid price is quoted in a proposal/contract that has been calculated using Time & Materials formulas. Even if you plan to bill using Time & Material costs, it rarely adds up and the initial price quote is all the buyer cares about.

Each method is effective when used appropriately. Rather than always pricing work the same way, let the market and project dictate which method is best.

The Photo District News Photo Annual offers work from some of the finest photographers in the biz today.

I’m working on several projects for a corporation to improve different processes centered on their web development efforts: better proposals, better cost estimating, better cost reporting, and standardization of workflows.

Each of these assignments is independent on one level, but also interrelated on another. Herein lies the rub. Every time I make progress, a meeting is required to communicate my findings – emails don’t get replied to; phone calls are out of the question; if it isn’t in Outlook it doesn’t exist. At every meeting a new caveat is introduced eradicating any realized progress.

Should Sue be involved? You need to double check that with Bill. That’s not how we do it. That won’t work. Isn’t that related to John’s initiative?

Maybe Sue should be involved but she is way too busy already. Bill didn’t reply to my emails and after three weeks I guess he doesn’t care. I know that’s not how you do it. Your way isn’t good. That’s why I’m suggesting a different approach. Let’s try it to see if it “won’t work”. Yes it is related to John’s initiative, but what’s the chance of accomplishing anything by getting more people involved?

All I hear is “We want change, but only if we don’t have to change or do anything”

Typical corporate grid lock. A small smart company tries things out, changes constantly, accepts failure, adjusts and moves on. There is a lesson here. By tackling issues one at a time, whether related or not, incremental change can happen and results realized much faster and painlessly than forming a committee, having umpteen meetings and waiting on everyone and their brother to weigh in. Assume the risk and go for it.