Welcome to fmbb.net

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.

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.

Tackling those Second and Third Interviews to Land that Job If you make it to a second or third interview, you are a serious candidate for the job. The key now is to narrow down the candidates. This moment is when you will determine if you get called with a job offer or receive a notice of rejection in the mail. Arm yourself with the proper tools and make an even bigger splash on the second and third interviews than you did at the first one. The first thing to remember when you are going into a second or third interview is what you said in the first interview. The interviewer will have notes from the first interview so you need to be ready to follow up on things you said initially. This is why it is important to be honest and realistic in the first interview. If you work hard to impress the interviewer and end up lying, you may not be able to recall they lies you told in the first interview. Eliminate this from being the case by telling the truth the first time around. Be armed with questions about the position and the company in generally. Search through information online about the company and get a feel for day-to-day operations. Type in the name of the company in Wikipedia and see what comes up. Many corporations are listed in this massive Internet encyclopedia and information about the company can be found there. Find out as much as you can about the company you are interviewing with. If you are interviewing with the same person the second or third time around, ask about their experience with the company. Questions like, “What is a typical day for you on the job?” or “How long have you been employed with the company?” can help to build a relationship with the interviewer. It also signals that you are comfortable with the interviewer. Not to mention, who does not like to talk about themselves? This is a great way to keep the interview moving on a positive note. Have plenty of questions about the position. Show that you have researched the job and are very confident that you are going to get it. The more inquiries you have about the position the more serious and interested you will seem. By the second or third interview, you will probably meet a number of different people. Shake hands firmly and look them in the eye when talking to them. If you are given a tour of the facilities, ask questions. Do not just let your tour guide point out areas without you taking an interest in them. Although it may seem like second and third interviews should be easier, do not let your guard down. Stay on your toes and be even more prepared than you were for the first interview. As the interview process moves on you will probably be meeting with the person that will be your direct boss or the director. Interviews with these figures may be much more difficult than the first interview which was probably with a human resource person. Be aware of this fact and have answers for those tough questions like, “What makes you the right candidate for this job?” Also be prepared for hypothetic situations that may take some spur of the moment problem solving. No matter what number interview you are on, there are some standard rules to follow. Take copies of your resume to your second and third interviews. Even though the interviewer may have a copy of your resume, you want to be armed with extras just in case there are other people in the department that would like copies. If you meet with different managers they may all ask for copies of your resume. Yes, they have copies, but they want to see if you are prepared.