Anonymous user
Beginner Mistakes: Difference between revisions
moved "Naming" to new "Promotion" section and added "Project Website" information
| [unchecked revision] | [unchecked revision] |
(Added a section on very basic troubleshooting guidelines to avoid some common pitfalls of those asking for help on the forums / IRC.) |
(moved "Naming" to new "Promotion" section and added "Project Website" information) |
||
Line 62:
So instead of focusing on emulating other systems, focus on your own. Design it, develop it, and be friends with it.
=== Naming ===▼
Naming is usually the last problem to be solved, even while we all wish for a cool name to our cool concept. Since the "coolness" of a name is a matter of taste, we cannot help you finding it. Moreover, if you tie your project name to a certain feature, you might discover somewhere down the road that no concept is perfect and that you might want to change what you initially thought a key feature. Nothing would be more stupid not to evolve just because you 'want to stick to a name'...▼
A lot of good information on naming can be found in [[Topic:15250|this]] thread. Simply put, naming your operating system <name>OS (JackOS, FredOS, etc) may seem like a good idea, until you get a second project member. A good idea (courtesy of Solar) is to choose a codename (like Longhorn, Chicago, etc) and then make up a better name closer to release time.▼
=== Programming Languages ===
Line 99 ⟶ 94:
For a much more in depth guide on how to be a good community member when asking for help, consult [http://www.catb.org/~esr/faqs/smart-questions.html How to ask questions]. It's a great read, and ideally, you should read the whole thing before asking for help anywhere (it's not that long, and well worth the read).
== Promotion ==
▲=== Naming ===
▲Naming is usually the last problem to be solved, even while we all wish for a cool name to our cool concept. Since the "coolness" of a name is a matter of taste, we cannot help you finding it. Moreover, if you tie your project name to a certain feature, you might discover somewhere down the road that no concept is perfect and that you might want to change what you initially thought a key feature. Nothing would be more stupid not to evolve just because you 'want to stick to a name'...
▲A lot of good information on naming can be found in [[Topic:15250|this]] thread. Simply put, naming your operating system <name>OS (JackOS, FredOS, etc) may seem like a good idea, until you get a second project member. A good idea (courtesy of Solar) is to choose a codename (like Longhorn, Chicago, etc) and then make up a better name closer to release time.
=== Project Website ===
Many newcomers to osdev create project websites before they have anything worth showing on the website. There's no value in creating a website making dramatic claims about the future plans for your project before you've got any idea where your project is heading or any code, screenshots, or downloads to showcase what you've already produced - such a website looks dead and creates a bad reputation. Announcing your website (such as in the Announcements forum on the OSDev.org forums) or linking to it in your signature when there's nothing more than a "welcome to <insert fancy project name here>" message on it just makes people lose interest in your project before you've even started, and if/when you do eventually produce something worth showing off you'll be faced with an already-terrible reputation that will be hard to overcome.
== Teamwork ==
| |||