Welcome to makedonikajournal.org

Networking Know-How: How to Get Through to the Busiest of People When you are job hunting, sometimes the most frustrating part is just getting your foot through the door to let the right people know that you are out there and available for work. Companies can be like members-only clubs; they tend to be a little distrustful of cold callers and most executives advise their assistants to run interference for them on the phone so they do not get stuck having a protracted conversation with someone they just aren’t interested in doing business with. The thing is that to get an interview, these people can be the very same people you need to talk to. How do you get these busy people to clear some time off in their busy schedule to speak to you? First things first – you have to get the right attitude. If you want busy people to make time to talk to you, you have to present yourself in a way that makes them feel like you are worth the time investment. The trick here is that you have to do this by phone, and often, you have to first convince an operator or personal assistant that your call is one worth putting through to the boss. Your phone etiquette and vocal confidence will be the key here. Consider you basic phone manners first. Instead of launching right into what you want, respond to the greeting of the person who answers the phone with a hello of your own. Animate your voice and always remember that simply saying “please” and “thank you” can go a long way. Be the kind of caller that you would want to talk to if your job was answering the phone all day. People will respond to your positive attitude with a positive attitude of their own. Next, consider your confidence level on the phone. Do you tend to get tongue-tied and stumble over your words? That kind of delivery from you will set all the warning bells ringing on the other end of the phone, and you will find the person with whom you wish to speak always “out of the office.” Instead, work on sounding like you are confident that it is a forgone conclusion that you will get to speak that busy person you want to talk to. Be confident that what you have to say is something that is worth hearing. It may help to write out a framework of what you will say and practice a few times so you sound relaxed and composed when you make that call. Once your attitude is right to make the call, you can then employ a few tricks of the trade for getting through to those busy people. Instead of giving away too much up front, start your call by asking if the person with whom you need to speak is in. If the answer is yes, then you can remove on potential “excuse” for not putting your call through. If your call can’t be taken at that time, skip the message. Let the PA or operator know that you will call back again. That way you have a legitimate reason to keep calling. Of course, you might have to keep calling and calling, and that assistant might start knowing the sound of your voice. If you keep speaking to the same person, it’s time to open up with some person details. Let them know your name, why you’re calling, and if someone referred you, who that person is. Developing that personal relationship can help you get your call through to the boss. Last but not least, don’t give up. Busy people are, well, busy, and not necessarily avoiding your call. Persistence pays off, so keep on calling until you get through.

Web Hosting - Sharing A Server � Things To Think About You can often get a substantial discount off web hosting fees by sharing a server with other sites. Or, you may have multiple sites of your own on the same system. But, just as sharing a house can have benefits and drawbacks, so too with a server. The first consideration is availability. Shared servers get re-booted more often than stand alone systems. That can happen for multiple reasons. Another site's software may produce a problem or make a change that requires a re-boot. While that's less common on Unix-based systems than on Windows, it still happens. Be prepared for more scheduled and unplanned outages when you share a server. Load is the next, and more obvious, issue. A single pickup truck can only haul so much weight. If the truck is already half-loaded with someone else's rocks, it will not haul yours as easily. Most websites are fairly static. A reader hits a page, then spends some time skimming it before loading another. During that time, the server has capacity to satisfy other requests without affecting you. All the shared resources - CPU, memory, disks, network and other components - can easily handle multiple users (up to a point). But all servers have inherent capacity limitations. The component that processes software instructions (the CPU) can only do so much. Most large servers will have more than one (some as many as 16), but there are still limits to what they can do. The more requests they receive, the busier they are. At a certain point, your software request (such as accessing a website page) has to wait a bit. Memory on a server functions in a similar way. It's a shared resource on the server and there is only so much of it. As it gets used up, the system lets one process use some, then another, in turn. But sharing that resource causes delays. The more requests there are, the longer the delays. You may experience that as waiting for a page to appear in the browser or a file to download. Bottlenecks can appear in other places outside, but connected to, the server itself. Network components get shared among multiple users along with everything else. And, as with those others, the more requests there are (and the longer they tie them up) the longer the delays you notice. The only way to get an objective look at whether a server and the connected network have enough capacity is to measure and test. All systems are capable of reporting how much of what is being used. Most can compile that information into some form of statistical report. Reviewing that data allows for a rational assessment of how much capacity is being used and how much is still available. It also allows a knowledgeable person to make projections of how much more sharing is possible with what level of impact. Request that information and, if necessary, get help in interpreting it. Then you can make a cost-benefit decision based on fact.

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.