Welcome to elreno.org

A Brief Guide to Writing Short Stories Effectively (writing short stories) A short story is basically a condensed version of a book or a rapidly progressing story. It has fewer characters than a novel and covers less amount of time. A short story generally is around 6,000 words or 6 pages. Do your research and organization before you begin to write. Outline your plot and the background. Make sure they make sense and flow together. Individually list the events of the story in the order in which they occur. Create your characters. Not just their name and role in the story, but as if they were real people with real lives. By creating more information for your characters you will get a sense of what they would do or how they would be and convey that to your writing. By creating an outline you will have a point of reference to look back upon and make sure you have included all vital points of the story. When writing a short story, you will need a captivating first paragraph. You have roughly 5 to 7 lines to appeal to your reads unlike novels that have the whole first chapter. This can actually make or break your story. You will need to grab their attention and keep it to make them want to read more. By starting the plot in the first few sentences it will make people want to know more. They will keep reading to find out who is involved and why. Keep the timeline of events brief. You are writing a short story and the timeline should match that. A timeline of a day, a week, or maybe even a month is generally the span a story should cover. Use character dialogue as a way to move the plot ahead. In a short story there is no time for general chitchat. By using the character dialogue you are deepening the plot as well as moving it along. Do not add unnecessary characters. By adding them you are wasting time one someone that is not linked to your story or its plot. Provide swift and precise details to keep the story moving. Elaborate descriptions of characters, plot, or surroundings will only waste your words and are not essential to making a good story. Use short words instead of phrases that mean the same thing. Building to the climax should be most of the story. Keep the conflicts building to the climax simple and easy to understand. You writing should be able to evoke the following emotions empathy, pain, hurt, despair, surprise, and desire just to name a few. Since the story is only a few pages long in its entirety it is necessary to maintain consistency through out the beginning, middle, and end. Make sure the dialog and plot complement each other. Keep the same point of view through out the story. You are almost ready to be published. After completing your own proofreading and editing, let someone else read it, a neighbor, your spouse, colleague, or a close friend. Even if they are not writers themselves they will be able to help point out any grammar errors. They will be able to tell you if something just doesn’t make sense. You are trying to fit a lot of captivating information in a small space; it is easy to leave something out. Something you may not catch because you know what is supposed to happen, while your will not. By following these simple rules, you will be able to write a short story that is captivating and effective. Writing short stories isn’t for everyone. Many writers like more detail and for short stories the space is just not available.

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 - When Changing Web Hosts Nearly everyone will want to change to a new web host at some point. It may involve just changing out old hardware for new. It usually means finding an entirely new web hosting company. When faced with that decision there are a number of issues to be considered. Swapping hardware and/or software is a fairly straightforward decision. There are two possible scenarios. Either you maintain your own hardware and software at a facility managed by others, or you are considering upgrading to newer (usually more expensive) systems maintained by others. In either case, it's simply a matter of estimating the cost and the short-term impact versus the long-term benefits. If the system(s) you currently use are short on capacity, sooner or later you'll be sufficiently motivated to make the change. Either the hardware will become unreliable or loaded to the point you'll be forced to migrate, or your needs will expand enough to justify the effort and expense of moving. Similar considerations apply to the scenario in which you rely on the web hosting company for everything, and want to find someone else to rely on. Regrettably, that's a very common situation. Many web hosting companies provide systems and staff that sooner or later fall below an acceptable level. Most people make the decision to change based on emotion. That's not entirely bad. Emotions incent you to take action. But you need to keep a cool head, too, in order to calculate your long-range self-interest. Bearing some minor inconveniences from time to time is usually worth the trade off. When it begins to affect your site to the point you're losing visitors, it's time to make a change. To get a more objective handle on when that point is reached, reach for some numbers. Maintain, or get from the hosting company, a factual report about availability and current usage. If the server is down so much, or so heavily loaded, that it drives your visitors away, it's time to take action. There are other less easily quantifiable but equally important factors, as well. You will at some point need to communicate with one or more persons who help maintain your site. Even if you do all your own server, database and web site maintenance, someone behind the scenes is helping to keep things running smoothly. That's called 'infrastructure'. If the road you drive on has potholes, it's not enough that you can fix your own car. In terms of network bandwidth and availability, server capacity, disk space, security and a whole array of other aspects, the web hosting company has to have competent people who care (and are allowed) to do the job well. When the company's people fall down - because of incompetence, lack of resources or absence of a culture of excellence - or for any other reason - your web site suffers. This issue more than any other is what drives people to seek another web hosting company. Even if you choose well at the outset, things can change. Management changes, staff changes and companies are taken over by other companies. Sometimes, it isn't simply a matter of swapping out an unreliable piece of hardware or software. When it's time to swap out people, you look for the same aspect: doing the job required.