Welcome to www.minisinbox.com

Helpful Hints on Getting Better Respect in the Workplace Sometimes, an inhospitable work atmosphere can ruin the best job in the world. If you work in an office where people don’t respect each other and you feel undervalued and taken advantage of, then you are likely to give up and move on--no matter how much you love the work. When people work closely together, disagreements and problems are bound to arise from time to time. There are, however, ways you can get more respect in the workplace, so you don’t have to dread heading to the office every morning. As the old adage goes, you have to give respect to get respect. Are you doing everything you can to treat your co-workers with dignity and respect? Put another way, are you doing everything you can to avoid annoying everyone in the office? There are a lots of little ways you can make the day more pleasant for everyone, including showing up on time for work and for in-house meetings, not talking too loudly on the phone, keeping your personal cell phone ringtone on silent or vibrate, and cleaning up when you use the common break rooms and kitchen area. Things like spamming everyone in the office with incessant “funny” emails, sending political or religious emails (or challenging everyone on political or religious issues), or invading privacy by looking at someone else’s emails, phone messages, or mail are also not a good idea in the office setting. Then there are the big ones – you should never take credit for someone else’s work, talk behind people’s backs, lie, steal from other’s desks (even if it is just a post-it note or white-out), or have a general bad argumentative attitude. If you are doing anything of these things, trying to correct your own behavior is the first step to earning a little more respect in the workplace. What happens if you are doing everything you can and you still aren’t getting the respect you feel you deserve in the office? How you handle things may partly depend on who is showing you the disrespect. Are your subordinates treating you like you’re not the boss? In this case, having a little one on one conversation might do the trick. It doesn’t have to confrontational. You can simply point out that you are getting the impression that they may be having a little trouble with your leadership style and offer them a chance to raise any problems. If they bring up a legitimate problem, then there is something you can work on to make things go smoother in the future. If they can’t point to any one thing, let them know politely, but firmly, what you will need from them going forward in terms of respect. And then, stick to it and hold them accountable for their behavior. If your boss is not respecting you, things can get a little trickier. If your boss has a bad attitude, being pulled up on it by his subordinates is probably not going to do much to improve it. Your company may have a grievance policy in place to deal with issues like this, and it is best to go down this path when dealing with a boss with a respect issue. There are some respect issues in the work place that can’t be resolved with the softly, softly approach. If you are being persecuted on the basis of your gender, your race, your disability, or your sexual preference, you have a right to demand a stop to that at once. If the abuse is coming from your co-workers, go straight to your boss. If your boss is unresponsive, or if your boss is the offender, go right over their head, and keep going until you get some satisfaction.

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.

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.