Are you looking for the real computer revolution? Join the club!
The Future of Coding Community 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 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) and The New Media Reader.
On desktop, you can join the Slack community here. The link doesn’t work on mobile for some reason.
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!
|⚠️ This is a public, archived Slack, so treat it as a public record. For example, it is publicly accessible here now and maybe in other places in the future, including indexable on Google.|
The purposes of the Future of Coding Slack are:
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.
Share interesting links you’ve found and want to spark a discussion over. Ask questions, or
/poll the crowd.
Share your own projects for high fives or feedback (after reading the etiquette for sharing your own work)
Discuss ways to better collaborate, improve this Slack, or resolve community issues. This is place to propose the creation of new channels.
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.
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.
This slack discusses nuanced topics, so we have a strong preference for organizing conversations by thread. If you want to respond to someone, please respond in the thread of that message, and not with another top-level message.
When you have something to share, try to post it as a single message (rather than posting several messages in quick succession) so that it’s easier to start a thread of replies. You can create newlines with
shift-enter. It’s helpful to draft longer messages in your text editor of choice, and then paste them into Slack when you’re ready to post.
When sharing your own work, it’s a good convention to 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:
If you have an inspirational quote to share, add it as a Loading Message.
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.