Welcome to twitnerd.com

Five Flex Time Options that Can Propel your Employee Productivity Flex time is something that is still very rarely used in the United States, but has many followers in other countries, especially European countries. Flex time in general means flexible working hours for employees of a company. They way the flexible working hours are implemented can differ greatly. But one thing is for sure, flexible working hours can greatly propel the employee productivity in your company. Take a look at five different ways to implement flex time in your company. The first and probably easiest way is to give your employees the option to come in to work and leave work within a certain time range. For example, so far your employees worked from 8am to 5pm, now you might give them the opportunity to come in to work anywhere from 7am to 9am, and of course, leave somewhere between 4pm and 6pm. This first model would give your employees an opportunity to be on time as long as they are within that range and their individual habits are considered in regards to being an early riser or a late sleeper. This first model would set the rule that there are 8 work hours plus a one hour lunch in a work day and these are not variables. Therefore, you only have to check their arrival and leaving times in one way or another. A second option is very similar to this, but you can expand the hours worked to a weekly or monthly check, where the employee is responsible to work 40 hours a week with one hour lunch everyday. Then he or she can come and leave in the morning and afternoon in the specified time ranges. For the employee, this means maybe on days that he or she is more energetic, they can spent more hours at work to get their work done and on days they do not feel so energetic or so good or they have family things going, on they can come in the minimum hours established from 9am to 4pm. This version of flextime is a much appreciated model by many employees, but for the employer, it means more work in tracking hours worked and arrival times, to make sure the required hours per week or months are worked. An even more advanced version of the first two flex time themes is a theme where the worker can accumulate time to take off at some point in the future. How specifically you are going to use this version is up to you. You basically are making sure that your employees are not working more than the required amount of hours. Why would you profit from this? Less time spent at the work place makes for more time to relax and regenerate and your employees will be more efficient and motivated throughout your work week. In some companies this flex time method allows the employee to accumulate hours up to a certain amount and then for example, they are allowed to leave after six hours for several days to be home for activities with their family. In an even more expanded version, a fourth version of flex time options, the employee can actually take full days off after having accumulated hours. These days are in general additional to vacation and holidays and can be taken in agreement with their supervisor. The fifth option that has been adopted by some companies actually gives the employees the chance to go into negative hours on their time account. This means if you do not have the required hours, you can still take a flex day off, but have to make sure that after a period of time, that the employer sets in the contract your account goes back to zero or higher. If the employer is a really generous person, he might allow you to completely choose the hours you want to work. You might be able to take work home or work from 10pm to 3am if you desire, as long as you have your assignments done on time and your hours are fulfilled.

Web Hosting - Unix vs Windows-Based Hosting, Which Is Better? An operating system functions largely out of sight, or at least is supposed to. It doesn't matter to non-geeks how a file gets stored, or how memory is used, or how simultaneous processes share the limited resources available on a computer. These are among the basic functions of any operating system. Yet, you can find very passionate supporters - who offer very detailed lists of pros and cons - for every operating system. Why? Because, though the low-level functions of an operating system do their work out of sight, there are many other features that rise to visibility. Sometimes, they do so when they're not supposed to. Weighing the pros and cons objectively could consume a book. But to select a web host operating system, a manageable level of considerations apply. They can be weighed even by those who don't know a processor queue from a pool cue. Learning Curves For most web site owners, administering the site/server is just overhead. It's not something they take pleasure in doing and they have plenty of other things to worry about. Many wouldn't know how and have no interest in learning (rightly so, given their priorities). Consequently, ease of administration is paramount for such people. Whether a Unix-based site (usually Linux these days) is easier to administer than Windows depends on your current skill set and the type of tools and level of access the web hosting company provides. But in general Linux is more difficult to install and maintain than Windows and the learning curve is steeper. FTP and Control Panels Often, you don't have to care. For many, the operating system is fairly transparent. FTP file transfers to get a new web page up to a Windows server are very much like they are to a Linux-based site. The user/administrator simply doesn't see what's behind the curtain. Many companies provide other utilities that completely mask any awareness of the operating system underneath. When that's the case, the web site owner has no reason to care, until or unless they need or want to go 'inside the black box'. Performance Performance issues can be relevant in selecting which operating system host type to choose. But for the most part, that aspect is outside the web site owner's control. Overall performance can be good or bad on either system, depending on many factors that the publisher will rarely see. The issue is a wash, as far as tipping the scales is concerned. What is more likely to be seen by a web site owner, at some point in their (and their site's) development is the database product that can be used to store information. Databases Microsoft SQL Server is relatively simple to use, yet extremely powerful and can deliver great performance. But it doesn't run on Linux. At least, not without special software to emulate Windows, which usually kills performance. On the other hand, with a bit of time invested, MySQL isn't significantly more difficult to learn than MS SQL Server and there are many free installations. Cost may well outweigh other considerations for most on this issue. Programming Languages Last, but not least, there are differences in programming languages that can be (or at least typically are) used on Windows vs Unix. If you have programmers who are skilled in Visual Basic, ASP and other Microsoft technologies, then a Windows-based host will be your preferred choice. For Perl and PHP programmers, Linux is the more common platform of choice. No single factor can push you to one versus the other operating system. And, in the long run, it isn't the primary consideration, unless you just enjoy playing with operating systems.

Web Hosting - Bandwidth and Server Load, What's That? Two key performance metrics will impact every web site owner sooner or later: bandwidth and server load. Bandwidth is the amount of network capacity available, and the term actually covers two different aspects. 'Bandwidth' can mean the measure of network capacity for web traffic back and forth at a given time. Or, it sometimes is used to mean the amount that is allowed for some interval, such as one month. Both are important. As files are transferred, emails sent and received, and web pages accessed, network bandwidth is being used. If you want to send water through a pipe, you have to have a pipe. Those pipes can vary in size and the amount of water going through them at any time can also vary. Total monthly bandwidth is a cap that hosting companies place on sites in order to share fairly a limited resource. Companies monitor sites in order to keep one site from accidentally or deliberately consuming all the network capacity. Similar considerations apply to instantaneous bandwidth, though companies usually have such large network 'pipes' that it's much less common for heavy use by one user to be a problem. Server load is a more generic concept. It often refers, in more technical discussions, solely to CPU utilization. The CPU (central processing unit) is the component in a computer that processes instructions from programs, ordering memory to be used a certain way, moving files from one place to the next and more. Every function you perform consumes some CPU and its role is so central (hence the name) that it has come to be used as a synonym for the computer itself. People point to their case and say 'That is the CPU'. But, the computer actually has memory, disk drive(s) and several other features required in order to do its job. Server load refers, in more general circumstances, to the amount of use of each of those other components in total. Disk drives can be busy fetching files which they do in pieces, which are then assembled in memory and presented on the monitor, all controlled by instructions managed by the CPU. Memory capacity is limited. It's often the case that not all programs can use as much as they need at the same time. Special operating system routines control who gets how much, when and for how long, sharing the total 'pool' among competing processes. So, how 'loaded' the server is at any given time or over time is a matter of how heavily used any one, or all, of these components are. Why should you care? Because every web site owner will want to understand why a server becomes slow or unresponsive, and be able to optimize their use of it. When you share a server with other sites, which is extremely common, the traffic other sites receive creates load on the server that can affect your site. There's a limited amount you can do to influence that situation. But if you're aware of it, you can request the company move you to a less heavily loaded server. Or, if the other site (which you generally have no visibility to) is misbehaving, it's possible to get them moved or banned. But when you have a dedicated server, you have much more control over load issues. You can optimize your own site's HTML pages and programs, tune a database and carry out other activities that maximize throughput. Your users will see that as quicker page accesses and a more enjoyable user experience.