Indoor enthusiast. Co-founder of Stack Overflow and Discourse. Disclaimer: I have no idea what I'm talking about. Find me here:
Remember how people in the year 2000 used to say how crazy and ridiculous it was, the idea that Anyone Would Ever Run Photoshop in a Web Browser? I mean come on. Oops [https://thenextweb.com/creativity/2014/02/24/9-browser-based-photo-editing-tools/] . One of my big bets with Discourse [https://www.
One of my favorite insights on the subject of online community is from Tom Chick [http://en.wikipedia.org/wiki/Tom_Chick]: > Here is something I've never articulated because I thought, perhaps naively, it was understood: The priority for participating on this forum is not the quality
What are the real world consequences to signing up for a Twitter or Facebook account through Tor and spewing hate toward other human beings? > Facebook reviewed the comment I reported and found it doesn't violate their Community Standards. pic.twitter.com/p9syG7oPM1 [http://t.co/p9syG7oPM1] — Rob
Way back in 2007, before Stack Overflow was a glint in anyone's eye, I called software development a collaborative game [https://blog.codinghorror.com/software-development-as-a-collaborative-game/]. And perhaps Stack Overflow was the natural outcome of that initial thought – recasting online software development discussion into a collaborative game where the
Let me open with an apology to John Gruber for my previous blog post [https://blog.codinghorror.com/standard-flavored-markdown/]. We've been working on the Standard Markdown project for about two years now. We invited John Gruber, the original creator of Markdown, to join the project via email in
In 2009 I lamented the state of Markdown [https://blog.codinghorror.com/responsible-open-source-code-parenting/]: > Right now we have the worst of both worlds. Lack of leadership from the top, and a bunch of fragmented, poorly coordinated community efforts to advance Markdown, none of which are officially canon. This isn'
I've long believed that the design of your software has a profound impact on how users behave within your software. But there are two sides to this story: * Encouraging the "right" things by making those things intentionally easy to do. * Discouraging the "wrong" things
Computer performance is a bit of a shell game [https://blog.codinghorror.com/the-computer-performance-shell-game/]. You're always waiting for one of four things: * Disk * CPU * Memory * Network But which one? How long will you wait? And what will you do while you're waiting? Did you see the
(The title references Shanley Kane's post by the same name [https://medium.com/tech-culture-briefs/a1e93d985af0]. This post represents my views on what men can do.) It's no secret that programming is an incredibly male dominated field [http://en.wikipedia.org/wiki/Women_in_computing#The_Gender_
I've expressed my disillusionment with to-do lists [https://blog.codinghorror.com/todont/] before. But let's try something simpler, a little experiment. What do you use to keep track of what you need to do? Hold it up, so I can see it. Humor me. Seriously! No
I find the Don't Read The Comments [https://www.google.com/?q=don't+read+the+comments] movement kind of sad. > Comments sections are frequently misogynistic, homophobic, racist, and very often POORLY WRITTEN. Why bother reading them? — Don't Read Comments (@AvoidComments) March 8, 2014
The Dan Ariely books Predictably Irrational [http://www.amazon.com/dp/0061854549/?tag=codihorr-20] and The Upside of Irrationality [http://www.amazon.com/gp/product/B003JBHVZY?tag=codihorr-20] profoundly influenced the way I design my massively multiplayer typing [http://www.discourse.org] games [http://www.stackexchange.com]. These books offer