The thing about computer languages is that there is some weird heaviness on the actual work involved. People are scared of by codes and although they see the power, they just can't seem to get going because they have no idea where to start.

That is where training comes in. And of course, fun training. You need to be taken by hand and shown exactly what you need to do, where you need to do it, and when you need to take the right action.

The funny thing about CSS is that it allows you to create your website in the fraction of the time when you would do it using tables. It's hard to believe, but still after all these years of promotion for CSS people (and companies!) still heavily rely on tables for layout. They have no idea that they are simply wasting time on old techniques that will be useless in a matter of time.

So where do you need to pay attention on when you are looking for a CSS Guide?

1. The Teacher

The number one thing you need to be sure of is that your teacher knows where he or she is talking about. Why is he or she teaching about Cascading Stylesheet, because they need to from their boss? Because they think they can teach, no matter the subject?

Think of that, how many teachers are only "teaching" stuff, and never practice it their own? Ask yourself "why" are you teaching you me this. Are you the best in the field? Where did you get your knowledge from?

2. Teaching Style

So the teacher may be a great person, has all the required skills, has a passion for the subject and knows about everything of it. But can your teacher deliver? Does he or she KNOW how to explain things? How to take you by hand and show you step-by-step how things work?

Is it fun to follow along with the teacher? CSS is one of those topics that can become boring easily when it's only discussed in a technical way. Make sure you know what you can expect!

An even more important thing is cutting right to the case. You don't want to end up with all kind of knowledge that you will never use in practice. It simply isn't useful to learn every possible css style there is when you just get started. And this brings us to the third point you need to pay attention on when you are looking for a css guide.

3. Teaching / learning speed

Can you keep up with the course? Does your teacher decide the speed, or do you? Of course a great way to follow a course is one that allows you to define your own speed. Home study courses and guides are wonderful for that.

4. Delivery

How is your guide delivered? Are you somebody that likes to read, follow along with a training video or both? Decide what you like, training videos are great, because they allow you to follow along in a real life situation. This means hands on practice, which is exactly what you need if you want to become good in CSS.

5. Contents

Last but not least, content. What is discussed in the guide? What is marked as important? Do you get a total reference, or do you know you don't need that, that the real thing you need is a hands on course with day-to-day subjects? Decide what you want to know, just the basics, how to create full layouts, or just how to create a menu using 100% CSS.

It's up to you now, decide what you need, you know how important the 5 above points are, and where you need to pay attention on. And one last tip, make sure you get some preview videos or sample chapter before following any course, it can save you a lot of time and money at the same time.

Hilco van der Meer
CSS Expert

Don't be fooled by seeming simplicity. A lot of developers get comfortable with a certain way of designing a database for their web applications that they miss out on techniques they should rather employ to make things run faster and more efficiently. A lot of developers don't bear in mnd that the small site they are creating now might grow into something incredibly large and complex, and the database they designed has become bloated and doesn't scale well to meet the demands of the increased traffic.

This article hopes to provide web developers with a few techniques to help make their database and queries faster and more efficient.

1. Avoid Character Types

When you are designing a database, it is so easy to set all data types to the VARCHAR type as it can then contain any data you want; numbers or text. But character data is amongst the most inefficient data type you can get. If a field is only going to contain numbers, then make it one of the appropriate types (INT, DOUBLE, etc).

Also, wherever possible in your web development code, try to use numeric data types as opposed to characters. One of the most common things a script has to store are flags like whether someone answered yes or no to a question, etc. You could of course store it as 'Y' or 'N' but why not store it as 0 and 1?

The reason this makes a difference is when you have a database, for example, with over 500 000 entries, and are running a SELECT on that field, comparisons are processed a lot faster for numeric data types than character types. Also, if you need to return data to the calling script, numeric data is less memory intensive than character data. In addition, your web development language (PHP, ASP, etc) would also be able to process and perform functions on numeric data better than character data.

I am not trying to convince you never to use character data types. Sometimes it is a necessity, but if you can find ways to reduce the amount of character data processed by your SQL database, the better your server will cope.

2. Normalization

Normalizing a database is really quite a complex process. It is a process that describes a way to design a database structure to avoid repetition of data in your database and can lead to significant performance benefits if employed correctly. However, the entire process of normalisation is a bit beyond the scope of this article as it can fill books on its own, but any developer designing a database should seriously consider becoming knowledgable about normalisation and employing it in their own designs.

For a good tutorial on this process: http://www.keithjbrown.co.uk/vworks/mysql/mysql_p7.php

3. DateTime vs Timestamp fields

This actually relates to 1. a bit. The big difference to bear in mind here is that a field of type DATETIME is actually stored as a series of characters. A field of type TIMESTAMP is actually stored as an integer. So therefore, a more efficient way of storing dates is using the timestamp method. The timestamp has its drawbacks however. For one, you cannot store a date early than 1 January, 1970. Also, timestamps in your script will need recalculating to get to the character format. Because of this recalculation, it may not be better to store as timestamp. It really is a case of testing which format works better for your needs.

4. Use LIMIT where possible

In your queries, if you are doing a SELECT to a database and you only expect a certain number of results, using the LIMIT statement can speed your query up incredibly.

For example, if you have a table of users and you need to run a query to search for one users record, you can use a query like:

SELECT user_name FROM users WHERE user_id = 453;

This query is perfectly valid and will return the right result. But you also know there will only be ONE result. The query above will search the database, find what you want, but then still continue searching after that. It would run a lot faster if you could tell the query that once it has found what you are looking for to stop searching. LIMIT can do this, as this query shows:

SELECT user_name FROM users WHERE user_id = 453 LIMIT 1;

Imagine this scenario. You have a table called logins, that records every login from a user. It currently contains over 2 000 000 records, and you want to find the first time a user logged in. Now bear in mind that because this table inserts data over time, it is already sorted for by date. You could do the following query:

SELECT MIN(login_date) FROM logins WHERE user_id = 4876;

This will return the record you want, but SQL will now have to get all dates for that user, sort them and then return the lowest value to you. Our table is already date sorted simply because of the way it records data for us. So using LIMIT can be more effective:

SELECT login_date FROM logins WHERE user_id = 4876 LIMIT 1;

Because it is sorted, the first one will always be a users first login.

5. Avoid using LIKE

If you have tried to employ 1. above, then hopefully you will be in a scenario where you do not need to use LIKE all that much. LIKE is one of the most inefficient ways of searching a table. LIKE performs a text comparison search in a field and with no wildcards is as efficient as a direct comparison; i.e. WHERE name = 'Jane' is equivalent to WHERE name LIKE 'Jane'. It is when you start introducing the wildcard characters like '%' that things get really hairy.

If you do have to use LIKE, then at least try and make efficient use of the wildcards. These are '_' (underscore) and '%'. Let me explain all this with a real world example.

In a project I was involved in, we had a SQL database storing logs generated automatically from a mail server. Unfortunately, the mail server pretty much just dumped a very long string of text data into a field that contained the data we wanted. A script had to be written to find all logs that referred to a login by a user into the POP server. The only way we could do this was to search every record for a string in the msg field that had the text "User logged in" in it. The first query developed was something like this:

SELECT msg FROM logs WHERE msg LIKE '%User logged in%';

This query took on average of about 35 minutes to process. Obviously not an ideal situation. The way the LIKE worked here was that it had to parse through every single portion of each and every record in the msg field looking for text that matched "User logged in" anywhere in the text. We were able to determine eventually that the text "User logged in" occured at the end of that text in the msg field and so we altered the query:

SELECT msg FROM logs WHERE msg LIKE '%User logged in';

The '%' at the end was removed as we do not want to worry about text after because there is none. The query now only compares text to our string in the msg field at the end of the field and no longer parses through the entire piece of text stored in msg. The query now ran in under 2 minutes. (This was actually still too long, but how we optimised from there is a little beyond the scope of this article.)

Hopefully with all these elements put into practice on your next web development project, you can have a database that runs quickly, efficiently, uses as little resources as possible and wont grind to a halt when the load suddenly increases.

Whether you're a blogger or just have a personal web site, you need to know something very important: With just a little bit of effort you can be making money from your web presence. It always amazes me the number of blogs I see that aren't taking advantage of some simple tactics to bring their owner some additional cash. I'm not saying you'll make thousands of dollars a month (although some people do), but even making $10-$20 a month can be a rewarding feeling. This article will introduce you to two of the most common ways of generating additional income from your web site: Pay Per Click (PPC) and Web Affiliates.

Pay Per Click (PPC)

The idea behind PPC is that your site will display ads or links for other web sites. If a visitor to your site clicks on one of the links you will get paid. There are many different PPC options out there, but by far the most common one is Google Adsense. The best part about PPC is that signing up to be a "publishers" (i.e,. one that publishes the ads on a site) is FREE! That's right, you can sign up for a Google Adsense account in just a few minutes and it costs you nothing. Once you sign up you can quickly use the online tools to generate some script code that you add to your web page(s). That's it. Then when a visitor comes to your site they will see context-relevant ads and links being displayed. If one of them catches their interest and they click on it you make money. The amount of money you make per click can vary greatly depending on the content of your site and the link clicked. I've gotten has little as a penny for a click and as much as $3.76 for a click! The great part about PPC is that you really only have a little initial setup time and then you just sit back and wait for the clicks to generate you money.

If you are a blogger and use Wordpress there are several plug-ins available that will allow you to display Google Adsense ads on your blog.

Web Affiliates

The other money generation option I want to present is web affiliates. The world of web affiliates is huge. It seems that almost every business on the Internet offers an affiliate program. An affiliate program is when the business allows other people to market their products or services. If you send them a customer that buys something then the business will pay you a portion of the money or a fixed fee. Just like with PPC, the great part about affiliate programs is that there is no cost to you.

When it comes to web affiliate programs you have two basic paths you can take. You can search out companies that seem to fit with the theme of your site and see if they offer an affiliate program, or you can sign up for an account (for no cost) with a large affiliate marketing company like Commission Junction, Clickbank, Share-a-Sale, and so on. There are certainly some difference between the affiliate companies I listed, but the common feature is that they have already found a bunch of companies with affiliate programs and they provide an easy way to search for what you want.

Once you've found a few companies of interest and established an affiliate relationship with them, you can get links and banners from them. You take the links and/or banners and add them to your web site. If a visitor to your site clicks on one of the links or banners and ultimately purchases something from the company, the company will pay you. This is different than PPC, which pays you just when the person clicks the link. The upside of affiliates is that when you do make money it can be quite a bit more. I have some affiliate relationships that pay over $30 for each new customer that comes from my site. Not bad for just displaying a link or banner!

Conclusion

I hope you found this information helpful and understand enough to get started making some extra money. It really isn't that difficult and you might as well try to make a few dollars from something you're already doing.