How can we work together to achieve a common goal: whether in our code, cities, or infrastructure.
What's life after removing yourself from social media? Philip Gee joins Henry (the last in the "trilogy") to chat about LAT, life after Twitter. We discuss being irrelevant, forcing yourself to think about different things, treating a newsletter like email, restraining your growth, moving to the digital suburbs, engaging with the past, directing your attention and production, being particular and local, making it normal again to not have to create. (recorded in July) Transcript: https://hopeinsource.com/digital-death.
First chat (MA 7): https://hopeinsource.com/growing-old
Second chat (MA 15): https://hopeinsource.com/unlisting
Henry: https://twitter.com/left_pad
Headings:
Why would you choose to leave the public internet on your own terms? Philip Gee joins Henry (for the 2nd time) to chat about his recent choice to make a minimal public web presence after being on the web for many years. We discuss the logistics of removing social media (Twitter, Facebook, YouTube), moving to longer forms of media (podcasts, essays, books), making introductory content, recognizing different stages of your career, being out of touch, freeing your mind for the next thing, not being ashamed of previous work, taking time to reflect, and friction. (recorded in May) Transcript: https://maintainersanonymous.com/unlisting.
Previous Episode: https://maintainersanonymous.com/growing-old
Henry: https://twitter.com/left_pad
Headings:
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. Transcript: https://maintainersanonymous.com/open-knowledge.
Shawn: https://twitter.com/swyx
Henry: https://twitter.com/left_pad
Headings:
Why attempt to faithfully recreate the past? Jordan Scales joins Henry to chat about 98.css, design systems, being pixel perfect, accessibility, the Microsoft Windows User Experience reference manual, using VMs, MSPaint and Figma, whimsy and having fun with coding, creating satire at no one's expense, and even how Babel's Guy Fieri meme could of been Jeff Goldblum in another universe. Transcript: https://maintainersanonymous.com/nostalgia
Jordan: https://twitter.com/jdan
Henry: https://twitter.com/left_pad
Is the open source community a gift economy? What even is a gift? Maggie Appleton joins Henry to discuss open source as a gift economy (versus a market economy), why we participate in open source and exchange gifts, rituals and habits, patronage and crowdfunding, quantified self and disembodiment, our role in tech
Transcript at: https://maintainersanonymous.com/gift
Maggie: https://twitter.com/Mappletons
Henry: https://twitter.com/left_pad
How should we think about saving something forever? Jonathan Farbowitz (Guggenheim) continues the on-going discussion of software preservation with Henry in talking about the goals of museums, the hard (and maybe impossible) task of keeping something intact, norms and steps of conservation, comparing physical and digital artwork, the importance of authors in conserving a piece, emulation vs. language porting (rewrite), a discussion of legacy/dependencies/testing, and deprecations/breakages in environments/standards.
Jonathan: https://twitter.com/jfarbowitz
Guggenheim: https://twitter.com/Guggenheim
Henry: https://twitter.com/left_pad
In our pursuit to create products for the future do we neglect the past? Wendy Hagenmaier (Georgia Tech) discusses with Henry on the importance of maintaining our history, especially in software itself. They chat all about archival: what is it, what should concern an archivist, differences b/t physical/digital, artifacts/process, value/worth of things to preserve, struggles, places where archival can happen (personal, libraries, companies, museums), and our shared responsibility and knowledge.
Wendy: https://www.library.gatech.edu/wendy-hagenmaier
Software Preservation Network: https://www.softwarepreservationnetwork.org/fcop/
Henry: https://twitter.com/left_pad
Why play or even make games? Anthony Giovannetti (MegaCrit) joins Henry to chat building video game Slay the Spire with the community. They discuss games an a interactive medium, immersion, player incentives/tradeoffs, emergent gameplay through roguelikes (procedural generation, permadeath), player mastery/difficulty, Steam early access, user feedback, importance of testing, data-informed balancing, and player accessibility driving features via streaming, translations, and UX.
Anthony (MegaCrit): https://twitter.com/megacrit
Henry: https://twitter.com/left_pad
Do we learn in a vacuum, or does it involve our whole selves? Philip Gee (UC San Diego) joins Henry to chat about maintaining a web presence since its beginnings. We discuss some of the points made in Nadia's post on ideas carrying us forward, even beyond what we are known for, the greater intimacy of podcasts and vlogs, attaching ideas to people, science as subjective vs. purely objective and in community, knowledge as opening up possibilities, embracing whimsy and being random (haircut podcasts), embracing spontaneity and cities, understanding our bodies and mortality and it's relation to our digital lives and rest.
Henry: https://twitter.com/left_pad
Show Notes:
Tyranny of Ideas (Nadia)
★ Support this podcast ★Why should we standardize? Jory Burson (Bocoup) joins Henry to talk open source and standards: what they are, why we need them, what should be standardized, lifecycles of standards, past/future accessibility of participating in the process, and more!
Jory: https://twitter.com/jorydotcom
Henry: https://twitter.com/left_pad
Your feedback is valuable to us. Should you encounter any bugs, glitches, lack of functionality or other problems, please email us on [email protected] or join Moon.FM Telegram Group where you can talk directly to the dev team who are happy to answer any queries.