Welcome to beszeljukmac.com
|
Ways to Quit your Job Yet Still Maintain Positive Ties
Just as there are ways to get jobs, there are also ways to leave jobs--especially one where you have cultivated relationships. Moving on to a new position does not mean that you have to leave on bad terms. Get the job you want without leaving your current job on bad terms.
Choosing to leave one job for another one is a decision that is often unavoidable. In order to progress in life, changing jobs may be necessary. Whether it is increased pay, more room for advancement or a better work environment, changing jobs is a natural part of life.
While some employees leave jobs because they are unhappy, other employees leave because they simply need or want a new job. These employees may have great working relationships with their employees and co-workers. They may even have good personal relationships with these people. Extenuating circumstances like friendships can make it difficult to move from one job to another. However, this necessary move can be made without destroying ties that are important to you.
Being professional and careful when leaving your job can make leaving much easier. First of all, do not tell anyone you are planning one leaving. No matter how close you are to your co-workers, keep your intentions quiet. Arrange interviews during times that do not conflict with your current job. You do not want to miss work for an interview. Remember your current employer is an excellent reference for you. Maintain your good reputation at your current job. Continue to do a good job and care about your particular position.
Using the company phones, e-mail or fax machine to contact your new potential employer is not appropriate. Use your own devices to contact the interviewer. Until you have the new job, things should be business as usual on your current job. Also, never give your notice at your current job until you are sure that you have the other job. Having to retract a two-week notice because you prematurely gave it is a sure way to cause friction.
Once your new job is secure and you have given your tow week notice, continue to be a good employee. Be on time for work and complete your projects. Remember, no matter what your new job is, you have obligations to your current job.
Write out your notice. Compose a nice letter thanking your boss and co-workers and provide two or more weeks notice. By giving a written and dated letter no one will be able to dispute the length of your notice. Also, you will be providing a professional and considerate notice.
Allow your co-workers and bosses to say goodbye to you. If they want to take you out for a drink on your last day, oblige them. Enjoy celebrating an end of an era. You may keep in contact afterwards but you probably won’t be working together again. Let them know that you realize this and that you leaving is not personal.
Sometimes, no matter what you do, some people are not going to be okay with you leaving a job. There will always be someone who thinks that you getting another job is not a good idea for you. This is especially true for co-workers or bosses who you have a relationship with. Some of that is probably coming for the fact that they will miss you being around the office. Others can be envious of your boldness. It takes a lot to leave a comfy work environment for a challenging job. There is no way to please everyone. In these cases, just remain positive and ignore any backlash you may face.
Web Hosting - Look Before You Leap Companies that offer Internet-connected servers that provide space and bandwidth for a domain, for one or more web sites, are called Web Hosts. Large companies have private networks that allow them to host domains on their own equipment and IP address range. But for the majority of those who want an Internet presence, a 'rented' web host is a necessity. There are a wide variety of hosting plans available. Some are free, others charge up to a $100 or more per month. Some provide nothing but a tiny amount of disk space and minimal network bandwidth. The web site owner is on his or her own for any thing else. Others offer a range of services, including server and email administration, backups, web site design assistance, troubleshooting and many others. In the world of web hosting, you may often find yourself sharing a server with anywhere from one to a thousand or more other web sites. That allows the web hosting company to keep equipment and staff expenses lower. Many web sites are simple and low-volume enough that the arrangement works fine. When you or one or more of the others grow, it may be helpful to consider a dedicated server. A dedicated server, as the name suggests, hosts only your domain. You can put one web site on it, or as many as you wish. You control the access. You may also, as an option, take over much of the server administration yourself. That may save you money on support costs, but cost you considerable time. If you don't have the expertise, you can end up costing yourself much more than you save. In order to carry out those administrative functions yourself, even if you hire help, it's desirable to have some technical knowledge under your belt. Some of that knowledge will be useful, even for day-to-day tasks apart from dealing with emergencies. FTP, email administration, backup methods and other technical areas are among the more common areas you'll need to be at least somewhat familiar with. When your web site grows to a certain size and level of complexity, you'll begin to find it worthwhile to look at implementing a database. But that brings with it a still higher level of ability, both technical and logistical or creative. Implementing a database can be relatively simple. Designing one that provides what you want, with decent performance and maintenance that doesn't become a nightmare, will take some careful thought. Not everyone has the temperament for that type of work, especially those who prefer graphical design, content creation or development, and the many other web site tasks that are part of every implementation. There are other, more low level administrative matters. Managing disk space, maintaining domain names, dealing with registration and changes, and a number of other 'utilitarian' tasks are also not everyone's cup of tea. Some understanding of how DNS works, as well as the design of the Internet itself, are helpful. That provides a good context for understanding the role of some of those tasks. When you begin to seek out a web host to implement a web site, consider all these factors and look in the mirror. What kind of web hosting you should pursue is determined by a combination of who you are and what's being offered. Look before you leap. 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. |