Web Analytics: Ten Ways to shorten web page development time

Intermediary transaction SEO diagnosis Taobao guest Cloud host technology Hall

In today's development environment, fast is good.

Original: http://sixrevisions.com/web-development/10-ways-to-cut-down-web-development-time/

In today's development environment, fast is good.

Popular words and terminology such as "rapid application Development", "Agile Software Development" and "Asynchronous JavaScript and XML" (now we can't even wait patiently for a Web page to reload) give you an insight into what a fast-paced world it is.

But being in a hurry doesn't mean you have to work overtime-you need to be a bit of a brain at work. This article will provide you with ten time-saving tips for shortening Web application development.

I. Use of the framework

The framework extracts regular code and provides a basic structure and foundation for you to write Web applications.

A very typical example of a framework is that Rails,rails is a Web application development framework for the Ruby programming language. By providing you with a prepared code package (for example, like user input validation-you're not just saving time to write your own code in Ruby--you're also aware that these packages have withstood the testing and testing of other developers, which can cut you a lot of trouble when it comes to breadth testing, You can also avoid potential vulnerabilities caused by a lack of testing.

The same benefits apply to JavaScript frameworks such as MooTools. These frameworks provide you with a number of classes of methods that are provided by core developers and communities and are tested by extensive testing in many browsers. Client script language Framework also has Jquery,prototype JS, as well as Yui. If you want to use some Non-mainstream JS framework, you can look at this very potential JavaScript framework list.

For server-side frameworks, you can consider cake, CodeIgniter, Zend, or Symphony. If you like VB and C # Microsoft supported languages, you can consider. NET Framework.

You can even use CSS frameworks like 960Grid or blueprint to quickly write and standardize your own style of page structure.

Second, the use of integrated development environment

Of course, you can create Web applications and their pages using only a text editor like Notepad and FTP. But I think most people think this is not a sensible way to develop complex and robust web projects.

The integrated development Environment (IDE) prepares you for the collection of tools you need to create and manage large web site projects. The functionality of the integrated development environment has been changing, but they all have the following common features

Project management and team collaboration capabilities.

Debugging and Diagnostics.

Syntax hints and autocomplete (the IDE guesses the syntax you want to write)

Syntax highlighting

Built-in FTP to synchronize files on local and remote hosts

The word "IDE" may be a bit fancy, and some people are not familiar with it, but large data people should have heard of Adobe's Dreamweaver. Dreameweaver can be viewed as an integrated development environment. Because it contains some of the features mentioned above to help you write code faster. (He is usually suitable for front-end production.) But it also supports server-side languages like PHP and ASP.net.

Now that you have a lot of Ides on the Web, all you have to do is pick one for yourself (or your team). Like some popular, full-featured Ides such as Eclipse, Komodo IDE, NetBeans, Visual Studio, and Aptana Studio.

If, as you see here, you're still determined to use a text editor, you should at least look at the text editor collection for code workers.

Iii. appropriate modularity

Modularity is the key to creating a complex application that is easy to maintain and extend. In essence, this means that the code is written in small parts, rather than writing all the code in a large file.

Modularity starts with its own time cost (because you have to spend a lot of effort in designing the file structure). However, when you need to change a part or want to expand your application, this will save you a lot of time.

Modularity also allows bugs to be confined to the module, and if there is a problem, you will quickly find the problem.

But the misuse of modularity can lead to bloated code and too many unnecessary include statements, which can greatly slow down the entire application. So between the high and low modularity, we need a good balance.

Some modular design patterns include MVC and PAC patterns.

Iv. using browser tools to efficiently troubleshoot front-end problems

There is nothing worse than dealing with Cross-browser compatibility and parsing problems. This pole thing is going to make you mad, and it gives you a sense of frustration that almost makes you feel like you can't drop something. But the debugging tools that integrate into the browser make it fast and efficient to find and diagnose front-end problems.

Firebug and web Developer are absolutely necessary time-saving tools, and they have become a prerequisite for front-end Web developers. Firbug can easily view the DOM to understand its rationale, and can adjust css/html/js in the run, and in addition to debugging and commenting (profile) your javascrpt code, help you get at the beginning what is the situation that caused your script to run interrupted. Web Developer provides you with a series of useful tools, such as tools that let you click on a page element to see which style statements affect the element, or you can easily disable JavaScript and CSS, Lets you know how your page works without javascript or CSS.

If you need to debug in IE browser, you can try IE Developer toolbar. It is functionally similar to Firebug and web Developer. If you want to find more integration in the browser in the IE debugging tools to help you I save debugging time, you can click on this link.

V. Code REUSE

If you find yourself always doing repetitive things, you should rethink your code structure. Consider learning common design patterns that will help you create reusable, flexible methods, functions, and objects.

For example, if you need to link to a database frequently, you may need to create a database access class to handle database links, queries, and data submissions.

VI. Online collaboration and tracking project status

Actually--you're not alone in your work. Whether you work for a development team or work for someone (this person may be your boss or your client), you should fully enjoy the benefits of online collaboration and tracking project status.

The less time you spend on administrative tasks, or the less time you spend on endless meetings (or, worse, the kind of face-to-face meetings that require travel)-the more time you spend on your code.

Tools like Basecamp, Lighthouse, and Activecollab provide you with a one-stop team collaboration that allows you to keep track of the status of your project, and you can set goals and milestones (milestones)-so that everyone can sync automatically, Save time for frequent emails, and you don't have to spend a lot of time on a schedule confirmation meeting.

These tools will also help you distinguish between things and ensure that everything is organized and documented in a centralized place.

Vii. Automatic formatting and standardization of code

You need to standardize all your code formats, which is not only a good habit, but it will help you understand the code quickly when you need to come back and look at the code later.

The automatic formatting of your code allows you to format all your code in one key, rather than doing it on a line, which also ensures consistency in code writing. Automatic formatting also reduces the risk of manual modifications producing errors,

We have a lot of tools to help us do this, many of which are web-version tools. A popular open source solution for CSS is Csstidy (the online version of the clean CSS is Csstidy). We have HTML Tidy for HTML.

For scripting, we have PHP Source code Formatter, Ruby script beautifier, and Code beautifier Plus (This tool is used to format C #, ActionScript, and Java).

Viii. spend more time in the demand collection and planning phase

Prevention is far better than remedy. Perhaps some thought-school figures emphasize not wasting time on planning-making sure you've collected all the information you need to know, and it's still necessary to spend the necessary time doing your homework. Failure to do homework in demand collection can lead to a function overrun (feature creep) because of unexpected functional requirements

Nine, use already prepared code

The ancients and help us invent the chegulu, so we do not need to chegulu. If you see an interesting feature somewhere, someone else is probably already writing code for you (well, not just for you, but for all of us.) For PHP, PHP Classes repository provides you with a large number of classes and scripts to download and use. Hot scripts provides a variety of scripts for other languages. If you just want some small code snippet, you can go to Devsnippets to Amoy Taobao.

Note: If you have enough experience to distinguish between good code and bad code, the above approach will really help you. Otherwise you'll find that your final product is riddled with bugs and confusing writing.

X. Streamlining functions

You must evaluate some of the features of the Web application to determine whether the time spent on this feature is worthwhile.

Does your user really need a content management system that is not often updated to provide a custom RSS output for each category of articles? You really need a website style converter to help you detect where the user is located and then present the site in a different style.

Writing a Web site is a tough fight, not wasting development time on useless functionality for end users, which can complicate the user interface.

Original link: http://21haolou.com/articles/show/150