Ten Web Development Tips I Wish I’d Known Two Years Ago
A couple of years ago I started doing more and more web development and web design, and less and less desktop development. Here’s a few things I wish I’d known then:
1. Use a Reset Stylesheet
Different browsers are free to set default styles for font sizes, margins, and so forth. It’s a silly part of the specification but there you go. Rather than trying to eliminate these differences on a case-by-case basis, many web developers now make use of a reset stylesheet to set all margins to zero, remove all borders, standardize all font sizes, and so forth.
There’s dispute over which particular features need to be reset; but to be honest having any one of them is going to be better than none. Here’s a few examples:
2. Use a Browser Development Plug-In
When you’re learning it’s useful to be able to visualise “invisible” parts of your web-page - margins, padding, parent positions, and so forth. Unless you fancy setting debugging background and border styles, or guessing why your functions stop half-way through, I’d recommend getting a web development plug-in for your browser.
Most plug-ins will let you dig trough your DOM, debug JavaScript functions, and provide statistics about document load times.
- Firebug - plug-in for Firefox. This is an absolutely fantastic and invaluable tool for web development.
- Yahoo!’s YSlow - plug-in for the Firebug plug-in. Analyzes web pages and tells you why they’re slow.
- Internet Explorer Developer Toolbar - plug-in for Internet Explorer. It feels like it was written in an afternoon by someone who had no idea what web development involves, but there isn’t really any alternative for IE.
3. Learn JavaScript
Learning JavaScript is still a work-in-progress for me. When I started web design I assumed (please note that word “assumed”!) that JavaScript was a toy language, suitable only for pointless browser effects. Boy was I wrong!
JavaScript, especially with the rise of AJAX, is becoming less an optional add-on, and more and more a vital part of modern web applications. It’s an elegant language, possibly let down by poor IDE support, and used correctly, will let you jump your browser through hoops. Imaging Google Maps or Yahoo! Pipes without it.
4. Pick a JavaScript Framework, and Learn It
Learning JavaScript is all well and good, but once you start trying to use it in anger you soon learn that each browser has a subtly different DOM API (or not so subtly different in the case of Internet Explorer).
You could re-invent the wheel and spend ages handling these different edge cases, or, I’d suggest, you could learn a framework and let it do all the heavy lifting.
Not convinced? How about this jQuery code to stripe table rows (details omitted for clarity):
$(function() {
$('.stripe tr:even').addClass('alt');
});
(Yes I know in theory you should be able to do that in CSS. As always, Internet Explorer raises its middle finger to CSS theory).
Here’s a few links to some major frameworks:
5. Learn Photoshop
Ahhh, Photoshop. If you’ve only used simple paint programs before, using Photoshop is like emerging from a cave into the sunlight. (OK, that’s a bit of an exageration).
Traditional paint applications work on the basis that you want to change the color of pixels. Photoshop (at least for web design) works on the basis that you define regions, which are then styled. Pixels are assigned colors as a side-effect. The rules are:
- Layers are king;
- Selections are queen;
- Nothing should ever be destroyed or lost.
So as a little example, if something needs a drop-shadow, you don’t start trying to draw one. (That would destroy or change the original thing). You simply make sure the thing is in its own layer, and apply a drop-shadow style.
6. Use Semantic HTML - And No Cutting Corners
Web design usually starts with graphic design, but really it should start with the content and proceed from there. If you start with the visuals, it’s all too easy to fixate on why things don’t look right, and from there it’s slippery slope to using non-semantic elements and inline styles.
Start with the content; use appropriate elements without regard for style; and only once you’ve done that should you move on to writing an appropriate stylesheet. (Of course, you may sometimes need to add stylistic divs… although you’d be better off using JavaScript to modify the DOM, rather than modifying the source itself).
A corollary of this point is that tables should only be used for tabular data - there’s no usual need to use them for layout.
7. Find Out Why It Doesn’t Work - Don’t Shotgun-Debug
The HTML/CSS visual model is pretty complex: inline vs block elements; different position modes; and so forth. What makes matters worse is that there’s no definitive reference HTML renderer implementation: you can never be sure whether your page doesn’t look right because you’ve made a mistake, or whether it’s some browser bug.
This state of affairs can lead to shotgun-debugging: tweaking a value to see if it fixes the problem; tweaking another value and checking again; and so on and so on…
Obviously this way of learning isn’t ideal. If you ever want to learn, I’ve found that you need to be predicting the effects of your changes. Before you make a change, you should have an idea in your head of the expected effect. If the actual effect isn’t the intended effect, you need to find out why. Is your understanding of HTML/CSS wrong, or is it a browser bug? Test on more browsers, and if your understanding is wrong, correct it. (Of course, if it’s a browser bug, then you’ve learnt something afterall).
8. Test on Internet Explorer Earlier
You might have noticed from my snide comments about Internet Explorer that it’s not exactly my favorite browser. If I’m going to be fair, IE7 isn’t too bad, and IE8 promises to actually be standards compliant (gasp!). What bugs me is that (at the time of writing) about 30% of the world is still using an eight-year-old browser that doesn’t even get the basics of the HTML box model correct, and we web developers are expected to support it.
Anyway… I didn’t intend this paragraph to be a rant, so deep breath… and… we have to live with the situation as it is. Firefox has great standards compliance and great developer tools, so it’s tempting to use it as your primary development platform until right at the end, when you do cross-browser testing.
Don’t do this. I’ve learnt the hard way: you need to test your work at each stage, on all browsers. Even as recently as six months ago I was caught out by this: I spent a lot of time coding some web code that relied on z-indexing, only to discover that IE7 doesn’t support this feature fully. In the end I was able to bludgeon Internet Explorer into working properly with some JavaScript, but it wasn’t fun. Lesson learned: check each feature is going to work properly on IE before coding it completely.
9. Don’t Be Afraid of AJAX
Normal web-pages are pretty easy to understand. The browser makes a request; the web server sends back some HTML. AJAX is a little more difficult to understand, so I steered clear of it for two years.
I finally got stuck in when we started writing EasyAs123Web.com. I wanted the user to be able to edit the website in-place, so that forced the issue.
When you get down to it, AJAX is pretty simple.
- User does something (eg clicks) in the browser;
- JavaScript makes request to server (in a thread);
- Server replies with an XML document describing what to do;
- JavaScript received the reply and modifies the DOM based on that XML.
Of course, the devil is in the details, but a decent AJAX library hides most of that for you.
10. Charge For Old Browser Support
Asking a client if they need Internet Explorer 6 (or earlier) support is a recipe for extra work. They’re hardly going to say no when you phrase it like that. You then sit down and make a working website, and test it in IE6. Argh! Scrambled website! Eventually, you get it working, and you find that you’ve spent twice as long on the actual HTML/CSS as you planned to. Bad times.
Here’s my suggestion: treat older browser support the same as any other feature: as a chargeable item. Explain to the client that since older browsers work in a different way to modern ones (which they do), that’s extra work and hence extra cost. (I’d suggest approximately 10% on top). Explain that IE6 has approximately 25-30% market share, and let them make the cost/benefit call. Money has an amazing focusing effect: it forces people to really think about what they want and need.
Your Thoughts?
Got your own web development tips? Feel free to share them below!
A very nice list.
I only disagree on the “Photoshop” item… C’mmon man, Photoshop is really, really, really expensive! And it’s for… photography…
IMHO, Inkscape or Fireworks are much better options when its up to web design.
EasyAs123Web.com is going to easyas123wen.com
Great tips! Especially number 3!
Your number one is my most important one I wish I’d known when I took up web development, the one about reset stylesheets. It makes a hell of a lot of easier, from general design to developing in different browsers.
Great advise. Your link to EasyAs123Web.com is to EasyAs123Wen.com. Might want to fix that up
9. Don’t Be Afraid of AJAX
If you’re not worried about SEO
@radioxenu, @nadb -
Thanks! Link is now fixed.
@Rob -
That can be true about SEO… I guess it depends how you structure your site. I guess a guiding principle is that the static bits of the site should describe (in a semantic way) what the AJAX-y bits do.
@facundo -
Photoshop is expensive unfortunately. I’ve never used Fireworks (see, I’m still learning). I haven’t upgraded to Photoshop CS4 yet so I might just buy Fireworks instead… I’ll have a little dig around there, cheers for the advice!
to facundo
Photoshop is DEFINITLY not just for photo’s. You should look around a little bit and you’ll find out that Photoshop is used for most graphic work, including webdesign
Rather than paying for PhotoShop or Fireworks, check out the Gimp (www.gimp.org). It’s come along way. There is a slightly longish learning curve–you can’t translate much from Photoshop ot it, but it is very powerful out of the box.
Pretty nice list, but your #8 I disagree with. IE has shown blatent disregard for standards compliance and as a serious web developer (at least in my private projects) I refuse to even test my websites in IE. On commercial projects obviously I have to, but I’m actually thinking of creating a script to include on all my personal projects to block people from using IE, especially IE6, since that is like, what 10 years old?? I mean c’mon, if you can’t upgrade by now you shouldn’t be using a computer. Even my phone is more standards compliant.
Great article! But, please, may I use GIMP instead of Photoshop?
GIMP is a great cheep replacement for Photoshop. Works in win32 as well.
Ah Photoshop such a great tool. It will do just about anything you want after emptying your wallet.
Inkscape is good, I have not seen Fireworks but the best replacement for Photoshop is GIMP (The Gnu Image Manipulation Program). There is very little Photoshop can do that the GIMP can’t. The GIMP will not empty your wallet and it is available on most every platform you can desire.
Oh, and it’s free and open source.
Good list but I’d be wary of using a blanket reset for everything. Sometimes having none at all is better if you don’t know what to expect. Resets can be like taking a sledge hammer to a tack, you may only need to reset certain elements. I’ve found it best to write your own CSS base for your coding style. If you write semantic markup you aren’t going to be using things like B, U or I so why include it in your reset?
Also be wary of AJAX… It isn’t accessible yet. So folks with screen readers are missing out on your site. The SEO argument can be throw out the window when you make your site accessible (after all google is blind).
Good article.
First off I am a HUGE supporter of FOSS (Free and Open Source Software), and therefore really do like the Gimp project. But, the advice here doesn’t seem to me to be how to make websites in ways that make you happy, it’s how to do commercially viable web development. And in that case, unfortunately perhaps, I believe you have to use industry standards. Like it or not Photoshop is the industry standard for graphic design, be it for a photo project, a web page, or any of the multitude of other computer based design projects it’s suitable for.
I’m not saying that you can’t use Gimp for your own projects or quick and dirty ones. It’s a good idea to have skills in multiple programs. But what happens if a customer has existing PSD originals, or 6 months later decides they want to buy the originals from you. Yes Gimp can import and export PSD’s but it’s not a flawless conversion and it most certainly doesn’t have the version compatibility that an original Adobe file would have. I love Gimp but if your trying to be taken seriously as a designer you need to at least have access to and be comfortable with Photoshop.
Also to whoever wouldn’t test their site on IE I wish you would rethink calling yourself a web designer. The whole idea of the internet is access. Sometimes paid, usually free, access. If you are going to cut someone off from your site solely because they haven’t upgraded to a browser that you are pleased with (often times purely out of lack of information on the end user’s part) then you are ruining that idea. If you are really that spiteful of IE then punish the software not the mis-informed user and redirect everyone using an offending browser to a page that says you browser is not supported, I suggest these browsers instead, if you choose not to change browsers go ahead knowing that this site many not look as it was designed.
14. Stop integrating CSS hacks. Build separate CSS pages for the browsers and use conditional loading. This is much easier for testing and subsequent maintenance. And it’s better organized. All your IE6 styles in one place. Delete when ready.
All the designers I know use photoshop - use fireworks if you want to create a bad looking site
It’s very good post. You have given very good tips to all infect it is very useful for newbie. Its good thanks for sharing.
11) Use a decent checklist
http://www.digitalgarde.com/strategy/blog-design-secret-tip-1/
Great article. Like you I learnt the hard way! I would also add the Dust-Me-Selectors to the list. https://addons.mozilla.org/en-US/firefox/addon/5392
There are some who use corel. But i think photoshop has a better quality of output.
Great list. I’m considering charging for IE6 support on my next project. It’s still kind of a sketchy subject though.
For those comparing GIMP with PS, it’s no comparison. Yes, GIMP is by far the best free graphics tool out there, I have it on my laptop and use it soley on my laptop, but Photoshop far exceeds the abilities of GIMP. If you were a “real” graphic or web designer and charged “real” prices, you’d be able to afford the small price for PS.
I poop on your list.
How do these help, really?
And why Doesn’t google or yahoo or msn or anybody listen to your list?
[...] Idea that I have heard bouncing around the web for a while now. I read a very insightful article on hacification which strengthened the argument [...]
If you are using a CMS behind your website, will you still face some issues?
Thank you for putting all these great ideas in one place. I an intermediate level developer who has run across most of these issues. I love the idea of charging for IE6, but wonder if that would be the edge that got someone else the job because they did it for free. Maybe once IE goes a bit further, IE6 will be a bad memory from the past.And also….hooray for the Creative Suite 4! Go Adobe.
Great site! Cathy
I would also like to add broken link checker http://validator.w3.org/checklink and http://www.dead-links.com/
Great list. I would say from experience that typically getting something to work in IE6 can be 50% of the design time. I can spend 4 hours on the design and another 4 hours to make it look perfect in IE6, depending on the complexity of the project. Good idea to make the client pay for it
What goes for JS also goes for the server-side.
Learn and use a framework rather than re-inventing the wheel for common tasks like database connections, sending emails accessing webservices etc..
There are numerous and they are usually free, e.g.
Zend Framework
Symphony
CakePHP
CodeIgniter
Ruby on Rails
[...] Ten Web Development Tips I Wish I’d Known Two Years Ago [...]
A tip for those who have issues with Photoshop’s cost: take a course in anything at your local community college. You now qualify for academic pricing. I just bought CS4 Creative Suite Design Premium for $350.
As Zog says above, I’m surprised you didn’t mention the first step: Learn a framework like rubyonrails or django.
There really is no other way to develop for the web. You learn a skill and are able to grasp the rest of the 10 tips you offer, more easily.
http://GoingManual.com has a lot of beginner advice for the Gimp. It’s for photographers but should help anyone get started.
Great post, totally agree, thanks!
@stealth
According to your argument about access, no website should use any JavaScript-dependent content, Flash, sounds, etc, etc, etc, because there will be some users out there who, because of out-of-date software, higher security standards, or any of a number of other reasons, will not have access to your site. It’s a nice idea in theory (I would LOVE to see Flash-based sites disappear altogether), it is not practical for commercial web-design. I agree that sites should be cross-browser compatible, but I also think browsers (well, one in particular) need to shoulder more of the responsibility of supporting the standards. I mean, AJAX as ActiveX? …honestly…
Great tips! Comment on #4 - I’ve been working with jQuery for a few months now, and it’s freakin’ amazing what you can do so easily and with so little code!
Good article, and definitely ten items I wish I adopted years ago. The one addition I would make to your #2 (Use a Browser Development Plug-In) is that DebugBar (http://www.debugbar.com/) is a great alternative (or additional tool, in my case) to IE Developer Toolbar
I hear that Mozilla is going to start developing plugins for IE to make it standards compliant since MS refuses to. Gimp gets the job done..are you making graphics or a website? I think people should focus more on what the site does vs. how it looks. Look at some of the most successful sites out there and tell me how much is put into “graphics” e.g. Google, Facebook, etc…
Thanks for a lovely site, I am very impressed
Boy, this is some high-class site
facundo! If you think photoshop is only for photography you have no idea what you’re talking about. It is THE indispensable program for anyone in any field of design ever.
Good article, but I have to disagree with #10
As a professional web developer you can’t disregard a browser that is still used by 25-30% of people, let alone charge extra for the privilege of having a website that will work in it.
The client shouldn’t have to care what browser their potential customers are viewing the site in - if the client loses potential customers because they can’t see the website, I would say the developer simply hasn’t done their job.
If anything I would give a discount if I couldn’t build a website that wasn’t supported by IE6.
*was* supported even!
Things you’ll wish you’d known/done two years from now.
1) Ended support for buggy crap browsers (aka IE6) sooner.
Why would you have wished to know these stuff 10 years ago? Then you’d have to wait for years to actually use these in practice, in most cases at least.
Good stuff there mate, not sure about charging extra for the old browser support, I mean I do agree that it is more work but whatever you create needs to be backward compatible to an extent. It also needs to be approached from the right angle otherwise the client might think you’re taking them for a bit of a ride and im sure there will be some other design company that will laugh at the comment and speak badly about you for even mentioning it as you’re client will not explain the true ins and outs to it in to defend your corner.
Maybe the approach that the ‘new technology used in your new site might confict with a few issues on older machines and internet broswers’ and we could ‘therefore do some extra work to take this into consideration’. Truthful but explained in a way they dont think you are taking them for a ride.
Diego
http://www.corporatewebsolutions.net
http://www.thatplaceigo.com
Fireworks is built for webdesign, Photoshop is for pretty pictures.
I use photoshop at home for many things, but you guys should check this out…
Photoshop away from home web based, you can save a file, and it’s free. I feel like I am sponsored or something by these guys. No, not really I just read all sorts of these forums all the time and never contribute… So let me know what you think; guarantee whoever looks at this will use it in a bind at some time in the near future.
http://www.sumo.fi/products/sumopaint/index.php?id=0
This site is good too… http://old-versions.net
Anyway i appreciated the article; #1 is a winner for sure.
Ten Web Development Tips I Wish I’d Known Two Years Ago…
Ten Web Development Tips I Wish I’d Known Two Years Ago…
found your site on del.icio.us today and really liked it.. i bookmarked it and will be back to check it out some more later ..
Simple. Clear. Useful
I’ll get back here to read your blog.
Thanks !
Brilliant post, thanks for the firebug heads up!!
5. Learn Photoshop - Yes! lol. I’ve had to learn this same lesson some years ago - but I’m glad I picked it up and ran with it.
You are right about Photoshop. I have been a Fireworks fan for years - so it is hard to admit - but for beautiful graphics there is no competition.
Try cutting a bear out of a complex background in Fireworks…
You are voted!
Track back from http://www.webdevvote.com/Tips_And_Tricks/Ten_Web_Development_Tips_I_Wish_I_d_Known_Two_Years_Ago
Ten Web Development Tips I Wish I’d Known Two Years Ago…
If you already know these things, you’re well ahead of the curve. Otherwise, you’re wasting a ton of your development time….
Thanks for the quick list.
I agree with all the mentioned things and on the IE esp. IE 6 I believe that we should drop our support for it now.
enjoy
Hi Stu. Like the site - very impressive.
Got to agree with most of the opinions here, except that AJAX, SEO and accessibility are not mutually exclusive. You can create a standards-based site that’s fine in all browsers and use progressive enhancement techniques such as Hijax.
Whilst I cannot stand IE6, dropping support for 30% of users is not a good idea. In fact, some sites have a far higher percentage of IE6 users.
IE6 is a pain, but with a little experience, you can get around any of the complications it throws up. In fact, most sites will work in IE5 and IE5.5 with a little effort. If you develop in Firefox and regularly test in IE6, then you’ll solve 95% of browser issues.
I’m not sure about charging extra for IE6, when you - as a web development expert - should factor it in from day 1. Few clients even know what browser they’re using and they’re hiring you for your technical ability.
Glad to hear that you’ve rediscovered JavaScript. It’s very powerful and completely underestimated by most developers. Finally, jQuery is great, but I’d recommend trying out your own Ajax and DOM manipulation routines - it’ll teach you a lot and certainly help when you have problems with the library.
Forgot to mention - I agree that CSS hacks should be avoided, but conditional stylesheets are also a nightmare and can encourage sloppy coding. Ultimately, you can end up with CSS files for every browser and need to introduce further ones every time there’s a new release.
I’m yet to come across a design that can not be coded using standard CSS. That said, you do need to know a few IE6 tricks (like ensuring hasLayout is set), but they’re not hacks and you create a far simpler stylesheet that’s easier to maintain.
so true!
great list.
[...] each of which contains ten Web development tips. The first is at hackification, and is called Ten Web Development Tips I Wish I’d Known Two Years Ago. This seems to be a generally good blog, with lots of stuff worth reading. In this particular [...]
It was really really very informative article. and have a depth knowledge.
Very very Thanx
afraz.shahid@gmail.com
Nice list! It’s always good to see how people learn from their mistakes and are willing to pass that on.
NATURALLY people are going to disagree with points. Even whether or not to use Photoshop! That depends if you’re working or not. If you don’t care if other people can open your layered images, then yes, use GIMP. If you want to be professional, use PS. The price tag is just a detail.
My only gripe would be concerning coding before designing. There’s no way on God’s green earth that I’m touching my computer before I know what the thing is going to look like! People really do shop with their eyes first, so if you have a site that has great content but bad design, they won’t read it.
Of course, I’m biased since I’m more designer than programmer! But that’s my 2c worth. I definitely see your point and it’s well taken. (To be honest, I design with CSS in mind anyhow!)
to facundo: things you can do with photoshop:
… yes it’s the best for photos…
web design
3d illustration
2d illustration
animation
graphic design
textil design
architecture
industrial design
publicity
fun…
etc.
I am sure I missed it in the comments someplace but any links that are ajax that should be SEO’ed should work without the ajax …
link
or
link
This is the same with image navigation. Good idea to do something like
link
.imageLink span{
display: none;
}
This article deserves a big “wow” as it explains some basic web development ideas so beautifully that I would say, priceless !!!
Use Gimp (for raster graphics) and Inkscape (for vector based grapcics) instead of Photoshop. They can do the same job, and costs nothing. FOSS powa!
If you properly structure your web site, being afraid of IE is not needed.
If you build your pages the correct way, you will be able to test everything step by step, and adapt accordingly.
Even reset style sheets are unneeded in this case.
Especially blocking IE or something is BAD.
If you really don’t want IE users to see your page in full glory, just don’t apply to style sheet for IE users. Your web page should look basic, but still well-structured. If it does not, you probably have done something wrong at the very start. Another idea is just to use a basic style sheet for browsers that do not support CSS2 in a proper way.
And my last point: do NOT charge for something that is not optional.
As a website builder, you are the one with the knowledge about websites.
Other people tend to trust you in some things, without knowing the consequences.
Browser support is _always_ mandatory for public web sites.
You do not want your customers to miss any visitors because you were too lazy to get your web site to work in their browser.
And imagine your client trying to open your website at home and finding a large error message, or a garbled website. A basic version of the website however, with a small notice that it looks better on newer browsers, should be fine.
Web Tools Tips and Talk…
Today, I am going to post a little weekly wrap up of links, tidbits, and other sites that came across my plate. Anything that I found useful, and aids web development and/or team management. This will not be a huge list of links, it will be tools I a…
Criag said “If you develop in Firefox and regularly test in IE6, then you’ll solve 95% of browser issues” … Worked and still works for me absolutely! And I came across this serendipitously as I run the lastest FF and never bothered to upgrade to IE7
Recently re-discovered javascript too! Does nice things for me, eg web ad split testing, etc…
Keep up the great work!
.S.
A great article! I feel motivated! You’re right on about the IE testing. I’m amazed at how many people are still using IE 6.
One to add — “Learn the difference between GET and POST.” Otherwise you will shoot yourself in the foot.
The theoretical difference does NOT concern the amount of data you can send, nor is POST a deterrent to a determined hacker, although both can be practical concern. Here is a good explanation: http://www.cs.tut.fi/~jkorpela/forms/methods.html
A nice collection of tips.
Let me get this straight - just two years ago, you didn’t think you’d need Javascript, and you’re just now realizing that you do? No wonder you’re so out of the loop that you praise Photoslop like it invented graphics editing (it didn’t, it ripped it off). Go Gimp!
I really like the ie6 charge idea. it makes sense: extra pay for extra work for a backwards browser. let the client decide. i might just bring that up to my boss.
IE, as we all know, has a long history of “my or the high” attitude. A some people rail against it, especially IE6. And some people are talking about not coding for IE6 or 7 or IE at all. this is plain stupid for this reason alone. Businesses, large and small are microsoft domains. And a lot of them are running Windows Professional 2003 or server 2003 or whatever it is. IE7 and IE8 will not run on these operating systems. Do you have any idea how much it would cost a business with 500 pc’s to upgrade to XP or WinX? It isn’t going to happen, or even soon. IE6 is going to be around for a long time. Don’t throw away those page hacks just yet.
Also, as far as Photoshop is concerned, if you want to have a job in this field, Production level Photoshop skills are a must. I’ve been paying for PS since PS4. And I’m not a PS wizard. And while it has a place in a photographer’s tool kit, it probably isn’t the first thing that is used by a photographer. Gimp is a good program, great considering it is free. but, if you are serious about making or manipulating images, Photoshop is the only way to go.
My Tip would be learn the basics first. When I was starting out I wanted to learn Ajax, PHP, Rails ect. But what I didn’t think about was the fact I needed HTML for the foundation. So, If you don’t understand HTML well, you can’t build the other stuff.
[...] [upmod] [downmod] Ten Web Development Tips I Wish I’d Known Two Years Ago (www.hackification.com) 1 points posted 5 months, 3 weeks ago by SixSixSix tags imported [...]
Nice list!
I don’t know where you all get this “30% of people still use IE6″ nonsense from.
Here: http://www.w3schools.com/browsers/browsers_stats.asp
Currently only 15.4% and dropping fast. At what point do we decide to stop developing IE6 support? At this rate it will be well below 10% by the end of the year and falling. I don’t think we’re quite there yet, but I’m seriously thinking about stopping IE6 support by the end of the year.
Learn SQL? I couldn’t live with out it!
HTTPWatch