Welcome to beszeljukmac.com

Web Hosting - Why Backups Are Essential One thing most web site owners have little time for is... anything! Anything other than focusing on their site content and the business or service it supports and the information it provides, that is. That means that administration often suffers, as it frequently must. There's only so much time in the day. But the one thing that you should never let slide are backups. They are like insurance. You rarely need it (you hope), but when you do you need it very badly. Performing regular backups - and testing them - doesn't have to be a nightmare. A little bit of forethought and effort and they can be automated to a high degree. And, they should be tested from time to time. Even when a backup appears to have gone without a hitch, the only way to know whether it's of any value is to attempt to restore the information. If it can't be restored, the backup is worthless. Even when the web hosting company provides the service, there is still some planning involved for the site owner. Hosting companies often rely on one or both of two methods. They backup everything (called a full backup), then backup anything which has changed since the last full backup (called an incremental backup). Of special interest are any configuration files that have been tailored. If you've modified the default installation of a software package, you want to be able to recapture or reproduce those changes without starting from scratch. Network configuration files, modifications to basic HTML files, CSS style sheets and others fall into the same category. If you have XML files, databases, spreadsheets or other files that carry product or subscriber information - about items purchased, for example, or people who signed up for a newsletter - those should get special attention, too. That's the lifeblood of your business or service. Lose them and you must start over. That can break your site permanently. It should go without saying that all HTML and related web site files that comprise visible pages should be backed up regularly. It isn't necessary to record every trivial change, but you can tailor backup software to exclude files or folders. Usually they're so small it isn't worth the trouble. But in some cases those small changes can add up in scenarios where there are many thousands of them. Here again, the backups are worthless if they can't be used. Even if the hosting company charges for doing so, it's worthwhile to test once or twice a year at least to ensure the data can be restored. That's especially true of database backups, which often involve special software and routines. Database files have a special structure and the information is related in certain ways that require backups be done differently. Developing a backup strategy can be straightforward. Start simply and review your plan from time to time, modifying it as your site changes and grows. But don't neglect the subject entirely. The day will come when a hard drive fails, or you get hacked or attacked by a virus, or you accidentally delete something important. When that day comes, the few minutes or hours you spent developing and executing a backup plan will have saved you days or weeks of effort.

Important Networking Follow-Ups: How to Get Those Job Leads Calling When you leave a networking event, you may be buzzing at the prospects offered by all of those new contacts you made, but soon, the cold reality sets in. How will you be able to convert those contacts you made over a glass of wine into valuable business opportunities for you? Successful networking is all in the follow-up. If you’re looking for a job, following up is all the more crucial. Without touching base after a networking event, you become just another face in the crowd of job hunting hopefuls. The first important rule for following-up with networking contacts is to lay the foundations for the follow-up during the initial meeting. At networking events, there can be a lot of empty promises thrown around. Use that first meeting to convey the message that you haven’t gotten caught up in “networking fever” but instead that you are very serious about exploring the job opportunity that you’re discussing with your new contact. Ask the contact when would be a good time to follow-up with them, and then reiterate the information back to them at the end of your conversation: “I look forward to speaking with you Friday at 2 p.m.” If they don’t give you a specific time, then suggest one to them. This rule holds true even if your contact is giving you a lead on a job not with them but with another contact of their own. Let them know you appreciate the information by saying, “Thanks. I will plan on calling Mary on Monday afternoon at 1 p.m.” Not only will this convey your seriousness about the opportunity presented to you, but it may also get you some handy inside information, as the contact may reply, “Oh, no, Mary will be out of town until Thursday – call her then.” The next important rule to networking follow-ups is to follow up with EVERY lead a contact gives you. If a contact suggests that you call someone whom you know won’t really be able to help you in your job search, call him or her anyway. Otherwise, when your contact finds out you aren’t taking their advice, they may just decide not to give you any more the future and any business person can tell you that you never know from whom the most valuable lead will come some day. Keep the lines of communication open by giving any and all suggestions a whirl. Last but not least, do the actual following-up. Follow up with your contact exactly when you said you would, and in the exact manner you said you would (phone, email, letter, etc). If for some reason you can’t make contact at the arranged time, keep trying. If you haven’t made arrangements for a follow-up with a contact, then the rule of thumb is to follow-up with them as soon as possible after meeting them. Try to at least send an email or letter the next day saying what a pleasure it was to meet and that you look forward to talking more in the future, and then say in that note when you plan to follow-up with your contact by phone. Then, of course, stick to that new follow-up obligation. Even if the promises made by a contact while networking don’t pan out for you on the job front, don’t cross them off of your contact list. Keep them in the loop about your job search and your career goals. While they may not have been able to make if happen for you this time, you never know what they might be able to do for you in the future. Your most promising business contact may be someone you already know.

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.