Knowledge Base Wiki

This user develops user scripts;

This user is a They Might Be Giants fan.

This user is interested in compilers.

This user operates EnterpriseyBot on the English Wikipedia.

This user plays Rocket League.

#	This user chats on IRC under the nickname enterprisey.

This user previously used another account: APerson.

ET	This user's time zone is ET, but you wouldn't really know it from his contribs....

This user received the Editor of the Week award for the week beginning 18 November 2018.

• WP:Database reports/Active editors with the longest-established accounts
• Check out this title
• User:Jorge Stolfi/Templates that I sorely miss / User:Antandrus/observations on Wikipedia behavior / User:Guerillero/Quotes
• WP:IS example
• WP:Editor's index to Wikipedia / WP:WikiSpeak
• RF's celebrated meta-BRFA
• Special:MostInterwikis
• Vintage permalink
• WP:Editors have pride

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 https://blog.codinghorror.com/falling-into-the-pit-of-success/)
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)
3. "Signatures and talk pages are the Number One barrier to entry for new editors. Everything else is a fart in the wind." By Jorm, May 2021. He elaborates in his next comment.

• The massive @ifixcoinops@mastodon.social thread
  • The Improbable Island CoC
  • The Improbable Island 'Missing Stair' MotD (see Missing stair)
• "On a technicality" at eev.ee
• burntsushi in r/rust about shutting down discussions
• Cat Piss Man
• Former Reddit CEO on moderation and censorship (Thread Reader App) – note that I do not endorse the underlying worldview, but the observations on social dynamics are solid

And of course, the classics:

• "A Group is Its Own Worst Enemy" by Clay Shirky
• The Tyranny of Structurelessness

• User:Enterprisey/Less interesting links, for links that didn't make it to the section above.
• User:Enterprisey/Accounts, a list of all the accounts I have.
• User:Enterprisey/Pastebin, the pastebin I stopped using.
• User:Enterprisey/Miscellaneous, miscellaneous stuff.

• https://github.com/enterprisey
• https://gitlab.com/enterprisey
• https://sr.ht/~enterprisey