This is Christine Cavalier’s submission for the HP Magic Giveaway. Feel free to leave comments for this article as you see fit – your feedback is certainly welcomed! If you’d like to submit your own how-to, what-is, or top-five list, you can send it to me. Views and opinions of this writer are not necessarily my own:
Prerequisite to this course includes Birds & Bees 101. The “Marriage and Family” course helps, but is not necessary.
In this course, we will learn how to teach our iterations to carry the torch of the geek culture onward. We will be studying these five main guidelines on how to properly raise geeky spawn from pre-alpha stage to formal launch and Initial Public Offering:
- Assume your spawn, even at an alpha release, knows how to do a lot of stuff already. “Baby” comes with a lot of bundled knowledge, including its own maintenance schedule. You shall not disregard this build. The notifications (a.k.a. “crying fits”) are varied, and you can learn to read them for the different error messages that they are. If you institute this strategy effectively, you will have a healthy spawn who has faith that you can respond quickly to issues.
- Always read to your spawn, even in the pre-alpha stage. Your spawn has voice recognition software that kicks in at about 14 weeks after start-up. Contrary to lore, it actually doesn’t matter what you read. Code manuals are acceptable, but may educe error messages from your partner / venture capitalist (a.k.a. “significant other”). Lord of the Rings may be a bit more entertaining for your start-up’s advisory board.
- As your spawn reaches the late beta stage, you will have been working in the “Attachment Parenting” model for a few years. You will have mastered the immediate response to bugs by instituting the Time Out malware. Sometimes repeated physical download of Time Out is necessary. Along with Attachment Parenting theory, you will also be comfortable with the behavioral / cognitive approach adopted by the ultimate geek spawn master, SuperNanny.
- Share the geek culture early on, but in small doses. Overtaxing your spawn’s disk with too much data will crash it. All geek input may be rejected after a crash. There is no way to wipe the disk. Work out a timeline for geek upgrades and stick to it. Remember: Less is more.
- Encourage Open Source. Share your knowledge and explore the world together with your spawn, but always remember to embrace your spawn’s unique abilities. Each spawn is an independent client. Remember that the geek culture is wide and vibrant. If your spawn chooses a different version of the culture to adopt, be Tier One line of support for that option. With copious application of the Love and Respect donationware, you will have a spawn that will not only continue our time-honored geek traditions but you will get profound Returns On Investment.
Please comment with any additions to the syllabus of this course. We encourage a “Devcamp” atmosphere, so please share any knowledge or insights you have about the subject in the comment section. Thank you.