Welcome to elreno.org

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 - Domain Name Changes and How They Affect You New domain names are registered all the time, and ones previously registered expired. Sometimes that's the result of simple neglect. The owner of the name chose not to renew his or her ownership, so the name became available for someone else to use. In rare cases, a highly original mind managed to think of a new one. In the other common scenarios, someone chose to just let it go or sell it. When you choose to change your domain name, there are actually two separate steps involved: releasing the old name, and adopting the new one. But, just as the postal system can have difficulty forwarding your letters when you change your personal name, changing your domain name brings certain difficulties. One of the most prominent is the fact that any name change requires a change to thousands of DNS Servers around the globe. DNS (Domain Name System) is the set of software/hardware components that allows domain names to map to IP addresses. IP addresses are what are actually used 'under the covers' when one computer communicates with another. Note that there isn't always a 1:1 correspondence between a name and an IP address. One IP address can serve multiple domain names and one domain name can have multiple IP addresses. For the sake of simplicity, we'll stick to the common case here. DNS servers around the world maintain internal databases that match the name to an IP address. Not all servers have all pairs of names/addresses. A series of complex routines allows a request to be forwarded when the particular DNS server doesn't have a needed record. When you acquire a domain name that used to be associated with a given IP address, the odds of you acquiring the same IP address are extremely low. In the unlikely case, for example, that you acquired the domain name yahoo.com, you would almost certainly not get the IP address that was matched with it (unless you bought the Yahoo! company). So, as a result of the change, the name/IP address pair is no longer what it was. A similar circumstance exists when you retain your IP address, but want to change the domain name associated with it. In either case, the pairing has changed. The catch is this: when the change takes place, those DNS databases are not all updated instantaneously around the world. Even apart from the limited speed with which computers and networks operate, (and neglecting the human factor if/when the change is made manually to more than one server) the reason is something called caching. In order to communicate efficiently, DNS servers are designed to assume that changes will be relatively rare. Just as with the postal system, you don't move your address or change your name every minute. Since that's true, in general, the name/IP address pair is cached. A cache is a set of stored information that is reused so that fresh information doesn't have to be communicated with every request for a web page or data. A chain of DNS servers pass requests to the last known address. There is usually more than one system between your computer and the server you want to communicate with. Most of the time, that's your current name/address. When you change the name, that pair is no longer valid. In order to propagate the new name/address pair (so the terminology goes), that cache has to be refreshed. Something similar happens when you establish an entirely new name. That name is first associated with an IP address and that pair has to be communicated to DNS servers around the world in order for you to be able to reach any one of them at random. But DNS servers don't do that until they are requested to do so by your action of asking for information from a remote server. Because of that, but chiefly because of caching, it can take quite a while for the new pair to become known around the Internet. Caches can expire and get refreshed in a few minutes or a few hours. It varies. That time can be as short as an hour or less, if the path between your computer and the web server is very simple and only one DNS server needs to be updated. Or, it can take up to 48 hours or more. Though the 'official' range is often given by registrars as 24-48 hours, the average is closer to about six hours. But that's an average. The actual time in any given case can (and does) vary widely. In the meantime, a number of effects can occur. The most obvious is that, since the name/IP address pair can't be resolved properly, you don't reach the server you want. Your browser points to the old one (in the rare case it's still accessible by that name and address), or it simply reports there's no such name at that address. So, when registering a new name or buying an old one, you should establish the site, but not advertise it for at least a couple of days. Better to wait to get visitors than to turn them off by being 'not at home' when they call.

Software copyright statement A Software Copyright Statement Protects Current and Future Works If you have a site that is dedicated to the sharing and distribution of open source software it is a great idea to have a software copyright statement that explains the limits of use for your software as well as the limits of your responsibility for those uses. I also recommend getting an attorney to look over the statement before posting it just to be sure there are no legal issues that you may be unaware of. A software copyright statement doesn't have to be a 10 page booklet on the law or the protections that copyright offers, it should be a simple short paragraph stating the basics and hopefully covering your rear from litigation and/or responsibility should someone use the software you are allowing them to use for something insanely stupid or frighteningly criminal while establishing your ownership of the material and expectations of those you are allowing to use your creation. This for some is a no brainer because they've done it before and know the ropes. There are new software developers born and made each and every day and this type of software copyright statement may serve to save them a little grief of their own some day. If you are being kind enough to freely share the software you created with others, you'd like to think that they would at least return the favor of using it within the letter of the law or the manner in which it was intended. This, however, is rarely the case so protecting yourself, your copyright, and your future interests by posting a software copyright statement on your website is really the best way to go in a situation such as this. Trust me I'm not trying to talk anyone out of sharing his or her software with the world. I rather like open source software and admit to using it freely (no pun intended). I love saving money almost as much as I love playing around with new technology. Software allows me to do that and find likes and dislikes about all kinds of programs. Issuing a software copyright statement is one way of protecting your investment of time, effort, energy, and sheer brilliance in the making and design of your technological masterpiece. Hopefully that flattery will keep you going a bit longer at any rate. It is important to know that a software copyright statement is only part of the process required to protect your software but for the most part poses a significant deterrent to those that would abuse your copyright and/or your kindness in allowing the distribution of your software. Even if you are charging people for the use of your software (we are a nation of capitalists after all) you still need to protect the labor you have put into making not only the software but the distribution method, the website, the payment method and the thousands of other things that are part and parcel of the business model for your software distribution. Your software copyright statement is a very small protection for your software don't expect it to be the brunt of your protection. Most of the software developers, coders, and programmers (and any other name you wish to call them) that I know aren't as concerned nearly as much about associating their name with the products they create as they are with protecting future potential income from both the products they are currently designing and the future, improvements they will make to the software and the much improved finished product that comes later. By protecting all your work with a software copyright statement you are not only protecting current works but future works as well.