Yahoo Design Patterns For Web Design

Hmm -- my2cents, can you remember we had a discussion about standards and all that once?

I think every developer should have his own design standards. In creating yours, it would be nice to review that f various proven devloper communities. I have reviewed Yahoo, Google, Microsoft, etc etc and picked things I thought were best about their patterns.

That way, I feel a sense of pride in knowing that I have Design Patterns that were created by me -- it's easier tow ork that way. That's my two cents 

So the people that change design patterns nko? Why don't Microsoft, Oracle, Yahoo, Google etc use the same patterns?

I don't know -- but using something I'm comfortable with is my own preference -- and that's my two cents.

_{Is this plagiarism?}

prodgalson, thanks for the lecture, but my2cents understands me perfectly. I'm not talking of visual stuff here -- I'm talking of code as you are.

I must put in my remaining 1cent of objection,  ever since my2cents started leaning strongly on guys who did not stick to standards; i have been very uncomfortable, why,  because most of it is true and you sort of feel either angry because someone told you or guilty because you know it is true.

I started out as a VB interface developer for a stockbroking company back in 1997, I would cause the coders severe fever and hypertension by making a single interface that handled 90% of everything the application had to do, which  meant using a single button in at least 10 different context (changing its name color and position etc)

Until one barely computer-literate user called me out of frustration "Why can't it be as easy as winzip" I literally banned him from using the computer until he upgraded his skills to the level where he realised winzip is a utility, i was building applications. One day i came upon an interface I had built a year back,  I could not use it, I cursed whoever designed it and took it to the drawing board for re-design.

Right there and then i realised what my problem was, I was an artist who loved his own style and would not stick with successful design patterns that are known to work. From that point on,  I started looking at the Windows interface closely and modelled my designs after that. Voila,  users were impressed, work got done a lot quicker and things became so logical that i hardly have to do a manual to users on how to use my applications.

so the is in order.

I have yet another acronym for you: KISS - Keep It  Smart and Simple.

Note to Zahymaka: If you must respond to this, keep it +vely constructive  and less "antagonistic"