Skip navigation
factory /><div class=

Web Development Fallacies, Part 1

Originally published December 2001 - Updated July 2006. By Eric Holter.
print PDF email a friend
1 | 2 | 3 | 4 | 5 >>  

Web Development Fallacies, Part 1
»Web Development Problems
2.Presenting Designs
3.Communicating
4.Website Specification
5.Website Frustration

Sign up to Web Smart:


| RSS

Developer Fallacies
It can be tempting to blame and criticize clients when projects go bad. But more often than not, problems can be traced back to mistaken assumptions on the part of the developer. Recognizing these fallacies can help clarify our responsibilty as the developer in a web project.

Many of the concerns identified in these developer fallacies apply to Newfangled as a web developer. However, when working together with an agency in a development project, clients do not make much distinction between what the agency is responsible for, and what the developer's responsibilities are. Because of this it is appropriate for you to be aware of these common developer fallacies.

These fallacies were originally written as stand alone articles. Each one is accompanied by a corresponding solution examining how grayscreen prototyping can help overcome these common web development problems.   next >

print PDF email a friend
1 | 2 | 3 | 4 | 5 >>  
FACEBOOK


Comments


 Zeal Murapa February 25, 2009 4:43 AM
Good Articles! Well written too