Welcome to elreno.org

Preparing Questions to Ask in your Upcoming Job Interview When you get ready for a job interview, chances are you have spent a lot of time trying to guess the questions you will be asked and prepare your answers to them. How will you explain that gap in your work history? What will you say when they ask you why you left your last job? In the rush to make sure that you have all of your answers perfectly prepared and ready, don’t forget to prepare a few questions of your own to ask the person who is interviewing you. Asking questions is an important part of your interview. When you get asked the old “do you have any questions for us” one, it pays to actually be able to come back with a few questions instead of a, “no, I don’t think so.” Asking questions will show that you are engaged in the interview and have done some thinking about the position, plus, the questions you ask will help you elicit valuable information you need when you have to decide whether or not to actually take the job, should it be offered to you. The first thing you should want to find out is why the job is open in the first place. Is the job you are applying for a new position? That means you can expect to have a lot of transitional bumps along the way as you are integrated into the company. If the job is not new, and the person before you was fired, then you can expect things to be in a state of disarray when you take over and that you will have to spend a lot of time up front cleaning up spilled milk. If the job is open because the person who had it before you moved up in the company, then you will know that this is a job with a lot of future potential. Next, find out a little bit about the person who will actually be your boss if you get the job. Sometimes, this person will be involved in the interview, but often they will not. Finding out how high up in the company chain you will be reporting will help you gauge how important the position for which you are applying is to the company. Also, it helps to know a little bit about the personality type of the boss to be. If you like to keep your head down and do your work, and your potential new boss is one of those “wacky” types, then you may want to look elsewhere. From there, ask about the kinds of responsibilities you will need to take on board right out of the gate. When companies are hiring for a new position, they usually have a few ideas about what that person will need to start working on right away. Getting a clue about your first project will help you decide if this job is right for you. This is also a good time to ask the interviewer about their job and why they like working the company. You may find out that this really could be your dream job, or you may end up sensing from your interviewer that you should run away, fast. Last but not least, ask your interview when you should follow-up on your interview. Don’t open the door for a “don’t call us, we’ll call you” kind of interview closing. Let the interviewer know to their face that will be making the effort to contact them again. You may get the vibe from your interviewer that the job probably will be going to someone else, so you can move on quickly, or you may end up being offered the job on the spot. Either way, you will have opened the lines of communication to take the next step.

Web Hosting - DNS, How The Internet Keeps Track of Names The way computers communicate is, in a way, very similar to something very familiar: the postal system that delivers letters and packages. Here's how... The Internet is just what the name suggests, a large inter-connected set of networks. But those networks are pointless without the one part that forms what is called their 'end-nodes', otherwise known as computers. Those computers often need to share information because the people who use them want to share information. But, in a system where there are millions of separate computers, how can you enable them all to communicate? One very important feature of that solution is performed by something called DNS, the Domain Name System. Every part of a network that is going to send or receive information is assigned an IP address. That's a numeric identifier that uniquely specifies a particular 'node', such as a computer, a router that directs traffic or other component. They look like this: 209.131.36.158 But those numbers are more difficult for people to remember and work with. They also aren't very attractive from a marketing perspective. So, a naming system was layered on top of some of them, mostly the computers involved, though routers have names, too. But once you have a system that associates a unique IP address to a given name, you need some way of keeping track of all of them. That's carried out by several different pieces of the system: Name Registrars, DNS Servers and other components. The Name Registrars, overseen by IANA (Internet Assigned Numbers Authority) and other international bodies, provide and keep track of domain names. When you register with GoDaddy or any of a hundred other intermediate companies, ultimately that information makes its way into a number of specialized databases stored inside DNS Servers. A DNS Server is the hardware and/or software that tracks and forwards the IP Address/Domain Name pair from one place to the next. In many cases, there are a number of them between your browser and the remote computer you want to share information with. Suppose you request information from, say, Yahoo's site by clicking on a link on their site. DNS resolves (translates) the name of WHO IS making the request and OF WHOM, to addresses, then passes the request through the network to the requested IP address. The requested data is then passed back through the mesh of network components to your computer and displayed in your browser. Whether the communication is between a desktop computer and a server somewhere, or between one server and another, the process is essentially the same. DNS servers translate names into IP addresses and the requests for data are forwarded on. In some cases those DNS servers are part of a specialized network computer whose sole job is to do the translation and forwarding. In other cases the DNS software may reside on a server that also houses a database of general data, or stores email, or performs other functions. But however complicated the chain or the parts, the basic process is simple. Translate the name to an address, just as the postal system does. Whether international or local, your name is associated with an address, and the deliveries are made to the address, then forwarded to a particular name.

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.