Common Mistakes Made By Web Developers


Published on

Common mistakes made by Web Developer observed by our "Quality Assurance" team member at BOSS Webtech.

Published in: Technology, Design
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Common Mistakes Made By Web Developers

  1. 1. Common Mistakes Made BY Web Developers Prepared by: Mansi Godayal Sep -29-2011 BOSS Webtech Private Limited
  2. 2. Flexibility with Different Text Sizes <ul><li>Website users having low vision may keep their font-size magnified, for their easier reading. </li></ul><ul><li>Many website fall apart in unfortunate ways if font is enlarged. </li></ul><ul><li>Resultant problems: </li></ul><ul><li>Overlapping text, which becomes unreadable </li></ul><ul><li>Text disappears from the page when it overflows the layout. </li></ul>
  3. 3. Ignoring Web Standards <ul><li>Web standards were invented for a reason </li></ul><ul><li>Most developers will disagree with some aspects </li></ul><ul><li>A novice developer will make typical mistakes such as: </li></ul><ul><li>Forgetting or using inappropriate DOCTYPEs. </li></ul><ul><li>Using old-school HTML such as table layouts and center elements </li></ul><ul><li>Not appreciating the subtleties of inline or block elements, e.g. putting h2 headings inside a span </li></ul><ul><li>Not validating their code. </li></ul><ul><li>Using a validator then ignoring the results and arguing that validators are inherently flawed </li></ul>
  4. 4. Lazy browser testing <ul><li>Test in one browser throughout the whole of the development process </li></ul><ul><li>Spend more time persuading people that other browsers are rubbish rather than fixing their application </li></ul><ul><li>If they’re given no other choice, they’ll implement horrible quick fixes using browser-sniffing </li></ul>
  5. 5. Spending too much Time with the Choice of Framework <ul><li>If we have a small application (say less than 10 lines of code) the framework probably isn't your problem anyways. </li></ul><ul><li>And if you have more code than that, it's still not that hard to switch systems when you really have to. </li></ul><ul><li>The framework choice used to be a lot harder when the systems were incompatible. But this clearly no longer is the case. </li></ul>
  6. 6. Text that Looks Like Links; Links that Look Like Text <ul><li>There's a well-established expectation that linked text is underlined. </li></ul><ul><li>As a result, any underlined text will receive attention on your website as if it were a link . </li></ul><ul><li>Similarly, if your links are not underlined, or do not in other ways appear to be links, they will frequently be overlooked. </li></ul>
  7. 7. (Too much) Visual thinking <ul><li>Treating the web as WYSIWYG – starting off by focusing on how things look instead of thinking about structure first, and presentation later . </li></ul><ul><li>There is no way of making the web WYSIWYG. </li></ul><ul><li>There will always be variations as long as people use different browsers, OS, monitor sizes, screen resolutions, window sizes, colour calibration, and font sizes. The web is not print or television. </li></ul><ul><li>Make your design flexible. </li></ul>
  8. 8. CAPTCHAs <ul><li>The compromise between spam prevention and accessibility is always a problem. </li></ul><ul><li>However, there are much better tools for spam prevention than the CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart). </li></ul><ul><li>A little bit a content analysis can go a very long way in removing spam, without having any negative impact on visitors with disabilities. </li></ul><ul><li>Using a CAPTCHA creates significant barriers for customers with disabilities.. </li></ul><ul><li>  </li></ul>
  9. 9. Security Issues <ul><li>SQL injection (still see it around unfortunately) </li></ul><ul><li>Emailing credit card details (most cases they shouldn't be stored anyway) </li></ul><ul><li>Storing passwords in plain text </li></ul><ul><li>Trusting the client data - things like putting the amount for an order in a 'read only' text box and just expecting users not to tamper with it </li></ul>
  10. 10. Bonus blunders <ul><li>Continually rewriting and refactoring the same code </li></ul><ul><li>Under-estimating development time </li></ul><ul><li>Inappropriate use of Flash </li></ul><ul><li>Creating separate CSS files for every browser </li></ul><ul><li>Spending hours arguing why technology X is better than technology Y rather than getting on with the task </li></ul><ul><li>Quoting statistics as justification for ignoring or not testing in some browsers </li></ul><ul><li>Not validating user input or assuming client-side-only validation is adequate </li></ul>
  11. 12. About BOSS Webtech <ul><li>BOSS Webtech  is a process oriented design house specializing in web design, web development, backend web programming, mobile application development and other web and mobile related design and support services. </li></ul><ul><li>Recently launched BizPlus – Mobile based survey software. Check it more here </li></ul><ul><li>More products here </li></ul>CONTACT BOSS WEBTECH <ul><li>Call 831-998-9121 at US EST/CST/MST/PST Zone or email [email_address] </li></ul>