10 skills to make you a good web Developer

One thing I like most about web development is that it includes many different skills. As a good developer, be sure to study hard and make progress every day, because we have a lot of important skills to learn, and they always change constantly.

Here I've listed 10 of the most important skills, which are a bit inclined to front-end development, but are generally suitable for all developers:

Regular expressions

Basic SEO

Nice JavaScript library.

Cross-browser debugging

Image processing and optimization

Layout with valid HTML/CSS (table not applicable)

Copyright/Basic Network Regulations

Apache rewrite

Debugging software

Version control

1. Regular expressions

Regular expressions are often used for parsing strings. The most basic use is to find and replace the characters in the text. And that doesn't seem to be much of a problem, and the diversity of regular expressions is why it's really powerful. There are many ways to optimize your regular expression, which also means a significant increase in the performance of your application. Regular expressions apply to any programming language, such as the JavaScript replace (), PHP preg_replace (), Apache rewrites, and so on. It's weird. Only a handful of web developers think regular expressions are pretty useful, and if you're not learning, get ready to start learn regular expressions.

2. Basic Search Engine Optimization

For web developers, it is necessary to understand the basic information of search engine optimization. While you can reserve keywords that guide your client, developers should use a more reasonable strategy for arranging these keywords on the page. This means that, in collating the front end of the tag, make good use of TITLE, META, H1 and H2 tags, while at the back end of the organization of more stable links and directory structure. I found the best resource for learning SEO is Beginner's Guide to search Engine optimization and search Engine, ranking Factors, both from V2.

3. A good JavaScript library

Even if you don't write JavaScript code very well, mastering a good JavaScript library can be a big help. Whether it's jquery (My favorites), Mootools, or whatever library you have, you can make your JavaScript development work a little easier. First of all, these libraries offer cross-browser capabilities that allow you to get started without having to take care of things. Moreover, they all provide a lot of simple animations, such as selecting nodes in the DOM, which makes it easy to work. Bolder JavaScript programmers may want to touch the JavaScript UI language. Several of the above mentioned libraries have related plug-ins, but I personally recommend dojo with Dijit.

4. Cross-Browser debugging

In order for the site to be seen by more people, it is clear that it should support all major browsers (IE6, IE7, IE8, FF2, FF3, Safari 4 and Opera 9). Everyone is disgusted with Cross-browser debugging, but the best way to prevent it is to start with valid HTML and a good reset style sheet. As far as I am concerned, it is using the * {magin:0; padding:0}. But you can also use other, more robust ways. In addition, you should understand the quirks of some browsers. The most famous of course is the IE family, especially IE6 (yes, it always is, it is still). While most of the problems can be attributed to notorious haslayout bugs, you can't rely on some clumsy way to fix it, such as * {zoom:1}.

5. Picture Processing and optimization

Although most programmers rely on professional designers to design pictures, it is also important for programmers to know a little about Photoshop. Master some of the image processing technology, some small changes do not need to be kicked back to the designer, the direct change is, and, in the modification of the design, you will immediately know whether it is feasible. Picture optimization is one of the most important skills in Photoshop for Web programmers. Picture size is often the biggest threat to bandwidth, picture optimization directly related to the loading time of the site. Photoshop and Illustrator's "save for web" options greatly simplify the image optimization process by pressing the ctrl-alt-shift-s on the PC or pressing the command-alt-shift-on the Mac S can enter this wizard.

6. Use effective HTML/CSS for page layout (not tables)

We need to focus on: It's not 1996 years now, and the backend developers should know how to write the front-end code--using valid HTML and css--rather than a bunch of tables. tags should be neat, CSS and other types of documents should be separated from HTML, so there will be no inline styles, especially the font label. Beginners should learn CSS tags and css box models. Then learn the rules of the game and learn how to write reasonable code. The HTML you write should conform to the XHTML rules; You should have a reasonably nested, closed picture label that contains ALT attribute information, and so on. Then you can understand that the nodes can be nested in other nodes, and already other complex content. Finally, you will find that the HTML Tag Verifier of the consortium is no longer an error, which is really cool.

7. The basis of copyright/network regulations

While no law degree is required, developers are better able to have a basic understanding of copyright and Internet regulations. Because the web is essentially a publication, copyright is the most common legal issue on the site. From a user-generated steal flicker picture to a quote from a large section of the New York Times, you'd better understand if you don't want to be sued or receive a complaint letter. Of course, if you want to bring a lawsuit or send a letter of complaint, you'd better understand that. In addition to the copyright law, you should also take a good look at the privacy agreement and the COPPA (American children's Internet privacy law) when signing up for registration/use of hosting or software agreements.

8. Apache Rewrite

The Apache rewrite feature makes the original messy URLs neater (as long as you understand regular expressions). You can put an ugly address: Index.php?section=about&page=bioand rewrite bit prettier: About/bio. Not limited to structured URLs, using Apache mod_rewrite makes it easy to turn a simple page into a full application of the inclusion path. You only need to rewrite the query's variables to a path.

Again, you should note that Apache rewriting is also a bad name for debugging. An overriding rule cannot contain any debugging information and often ignores information about other methods that you refer to. Therefore, rewriting can also cause some untraceable errors.

9. Debugging Tools

A good debugger allows you to do web programming faster. When debugging on the front end, I like to use Firebug, you can click on the elements on the page, it will be statistical style sheet in the settings that are in effect. You can add or remove styles, and you can also modify the page. Firebug can also be used to debug Javascript. As a Javascript run console, it can better organize error messages, displaying the output of Fromconsole.log (). Finally, it provides network information, display page element loading events, and those that cannot be loaded and cannot be retrieved. I don't know how to debug back-end, but I've heard that PHP has something called XDebug.

10. Version control

Last but not least, a good programmer should learn to control your version. Versioning is not just a way to backup your work, it's also an important way to collaborate with other developers. I personally prefer distributed as opposed to centralized (distributed, relatively centralized) version control because it has two different levels of versioning: You can first commit your partial modifications to the local storage center, All changes are then pushed to the server-side storage. This allows you to make a small, volatile change locally, and then commit the update set in the team. If you are using Distributed version control I am more optimistic about Mercurial, and if it is centralized, subversion is good.