Marco Rogers Profile picture
25 Jan, 10 tweets, 3 min read
This went pretty well. Thanks again to everyone who participated. Also huge thanks to @wwitzel3 who volunteered to take notes. I'm working with them to curate a bit, and then we'll share.

Let's do a quick debrief again.
Similarly to last time, we talked about for about an hour and 45 minutes before officially closing out the discussion. I didn't track how big the room got, but bigger than last time. Maybe 40+ people at the largest? Good crowd.
It felt a little tougher to moderate the room and rotate participants through. I think that's largely because I was doing it on my own this time. Some folks ended up waiting for quite a while before getting to share. I don't love that, and I think it's a common problem on CH.
Talking about the concept of state management was a good idea. It allowed us to talk about the problems we all need to solve, rather than some people being unable to follow because they may not be aware of a particular tool.
As a secondary goal, I'm interested in what it looks like to help people build strong mental models of what we do and how it works. I believe getting that understanding is so much more valuable than learning a tool. Especially since we have to learn new ones all the time.
What was really great is that we also started to get into team dynamics at work. e.g. "i have to work with this API from another team that is awkward and sends too much data". People were animated about sharing that experience. And it was interesting to see common themes.
I'd love to get into team dynamics more. It's tough to do while remaining respectful and constructive. But I think it would be hugely valuable for people to have a space to talk through those kinds of struggles.
Another good discussion point was how to choose the right technologies, and whether they will have longevity. For example, REST apis vs GraphQL comes up a lot. As time stretches on, nobody remains happy with the choices that were made.
Just to round things out, I think maybe I talked a little too much this time around. I try to throw it to other people often. But I have a lot of thoughts to share and I can take up a lot of space. I have to work hard to be mindful.
I'm still pretty unhappy with how hard it is to get people into Clubhouse. And I don't think the platform will make that easier in the near future. I'll probably to explore other platforms if I keep doing this.

Anyway, that's all. Thanks again for going this experiment with me.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Marco Rogers

Marco Rogers Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @polotek

26 Jan
Did y'all know that a lot of white people don't have the cultural concept of "real talk"? You know where you stop saying the diplomatic thing and tell people what's really going on. They just don't have it. You try to have a moment of "real talk" and they freak the fuck out.
It's one of the things that makes it difficult for PoC, and Black people especially, to form real trust relationships with white people. Y'all don't know what's going on because no one tells you. And no one tells you because you can't actually handle the truth.
I've come to understand that white people have their own seemingly convoluted way that they decide what's going on and what to do about it. I have a really hard time navigating those rituals. I think a lot of us do. And it damages our ability to be successful in white spaces.
Read 5 tweets
24 Jan
Let's talk about something else. I need to get ready for this, but I'm being lazy and burning daylight. Let's set some details again.
I want to continue the frontend discussion. Specifically I want to talk about "state management". It's phrase that gets used a lot. I think it's the source of a lot of complexity in frontend today. What's the right framing of a question around that?
Let's do 5pm Pacific time again. Nobody suggested big changes to the format, so I'm going to do it the same way and maybe we'll learn some more. I'm also open to a volunteer to do detailed note taking.
Read 8 tweets
24 Jan
Are we gonna talk about how people also do this to their managers when they're about to quit? No? Okay nevermind then.
It's not ignoring anything. A power dynamic doesn't mean your manager is not a person. Nor does it mean they are unaffected by your unexpected departure. Just say you don't give a shit about managers. It's okay.
Y'all: I've had so many different managers. They keep leaving.

Also y'all: Fuck how my manager feels!
Read 14 tweets
18 Jan
I want to get something off my chest. I’ve been spending today doing house chores while listening to technical videos and podcasts. After my Clubhouse experiment yesterday, I’m thinking critically about how we expect developers to learn and grow. And... it’s a mess y’all.
The quality of information out there is all over the place. The time commitment of doing all of this watching/listening is significant. There is so much content that is seeking people’s attention. And there’s no good way to know if what you’re gonna get is any good.
I’m not about to hop out here and put anybody on blast. People put a lot of effort into creating content. (I know because I started looking into doing it and I’m way too lazy for all that). The problem is there is no good way for people to navigate this marketplace.
Read 19 tweets
18 Jan
So this turned out pretty great in my opinion. I wanna do it again. Thanks to everyone who participated and those who showed up to listen. Thank you to my brilliant co-moderator @betsythemuffin.

Let me do a quick debrief.
First let me apologize again to those who expressed interest but were not able to get into Clubhouse. What I learned is that they have intentionally made it quite difficult to bring more people onto the platform. To be fair, it is a closed beta. But this was pretty disappointing.
I think at the maximum we probably had 30 or so people in the room. Not huge. I think it was good that the room stayed small enough that there was plenty of space for anyone who wanted to talk. I can imagine that not being true as the audience grows.
Read 10 tweets
17 Jan
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.
Read 17 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!