The internet first came into existence back in the early 90's. Back then, we used things like HTML for our custom web application development. Times are changing. Now we use things like digital prints and other valuable resources to aid us in our web-based application development and web application services.
We live in a different time period. We can now catch many of the mistakes we make early on. The mistakes that are made now are not so much happening on a larger scale. The mistakes we make now are happening on more of small scale. These mistakes we make now tend to happen during the process of web-based application development.
The only difference is that we still fail to see the mistakes we are still making. We may have cleaned up the mistakes when it comes to the bigger picture, but they still remain on the smaller scale. How can we improve upon the process when we do not know what we are doing wrong?
These mistakes are not being made by everyone all the time. This list is meant to be viewed as a guide to what can potentially happen when a web software developer is not paying attention.
Cloud Software Development: The Nine Mistakes That May Still Be Happening
1) Some people are still not validating their user input. It is something that everyone has to do. There is an old saying that dictates the importance of not trusting user input that comes from the server. You are going to be surprised at how many still do not take notice or listen to this advice.
The SQL Injection is still a common mistake with this process users make.
There are front-end and back-end rules that must be followed. It is going to be time-consuming and no one is denying this. The point is, it still needs to be done.
2) There is the proper authentication without proper authorization. You cannot have one without the other.
- Authentication: The person who is logging in is who they say they are. They have provided the proper security clearance and codes.
- Authorization: In lamens terms, it means the user has the right to do the action they are doing.
In other words, the user is the holder of the account and is the person responsible for the appropriate actions. Too many users are logging in that should not be logging in. Too many users have access to accounts and actions that are not supposed to. They go in and authorize actions and applications that are not supposed to be authorized.
Companies need to take more of stand on this. Only those with proper authority for certain web development applications should be there and do what they need to do. This is a mistake that far too many make.
3) There cannot be any missing SEO or wrong SEO. There are many SEO specialists who are misinformed. They all assume that they know enough about SEO and SEO practices. They assume they have a handle on what is happening. 9 times out of 10 this is untrue. Too many specialists are making mistakes.
More of than not, a misinformed SEO specialist will put out the wrong SEO content. They will put out the wrong links. They will use the wrong content. Then, the web developer wonders why their content and site is not ranking as high as the other sites. The reason is that they are trusting a "misinformed SEO specialist" to take care of everything.
Every SEO specialist needs to be more than "adequately trained" in their field. Those who are not what you call "highly-trained and experienced" should not be in the position of "SEO specialist".
Some actions are going to have to be put off until the end, but this may be necessary. It takes more than just meta tags, imaging, alt tags, keywords, and good content to make it in the field of SEO. Anyone who does not know the ins and outs should not be doing it.
4) Sending a message to a request handler is another mistake that is made too often.
Here is a "for instance".
You or Chad start an online store selling books. He assumes he is going to be selling maybe 100 books every day. Every time Chad gets an order he sends out a confirmation email. Some of you may have seen this happen when you place an order with either eBay or Amazon.
This may work in the beginning for you or Chad. What happens when the daily goal of 100 books begins to increase? What happens when you or Chad start getting over 1,000 orders every day for different books?
There may be SMTP connection timeouts. There may be times when you exceed the bandwidth. The response times start to go down in a big way. People are going to get very unhappy and frustrated with this.
You need to have some kind of external email notification service that sends out the notifications for you. This happens a lot for some sellers on eBay and Amazon. When their customer base and inventory begin to go into the 1,000's, they outsource the problem.
5) The bandwidth option is a common issue for many developers. This one goes along with what we were discussing in number 4. Some people do not take into account the amount of bandwidth they will need. Some overestimate their goals and some underestimate their goals. The real goal is to strike a balance.
Here is another "for instance".
You, as the developer, has a 1G bit connections. Someone is downloading 5 images at about 3MB. There is not going to be much of a problem here. When a user begins downloading images of 15MB using a 3G connection, there is going to be an issue. You are going to get complaints about this.
6) You are not developing for different screens. More people are using their tablets and mobile devices to look things up and save images. More developers need to take this into account. Not every user is going to be saving things on their PC. The bandwidth of a PC is not the same as a mobile phone. The connections are going to be different.
When the bandwidth is exceeded the pages do not load properly. Some sites have hundreds of images available to view, but you cannot see them. This is because the bandwidth has been exceeded.
The best way to approach this is to use the Bootstrap guide. You can click here to see some examples of what we are talking about. You will get more of a response when you do.
7) Sometimes when you use the cross-browser, you end up with an "incompatibility" issue. Here are some things you can do to resolve the issue.
- You do not need to test everything during the process. Every few days switch up your browser. Try a new one. It is a good way to notice issues and fix them right away.
- Some web developers get stuck in the "specific codes" of the browser. This is not effective. Try not to get too involved.
- You should be using a browser for any and all work. Some stats show evidence to support not using one. Try not to pay attention to this either.
8) Never assume anything. This is considered the "mother" of all mistakes. Never assume that your development can work on a portable device. You need to test it out first. You need to plan for some kind of "portability".
9) There is something called "RESTful patterns" in web application services. They are here to stay, so you may as well get over it. Thes "REST" services are for both internal and external use. The only reason one of these gets broken is that they do not adhere to the proper protocols they need to.
- a) You should always use proper verbiage when writing them.
- b) You should send out proper HTTP status codes.
These are the two ways to fix the issue. Some like to send out an "HTTP 200 OK" code. You should only be doing this when the system has not given an error code. What happens when an error does happen? Send out codes like 400,401, and 500 only.
Bottom Line: Plan for everything and do not assume anything. Click here for a detailed outline for the various codes all web developers need to know.