MA 14: Open Knowledge
Apple • Spotify • Google • RSS • GitHub
What does it mean to be code adjacent? Shawn Wang joins Henry to chat about not just open code but open thinking with his experience in community managing, the idea of tumbling, moderating /r/reactjs, starting the Svelete Society meetup, documenting and learning in public, being historians of our field, fresh notes vs. awesome lists, the meta language, and adoption curves. (recorded in June) (54 min)
Conversations may be edited for clarity. (edit)
Henry: Hey, this is Henry. I have with me, Shawn.
Henry: Tumbling. You just mentioned this to me. Do you want to explain what that is?
Shawn: Yeah, okay. So hi and thanks for having me on.
Shawn: This is an idea that's kind of spreading a little bit, I heard it first from Joel Hooks and Chris Biscardi from the egghead crowd. And they heard it from Alex Hillman, who runs in the Amy Hoyt circle of sell products online and stuff. So if you're in that world, you know who these people are. If you're not, you have no idea. But anyway, I think this feeling is very common among people like us.
Shawn: So communities are important. We all get that. You can appoint a community manager to help to grow the community or coordinate events and stuff like that.
Shawn: But it's a very like draining job. (laughs)
Shawn: I've done it, right. You've done it.
Shawn: And every time you like try to put together something for the community, they might participate, but then they don't seem to really carry on that momentum. It's up to you again and again, and again, to get things going.
Shawn: So Alex Hillman, who wrote this blog post, was trying to popularize this idea of an alternative, which is tumbling.
Shawn: He also made the analogy, if you're community manager, you're like a cruise director and a single point of failure.
Shawn: Everything relies on you to get going. Everything relies on you to start and to organize schedules and stuff like that.
Shawn: Whereas, his idea of a tumbler is a person who makes things happen.
Shawn: In particular, a professional entertainer, a comedian whose function is to encourage an audience, guests at a resort, to participate in the entertainment activities.
Shawn: So you kickstart things, but then it's like a sustainable nuclear reaction between the participants in the community.
Shawn: Which is like, that's nice, right? Like I don't have to do everything.
Shawn: I haven't seen this online that much.
Shawn: So it really takes some talent in terms of community management to kickstart a many to many conversation, instead of many to one conversation with the community manager in the center of everything.
Shawn: So this idea of tumbling. I think it's an interesting word. That's why it catches attention. It doesn't really tell you how to do it. I mean, it'd be a good idea.
Shawn: I think it's a good goal though. For example, one actionable step is to remove yourself from being a blocker on things, right? Let people self-organize. Give them the power and trust them with the responsibility.
Shawn: I think you've had this of other people that you chatted with. Give responsibility early right, and you see them start to take charge and grow into their roles.
Specific, Limited-term Maintainer Roles
Shawn: One of the other things that, I think I was watching a Nadia talk. And she like started this chain of thought in me. I'm sorry, I can't remember which talk it was.
Shawn: But basically, you know how we have these roles, like maintainer of an opensource repo? That's so broad, and that used to be the only role.
Shawn: And now we have like write, maintain, admin, whatever. But then we also have triage and some smaller roles that only triage and do other sort of community manage-y stuff. So I think it's interesting.
Shawn: What if every project had a maintainers.md and then we separated the role of a maintainer into these separate roles and then people could sign up for that. And it'd be well expected what each role would do. And there'll be like a limited term. And then once that term is over, then we kind of just vote in the new ones.
Shawn: It's probably not voting. It's just like whoever wants to do it, but it's like a rotating thing. It's not the same person and you're not taking it on for the rest of their lives.
Shawn: It's kind of little bit like how I guess golf clubs and social clubs run. They have limited terms and that's great. Even the president of the club, right, gets to cycle over and then you can see past presidents.
Separation of Maintainer Concerns
Shawn: And that's a nice thing to have done, but you don't commit to it for the rest of your life.
Shawn: So I've been calling this idea, separation of maintainer concerns, but then also like it has this like term limits.
Shawn: What do you think?
Henry: Yeah. I like that. It's sort of deals with a lot of different issues at once.
Henry: One that you just pointed out now is this idea that you have to maintain something forever. And that's not necessarily a bad thing.
Henry: It's just that the assumption is that you need to do that. So people that are trying to get involved, they're like, Oh, if I start, I'm going to have to do this forever. And they don't want to commit to that, right.
Shawn: Well, sometimes I might not get involved because I'm just going to assume you're you're in charge forever. So I'm just going to just find something else to do.
Henry: That's true too. And there's this pattern of whenever new projects come out, all these people just show up out of nowhere that were capable of contributing before, but because it's new, it seems like it needs a lot of help, but all the old projects just need as much help as before too. It doesn't seem as like cool or fun.
Henry: What you said, everything's under control. Even though on the inside, it feels like everything's on fire sort of thing, right?
Babel W18, like YC W18
Shawn: Yeah. It could be like a thing that we formalize.
Shawn: You know how Y Combinator companies, they have like a batch, like I went through Y Combinator Winter 18. So for the rest of my life, I just say like YC W18.
Shawn: Or recurse center, you know, like RC W18 or whatever.
Shawn: What if we had like Babel W18 and I served as X of Babel for that term. And then I moved on. And someone else did that after me. And that's totally fine.
Henry: Yeah, I like what you said about differentiation of roles.
Henry: Maintainer is too broad and because it's so vague, people have their own assumptions on what that means. It limits what people can get involved with.
Henry: I think when people are getting into programming, they don't know what's possible. So I think that causes them to not want to get started.
Henry: We need to give them the concrete things, not just writing code, but all these other things and maybe giving those a name is a good thing, right?
Shawn: I mean, triager. Repro-er. I haven't thought this out.
Shawn: This is like a blog post that's been sitting on my mind for like a year, and I haven't done anything.
Henry: I know you probably don't consider yourself a maintainer, but if you're the one managing the subreddit or if you're the one that's making videos about some project, those are all parts of maintaining the community, right.
Shawn: Yeah, I mean, I don't have a name for what I do, but I think it's important. I think that code only goes so far, and I think that communities around code matters.
Shawn: And I think that people who can sort of manage between both actually do very well. You know, there's an amount of self-interest in this. I'm not doing this, like for the community.
Shawn: Because I've been so involved, I know everything is going on in React. If anything that I want done, I don't have to be an expert in everything. I know the experts on everything, right. So I can just call them. That's great.
Henry: Yeah, that's its own like skill or just knowledge that it's important.
Becoming a Moderator for /r/reactjs
Shawn: Yeah. Okay, so we can talk about the subreddit thing. So for those who don't know, I am one of the moderators of the /r/reactjs subreddit.
Shawn: I joined when we were maybe 30, 40,000 people, and now it's coming up to 200,000.
Shawn: And that's not me, right? That's that's just like the growth of React's popularity. I actually charted it once and it's round about 70% a year growth every year across GitHub, NPM and React reddit and what have you. So it's just an organic growth from people learning React. Feels like React is taking over, but actually there's tons of people who are still learning, right and still getting started.
Shawn: So I was an active moderator for two years, ish. I've been on reddit for like two years before that.
Shawn: And then I only got the job because there was some like framework war that was brewing.
Shawn: And then Dan Abramov was telling me.. There's some like nasty comments about Vue or whatever in the React community.
Shawn: And he was like, why don't you shut it down?
Shawn: And I was like, Dan, I don't have.. I'm not a mod. I don't have the ability.
Shawn: And then he's like, now you are.
Shawn: And, I thought it was a great opportunity and I enjoyed it. I'm on reddit anyway, so that bought me into reddit even more.
Shawn: The challenge has been sort of trying to get active participation.
Shawn: Trying to balance beginners and advanced people, because we all share the same board. It's just one message board that's just voted.
Shawn: So sometimes there are a lot more beginners in there. So you just get a lot of beginner stuff voted up.
Shawn: But then the really awesome stuff, like there are very advanced people there who have really good comments and conversations, and we need to encourage them and to make them stick around.
Shawn: So it's this weird balance of like are we beginner reddit today or are we like let's get deep into details, reddit, you know?
Shawn: And moderators have very limited control, because the mob just votes whatever they want.
Shawn: The only thing that you do, you know, you can prompt activity, right?
Shawn: You can post discussion topics, you can post like surveys, you can post job boards, like who's hiring, right. That's very popular. So stuff like that.
Shawn: But ultimately the conversation comes from the community and then your main job is to like shut off toxic elements.
Shawn: So that's what Reddit is basically for me.
Learning with "I Promise to Answer Every Question"
Shawn: I also started like a beginner Q and A.
Shawn: Basically, it serves as a sink for all the Q&A questions that otherwise would be posted elsewhere. And then it would make the whole thing, very, very beginner.
Shawn: But then also, it was a very good learning exercise for me, because I would just promise to answer every question.
Shawn: And that just gets you very good at answering questions.
Shawn: And then if you answer enough questions, you can see that you're repeating yourself, you make it a blog post, and then you can just like copy and paste, right.
Shawn: Actually, if anyone is looking to get started in React or just any technology, you just go answer questions enough. And then the best questions become your blog post, and then you build your reputation that way. It's not that mysterious, right.
Henry: That makes sense. I know Logan, who was a core Babel maintainer, basically did the same thing except with Slack. We had our just real time chat and then he just answered people's questions.
Henry: And I did the same thing when I got started and it's not like we knew the answer, you just look it up and you have to figure it out yourself. So I'm a maintainer. I don't know them either. I have to look them up and then you figure it out.
Shawn: Yeah. Let's say probably take like a year to know everything that people usually ask.
Shawn: But I'm also very obsessed with history.
Shawn: I definitely go back in time, and more than most people that I know, because I want to know origins of things and I want to know how things started and all that.
Shawn: I think people should do that as well, because sometimes it makes it easier, actually.
Shawn: If you look at a project from the beginning, then you're like, Oh, okay. This is the central idea. And then it just like accumulated a bunch of cruft along the way.
Shawn: But it's fine. That's how that's all these things grow.
History and Memento Mori: A Time Before Git
Shawn: But it also reminds you, you know, this like Memento Mori thing, like all things die or all things must pass.
Shawn: People don't know that git is only 15 years old. There was a time before git.
Shawn: And VS Code is five years old, you know, and there was a time before VS Code.
Shawn: But it also means that five and 15 years from now, we would be doing completely different things.
Shawn: That the presence of like, this is a special moment, but like not everything is fixed.
Shawn: Things can improve. But also like things that seem like a sure thing right now may not be.
Shawn: And I think I don't know what to do with that.
Shawn: You know, that's just like sobering and it helps you be grounded in like everything that you do.
Henry: Yeah, I think this aspect of caring about history, that's related to all this stuff I've been trying to talk about on the podcast.
Henry: Like people that care about archival and preservation, even the thing we talked about with Jordan, and he's trying to preserve the aesthetic of Windows 98.
Henry: Or people trying to preserve the artwork in museums, right. How do we do that in code? Are we even doing that, right?
Shawn: You can ask the creator.
Shawn: They like know things that happened before. And they're like, we were not going to repeat that again. So that's good. I don't have a problem with that.
Shawn: I do wish that every doc, every project had like you know, how this was made.
Where's the Story of How Projects Get Started?
Shawn: I was thinking recently about how little code gets documented.
Shawn: Like, we don't really know what Tobias Kopper's was thinking when he made Webpack.
Shawn: We have some reconstructions based on like podcast interviews and stuff like that, but like nobody ever like stopped and like wrote it down.
Shawn: It's just like, it just became a thing.
Henry: Right. And even now I want to write down a lot of stuff, but then I don't want to put it on the docs cause I don't want it to be like official. It's just like this is what we're dealing with.
Shawn: Yeah, but you can tell the story in podcasts and stuff that people pick it up, you know?
Shawn: Okay then, you know, even for Babel, the primary doc for Babel's origins is Sebastian's like 2016 year in review.
Shawn: It was just like, that's it? Like, it's just one of the most, you know, important..
Shawn: I want to know the journey. I want to know the pain. I want to know like the things that you tried and it didn't work, and then why it didn't work.
Shawn: Cause like someone else is going to try it and no one writes it down. So it's sad, but whatever.
Henry: I mean, there's so many of these things.
Henry: Like even us switching from GitHub to Phabricator, that was a whole thing, you know, like there's all these little, not incidents, but just events that happen that we learned something, but we don't talk about it. What you said, other people probably doing the same mistakes.
Shawn: Yeah. I mean, look, everyone's busy. I don't blame them, but I just wish that there were more.
A Culture of "Document Yourself More"
Shawn: And I feel like if we instill a culture of document yourself more, it helps historians like me, but then also it helps people get contributing. Cause they know the philosophy and all that.
Shawn: Like right now, even like Sebastian is making this almost the same mistake with Rome, like everything's in his head.
Henry: Yeah. What you're saying about culture is like, we're so far focused on making the new release or making it faster and less code size. Which is all good.
Henry: But at the same time, that same person that's doing all that, they're not spending the time to, like you said, write down their thinking, because it's hard to write down your thinking and you kind of just want make it work. And there's only one person.
Henry: Maybe it's similar to the whole community manager thing that is also a blocker on all of these different things. And not that they don't care about these things, I'm sure they want to do it, but just, you feel overwhelmed because of all the possible things to think about what's on your mind. I don't know what to prioritize all the time.
Shawn: I don't know. I tend to think that solution's pretty simple.
Shawn: Just like write more.
Shawn: Just be okay with like, this is what I think now, I might change my mind. I don't know. But here it is.
Shawn: We're always on Twitter so much. Like it's a form of sharing what I think, but like not really super committing into it that much. That's fine.
Henry: Yeah. I think maybe we could talk about that a bit. Similar to code, you don't want to commit it. And it's like, why do I feel like I can't put it down on paper sort of thing.
Shawn: So that's, I guess that's why I blog. I don't know. It helps you get into dev rel.
Shawn: That's the other part of my life I've kinda gotten into. And then obviously that also got me into teaching mainly for egghead, but I've done some other workshops.
Shawn: That's pretty good. I highly recommend people do that. It's kinda weird.
Learning Gears: Explorer, Connector, Miner
Shawn: So I call these learning gears.
Shawn: There's the explorer gear when you don't know what you don't know, and you're just going around and exploring and then taking notes for yourself.
Shawn: And then there's a connector gear where you're like teaching what you know.
Shawn: And then the final gear, it's either miner or builder. I think I've settled on miner. So it's like, when you struck gold, you should dig here. And then you just go.
Shawn: And that's when it's like, okay, no one else is doing this. I gotta do this. I'm abnormally good at it. I'm abnormally obsessed by it. I should just go all in and do that as like a form of R&D.
Shawn: When you're like a PhD student, you're like trying to push the boundaries of human knowledge, right. You know, ideally.
Shawn: I'm sort of like between explorer and connector. I look for stuff that I don't know. I learned that, and then I teach it. But it's not special. Like everyone can do it.
Shawn: But like some people really focus in, like Evan You, right? He found a thing. And it was like it's Vue. And he was like, I'm just going to go all in on it. And then the people like reward him by helping him right.
Shawn: I think when you have something that you really want out of the world, it's almost like the universe that conspires to help you.
Shawn: If you have like a general.. I wish things of just generally better, like that's not something that people can rally behind. But if you have a very specific vision, then that's something that people can get around.
Shawn: That's the kind of thing that I see in Rich Harris. And they can get people to come along with that vision, with the docs and the speaking that they do.
Shawn: It just seems like pretty inspiring.
Finding A Vision People Can Rally Around
Shawn: And I'm looking for that. I haven't found that yet.
Shawn: I always feel like, you know, cause I'm known for non-technical things. I'm known for like, okay, I manage the React community, whatever.
Shawn: I speak a lot or whatever, but it's not really super technical. It's just like how to like, be super noisy as a dev.
Shawn: So I'm looking for my thing and I still haven't found it yet, but I found a bunch of small little things along the way.
Henry: And you want that specifically to be technical.
Shawn: I mean, it would be nice. Just cause like, you don't feel like a real dev if it's not technical.
Shawn: But like the world seems to want me to do more nontechnical stuff, especially like with this book that I'm doing, because that's definitely been the most successful thing that I've ever written or said, which is kinda sad, but like, yeah, I think it's okay.
Shawn: I'm comfortable leaning into that. I also know that like, I want to do more, and I don't want to be only defined by the non technical stuff.
Shawn: So that's kinda what I'm like. I want to adjust the other way now.
Henry: Yeah, it's funny. I kind of.. It's sort of like the opposite for me. I've been doing all this technical and I'm trying to like, not not do technical stuff cause it's all technical in the end, but you know, how do I do sort of more on nontechnical?
Being Code Adjacent
Shawn: to code. You need to know how to code, but then you're like next to it.
Henry: That makes sense. Cause I wouldn't be able to maintain Babel if I don't know anything about compilers, I need to know something about it.
Henry: Just to think out loud there, to me, it's sort of like, is it even worth our time to spend all this time trying to make all these things faster when it really doesn't really change what our product is about?
Henry: Maybe the education stuff is more important in the sense, not really for Babel. It's just like, how do we get more people to understand ASTs, compilers, tooling, no matter what the tool is, right.
Shawn: So I think that one of the things that I'm interested in as well, which is kind of like, anti-Babel, which is this idea of collapsing layers, right?
Shawn: We went through this phase of every tool does one, one job well.
Shawn: But then it turned out that there's like 10 different config files in my repo. I don't know what they do. And they kind of don't work super well with each other.
Shawn: And it's like, okay, are we due for like a consolidation where everything just gets done in one pass? Like we know what to do now, we've kind of like explored a bunch of things.
Shawn: That whole Unix philosophy thing. That's good because they're small, they're easily maintainable. You can swap them out for other tools if you need to.
Shawn: A typical like production repo would have like 10 different config files in the top level of the repo. The VS Code won't really work super well with Prettier, with Babel and ESLint.
Henry: Yeah. I think about that too. It's not really about your individual tool because in the end, no one's going to use it by itself. So you kind of do have to know about every other tool anyway, no matter what you maintain.
Henry: What would it look like to be a maintainer of multiple projects, but then I guess the easy way out, in a way, is just make it all one.
Shawn: And that's what Sebastian did. I don't know. I think it's interesting. It's definitely above my pay grade.
Cheat Sheets and Awesome Lists
Shawn: So I think that the things that I focus on in my scale are open source knowledge. And that's probably the other thing that we can talk about, the cheat sheets that I do.
Henry: I guess it's just like, why did you start doing it? Why do we call them cheat sheets in particular? Are they just awesome lists or readmes,
Shawn: So, first of all, I feel like a lot of awesome lists become not awesome over time. Well, I mean, there's a process to add them, but there's no process to delete them, right. You're not going to come in like, okay, this repo is not awesome anymore.
Henry: No, I think that's a super interesting point.
Henry: It's almost like when we talk about like CSS, it's really hard to remove it, right? You don't want to like prevent someone from adding their awesome link.
Henry: And then later you realize that it doesn't fit with this whole thing and you can't. And it just gets bigger and bigger. It sounds like any code, I guess.
Shawn: Yeah. But the goal for this was actually more than just a repo of links, right? That's what awesome lists mainly are, they're good for that kind of surfacing.
Shawn: So I kind of compare it to Yahoo versus Google, right.
Shawn: Old Yahoo used to have humans who just like manually index the entire internet, right.
Shawn: And then Google trained us that you have to type it into the search box. And then you find the top 10 blue links.
Shawn: But it turns out that it's actually pretty easy to beat Google at surfacing the super relevant things, because you as a human know how to organize better to your domain. Google only has the template links.
Personalized Docs, Documentation Levels
Shawn: So this is kind of like my way of like organizing information. But the other element I want it to reflect was that it's personalized docs, right?
Shawn: So every project tends to have one set of documentation and that's fine for a certain project size. But actually I have this whole theory of documentation levels.
Shawn: When it get to another level that's big enough, there's like weird use cases that the main docs will never cover. Just never, right.
Shawn: So the way that I got started with the typescript thing was I got my first dev job, right. I went through boot camp. Like I graduated, I started my first day at the new job.
Shawn: And then my boss was like, do you know, TypeScript?
Shawn: And I said, no. And then I spent like six months, like struggling.
Shawn: And then I was just like, okay, I'm going back to my old code, to other files to copy and paste and then copy it to a new file just to make a component. I should probably like pull these out and then paste it in somewhere as a cheat sheet, right. So like it's not just links.
Shawn: It's also like copy and pasteable examples of common things that you're going to use. And the reason that React is never going to document in TypeScript is cause they use flow, right.
Shawn: And the reason that TypeScript is never going to document React is because they serve TypeScript. The TypeScript docs serve TypeScript users who are coming over from Node.js And just general JS Land. They don't have anything React-specific.
Shawn: So I found the hole where it was just like an intersection of React doesn't do this TypeScript doesn't do this, but there are a lot of me who are like React and TypeScript people.
Shawn: And why not just create the docs for us? And so like it started copying pasting, and then now a whole bunch of it's like been translated into two other languages and it strikes a nerve because it's underserved.
Shawn: And I think people need to get over this idea of like one single doc for that domain end those story. Like there can be different docs for different audiences and that should be totally fine.
Henry: Yeah, that makes sense. I guess it's similar to note taking and your own knowledge bank. And the idea that some of that you don't even need to share, but it's good for you just to have.
Shawn: Yeah. I mean, I share by default, and there's definitely a lot that I don't share.
Shawn: I take a lot of notes in one note and stuff like that, but on thematic stuff that I know other people will have interest in, I might as well share it. Because they actually helped me out and improve it and stuff like that.
Shawn: So I've been taught TypeScript by people at Microsoft and Uber and Airbnb and other places cause they PR stuff in, and then I have to learn from it, you know?
Open Source Knowledge, Proof of Work
Shawn: So I kind of call it open source knowledge.
Shawn: And it's the whole idea, open source code is better than closed source code because there's more people looking at it. It's easy to contribute. You know, open source has clearly eaten software, right. But the way that we treat our knowledge is very close source.
Shawn: Even this recent digital garden movement. It's all closed.
Shawn: No, one's sharing their knowledge.
Shawn: I mean, some, but they mostly want to share like the finished products.
Shawn: But for me, it's very easy to just put up a markdown file and just go like, Hey, you're all devs. This is a markdown file. You know what to do with markdown files. Just, you know, move stuff around, right.
Shawn: It's very like informal. I mean, I'm the curator, right? Under my name and all that, but people get value just cause like they can contribute what they know, but then they benefit from the rest. It's exactly the same as the open source code project.
Shawn: That's really good for one thing, but I find it helpful to establish expertise over time.
Shawn: Like when I started out, I was a complete newb. And then people could see that I was a complete newb and then they could help me. And then over time, by the process of having answered a lot of questions, I became less of a noob.
Shawn: And people could see that because all I needed to do was just drop them this cheat sheet and go, like, I made that.
Shawn: And for me, that's proof of work. So I'm bringing this idea in from cryptocurrencies and blockchains and stuff like that.
Shawn: The reason that the way that we interview is kind of like broken, you have to perform within a small interview window of I dunno a day, right.
Shawn: And then like, hopefully you serialize your experiences down to a certain format, like on a resume or in like 30 minutes. A technical interview or like a conversation in a fit interview. And then they like deserialize it from like what you say.
Shawn: And they'll be like, okay, I can see this person performing in my team. And that's it.
Shawn: And that's fine. That's the normal way of doing things. But I have had people interview me and they Google me in front of me and they can just instantly see all the work that I've done and know that I'm legit and it's like not fakeable, you know?
Shawn: And I'm not bragging, it just is. You can verify instantly because it's open. Whereas everyone else, if your work is closed, you cannot verify.
Shawn: So you have to do like reference checks, you have to do technical tests and what have you. And it just kinda sucks in general.
Henry: And it's happened over a long period of time, so it's not like people that just literally just copy paste someone's repo and then remove their attribution or increase their contributor counts.
Shawn: Yeah. I mean that's a little bit of like what Twitter is, right? It's a permanent hallway track.
Shawn: My new job, do you know Nader Dabit?
Shawn: You probably do, he knows everybody. He knew of me. And I knew of him for two years before we started working together.
Shawn: Right. Like at that point there's just nothing to hide.
Shawn: I'm sure there's stuff that he didn't know about me and stuff like that. But like most of the time, you've seen each other interact, how you behave. There's there's no like question of like, this is a total stranger and I'm inviting them into my team for like two years or four years, whatever.
Shawn: There's a lot less risk if everything's like open and it's instantly verifiable and you can see them work in public. And it's just a really nice thing to have. So I don't know. I have a lot of complicated thoughts about that and I try to write it down.
Henry: Yeah, my job at Adobe, same thing. They found me through open source and I still had to do the interview, but I think maybe trusted that..
Shawn: Like you kind of coasted through, right? You were like, they have things apart from this interview to judge me on.
Find the Intersection of Two Communities
Shawn: So that's the TypeScript thing. I'm planning to turn that into like a course someday. I definitely got lucky with that one, didn't really do much to promote it or anything.
Shawn: But I think that intersection, a pretty good formula for people if they're listening too and they want to do this, is to find the intersection of two big communities, probably underserved.
Shawn: Cause like each community has their own official set of docs. They won't acknowledge the existence of the other. Go target the intersection, and that's about it.
Henry: Right, you can definitely take the initiative.
Shawn: They just have different priorities, right. They're trying to maintain their thing and they don't have you at heart and that's fine.
Shawn: So I basically extended that approach to design. So I called it spark-joy, and that's just like a collection of design tools and that one got picked up by Addy Osmani. That one got attention, 'cause Addy just tweets really awesome stuff. So that was probably like one of the highlights of my like open source knowledge career.
Shawn: My designs suck, but I think that there's a market for design, for developers like me, who know they suck at design, but they want simple tricks.
Shawn: And there are other people who do that, but there's nothing stopping me from collecting my own list of stuff, right.
Shawn: So that's what spark-joy is about. This one's not an intersection. This is just like my take on people like me on something that's super popular, which is designed for devs, always sells out whatever.
Shawn: And anytime some designer goes like, Hey, what if I did a course on design for devs, devs just eat it up right there. And they never use any of the things that they learned.
Shawn: So this one is like biased where it's for me. I know some things about front end, but I don't know design, so here's my list of things that I use all the time.
Henry: Those are all things that you like personally really want to learn about. So it's not like they just came out of nowhere. It's just,
Shawn: Yeah. I'd say was less serious about that. Cause like design was never like a big part of my job, but I probably try to make it more, I don't know.
Documenting Underlying Assumptions
Shawn: And then this CLI cheat sheet. I was asked to make a CLI. I was maintaining the Netlify CLI because some guy left, then I took it on and then I didn't want to change my job to be a CLI engineer. So I asked for other people to be hired, to take over that job so that I could keep my existing job.
Shawn: It's an important thing to like, look ahead to like what you're painting yourself into, in your current job. And if you don't like that, then you have to pivot. Before you have no choice. It's just like unfortunate that people are pigeonholed into undesirable things within a company. And then once you're in there, you kind of have no way to leave and it's just kind of nasty.
Shawn: But anyway, like everything is a CLI and I think people don't understand that even Babel's a CLI. We all use the same set of tools and no one ever documented them, so that was CLI cheat sheet.
Henry: Yeah. There's a lot of assumptions that people have that if you're in it, you know it, but no one writes it down.
Shawn: Like, Sindre knows all this stuff, right? Like the kind of stuff that he does, he knows all of this CLI utils goodness. Right? Because he made most of that, but he doesn't write it down. He just like, open-sources yet another library. And people have to go use this library or they use a competitor library.
Shawn: But then we just, I don't know why we use it. So might be a good idea to write down. I don't know.
Shawn: The last thing that I have you listed here is Concurrent React notes. So I'm sure you know, this like whole hoo hah about Concurrent React? It used to be Async React, covering React Suspense and time slicing, now it's just Suspense.
Shawn: Used to be a super exciting thing in React. Now it's just super boring.
Shawn: But I took it on myself to like be the central repo of knowledge for everything new in React, and I called it like fresh-async-react at the time.
Shawn: So the fresh repo idea was like a twist on Sindre's awesome repo. So awesome repo just like lists things that are awesome and maybe less awesome over time. Right.
Shawn: Whereas fresh is like for things that are new and constantly evolving. So actually chronological order is more important than alphabetical or categorical order.
Shawn: Chronological means, okay, things that are three months ago, no longer relevant. So let's just delete all this stuff. So let's just like, keep it fresh. So that was essentially what I was doing there.
Shawn: And then it became Concurrent React and became not so fresh anymore, so I just turned it into notes. And these were the unofficial documentation for Concurrent React, and then they actually released the beta. So then I archived it.
Shawn: And it's good to have projects that end. It's good to give closure to yourself, but then also to the people who might see it in future and go like, is this still maintained?
Henry: I guess that's like history as well.
Shawn: It's history! It's still there.
Henry: It's still useful to see like how people were thinking.
Shawn: Yeah so cheat sheets are like one way where it's like collaborative. I have an open source license, anyone can fork in and contribute and whatever.
Starting a Meetup: Svelte Society
Shawn: And then I also do a lot of real life community work. Cause like cheatsheets are kind of ad hoc on GitHub, but the real life things started with the Svelte Society stuff.
Shawn: So this one was because like you, me, Rich Harris and a bunch of other people are all in New York and like we don't meet up enough.
Shawn: So there was going to be the world's first Svelte Meetup in London.
Shawn: And I was like, we have Rich Harris in New York. We should have a New York meetup.
Shawn: So I realized this with one week to go to the London meetup and I was like, we have to beat the London meetup.
Shawn: So I just like put out a call and I was like, well, we're having a meet up on this date?
Shawn: I don't have a venue. I don't have a time. I don't have people.
Shawn: I don't have speakers, but we're just going to meet up and Rich is going to be there, cause I'm going to drag him there.
Shawn: And then like stuff got together because like you have a specific want, right? We are going to have a meet up before London.
Shawn: And people just like helped out. Tierney chipped in with the Microsoft space and people helped me promote it and get speakers and stuff like that. And it turned out really well, you can organize a 50 person meetup in one week. Just, just like that.
Shawn: Yeah that was pretty fun. And then we moved online, right? I think it was more building out the Svelte community.
Shawn: Cause there was some on Discord and some on GitHub, but not really like people trying it out, talking about it, and then also putting it into toy apps at work, and then eventually production apps, right?
Shawn: Like if you want to grow a community, even in coding, you can write the most perfect code, but then if you don't see other people using it, you don't have a lot of confidence in this library or this framework.
Shawn: So you need some social proof. Things are going, things are alive in this thing. It's not just the side project of like one crazy Brit in the New York Times.
Keeping it Alive
Henry: What was it like, the difference between maintaining this meetup versus the first time. It's one thing to just be like, Oh, let's just meet up. But I want to continually do this.
Shawn: Yeah. I mean, the excitement definitely dropped off. We probably went from like 50 to like 30, but it's still there, you know.
Shawn: And then it's the classic difficulties of getting speakers and doing logistics and stuff. I was definitely kind of like one person on that for awhile.
Shawn: I do the same thing that we should do in GitHub. I delegate and people want to volunteer for stuff, I give them stuff to do.
Shawn: But they don't stick around. You know, they're not that super committed to it right now.
Shawn: So they'll commit for one thing and then they'll leave.
Shawn: I'm sure you, you know, I did that for Babel. So but that's life. And then you as the community manager, you kind of have to like stick through that.
Shawn: And I think what really kind of bailed me out. It was honestly this Coronavirus, because I was already thinking, like this in person thing is really a mess.
Shawn: Cause I have to organize venue and then people and then do AV and then do talks. Cause no one else speaking. So I have to be a speaker.
Shawn: It's a lot, right. And it's super stressful and I don't get to enjoy it. I don't get to hang out with people and stuff like that.
Shawn: So I was already thinking of going online anyway, and then this Coronavirus thing happened. So I was like, Oh yeah, now we are online.
Shawn: I got really lucky in that, there are other people from Sweden and London who are, as interested in building a community.
Shawn: It's weird. I'm not even like super passionate about this. I just want to see if I can do it. It's just like a interesting challenge. Can you like take this thing which is almost there and then just like give it that push to become huge. It would just be like a fun thing to do.
Taking Part in Category Creation
Shawn: Like I don't even necessarily need to see Svelte take over the world or anything.
Shawn: I just want to see how far can I push it to make it a thing?
Shawn: Cause I saw it happen in Netlify where it used to be cheap, free static site generators. And now people are like, yeah, I'm the JAMstack person, right?
Shawn: But I saw category creation at a company that was kind of fringe. To the point where like, I wasn't even sure about joining them because I was like, how far does this JAMStack have to go? And now it's like people writing books and creating the careers and all that. And that's amazing.
Shawn: And that gives me a lot more confidence in like, things can start small. And with your help, they can get huge.
Shawn: And you just got to stick it out long enough and do all the dirty work of getting things in place that need to be in place.
Shawn: That's kind of what we're doing now. We had a big conference about 4,000 people attended, which is huge. I mean it's easier online, which was fun. Then we need to keep going with a site and everything.
Shawn: It's just like this, you know Cheng Lou, from the old React team? He calls it meta-language around the language.
Shawn: The core thing is always the language. Whatever it is, like Svelte, React, whatever. And then the meta-language is like all the docs, community workshop, meetups, conferences, whatever.
Shawn: That needs to exist too, cause that helps you get the most use onto the language. So I'm kind of building that.
Shawn: I've never spoken to Cheng Lou. I'm curious what he thinks about it now. Cause they definitely have that problem for a reason.
Henry: Yeah, I guess there's a difference between what we say and how it plays out. I can say a lot of things about Babel, but if it's still stuck the way it is.
Shawn: Yeah sure sure. He's super intellectual. He doesn't have to be the doer.
Henry: That's the interesting part of like, how do we take the theory and play it out? Like, how does it actually happen in practice and how do we live that out, those things that we actually believe are true, right?
Shawn: Yeah, it's hard. And I'm not the most qualified person to do it, cause I have my own problems as well, you know?
Shawn: I have my own like insecurities and need to, you know, fix my own situations and all that. So it's kinda like, you have to be a leader of people without being perfect yourself.
Shawn: Like you're not done with, you know, your own problems, but then you gotta like assume the community's problems as your own, and then deal with that as well.
Shawn: And it takes a certain kind of. Yeah, I'm sure. I'm sure you feel that all the time.
Henry: You know, it's funny when people are always asking me for advice like, Oh, I know how to maintain this thing. There's a sense where I don't really know either.
Henry: And maybe I've done it, but then I don't know how to word it. I don't even know how to express or it's hard to write down even which sucks because people want the advice. Like you kind of have to get into it and just learn through the process. Yeah.
Shawn: Yeah. I actually came up with this analogy when I was writing in the book.
Parenting and Figuring Things Out
Shawn: I don't know where I applied this, but I really liked this analogy even though like, I'm the worst person to use it.
Shawn: You know how like when people are parents for the first time, they have no idea how to be a parent. They have a baby, they come home from the hospital, they have a baby in their hands and they are like, shit this is real now. And you figure it out and guess what? Like hundreds of millions of people every year, figure it out.
Henry: You can read a bunch of books, you do a lot of prep work beforehand, but then when you finally get to it, you're like, Oh,
Shawn: I'm sure even the prep is completely not reflective of like what it actually is like, you know, like there's all these prenatal things and you got to read about it and then, but then you're like, actually, you know, you wake up at 4:00 AM every day for like three years. And it's just really hard, you know?
Shawn: It's this whole idea of like, you'll figure it out, if you commit to the thing and then you go like, this is my baby now. And it will die without me. And I can figure it out because other people figure it out. I just have to stick at it for a long time and try to do my best every day, you know.
Henry: Yeah. I think there's a lot of faith, honestly, that you need.
Henry: Not just in yourself, but just that this will work out, I guess. Otherwise, yeah, you kind of don't have any reason to continue, if you feel like you have to have a hundred percent confidence.
Henry: I guess it's the same thing with anything, honestly, like writing and hoping that people like what you say, you kind of have to go for it, right?
Shawn: Well, they're things that you can do, especially for writing in particular. I finished a book like about two weeks ago, and then now it's just like getting reviewed by people who volunteered.
Not Everything Needs to be in Public
Shawn: And I'm glad that they're reviewing it before it goes out to like everybody, right. It's good to have a small group that you trust that will just give you a real feedback. Cause not everyone does, right?
Shawn: Most people just want to see the finished products and then they'll they'll judge you good or bad based on your finished product. But your smaller group of like fans and friends and supporters and all that. They're fine with your unfinished thing and they'll tell you where you go wrong.
Shawn: So you really need that separation of like, Hey, you guys are my ingroup. You get to see like the early drafts. And then you work on it.
Shawn: Because as much as I tell people to like learn in public, be raw, and perfect's the enemy of good, sometimes it really counts to get it right on the launch.
Shawn: Sometimes when it's meant for a general audience, you have to figure everything out before you hit them. So do need that sort of review process.
Henry: I think that's good. Like there's writing, but then also just examples for our community with like Vue 3 and React Hooks.
Henry: They weren't going to do that in public when they're trying to figure out how everything works, they did it after they had all the docs and planned through everything.
Henry: I think a lot of people are like, why don't you do it in public? Isn't it open source, that sort of sentiment. And it's like, no, they're doing this for the benefit, because they don't even know what it is.
Henry: It's hard, cause like we want to be inclusive and like you said, be in public. But then how do we balance that with things that feel like they're more experimental and we don't want to bother people with things that aren't actually going to happen.
Shawn: Again, it's a question of size. If it's just you, if it's just like 10, 2,000 people who cares, you know.
Shawn: But when you're hitting like hundreds of thousands, a million. The mass population are never going to contribute. They only want to see the finished product.
Shawn: And they'll they'll shit on you for showing something that is like not fully worked out anyway, cause they'll just pick holes and stuff.
Shawn: Like when I heard that Vue 3 was being developed in closed source or whatever, I was like, yeah, that makes a lot of sense. And Evan got so much shit for that. And I think like, geez, these people just haven't really been involved in a real nitty gritty opensource thing.
Shawn: They just expect everything to be open. I don't know. I just have no sympathy for that.
Shawn: Communication is important. Once you have a process with doing a thing, but then you also have to communicate it well.
Shawn: I guess that's like where I'm sort of specializing because that's kind of my day job. But I think a lot of people maxed themselves out doing the code, design, and docs and stuff.
Shawn: And then they don't think about the marketing and there's actually a lot of marketing to do in tech.
CSS 4: Does It Even Matter if No One Knows?
Henry: Yeah. I was just thinking, we can add a bunch of features. And then you write a blog post about it and then nobody knows about it. And then a few months later, you're just talking to someone like, Oh, I didn't know that this was the thing I could have used it a long time ago. Like the fact that it's been there for years, it doesn't matter.
Shawn: So two interesting antidotes. One supports this idea. One refutes this idea.
Shawn: Okay. So the first supporting idea is this idea of CSS 4.
Shawn: Do you know the CSS working group and the transition from 2.1 to 3?
Shawn: So there was CSS 1, which is the original spec or whatever, then CSS 2 and 2.1, cause 2 made some mistakes.
Shawn: And then CSS working group kind of like got together and said like, Hey having like these big specs is a lot of work. Like we should break out into smaller groups and then work on individual specifications for individual features.
Shawn: So Grid was a separate feature. There's like CSS for voice there's CSS for more media queries and user preferences and all that. They're all these like small little, tiny groups. They splintered from one big group to individual groups.
Shawn: And then they were like, we will all move at different paces. So this is CSS Grid Level 1. And then this other thing we'll have like Headings styling Level 4. And we'll just proceed at different levels.
Shawn: So there actually is no CSS 3. It's just this marketing term that everyone got together and said like, here's the.. I don't even know what was in CSS 3, but here's a nice logo and everyone can upgrade their sites to CSS 3now, because it's also in line with HTML 5 and JS.
Shawn: You know, those like shield things like HTML, CSS, all the numbers, right. That was like a cool, coordinated thing just to get everyone to upgrade to modern tech. And it wasn't that modern either.
Shawn: And then the CSS working group was like, okay, we're done now. Now we expect you to keep watch on every single movement going on in each of our working groups. We'll just release it in separate cadences.
Shawn: Which like is great for them, right? There's this tendency of maintainers to optimize for themselves and then just like completely screw it on how the external image looks. Which by the way is my problem with monorepos.
Shawn: But then it just became like, I know that all these things are going on independently, but I can't keep track of them. So I'm just not going to use them ever. So they have this problem of exactly like you said, they had new features and nobody was using them cause they don't know it's ready yet.
Shawn: So now, after like probably five years of denying that there was a CSS 3. Now they're saying let's actually have a move back to market ourselves as having a CSS 4, even though it's not actually going to exist, we're just going to lie to everybody and call it CSS 4. And Jen Simmons is leading this charge.
Shawn: And two years ago she was like making videos about how there is no CSS 3. And so like, there's been a huge 180, purely because of marketing reasons. Just to get people to use CSS the way that its intended. They realized that, Oh, we over adjusted on how CSS is run, but not on how it's marketed and super interesting stuff.
Shawn: That's a tech marketing story that like I like telling now, cause it's super cool. It's CSS, man.
Adoption Curves: Focusing too much on the head
Shawn: So the other narrative that kind of goes against it. So it's like, okay. Design things to make it easier for the general public to consume, right. Because at the end of the day, that's what you're consuming them for. You're not consuming for the kind of people that goes to CSS conferences and know the intricacies of your spec, right.
Shawn: That's not the kind of people that you want to reach. I mean, sure, you want to reach them first, but if you want real impact, you have to reach for like the person on the street who has like five minutes out of every year to care about CSS.
Shawn: So then we get to Ilya Grigorik.
Shawn: Do you know this guy? He wrote high performance browser networking. I've never met him, but he likes seems like a legend.
Shawn: Anyway. So there's this like, you know, adoption curve in the population.
Shawn: There's the head. There's the fat body. And then there's the tail, right.
Shawn: And the kind of people that go to conferences are the head. The kinda people that spend their free time arguing about progressive web apps on Twitter are the head.
Shawn: You know, we just talk to the head all the time, right. And then we have all these like fancy benchmarks and shit.
Shawn: No one cares in the body and the tail, right? So we can create all these like really awesome feature lists and stuff.
Shawn: No one cares.
Shawn: No one's gonna use it until you simplify it, right. Like make it easy for them to use it. Cause they have other priorities that that is going on.
Shawn: Like we are in the body and the tail in others areas of our lives, right. Like I don't know, finance and the climate. And then I dunno. Yeah.
Shawn: So like, you know, we have to be humble and get out of our heads and just make it easy.
Shawn: And for him it was like, okay, even a movement like CSS 4 is not enough. Because that means that implies that people have to know about CSS 4 and you've got to go reach out to them.
Removing the Learning Curve with Better Defaults
Shawn: What's even better as far as he's concerned, is to do it for them, right.
Shawn: His example was image optimization.
Shawn: You can do conferences about image optimization. Hey, run your thing. There's like this SVG optimizer. And it's like 30% smaller. And everyone should do that.
Shawn: Then you just like do nonstop lectures and like build, build tools.
Shawn: And people still won't do it, right. They just won't.
Shawn: So it's kinda. It's very depressing. Cause like any learning curve is bad.
Shawn: And so for him it was like, this should be built into the platform. For him, it happens to benefit him, cause he works on Android Chrome.
Shawn: Let's just like have native inputs that just optimize the image when you upload images and it would just be optimized forever, with no code. Cause it's at the earliest point of entry.
Shawn: And he was like, we need to find things like that, that will really reach the body and the tail because they don't even know. They don't have to know.
Shawn: We've made it simple enough that we don't tack on this universal tooling that all developers have to like learn and maintain and use, because we don't fix the things at the source.
Henry: Yeah, no, that makes sense. If you don't need that feature, it should just be a default. Like that's just how it works and it doesn't even need to have a name or a concept, but then you have to figure out how to do that, I guess.
Henry: And especially if it's like with the tooling, you have to make a breaking change. So, yeah, it's hard to find a trade off.
Shawn: Yeah. I don't know either. These are all super new ideas to me. I just think they were fascinating. Cause I'm always looking for like, what's the paradigm shift that will just invalidate everything I'm using today.
Henry: No, that's true, we're always adding. I want to remove config, not add more or at least make it so that the..
Henry: What do they call it, incidental complexity versus essential.
Shawn: Fred Brooks. I need to read that book.
Philosophy of Technology
Shawn: There's so many great books. What's a great program.. You know, you read way more books than anyone I know, what's a great programming book and just like philosophy of programming or like history of programming.
Henry: No, I think that was good. I mentioned this a long time ago, but programming as theory building is like an essay. It's not really a book.
Shawn: Yeah, that's fine.
Henry: It kind of even goes back to what you were talking about, almost life cycle of code, you know, like life and death, rebirth, if you want to use that metaphor of programs. Just thinking about people and how they relate to code and the fact that it's about mental models and stuff like that. I hadn't been reading too much about like philosophy of code in that sense, but that was the most that I've seen for that kind of thing.
Shawn: Yeah. Do you think developers care? Do you think were like married to incidental complexity? It's like, we're paid to do that, right? Okay, I'm glad they're shitty tools because then you need to hire people.
Henry: You keep the job. I guess they're both true. No one's like intentionally be like, "Oh, I'm going to make a tool that's hard" or anything. That that would be weird.
Henry: But I think you kind of get used to how things are and how we see the things. Like our answer is the tool.
Henry: Maybe another book would be Tools for Conviviality. People mentioned that one, a lot.
Shawn: I've heard that one. I need to go look into that.
Henry: Yeah. He's really talking about like technology in general and the idea of tools.
Henry: He would differentiate tools where someone designed something specifically for someone to do versus sort of like a hammer where it's a tool where you can almost create your own ways of using this thing that the person that made it didn't even think of, right.
Henry: How do you create a tool, sort of like the web it's supposed to be, right? Like supposedly anyone should be able to make their own website, but then we create all this tooling so that you have to learn it and you have to go to school or you have to go to bootcamp.
Henry: In a sense he's actually arguing against like professionalization of anything, to that extreme. Or industrialization of things.
Henry: Because that makes things very the same, like everything is a product.
Spatial Software, The Mind
Henry: Have you heard of Dynamicland?
Shawn: Yeah, Bret Victor's thing right?
Henry: Yeah. I think for a lot of people, it seems too far off.
Henry: There's a picture of a bunch of kids learning in school and they're all in a circle on the table and they're all looking at like a tablet or a laptop instead of they're all looking at the same shared space.
Henry: Actually I see this now with the zoom, right? Like we're all looking at windows of people's faces. And then now seeing how people are trying to create more like spatial software is really cool.
Henry: Almost like games. I've seen some demos. Being able to like move around in a space. And that kind of gives people the freedom to do things differently.
Henry: Like with Google docs or Figma or even actual games like Animal Crossing and Fortnite. People are able to create something different cause they have a platform for it versus you can't do anything other than like, screen share and chat.
Shawn: Sounds like you want to go into VR.
Henry: I think that barrier for that just having to buy that and being expensive, you have to have another computer, you have to like wear something. I think that seems a lot far off to me than just like, at least starting off with something 2D.
Henry: I dunno, like one example I saw. If say you have like a stand up or something and you want everyone to like, talk about what they're doing in a zoom call.
Henry: Like everyone's face is in a different place. You can't even have an order to it, but if you're in a 2D space, you could make an actual circle and then you could just be like, Oh, let's go counterclockwise or clockwise. Just like in real life.
Henry: I think that presents a better way of knowing where people are sort of thing in this virtual space versus just abstractly everywhere, right?
Shawn: It's good. We kind of have that in Figma. I don't know if you play around with Figma. Like this idea of cursors that represent people. Then people can kind of move around and communicate.
Shawn: We can even express like frustration with like our mouse movements, which is pretty cool.
Henry: No exactly. I think it's fascinating seeing how people..
Henry: You give them the freedom or just ability to kind of express themselves.
Henry: Even with like the card game, where they can hover over the cards. And if you do it really fast, you can tell how they act.
Henry: Actually, this reminds me of the game that I was playing a lot in-person of The Mind, which I liked.
Henry: I don't know if I even talked about that before. I wanted to write something about this, but it's a very simple board game.
Henry: It's just, the cards 1 through 100 and you need to play them in ascending order. It doesn't have to be one, two, three, but like 1, 10, 23.
Henry: The catch is that you're not supposed to talk. So you can only use body language. And this is like an in person game. You're all in a circle.
Henry: I actually played this at a lot of conferences. Just brought it in. It's very simple to learn. You just have to play the cards in order, but you don't know what other people's cards are and then you can't say I have three, so you just have to have sort of like an internal clock.
Henry: And the spirit of the game is you're not supposed to like count or anything or come up with signals, but use body language.
Henry: If someone is leaning backward, you know that they're probably not going to go. If they're like kind of hovering over it, they're probably wanting to go next. You kinda just have to go with your gut, right.
Shawn: Yeah. And you have to learn and adjust for people who are too timid and too aggressive.
Henry: The game is interesting because it helps you empathize with others and it's a cooperative game, right? We're all on the same team.
Henry: Oh, this person went too fast. This person went too slow. It's hard to say. They're both true, right?
Henry: Like the person that was too fast has to learn to like account for it. The person that's going slow should learn to be faster.
Henry: And then the fun thing is when someone else is around and like, Hey, you should join in. And now that person changes the whole dynamic of how the timing works, right.
Henry: And you're only supposed to play with like four people max. And at the conference, you know, there's like 12 people or something.
Shawn: that was a good game. You brought it to React Rally and it was a lot of fun. Psychic.
Henry: And it's funny cause people are like, Oh, that's some kind of cult thing, you put your hands in the middle, and say the mind, right?
Henry: When we all put our hand in the middle, it's just to say that the timer starts now, but it's not like you're literally counting in your head one, two, three.
Henry: I don't know, like how do we create that sort of thing online?
Shawn: I mean, it's interesting that we care a lot about jumping between physical and virtual presence. A game is a very small community.
Shawn: I think we always figure things out first in games, and then we bring it out to the rest of society, you know?
Shawn: I always think about how game tech is always so far ahead of everything else, right.
Shawn: But it's good.
Shawn: Cause like, we pay for entertainment and entertainment eventually benefits us.
Shawn: So you can say like when you're playing your Xbox or your Switch you're funding R&D!
Shawn: Basic science. Yeah. When you buy smartphones, we are funding research into making the smallest chips and most power efficient chips in the world, right.
Henry: Yeah. Just the way people think about interactivity and design.
Henry: One of the problems that we have with tech is like the idea of presence and immersion and participation, then I think involving the person more is a good thing, sort of passive consumption, right. I think games help with that.
Henry: I mean, a lot of times it's very trivial, right. You just kind of clicking on things, but how do we make it so that something real is happening there.
Henry: Going back to open source, it's like, I don't know.
Shawn: Emojis are good.
Shawn: I think I was actually reflecting that probably one of the best ways of expressing without plus one everywhere is emoji. People can express a lot of things with just like five or six, whatever they give us.
Henry: I guess even pictures of memes, I guess that's why people like those.
Shawn: it says a lot
Henry: Instead of just like typing out something like good job. That's interesting.
Shawn: Yeah, cool. I mean I appreciate you having me on. We always have good chats.
Shawn: And it can ramble, but I think we all like are exploring these interesting ideas. And they're all kind of related and we're just kinda mixing them up, you know?
Shawn: So yeah, thanks for having me on.
Henry: Yeah, thanks Shawn!
Hope in Source
is made possible by the support of the community!
Consider becoming a sponsor today!
Discuss on Twitter