Things you should know for Efficient web Development

Hi! there. Today we will discuss a little bit about some concern points that a web developer should know to make an acceptable web page. There is no thumb rule created for this. Then how this topic or concerns come?!. well, you can say these topics come from research/ survey/ experience. Three of these options lie in the same line. Remember, these are not rules rather these are just suggestions.

Of course, you need to know how to write code.HTML, CSS, and JavaScript knowledge is a must for the web developer. you should have good knowledge about some common Libraries and frameworks.

You need to keep your code clean and easily readable. Like using spaces in a proper way, keep the code simple, using indentation, etc.

Developers follow some general rules to keep the code cleaner.

• space between parameters.
• space for operators.
• keeping spaces (generally 2) between functions.
• keeping lines not too long.
• space before the opening bracket.

Again these are not must-following rules. This is just preferences. you can read more about coding style from the link given below.

Coding Style

you need to go through some steps to make a successful site.

1 …………………… 2 ……………… 3……………….4

Planning>code Development>testing>bug fixing+Iterarion

In the planning stage, you need to fix the idea of your site. Like features and theme. Then the technologies you will likely build these features with, should have a clear idea about your target audience and what kind of browser your targeted audience will likely to be used.

Then move to the next step Code Development. You should divide your work scope. split the different site areas up like home page, product page, shopping cart, Admin page, payment workflow, etc. Subdivision can be made likewise. now you need to develop the code step by step. While developing code you need to be concern about cross-browser testing. Now, what is cross-browser testing? Cross-browser testing is the practice of making sure that the websites and web apps you create work across an acceptable number of web browsers. an acceptable number of web browsers” doesn’t mean 100% of the browsers in the world — this is just impossible. You can make some informed calls as to what browsers and devices your users will be using (as we mention in step 1). You can read more about cross-browser testing from the link below.

Cross Browser Testing: Definition, Why it is Important, How to do it | BrowserStack

Now comes steps 3 and 4 simultaneously. After each implementation phase, you will need to test the new functionality. make sure you leave no general bug issues for every functionality.

1. Test your site in a different browser like chrome, opera, firefox, IE/Edge, Safari, etc.
2. Do some lo-fi accessibility testing, such as trying to use your site with only the keyboard, or using your site via a screen reader to see if it is navigable.
3. Test on a mobile platform, such as Android or iOS.

At this point, fix any problems you find with your new code.to make it budget-friendly you can take help from your family, friends, or working groups. but if you can manage some budget you can do these testings with the help of third-party tools. as I mentioned before steps 3 and 4 needs to be done simultaneously to make a fully functional acceptable code.

Another important topic is balancing client and server caching. Now, what is caching? Cache is a type of memory that is used to increase the speed of data access. Caching means storing or copying data temporally or locally so that it can be provided to the user more quickly. you can avoid a lot of extra data generation, optimize the request workflow, reduce time to delivery, and remove congestion on your API input/output path. Caching helps you to improve efficiency also, it can minimize your API Data cost.

Client caching helps to limit the data cost by saving commonly used data in local storage/session storage. Every time user requests for this common data will be sent from saved storage before going for the further API call. that will minimize a little bit of cost from the client-side. From the API point of view, the client makes a request to the API. The client first looks locally for the relevant data. If this data isn’t found, the request is then sent to the external resource, and the content is generated for the requesting client. The benefit here is that the network for the client does not face heavy traffic

The caching process from server-side will be like this-

The client makes a request to the API>request received by the server>server will check for a local copy(cost is minimal for this checking)>

1. If the local resource exists then response will be sent to URI.
2. If the local resource doesn`t exist then the process will be as normal API call response.

This doesn’t really save much cost for the client. But if you balance client and server caching that may help and minimize some cost with efficient loading.

Then the balanced scenario can be like this-

A client makes a request>It first checks for a local copy>If the copy doesn’t exist, it contacts the server with a request for this content>On the server-side, the server will then check for its own local copy>

1. If a copy exists, it will serve it
2. Otherwise, it will generate a new one

Last but not the least, commenting. comments can be single-line: starting with // and multiline: /* ... */.Comments that explain the solution are very important. They help to continue development the right way.If the code has anything subtle and counter-intuitive, it’s definitely worth commenting.

Read more about commenting from the link-

Comments

Concluding here. but again these are not any hard and fast rules. you can find your own rules complying with the basic rules. If you find any mistakes in my writings please let me know. I really appreciate every single comment from you.