Tips for writing a frequently updated blog
Blogging is hard business. No one has ever claimed otherwise, but it's worth restating.
I think the problem is that bloggers want to produce material that they're proud of. That's a mistake. To succeed as a blogger you must be willing to excrete defective conjectures out for everyone to see. The more typpos the better. And then you must defend those thoughts as if you actually believe them.
Only by moving the bar so low that it's scraping the floor will you be able to blog consistently. The goal for a blogger, then, is to make the act of writing take up less brainpower than any other of your daily responsibilities.
Water only runs one way: down. A blog should be no different.
Caring for your code
Hi I'm Kevin, a developer here at Edulence. A lot of folks have asked me about tips for getting started with programming. Usually I tell them that programming is just like growing your own garden. Don't believe me? Read on, pioneer.
Let's say you understand the health benefits of consuming fresh code, and you have an idea you've wanted to bring to life, but you're just not sure how to get started. Here's a few tips to get you on the path to putting fresh, delicious code on your computer monitor.
Think small. Especially if this is your first application, don't bite off more than you can chew, or type. You can always write more if you can't get enough of those crispy 1's and 0's.
Make sure to receive as much sunlight as possible throughout the day. Northern programmers in particular depend on getting the maximum amount of sun. A common mistake made by rookies is to code everything when the weather is bad, only to yield to lethargy during the summer months, letting their hard work go to waste.
Animals may show interest in your new program. Mice, cats, dogs, and even small children can be a problem. For most code, a simple fence can usually do the trick; this will discourage all but the most tenacious critters. I've seen some programmers take a wire mesh and staple it to the top of their computer monitors to keep out birds and other animals.
Other programmers may try and steal your code. While some people enjoy sharing code with others, for your first application it's generally a good idea to grow your own. You can cover ready-to-ripen code with straw to hide it.
Watch carefully for bug infestation. If you've taken the proper care of your environment, this shouldn't be a huge problem. Identify the bug quickly and decide on an insecticide to eradicate it. Proper re-factoring and unit testing are good ways to prevent disease and bug infestation without having to resort to toxic chemicals.
Before you know it, you'll be ready to harvest your code. Enjoy! For the maximum health benefits of your code, harvest when ripe and don't over cook. The most important thing is to enjoy consuming nutritious, tasty code that you grew yourself.
Happy coding!
