User:MikeMol: Difference between revisions

From Rosetta Code
Content added Content deleted
(Throw a twitter feed on there...)
(→‎Who am I: Updated page.)
Line 14: Line 14:
{{mylang|Python|Interested}}
{{mylang|Python|Interested}}
{{mylangend}}
{{mylangend}}
=Who am I=
{{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]].
{{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]].


=Contact=
I try to act as a facilitator, to let the site and its community grow, and give a push (or pull) when things slow down. I've got a full time job, family I'm responsible for and other things competing for my time, so the most I'm usually good for is catching up on the Recent Changes RSS feed once or twice a week, and respond to administrative needs that can't be handled by the bureaucrats and Mediawiki co-admins. (Though I've recently been given permission to work on RC while at work, while I'm waiting on work-related overhead like builds and such. So I'll be a bit more in touch than I have been for the past two years.)
==Talk page==

==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".
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===
==Email==
My email address is [mailto:mikemol@gmail.com mikemol@gmail.com]. Feel free to drop me an email if you so desire.
My email address is [mailto:mikemol@gmail.com mikemol@gmail.com]. Feel free to drop me an email if you so desire.
===IM===
==IM==
Google talk: mikemol@gmail.com
Google talk: mikemol@gmail.com
Yahoo: mikemol6453
Yahoo: mikemol6453
AIM: mikemol6453
AIM: mikemol6453
IRC: shortcircuit, shortc|work, shortc|laptop or shortc|desk on Freenode, Typically in #rosettacode.
IRC: shortcircuit, shortc|work, shortc|laptop or shortc|desk on Freenode, Typically in #rosettacode.
====Twitter====
===Twitter===
Twitter: http://twitter.com/mikemol
Twitter: http://twitter.com/mikemol
These won't necessarily RC-related. But feel free to follow or @ me. I've got Twitterfox installed just about everywhere...
These won't necessarily RC-related. But feel free to follow or @ me. I've got Twitterfox installed just about everywhere...
Line 36: Line 33:
</xfeeds>
</xfeeds>


==Voice==
=Voice=
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.
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==
===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=
=Languages=

Revision as of 06:45, 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

Twitter: http://twitter.com/mikemol These won't necessarily RC-related. But feel free to follow or @ me. I've got Twitterfox installed just about everywhere... <xfeeds contentcolour="#eeeeee" feedlimit="5" totallimit="5"> http://twitter.com/statuses/user_timeline/17652913.rss </xfeeds>

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 prioritized TODO list regarding activities on Rosetta Code.

  1. Rosetta theme. Get it working well under Firefox, then IE 7, IE 6 and IE 5.5. -- I'm stalled on this; The page tabs don't render properly in IE. If someone can send me a fix for the CSS, I'll set the theme as default and call it done.

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.