Thread by @polotek

Does anybody want to have technical conversations on Clubhouse? Not podcast style. I mean real in-depth discussion about experiences building real things. There's not enough of that, and there's a real opportunity with the clubhouse format.

Sounds like there is interest in technical discussion. Here are some completely self-serving topics I wanna talk about.
- When is it time to abandon your ORM?
- Was the redux pattern a mistake?
- Kubernetes? But y tho?

That's how Clubhouse is set up. You join a room centered around a particular topic. Most people are in the "audience" to listen. The people on the "stage" can discuss. People can move back and forth between audience and stage.

https://twitter.com/chuy_valadez/status/1350909086213107712?s=19

Clubhouse is actually very cool. It's just the fucking wild west right now. And they haven't added enough tools for moderation. So obviously a lot of people are on there doing way too much.

A few more words on safety if you're unfamiliar with Clubhouse.

The room moderators have full control over who gets onto the "stage". People can't just jump in and talk uninvited. And they can be muted or removed if they act up. The mods have to be diligent and trustworthy.

Nope. Not just you. Based on the words and actions of the founders so far, this is 100% the case. If the platform improves in the right direction, it will be because they are learning and changing how they operate. But the skepticism is warranted.

https://twitter.com/bcherry/status/1350910726815113216?s=19

One of the big problems I see with CH right now is "who gets to talk". It's set up so that the most intuitive thing is having a few chosen people on stage pontificating to an audience who can't respond. That's how it started and why it was an early draw for tech elites.

Black communities and others have pushed past that, and are using the platform in new and interesting ways. Lots of people on stage, rotating people in and out, etc. But that feels a bit too chaotic for me today.

One thing I recognized early on is that different people in the convo are operating at different speeds and wanna talk about different issues. So the conversation can tend to sprawl and meander. People can get lost or left behind. It privileges those who think fast on their feet.

I'm trying to think critically about how to get those things out of the conversation.
- A single convo that doesn't go off the rails
- An engaging convo with people who want to ask questions and dig deep
- One that feels inclusive for people to listen to. Not just supernerds

Okay, rather than over planning, I'm gonna try to set something up and see how it goes. Here's what I'm thinking.

Clubhouse technical discussion. Tonight 01/17 at 5pm PT / 8pm ET.

Topic: Was the redux pattern a mistake for frontend development?

- DM me if you want to be on stage with me
- DM me if you need an invite to CH
- DM me if you have invites to CH to give out

I'm pretty bad at organizing things. I apologize in advance if I'm not able to accommodate everyone who reaches out. This is an experiment more than anything. Hopefully there will be more opportunities.

Unfortunately it does not. I apologize that I don't know how to do something more accessible today. If this becomes a thing I put more effort into, I promise I will make that a priority.

https://twitter.com/NickColley/status/1350918076825559040?s=19

This is happening in about 35 minutes. But I'm already running into a few hurdles. Unfortunately I can't easily give out the invites I have. You can only use phone numbers (not emails). And you have to give the app access to your contacts. 🙄

https://twitter.com/polotek/status/1350917549798551553?s=20

I'm learning a lot just by trying to get this set up. Only US-based phone numbers work. This is turning out to be pretty inaccessible to most people. ☹️

We're getting started. You should be able to find the topic.

"Was the redux pattern a mistake for frontend development?"