10 HTML Mistakes that Should be Avoided
Here is a list of common mistakes in HTML that should be avoided.
Tweet


Here is a list of common mistakes in HTML that should be avoided.
A design pattern that allows you to make sure there is only one instance of a class. This is uber-important for fast and efficient code. You no longer have to worry if you created an instance somewhere that wasn’t cleaned up afterward (i.e database connections). Big time stress relief. If you have never used a design pattern or don’t know what one is you can check out this previous article that can walk you through it.
Are you not sure how to structure your code? Have you come across a problem that makes life difficult. Odds are many developers have been in your situation before. Design patterns are the antacid of the development world…finally relief.
Accommodating changes is one of the most challenging aspects of good program design. The goal is to isolate unstable areas so that the effect of a change will be limited to one function, class, or package. That way if there is any changes needed it won’t effect surounding code.
Front end development uses 3 things, content(HTML), styles(CSS) and possibly enhancements(Javascript/Flash/Silverlight). So it would make sense to do develop in away that makes sure it doesn’t hinder the content if the browser doesn’t allow styles or enhancements. Which a lot of developers painstakingly do, but there is an easier way.
Abstraction, we use it in everyday life. It helps us quickly understand what other people are talking about. So why not use it for code and make it that much more readable.
Recycling code is by far the best way to make the most of your code. Recycling…it’s not just for the environment anymore. Making sure your code is prepped and ready for reuse and it will save you a lot of time. Read more…