This user is a member of the Arbitration Committee on the English Wikipedia.
    This user has administrator privileges on the English Wikipedia.
    From Wikipedia, the free encyclopedia

    Golden Eagle (Aquila chrysaetos) - La Cañada, Ávila, Spain

    Hi! Welcome to my user page. I write tools, bots, user scripts, and sometimes articles.
    Wiki-tech-logo.svgThis user develops
    user scripts;
    They Might Be Giants New Haven 2009.JPGThis user is a They Might Be Giants fan.
    GNU Compiler Collection logo.svgThis user is interested in compilers.
    Robot-icon.pngThis user operates EnterpriseyBot on the English Wikipedia.
    Rocket League coverart.jpgThis user plays Rocket League.
    #This user chats on IRC under the nickname enterprisey.
    System-users.svgThis user previously used another account: APerson.
    ETThis user's time zone is ET, but you wouldn't really know it from his contribs....
    Editor of the week barnstar.svgThis user received the Editor of the Week award for the week beginning 18 November 2018.

    Interesting links[edit]

    Thoughts & quotes[edit]

    1. "To the extent that we make it easy to get into trouble, we fail." (Originally about API design, but applies to user interfaces too. By Rico Mariani, quoted in
    2. "[N]ot every argument or idea you disagree with has to be shouted down loudly. If a proposal (or a counter-argument to it) demonstrates value to enough people then it will gain support and can be refined into something that can reach consensus. If not, then it won't. Critiques of early-stage proposals in particular should be done with a goal of improving them, better understanding their motivation, or comparing them to alternatives. Comments that are closer to just 'voting no' on a proposal aren't really necessary.
      In disagreements, responding with new information is great, but try not to get in a mode where you are trying to convince specific people (or all people) that you are right and they are wrong. Focus on presenting your own ideas/needs/etc. as clearly as possible. Then people reading the thread (not just the person you are responding to) can judge competing arguments on their merits.
      For anyone who wants to [design new features], remember that the bulk of the work is not in coming up with ideas, but in building consensus for them. To succeed, you'll need to spend a lot of time on understanding other people's viewpoints and tweaking your designs and communication based on what you learn. (This includes any concerns from the people who would need to implement and maintain your feature.) This 'listening' is the part of the process you'll need to focus most of your time and energy on. If you don't invest in it, then the rest of your effort is likely to be wasted." (mbrubeck, posting on the Rust Programming Language Internals Forum, used here with permission)

    Links about moderating communities[edit]

    And of course, the classics:

    Other subpages[edit]

    Other contact info[edit]

    Committed identity: 72dfc03e516233d0c1f5426eca578e5efa435370ce35aef83b7fd24aa18bc0070b2f3150e8d77544d36c189d75d810d1ba89d63c4a0000f90073a9f3f6cb4cff is a SHA-512 commitment to this user's real-life identity.