I wrote this blog post a couple months ago, but it still applies: http://www.aclevercookie.com/10-tips-for-budding-web-programmers-and-designers/ Cliff notes: 1. Use Firefox 2. Be Compatible 3. Less is more 4. Want javascript? use jQuery 5. AJAX has its time and place 6. Search engines like structured code 7. DIVs not TABLEs 8. Minimize inline styles 9. Code with the future in mind 10. Know the standards, but you don’t always have to follow
Why use firefox? It certainly used to be true but since IE7 has add ons the case is no longer true that it is better. You need to have FF for testing, along with IE 6, IE7, Safari, Opera etc Divs not tables needs to be clarified that it is for layout only as tabular data should be in tables, likewise nesting Divs can be as bad as nesting tables was
this is great one thanks for ur nice article ... and even most of users are using IE , i m opera fun ...
1. Use Firefox (I use ff/opera/ie6/7, makes it easier to fix problems head on) 2. Be Compatible (with what ) 3. Less is more (in what respect?) 4. Want javascript? use jQuery (jQuery is great, but you shouldn't overlook the others like mootools for instance) 5. AJAX has its time and place (when & where?) 6. Search engines like structured code (define structured code? ) 7. DIVs not TABLEs (cool, but use tables for tabular data (calendars etc)) 8. Minimize inline styles 9. Code with the future in mind 10. Know the standards, but you don’t always have to follow (explain please)
Definitely great tips.. As for firefox, my awstats show more traffic from IE than FF.. so i think work for both.
Add Internet Explorer 5.5, Internet Explorer 6, Internet Explorer 7, K-Meleon 1.0 (for older Gecko engine testing), Opera (latest build) and Safari to the mix, and then test in each one as you go along with each section of the page rather than waiting until the end. With what? If you mean W3 specifications, then state so. I call it "Minimal Markup" for a reason. Better yet, write your own library. JQuery is a bloated piece of garbage. Besides, if you really want to use JavaScript, use it unobtrusively - meaning it must NEVER touch the HTML code. Yes, it's called progressive enhancement. No they don't. They could care less - all they care about is content. Use the proper HTML elements for the jobs they were intended to be used for. Forget inline styles exist completely, and keep everything in the external stylesheet. Coding to the standards will do this for you. That's fine if you don't care about quality and craftsmanship, or accessibility and usability for that matter.
I am not sure if thats true, but if you use valid markups with title, alt tags, it sure can help better page indexing IMO
If someone took away my Firefox and Firebug I'd go mad now, it's such a time saver even when fixing errors in IE. Instead of sifting through your code wondering whats wrong, inspect the element giving you problems and work it out much faster.
1. Use Firefox (and Opera, and IE, and Safari, and ....) 2. Be Compatible (see 1) 3. Less is more (more or less) 4. Want javascript? use jQuery (or Mootools, or Prototype, or ....) 5. AJAX has its time and place (see 4) 6. Search engines like structured code (do they? can you prove it?) 7. DIVs not TABLEs (unless it tabular data, then tables not divs) 8. Minimize inline styles (no, have zero inline styles) 9. Code with the future in mind (hindsight is always 20:20) 10. Know the standards, but you don’t always have to follow (unless you are designing for someone who expects you to be compliant and accessible).
Thanks for the tip. I still got alot to learn though ...<DIVS not TABLES> IS ONE THAT IM FOCUSING ON AT THE MOMENT
everyone has his/her own way of coding. Those rules are true, but above all is ready to learn more and to adapt.