20 things that drive web developers crazy

[kokoon]

http://www.netmagazine.com/opinions/20-things-drive-web-developers-crazy

 

1. Add rounded corners to every single element on the page. While you're at it, add shadows and gradients too.

 

2. Use the same PSD as a starting point for every project. Hide unused layers, but don't delete them. Make sure your PSD is at least 100MB.

 

3. Use sIFR on every piece of text. Bonus points if you choose a font that's very similar to Arial.

 

4. Never use the same dimensions on elements. Give each a different font size and colour (for black, use #000000, #111111, #121212 ...).

 

5. Use a lot of breakout images with transparency. Web developers love graphics breaking out of boxes and columns. Bonus points if you add text wrapping around images.

 

6. Add a modal window. At least half the site should happen in a modal window.

 

7. Add a Facebook Connect button. It's just a button. How hard can it be to implement?

 

8. Hide important PSD layers. Later, tell the developer that they missed a hidden element.

 

9. Create buttons with rollover, active and clicked states. Then don't tell anyone you've done this. Create a separate file for them and send it on at the last minute. We love surprises.

 

10. Tell the developer about some fancy functionality you read about somewhere on a blog. Then tell them to build it, because, if you saw it somewhere, clearly it's possible.

 

11. Add a carousel. Oh yeah, and make sure it's a full-screen carousel.

 

12. Use Lorem Ipsum instead of real copy. And make sure the reserved space is not big enough for real copy.

 

13. Randomly merge PSD layers. Why not? (But don't merge too many. It'll take you further away from the magic 100MB target).

 

14. Name all your files 'final', plus a date and a random letter (final-2010-12-01a.psd, final- 2010-12-01r.psd, final-2010-12-02b.psd).

 

15. Don't worry about making changes once everything is signed off. When we're done with a page, send another, completely different version of it. And tell us that those changes are necessary and essential for user experience.

 

16. Don't name or organise your PSD layers and folders.

 

17. If you're designing a form, forget about error and success states. We'll squeeze that stuff in somewhere. We love guessing your intentions.

 

18. When you're designing a website, don't invite any developers for brainstorming or design meetings. Make sure we're the last ones to see the layout. Show it to the client first, so it will be too late to introduce even a modicum of sanity into your work.

 

19. We should hang out more, so during QA don't use bug tracking software. Come sit with us for an entire day and point out changes you want made over our shoulders. Use the opportunity for some impromptu design updates as well.

 

20. And finally, this is the most important thing: don't learn anything about HTML, CSS, JavaScript or browser issues. The less you know about it, the more important we seem.

[Guest Iain C]

Most importantly, who cares about web developers?

[Guest Gary C]

Most importantly, who cares about web developers?

[Guest Benedict Cumberbatch]

http://www.netmagazine.com/opinions/20-things-drive-web-developers-crazy

 

1. Add rounded corners to every single element on the page. While you're at it, add shadows and gradients too.

 

2. Use the same PSD as a starting point for every project. Hide unused layers, but don't delete them. Make sure your PSD is at least 100MB.

 

 

 

8. Hide important PSD layers. Later, tell the developer that they missed a hidden element.

 

9. Create buttons with rollover, active and clicked states. Then don't tell anyone you've done this. Create a separate file for them and send it on at the last minute. We love surprises.

 

10. Tell the developer about some fancy functionality you read about somewhere on a blog. Then tell them to build it, because, if you saw it somewhere, clearly it's possible.

 

12. Use Lorem Ipsum instead of real copy. And make sure the reserved space is not big enough for real copy.

 

14. Name all your files 'final', plus a date and a random letter (final-2010-12-01a.psd, final- 2010-12-01r.psd, final-2010-12-02b.psd).

 

15. Don't worry about making changes once everything is signed off. When we're done with a page, send another, completely different version of it. And tell us that those changes are necessary and essential for user experience.

 

16. Don't name or organise your PSD layers and folders.

 

17. If you're designing a form, forget about error and success states. We'll squeeze that stuff in somewhere. We love guessing your intentions.

 

 

so so true

[QBLA]

I'm in the visual designer category. I've worked with a friend who is a web developer and he says that my psd files were the easiest to understand and follow.

[Guest KY]

Most importantly, who cares about web developers?

[kokoon]

http://www.netmagazine.com/opinions/20-things-drive-web-developers-crazy

 

1. Add rounded corners to every single element on the page. While you're at it, add shadows and gradients too.

 

2. Use the same PSD as a starting point for every project. Hide unused layers, but don't delete them. Make sure your PSD is at least 100MB.

 

 

 

8. Hide important PSD layers. Later, tell the developer that they missed a hidden element.

 

9. Create buttons with rollover, active and clicked states. Then don't tell anyone you've done this. Create a separate file for them and send it on at the last minute. We love surprises.

 

10. Tell the developer about some fancy functionality you read about somewhere on a blog. Then tell them to build it, because, if you saw it somewhere, clearly it's possible.

 

12. Use Lorem Ipsum instead of real copy. And make sure the reserved space is not big enough for real copy.

 

14. Name all your files 'final', plus a date and a random letter (final-2010-12-01a.psd, final- 2010-12-01r.psd, final-2010-12-02b.psd).

 

15. Don't worry about making changes once everything is signed off. When we're done with a page, send another, completely different version of it. And tell us that those changes are necessary and essential for user experience.

 

16. Don't name or organise your PSD layers and folders.

 

17. If you're designing a form, forget about error and success states. We'll squeeze that stuff in somewhere. We love guessing your intentions.

 

 

so so true

i know, right??

 

wait, you left some out - so that means that you never had problems with:

 

3. Use sIFR on every piece of text. Bonus points if you choose a font that's very similar to Arial.

- we've only just begun incorporating sifr fonts (see number 10) but it's already been a pain. mainly due to some funky characters that our language requires.

 

4. Never use the same dimensions on elements. Give each a different font size and colour (for black, use #000000, #111111, #121212 ...).

- this exact thing happens all the time. both the colors and the dimensions thing. sloppiness of the highest order.

 

5. Use a lot of breakout images with transparency. Web developers love graphics breaking out of boxes and columns. Bonus points if you add text wrapping around images.

- breakout images. designers love it. then you have to handle with different browsers (older IEs) handling absolute positioned block-level elements differently.

 

6. Add a modal window. At least half the site should happen in a modal window.

- really not that common, but it's happened. it starts out with a "send to friend", then another form, then feedback for that form, ...

 

7. Add a Facebook Connect button. It's just a button. How hard can it be to implement?

- don't get me started on facebook and our "creative team"...

 

11. Add a carousel. Oh yeah, and make sure it's a full-screen carousel.

- this happened. ended up making it in flash.

 

13. Randomly merge PSD layers. Why not? (But don't merge too many. It'll take you further away from the magic 100MB target).

- happens all the time. great fun.

 

18. When you're designing a website, don't invite any developers for brainstorming or design meetings. Make sure we're the last ones to see the layout. Show it to the client first, so it will be too late to introduce even a modicum of sanity into your work.

- the story of my life.

 

19. We should hang out more, so during QA don't use bug tracking software. Come sit with us for an entire day and point out changes you want made over our shoulders. Use the opportunity for some impromptu design updates as well.

- even if that happened only once it would be too fucking often.

 

20. And finally, this is the most important thing: don't learn anything about HTML, CSS, JavaScript or browser issues. The less you know about it, the more important we seem.

- qft.

[Braintree]

I've got a buddy helping me out with a site. I asked him for rounded edges on news entries

[chaosmachine]

I must be really good at screening my clients, I've never had to deal with any of these.

[Ego]

Why still bother with sIFR? You can get @font-face to work on most browsers.

 

I've had a lot of these things happen though. Requirements changing during development is my biggest frustration.

[Guest Benedict Cumberbatch]

http://www.netmagazine.com/opinions/20-things-drive-web-developers-crazy

 

1. Add rounded corners to every single element on the page. While you're at it, add shadows and gradients too.

 

2. Use the same PSD as a starting point for every project. Hide unused layers, but don't delete them. Make sure your PSD is at least 100MB.

 

 

 

8. Hide important PSD layers. Later, tell the developer that they missed a hidden element.

 

9. Create buttons with rollover, active and clicked states. Then don't tell anyone you've done this. Create a separate file for them and send it on at the last minute. We love surprises.

 

10. Tell the developer about some fancy functionality you read about somewhere on a blog. Then tell them to build it, because, if you saw it somewhere, clearly it's possible.

 

12. Use Lorem Ipsum instead of real copy. And make sure the reserved space is not big enough for real copy.

 

14. Name all your files 'final', plus a date and a random letter (final-2010-12-01a.psd, final- 2010-12-01r.psd, final-2010-12-02b.psd).

 

15. Don't worry about making changes once everything is signed off. When we're done with a page, send another, completely different version of it. And tell us that those changes are necessary and essential for user experience.

 

16. Don't name or organise your PSD layers and folders.

 

17. If you're designing a form, forget about error and success states. We'll squeeze that stuff in somewhere. We love guessing your intentions.

 

 

so so true

i know, right??

 

wait, you left some out - so that means that you never had problems with:

 

3. Use sIFR on every piece of text. Bonus points if you choose a font that's very similar to Arial.

- we've only just begun incorporating sifr fonts (see number 10) but it's already been a pain. mainly due to some funky characters that our language requires.

 

4. Never use the same dimensions on elements. Give each a different font size and colour (for black, use #000000, #111111, #121212 ...).

- this exact thing happens all the time. both the colors and the dimensions thing. sloppiness of the highest order.

 

5. Use a lot of breakout images with transparency. Web developers love graphics breaking out of boxes and columns. Bonus points if you add text wrapping around images.

- breakout images. designers love it. then you have to handle with different browsers (older IEs) handling absolute positioned block-level elements differently.

 

6. Add a modal window. At least half the site should happen in a modal window.

- really not that common, but it's happened. it starts out with a "send to friend", then another form, then feedback for that form, ...

 

7. Add a Facebook Connect button. It's just a button. How hard can it be to implement?

- don't get me started on facebook and our "creative team"...

 

11. Add a carousel. Oh yeah, and make sure it's a full-screen carousel.

- this happened. ended up making it in flash.

 

13. Randomly merge PSD layers. Why not? (But don't merge too many. It'll take you further away from the magic 100MB target).

- happens all the time. great fun.

 

18. When you're designing a website, don't invite any developers for brainstorming or design meetings. Make sure we're the last ones to see the layout. Show it to the client first, so it will be too late to introduce even a modicum of sanity into your work.

- the story of my life.

 

19. We should hang out more, so during QA don't use bug tracking software. Come sit with us for an entire day and point out changes you want made over our shoulders. Use the opportunity for some impromptu design updates as well.

- even if that happened only once it would be too fucking often.

 

20. And finally, this is the most important thing: don't learn anything about HTML, CSS, JavaScript or browser issues. The less you know about it, the more important we seem.

- qft.

 

just didnt connect with them as much as the others