Every developer has a unique set of tools he or she uses to help develop web applications. The main tools anybody will use are browser extensions, although there are still plenty of tools in the clouds that can be used to help developers. Here are some of them:
Web Developer Toolbar
This is one of the most common extensions that almost every developer has. It has essential tools for checking and modifying the generated HTML, debugging scripts, and viewing detailed errors. There are plenty of tutorials to help you get familiar with this tool. Chrome has an existing alternative to Firebug that is already installed.
Modern browsers already have a spell check for things you write into input fields or text areas. I also find it useful to Spell Check full pages, such as pages I dynamically created. I simply visit all the pages on the site to check for bad links and/or layout errors, then click a button to make sure every thing is spelled correctly.
Simply click the button and download as many elements on the page you want. I’ve used this a few times to download documentation that was only available on the web. Doing this allows me to not rely on a website for documentation, since it could cease to exist, thus causing the documentation to no longer be available.
Typically a designer will tell you which fonts to use when slicing their PSD’s, however there are plenty of instances when you could be unsure about a font. The designer may not have used a web-safe font. This tool lets you see a few web-safe fonts and pick from the list, making it faster than waiting for your designer to get back to you.
This tool is more for telling you what you did wrong. There are a few items I disagree on, but I’ll spare you the drama. It does point out a lot of obvious items you could be improving.
I like to format my code as much as I can when going live with my applications, and CSS is no exception. Input your CSS into this tool, select a few options, and you will have compressed CSS code you can use for live sites.
This tool is one of two formatting tools that deal directly with decompression. It will take messy code and make it easier for you to read.
In lots of the applications we create, we make AJAX requests sending JSON back and forth. The downfall is JSON needs to be sent without formatting, which helps you read it a bit better and tells you if it’s valid or not. You can compress and format JSON with this single tool.
Often, you may output SQL that is dynamically generated so you can test it. This happens a lot when debugging older applications. The downfall is longer queries are more difficult to read unless formatted.
(Source: Skynet Solutions)
By Blaine Schmeisser