Welcome to crazydating.net

The Job Interview – How to Handle Getting Around a Negatively Asked Question Many dread that day that they have to go for an interview. Looking professionally dressed, acting professional and displaying the knowledge is all important. Employers and interviewers test you for anything and everything that you can think about--from your likes and dislikes to the actual experiences with this type of work to the facts. Most of these questions you can dodge and answer safely and securely. But how about those negatively asked questions, how could you professionally dodge those questions? Often times a reaction to a negative question is what can make or break the deal. Sometimes employers ask these questions on purpose to see what your reaction might be and to be able to determine first of all your character and second of all, if the negative event in your life is related to a good or bad character. So how can you master these questions and possibly pass the tests? One of the most important factors when getting prepared to dodge difficult questions is to be secure and knowledgeable about any points on your résumé and in your life. If you have a good answer prepared for difficult situations that happened in your life, it will be an ease for you to get around negatively asked questions. Whenever an interviewer asks you a negative question, make sure you stay calm and do not answer hastily. Sometimes it is enough to give a very short answer and it does not necessarily need a complete explanation that might get you stuck. The longer the answer you try to make up, the easier you might stumble over something and then fall hard. When trying to get around a negatively asked question, besides that fact that you need to stay calm and give a short answer, try to get to a different topic. Strike up a conversation about your more positive skills and accomplishments and therefore get around that question that might have bothered you otherwise. In some instances, depending on the content of the question, it might even be best to answer truthfully. What if you were asked about staying home for no obvious reason? At least according to your résumé there is no job, no new degree or similar mentioned. Maybe it was for a sick relative or the birth of a baby? Why not use the truth in these cases as an answer. When answering difficult questions you might have to decide often on the spot how to answer. In any case, it will almost never help you to make up a lie for a negatively asked question. A lie can get you into a situation you cannot get out of, but the truth can never get you in a worth situation than you are in by answering the questions truthfully. If you do not want to answer truthfully because you think it can hurt your image, sometimes it then is better not to answer the questions. Try to divert the attention successfully to another more positive topic such as your achievements, earlier project or similar other experiences that led to a positive result. Keep in mind that the interviewer is testing to see if you are a good fit for the company and they do not exactly know you. They know a few facts about you, but the do not know the whole picture and especially not about the more negative things they might want to find moiré information about. So when going for a an interview and trying to get around a negatively question, make sure to be honest or to not get into details if you do not want to discuss the issue, but mainly make sure that you stay calm, do not get excited about it. A calm confident person can easily answer any and all questions that might be posed to him or her.

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.

Web Hosting - FTP and Other File Transfer Tools Anything related to the Internet or computers is bound to introduce technical issues pretty soon. One of the earliest that novice web site owners encounter is FTP, which is an acronym for File Transfer Protocol. Seeing it spelled out, it's easy to see why those in the know quickly move to speaking in short hand. The reason web site owners soon will (or need to) become familiar with FTP is obvious to anyone who has built a site on a remote server. You have to have some way of getting the files to the remote computer and FTP is one of the most common tools. It's also one of the simplest and most efficient. FTP is composed of two parts: the client software and the server software. It's similar, in a way, to talking to someone on the phone who writes down everything you say. You (the client) make a request ('transfer this file to the server') and the listener (the server) takes the request and acts on it. That request to copy a file from a local computer to the remote one is carried out (often 'under the covers') by a PUT command, as in PUT this there. You create the web page (in the form of a file) and then PUT the file on the server. To move a file in the opposite direction, from the remote server to your local computer, your client software issues a GET command. Many FTP clients have graphical interfaces, similar to Windows Explorer, that allow you to drag-and-drop or otherwise copy the file without ever seeing the actual commands that carry it out. But it's helpful sometimes to know what goes on underneath. In tricky cases it can be an advantage to use a command line interface (in Windows, the 'DOS box', with a similar interface familiar to most Linux users). Knowing the commands and being able to use them in the command line form can sometimes help you diagnose what is going on when the graphical tools misbehave. But FTP is not the only way to get a file from here to there. In fact, your browser moves files around from a remote computer to your local one all the time. In most cases, when you type in or click on a URL, what happens under the covers is in essence a file transfer process. The web page is transferred from the web server to your local computer then displayed by the browser. Alternatively, you can sometimes even email a web page/file from your local computer to the remote server, then use an email client on the server itself to get the file and put it in a folder. That requires that you have some form of access to the remote computer. But there are many ways of doing that, such as in-built utilities in the operating system or using commercial remote control programs. Those alternatives can be helpful to know in cases where the FTP file transfer process is misbehaving. Having more than one way to accomplish the task helps you diagnose what might be going wrong. It also helps you get the job done when the usual tools aren't cooperating. The more you learn about these sometimes puzzling acronyms, the easier you can accomplish your own goals.