Welcome to esiq.org
|
News is News All Over the World
(writing newspaper articles)
Writing newspaper articles is a fun and interesting line of work. Newspapers exist in big cities, small towns, within corporations and on college campuses. Newspapers are printed for special interest groups as well as for world and national news. There are free newspapers and papers that appear for sale on newsstands every day. With such a large variety of newspaper types printed, there are myriads of possible opportunities for writing newspaper articles. There are some basic rules to writing articles for any newspaper and there are also some specific aspects to know about each type.
Writing Newspaper Articles
In general, to write a newspaper article there are a few rules that apply across the board. First, the news has to be relevant. Because newspapers make up a genre of writing that is constantly refreshing itself, there is no room for common knowledge or historical pieces. The exception is if those kinds of writing serve to connect to a current issue or event. People who read newspapers want to know what’s happening now. For that reason, writing newspaper articles often involves relatively high pressure to get the latest news written each and every day. There are some low-pressure possibilities in writing newspaper articles though.
The Infrequent Print
Several newspapers are only printed weekly or even monthly. In small towns that must get their papers printed off-site, it is not feasible to create a paper each and every day. That means that there’s a week, every week, to get the news in and written. Another example of low pressure writing for newspapers is working for a free publication. Free newspapers are often geared to a special interest group. Since that group is not paying for its paper, they may only receive the interesting tidbits once a month. Writing for these kinds of newspapers becomes focused on creativity and niche writing because the current events will have already reached the audience through more frequent publications.
The Daily News from Top to Bottom
The most reliable and frequent publications are those of big, national newspapers. The staffs are very large and are able to print very clean copies of very full newspapers. By clean, that means without errors. Smaller papers are also printed daily, but they seem almost insignificant except to the people of the local community. They receive national news second hand and run very small staffs. Interestingly enough, none of these daily papers are really about the news. Of course that is where most of the effort lies and that is the reason that people buy the papers, but it is not the root of a newspaper. Writing newspaper articles is a job heavily dependent on the advertising industry. A newspaper will only be as large as there are ads to pay for it. Newspapers do not make their money at the newsstand. They pay the bills and the employees with money from advertisers.
On Campus News
Working for a university paper will not be representative in the area of newspaper advertising. While some businesses do pay for ads in university papers, the funding comes from the school. If for some reason there were no advertisers one day, the paper would still go out. University publications are much more focused on the development of the students than making a successful business. Most campus papers are free and are created by students. School is a great place to get started in writing newspaper articles. The environment is challenging, but nurturing at the same time. The deadlines and standards still exist, but the writer gets great encouragement and training through the work. After working for a college paper, it will be much easier to get a job with newspapers of the cities and towns.
Writing newspaper articles can be a great job. There are so many opportunities to get into writing that it is hard to pass them up. Some jobs may be very difficult to get, but others will be steps towards increasing writing success.
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. 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. |