User:MikeMol: Difference between revisions

From Rosetta Code
Content added Content deleted
m (Reverted edits by Short Circuit (Talk) to last version by Mwn3d)
m (Undo revision 25949 by Short Circuit (Talk))
Line 1: Line 1:
{{mylangbegin}}
{{mylangbegin}}
{{mylang|Visual Basic|Advanced}}
{{mylang|Visual Basic|Very Rusty}}
{{mylang|BASIC|Intermediate}}
{{mylang|BASIC|Very Very Rusty}}
{{mylang|Brainf***|Intermediate}}
{{mylang|Brainf***|Rusty}}
{{mylang|C++|Intermediate}}
{{mylang|C++|Active}}
{{mylang|Perl|Intermediate}}
{{mylang|Perl|Semi-active}}
{{mylang|PHP|Intermediate}}
{{mylang|PHP|Active}}
{{mylang|UNIX Shell|Intermediate}}
{{mylang|UNIX Shell|Active}}
{{mylang|C|Beginner}}
{{mylang|C|Semi-Active}}
{{mylang|Java|Beginner}}
{{mylang|Java|Rusty}}
{{mylang|Javascript|Beginner}}
{{mylang|Javascript|Rusty}}
{{mylang|SQL|Beginner}}
{{mylang|SQL|Rusty}}
{{mylang|Visual Basic .NET|Beginner}}
{{mylang|Visual Basic .NET|Rusty}}
{{mylang|Python|Want to Learn}}
{{mylang|Python|Interested}}
{{mylangend}}
{{mylangend}}
{{BoxImage|Short Circuit Avatar.jpg}}My name is Mike Mol. I founded Rosetta Code, contributed the first tasks and examples, went on a promotion drive, and now primarily provide guidance, administrative and hosting services and maybe a line of code here and there. Rosetta Code was an idea I'd had during a Christmas vacation, before I'd heard of [[Help:Similar Sites|other programming chrestomathy sites]].
=Who am I=


=Contact=
My name is Mike Mol. I founded Rosetta Code. It was an idea I'd had during a Christmas vacation, before I'd heard of [[Help:Similar Sites|other programming chrestomathy sites]].
==Talk page==
This page's "talk page" is a great way to have a public conversation with me. Click on the "discussion" tab above, and then click on "edit".
==Email==
My email address is [mailto:mikemol@gmail.com mikemol@gmail.com]. Feel free to drop me an email if you so desire.
==IM==
Google talk: mikemol@gmail.com
Yahoo: mikemol6453
AIM: mikemol6453
IRC: shortcircuit, shortc|work, shortc|laptop or shortc|desk on Freenode, Typically in #rosettacode.
Twitter: http://twitter.com/mikemol


=Voice=
But who am I, really? I'm the Administrator. That guy who's got so much to do, he has to have other people run the site for him. (Hats off to the Bureaucrats!) On a good week, I can give pointers to where I think RC should go, and how it should be organized. With luck, someone else has the time to make the changes.
I've got a few blogs and website in various places. I currently have blogs on [http://mikemol.multiply.com Multiply] and [http://mmol-6453.livejournal.com/ Livejournal] and Slashdot.


==Thoughts on Rosetta Code==
I try to act as a facilitator, to let the site and its [http://villagepump.rosettacode.org community] grow, and give a push (or pull) when things slow down.
===Language scope===
It's a given that not all of the languages will be able to accomplish all of the tasks; Just because two languages are turing-complete does not mean that all things possible in one language are possible in another; One language may have access to system and environment resources that another language doesn't. While it's certainly possible to transcode BrainFuck source to C source, you can't go in the other direction without providing language extensions. But before you dismiss that as a strawman, consider the same thing is true between C and Perl; Anything written in Perl can be transcoded to C, but the reverse isn't possible without providing native-code Perl modules for runtime. To borrow a term from the graphic design world, different programming languages have different gamuts; If you want two different languages to support all of the same features, it's highly likely you'll either have to prune one language's feature set or extend the other's.
===My role===
And, all of that said, I try to leave the decisions on these things to the CS professionals, academics and hackers* that frequent the site. They'll get on a talk page here or there and argue about whether a task is poorly written, whether an implementation follows the goal of the task, or both. Actually, one argument usually leads to the other, and the two sides hash out their points until they come to a consensus. When a question of "whether this suits the purpose of Rosetta Code" comes up, I'll drop in, write a few words about my opinion, and let them continue towards a consensus. After a while, things settle down, and someone with the appropriate privileges applies the consensus.

In short, I just run the servers, try to keep things running smoothly, add whatever features I think of or that people ask for, if possible. I enable the process; I try not to control it. Heck, when I created the site, I wasn't even sure what the process was, or what it was going to be; It more or less developed out of the interactions of people interested in learning languages, people interested in advocating languages and people for whom language chrestomathy tickles their brain.

* In the Jargon file sense


==Contact==
===Talk page===
This page's "talk page" is a great way to have a public conversation with me. Click on the "discussion" tab above, and then click on "edit".
===Email===
My email address is [mailto:mikemol@gmail.com mikemol@gmail.com]. Feel free to drop me an email if desired.
===IM===
If you have Google Talk, you can try adding me as a buddy, via my email address. Alternatively, use [http://www.google.com/talk/service/badge/Show?tk=z01q6amlqsu2sdt3muotj59ieri75fl3k0obubller5u3ikqqju22s51u600dg8up1mth0vip6d13p10in46bg9ht4t76htcrpk8l3culdlejubpfmal1tk89888quea8426m850kr9uj22kot7dus1qq548g6m2lclv7u6vs&w=200&h=60 this clever little chat thing]. (
===IRC===
You can stop by the Rosetta Code IRC channel on Freenode (#rosettacode), where a few RC members (and a few language bots) reside.
=Languages=
=Languages=


I've been a Linux geek since 1999-2000, so I've got a healthy respect for [[Perl]], the [[Bourne Again SHell]] and [[C]], but my day job involves coding in Windows, which means I've lately been spending most of my time in [[C plus plus|C++]]. I'm competent with [[PHP]] as well, and have written a couple applications that made good use of [[JavaScript]].
I've been a Linux geek since 1999-2000, so I've got a healthy respect for [[Perl]], the [[Bourne Again SHell]] and [[C]], but my day job involves coding in Windows, which means I've lately been spending most of my time in [[C++]]. I'm competent with [[PHP]] as well.


=RSS=
=RSS=


I currently keep an eye on Rosetta Code by adding [[Special:Recentchanges]] to my Google Reader. I find it's a great way to stay apprised. I also watch a number of other programming feeds, the most interesting of which is probably the [http://reddit.com/r/programming/.rss feed for programming.reddit.com].
I currently keep an eye on Rosetta Code by adding [[Special:Recentchanges]] to my Google Reader. I find it's a great way to stay apprised. Google Groups has an RSS feed for each group, with is another way to stay caught up on language discussions, even if groups like comp.lang.c++ move pretty quickly.


=Rosetta Code=
=Rosetta Code=
Line 43: Line 53:
Rosetta Code came from an idea I had during Christmas of 2006. I'd recently revisited Wikibooks' [http://en.wikibooks.org/wiki/List_of_hello_world_programs List of Hello World Programs], and didn't care for its limited scope. As I was President of the [http://grc4.org GRCC Computer Club] at the time, I convinced the club to host a project called Goodbye World (shortly renamed to Rosetta Code). I chose MediaWiki because I felt it would let me get started more quickly than any other system. Once I had a few categories and tasks set up, I submitted the page to Slashdot.
Rosetta Code came from an idea I had during Christmas of 2006. I'd recently revisited Wikibooks' [http://en.wikibooks.org/wiki/List_of_hello_world_programs List of Hello World Programs], and didn't care for its limited scope. As I was President of the [http://grc4.org GRCC Computer Club] at the time, I convinced the club to host a project called Goodbye World (shortly renamed to Rosetta Code). I chose MediaWiki because I felt it would let me get started more quickly than any other system. Once I had a few categories and tasks set up, I submitted the page to Slashdot.


Well, if you take Slashdot, a shared hosting account, and an uncached MediaWiki setup, and throw them in a blender, you get a big mess. The kind folks at Geekalize noticed, and offered RC free hosting on their dedicated server. That carried RC through until the end of the arrangement in the fall of 2007. From Fall of 2007 until June of 2008, RC ran on my shared hosting account. In June of 2008, [[User:Qrush|Qrush]] offered use of his Slicehost VPS account for hosting Rosetta Code.
Well, if you take Slashdot, a shared hosting account, and an uncached MediaWiki setup, and throw them in a blender, you get a big mess. The kind folks at Geekalize noticed, and offered RC free hosting on their dedicated server. That carried RC through until the end of the arrangement in the fall of 2007. From Fall of 2007 until June of 2008, RC ran on my shared hosting account. From June-August of 2008, Rosetta Code sat on a Slicehost VPS account paid for by [[User:Qrush|Qrush]]. In August 2008, Rosetta Code moved to a Slicehost VPS account paid for by me.

==Away==

My job will continue to consume my soul until mid-August, so I will not be able to follow RC closely for a while. If you need assistance with policy, see if you can come to a consensus or compromise. If you can't, try checking with [[User:Mwn3d|Mwn3d]]. If he doesn't want to touch it, email me at [mailto:mikemol@gmail.com mikemol@gmail.com] with the URL with the talk page where you've discussed it, and I'll weigh in.

Or you can skirt discussion and Mwn3d and come to me directly, but beware of the logic behind thought processes taking place after 2AM.
:For anyone who needs to contact me, it is easiest to talk to me in [[Special:Mibbit|the IRC channel]] (if I'm there), or to write on [[User talk:Mwn3d|my talk page]]. If that's too public for you, you can email me at [mailto:rekaeuqs1@gmail.com rekaeuqs1@gmail.com]. --[[User:Mwn3d|Mwn3d]] 19:36, 2 August 2008 (UTC)


==TODO List==
==TODO List==
This is ''my'' prioritized TODO list regarding activities on Rosetta Code.
This is ''my'' TODO list regarding activities on Rosetta Code.
* Get the per-language RSS feeds up
# Rosetta theme. Get it working well under Firefox, then IE 7, IE 6 and IE 5.5.
* Provide public anon SVN access to the cached category listings ImplSearchBot saves its category retrievals to.
# Add support for <code> to GeSHi. Phase out <lang> approach.
* See what I can do to get RC's host configuration to gracefully deal with Slashdot-level traffic. (It'd be nice to get 'dotted again, if it weren't so painful...)
# Finish Python port of RCRPG, post Perl and Python versions
* Get my butt out to New England to visit the Rosetta Code Power Apartment and buy those guys a pizza and a beer or two. And find out exactly what this "plate" experience tastes like.
# Investigate [http://www.mediawiki.org/wiki/Extension:Wiki2LaTeX Wiki2LaTeX]
# Poke around for GeSHi replacement that makes use of vim syntax highlighting configurations


==Policy==
==Policy==
Line 72: Line 74:
===Questions===
===Questions===


If you have any questions, you can try leaving me a note (I can't guarantee I'll get back to you quickly.), asking on the Village Pump, or dropping by on IRC. If it's about RC organization, you might query Mwn3d, IanOsgood and/or Kevin Reid.
If you have any questions, you can try leaving me a note (I can't guarantee I'll get back to you quickly.), asking on the Village Pump, or dropping by on IRC. If it's about RC organization, leave a note in the Village Pump or the relevant page's talk page; Interested parties will usually leave comments within a few hours.

Revision as of 19:39, 15 March 2009

My Favorite Languages
Language Proficiency
Visual Basic Very Rusty
BASIC Very Very Rusty
Brainf*** Rusty
C++ Active
Perl Semi-active
PHP Active
UNIX Shell Active
C Semi-Active
Java Rusty
Javascript Rusty
SQL Rusty
Visual Basic .NET Rusty
Python Interested

My name is Mike Mol. I founded Rosetta Code, contributed the first tasks and examples, went on a promotion drive, and now primarily provide guidance, administrative and hosting services and maybe a line of code here and there. Rosetta Code was an idea I'd had during a Christmas vacation, before I'd heard of other programming chrestomathy sites.

Contact

Talk page

This page's "talk page" is a great way to have a public conversation with me. Click on the "discussion" tab above, and then click on "edit".

Email

My email address is mikemol@gmail.com. Feel free to drop me an email if you so desire.

IM

Google talk: mikemol@gmail.com Yahoo: mikemol6453 AIM: mikemol6453 IRC: shortcircuit, shortc|work, shortc|laptop or shortc|desk on Freenode, Typically in #rosettacode. Twitter: http://twitter.com/mikemol

Voice

I've got a few blogs and website in various places. I currently have blogs on Multiply and Livejournal and Slashdot.

Thoughts on Rosetta Code

Language scope

It's a given that not all of the languages will be able to accomplish all of the tasks; Just because two languages are turing-complete does not mean that all things possible in one language are possible in another; One language may have access to system and environment resources that another language doesn't. While it's certainly possible to transcode BrainFuck source to C source, you can't go in the other direction without providing language extensions. But before you dismiss that as a strawman, consider the same thing is true between C and Perl; Anything written in Perl can be transcoded to C, but the reverse isn't possible without providing native-code Perl modules for runtime. To borrow a term from the graphic design world, different programming languages have different gamuts; If you want two different languages to support all of the same features, it's highly likely you'll either have to prune one language's feature set or extend the other's.

My role

And, all of that said, I try to leave the decisions on these things to the CS professionals, academics and hackers* that frequent the site. They'll get on a talk page here or there and argue about whether a task is poorly written, whether an implementation follows the goal of the task, or both. Actually, one argument usually leads to the other, and the two sides hash out their points until they come to a consensus. When a question of "whether this suits the purpose of Rosetta Code" comes up, I'll drop in, write a few words about my opinion, and let them continue towards a consensus. After a while, things settle down, and someone with the appropriate privileges applies the consensus.

In short, I just run the servers, try to keep things running smoothly, add whatever features I think of or that people ask for, if possible. I enable the process; I try not to control it. Heck, when I created the site, I wasn't even sure what the process was, or what it was going to be; It more or less developed out of the interactions of people interested in learning languages, people interested in advocating languages and people for whom language chrestomathy tickles their brain.

  • In the Jargon file sense

Languages

I've been a Linux geek since 1999-2000, so I've got a healthy respect for Perl, the Bourne Again SHell and C, but my day job involves coding in Windows, which means I've lately been spending most of my time in C++. I'm competent with PHP as well.

RSS

I currently keep an eye on Rosetta Code by adding Special:Recentchanges to my Google Reader. I find it's a great way to stay apprised. Google Groups has an RSS feed for each group, with is another way to stay caught up on language discussions, even if groups like comp.lang.c++ move pretty quickly.

Rosetta Code

Rosetta Code came from an idea I had during Christmas of 2006. I'd recently revisited Wikibooks' List of Hello World Programs, and didn't care for its limited scope. As I was President of the GRCC Computer Club at the time, I convinced the club to host a project called Goodbye World (shortly renamed to Rosetta Code). I chose MediaWiki because I felt it would let me get started more quickly than any other system. Once I had a few categories and tasks set up, I submitted the page to Slashdot.

Well, if you take Slashdot, a shared hosting account, and an uncached MediaWiki setup, and throw them in a blender, you get a big mess. The kind folks at Geekalize noticed, and offered RC free hosting on their dedicated server. That carried RC through until the end of the arrangement in the fall of 2007. From Fall of 2007 until June of 2008, RC ran on my shared hosting account. From June-August of 2008, Rosetta Code sat on a Slicehost VPS account paid for by Qrush. In August 2008, Rosetta Code moved to a Slicehost VPS account paid for by me.

TODO List

This is my TODO list regarding activities on Rosetta Code.

  • Get the per-language RSS feeds up
  • Provide public anon SVN access to the cached category listings ImplSearchBot saves its category retrievals to.
  • See what I can do to get RC's host configuration to gracefully deal with Slashdot-level traffic. (It'd be nice to get 'dotted again, if it weren't so painful...)
  • Get my butt out to New England to visit the Rosetta Code Power Apartment and buy those guys a pizza and a beer or two. And find out exactly what this "plate" experience tastes like.

Policy

(I'll have to find a better place for this eventually.)

I'm something of a benevolent dictator here on Rosetta Code. One thing I've discovered, though, is that other people are usually right. Hence, if you have a suggestion, let me know. However...

Language Promotion

I explicitly allow and endorse language promotion on RC, so long as it takes the form of code. I occasionally seek out language developers and enthusiasts to get regular contributors for new languages. Language comparison is the primary goal of Rosetta Code, and enthusiastic contributors help towards that. --Short Circuit 21:22, 11 December 2007 (MST)

Questions

If you have any questions, you can try leaving me a note (I can't guarantee I'll get back to you quickly.), asking on the Village Pump, or dropping by on IRC. If it's about RC organization, leave a note in the Village Pump or the relevant page's talk page; Interested parties will usually leave comments within a few hours.