Welcome to www.taxkingsandqueens.com

Do and Don’ts of the Interview Process No one likes job interviews. From the moment you schedule the interview you are under a microscope. Your potential employers waiting for you to make the move that make you stand out or eliminates you from being a candidate for the job. This necessary dance that just about everyone, has to go through can be mastered. Learn the key things to do to become a high-ranking candidate for a job. First of all, before you go to the interview be prepared. Having copies of your resume and pens are only half the battle. Where exactly is the office located? Do not leave the location or the interview site up to chance. The only way to know exactly where your interview is and how much travel time you should allow is to go there. Even if you are interviewing out of town, find out how long the drive is to the interview. Nothing disqualifies you, in most cases, faster than being late for your interview. Before you are sitting across from the interviewer, accumulate some knowledge about the company. Knowing about the position is not enough. Everyone that interviews will have read the advertisement for the position. You need to be armed with information about the company. Have they won any service awards? Are they ranked as one of the best companies in America to work for? Find out and impress the interviewer. Another way to impress the interviewer is to have intelligent, thoughtful questions to ask. Ask about productivity, benefits or training procedures. Show that you have done your homework and are truly extend about the position. Be attentive and bring the interviewer as much information as possible about yourself. If you have a portfolio or reference letters, be sure you take them to the interview. Also be prepared with complete work history and information as well as past residency information. Be ready to answer a few probing questions. Why do you want the job you have applied for? What makes this a good time for a job or career change? Have some intelligent answers for these questions. Interviews will know if you are nervous. No matter how badly you need the job, do not appear desperate. Show that you believe in yourself and are confident about your ability to do the job. Speak in terms of when you get the job opposed to it. While this is a bold move it is a way to reinforce the idea of you being chosen for the job. This is a trick for both you and the interviewer. No matter how true this may be, never tell the interviewer that you “really need a job”. If this is what you tell the interviewer they will think that you are willing to take any job. Also, never talk negatively about your current boss or co-workers. Give as objective view as possible if you are asked about your current job relationship. Inquire about the next interviewing steps. This will not only show the interviewer that you are interested in the position it will also give you some time to prepare if you are called for the next interviewing step. Be sure to keep a notebook in your car so you can jot down notes immediately after you leave the interview. This is the best way to keep track of important facts about the position. In a day or so, mail a thank you card to your interviewer. This could be the added interest they are waiting to see from you in order to eliminate the other candidates.

Web Hosting - Databases, What Are They and Do You Need One? 'Database' is one of the most commonly used terms that one encounters in web site design. Yet, what they really are and whether they're essential is often not clear to novices. A database is a collection of organized data, stored in files that have a specific structure. It's that organization and structure that allows for easy and rapid storage and retrieval. The need for a database generally only arises when you have a certain amount of information and that information needs to have some structure. If you have a half-dozen names and addresses to store, a database is usually overkill. If you have a blob of data with no relationships between any of the items in that blob, maintaining a database is usually more trouble than it's worth. Maintain a database? Yes, like other complex systems a database, to be effective, needs to be designed properly at the outset then kept 'tuned' for good performance. The alternative is to gradually allow the database to become more and more disorganized. That leads to difficulty in use, poor speed of retrieval and more frequent failures. With MySQL, Access or MS SQL Server, the three most common choices of database product for web sites today, setting up a database is relatively simple. Even those with limited technical skill can get one up and running just by following some simple instructions. But some thought should be given to how you want the information organized, and to maintaining the system during its lifetime. Suppose you have a set of names, addresses, email addresses, products purchased, date purchased and amount. If you have only a few dozen records it matters very little how these pieces are arranged and related. A database usually isn't even warranted in this scenario. Once you have several thousand or more records, it matters a lot. Speed, the ease of expanding the set of attributes (like adding, say, product category), and other issues come into play. Even those with little technical expertise, but a willingness to exert logical thought and invest some time, can build a very robust database. Think about how you would organize a set of data (called 'tables'). Should Name, Address, and Product be in the same table? Or should the personal information be stored in one table and any product information (product, price, ...) in another? Some experimentation may be needed to get it right, but the choices have an impact on how easy the tables are to maintain. It also affects the speed with which programs can fetch old data and store the new. Having a database also introduces new maintenance issues for the server administrator, since backups usually need to be done differently. Recovering a failed database is usually more complicated than simply re-copying files from yesterday. Ask your hosting company what tools and skills they have for dealing with any database system you consider. It's true that introducing a database creates more complexity and the need for additional thought and administrative effort. At a certain level, professional expertise will be needed. But clearly the advantages outweigh the costs in many cases. Companies large and small eventually use databases to store and organize data. At some point, you may be fortunate enough to be one of them.

Web Hosting - Redundancy and Failover Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad. Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily. Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams. A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'. A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path. Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy. That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place. And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later. One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem. Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine. The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience.