Slack README

About

The Slack is loosely connected to the Future of Coding podcast – people hear about it there and sometimes discuss episodes – but it's only one of many, many common touch points for the community, including Bret Victor, Douglas Engelbart, Alan Kay, Fred Brooks, HCI, HARC, Eve… For a fuller list of relevant people, topics, and links, check out Chris Novello’s Computer Utopias curriculum (particularly Week 3 & 4).

Purposes

  1. Sharing of ideas, debate, feedback, constructive criticism, and collaboration

  2. Encouragement, high fives

  3. Organizing IRL meetings and meetups

Getting Started

You can join the Slack here.

Upon joining the Slack, you get this automated message:

👋 welcome welcome @new_user_name! Head over to the Future of Coding Slack README for a 5 minute intro futureofcoding.org/slack-readme

So if you are reading this message, congrats on following the instructions!

  1. Introduce yourself in the #introductions channel (after reading the style guide)
  2. Join the relevant channels
  3. Be kind and have fun!

Channels

#introductions

Tell us about your background, how you got into these topics, and why you joined the Slack. Feel free to share past project URLs and tag other members you know.

#general

#meta

Discuss ways to better collaborate, improve this Slack, or resolve community issues. This is place to propose the creation of new channels.

#1-on-1s

Every 4 weeks, @donut will randomly pair everyone in this channel for 1-on-1 conversations. It's a good way to get to know others in the Slack.

#jobs

Post if you are hiring or looking for work. Work related to the future of coding is preferred but all paid opportunities are allowed. Don’t post more than once every couple of months about yourself or your company.

Locations

Topics

Style Guide

Threading

This slack discusses nuanced topics, so we have a strong preference for organizing conversations by thread. If you want to respond to someone, respond in the thread of that message. Do not respond with another top-level message.

When creating a top-level message, try to create it in a single message so that it's easier to thread off it. You can create newlines with shift-enter. It's helpful to draft longer messages in your personal channel @yourname channel.

Sharing your own work

When sharing your own work, start the post with "*Show FoC:*"

If you're asking for feedback, start the post with "*Feedback request:*" and specify the both the goal/motivation for the project (to avoid the XY Problem) and for the kind of feedback you want:

Loading Messages

If you have an inspirational quote to share, add it as a Loading Message.

Origin Story

This community was started by Irvin Hwang as a Google Group in mid-2017 for organizing NYC meetups, but was quickly turned into a Slack and taken over by Steve Krouse when Irvin got busy with his job.

Changelog

July 7, 2019

June 13, 2019

March 1, 2019

Feb 16, 2019

Jan 29, 2019

Jan 28, 2019

Dec 20, 2018

Dec 21, 2018

May 18, 2019

Proposed changes

Twitter

Many of us also congretate on Twitter. You can check out who I follow and what I like as a good place to join the conversation.

Others