Revision as of 01:33, 23 January 2007

Who am I

My name is Mike Mol. I'm President of the Grand Rapids Community College Computer Club. I founded Rosetta Code.

But who am I, really? I'm the Editor. I'm the guy who tries to watch all the changes on all the pages, and make sure they all follow the same style rules. What are the style rules, you might ask? Well, even I don't know. I try to give the pages a consistent appearance without sacrificing functionality.

So far, I've noticed contributors get the general idea behind formatting their contributed code. However, they don't usually put their code in the right place in the alphabetized list, and they often don't format their metadata lines correctly. (You know, those parts in bold that describe which compiler or interpreter or platform the code example uses.) I go in and fix it.

I also try to create pages for every language, compiler, interpreter, platform and what-have-you. This primarily involves looking for pages which haven't been created yet, and placing a stub. If I have time, I'll do a little research on the subject, and post a marginally informative one- or two-sentence article.

You might be wondering why I bother creating the articles. Well, it's because virtually every page should be categorized. Page categorization is the backbone of browsing Rosetta Code. If a language page doesn't get categorized, it won't show up in the official list of languages, the Programming Languages category page. Thus, if a language page isn't created to begin with, it can't be categorized.

As I write this, I'm behind somewhat due to a busy weekend. But I intend to catch up, just after I've gotten some sleep.

@@ Line 5: / Line 5: @@
 But who am I, really?  I'm the Editor.  I'm the guy who tries to watch all the changes on all the pages, and make sure they all follow the same style rules.  What are the style rules, you might ask?  Well, even I don't know.  I try to give the pages a consistent appearance without sacrificing functionality.
-So far, I've noticed contributors get the general idea behind formatting their contributed code.  However, they don't usually put their code in the right place in the alphabetized list, and they often don't format their metadata lines correctly. (You know, those parts in '''bold''' that describe which '''compiler'' or '''interpreter''' or '''platform''' the code example uses.)  I go in and fix it.
+So far, I've noticed contributors get the general idea behind formatting their contributed code.  However, they don't usually put their code in the right place in the alphabetized list, and they often don't format their metadata lines correctly. (You know, those parts in '''bold''' that describe which '''compiler''' or '''interpreter''' or '''platform''' the code example uses.)  I go in and fix it.
 I also try to create pages for every language, compiler, interpreter, platform and what-have-you.  This primarily involves looking for pages which haven't been created yet, and placing a stub.  If I have time, I'll do a little research on the subject, and post a marginally informative one- or two-sentence article.