Podcasts about John Resig

#1 ACS #2054 (feat. Jay Chandrasekhar, Vinnie Tortorich, Gina Grad and Bryan Bishop) Recorded 04-17-2017 – Release Date 04-18-2017 #2 ACS #2138 (feat. Jerry Rocha, Dave Dameshek, Gina Grad and Bryan Bishop) Recorded 08-09-2017 – Release Date 08-10-2017 #3 ACS #1057 (feat. Harris Goldberg, David Garrett, Dave Dameshek, Alison Rosen and Bryan Bishop) Recorded 04-15-2013 – Release Date 04-16-2013 #4 CS #1919 (feat. Steve Luthaker, John Resig, David Wild, Gina Grad and Bryan Bishop) Recorded 10-04-2016 – Release Date 10-05-2016 #5 ACS #442 (feat. Ed Asner, Matt Asner, Shira Lazar and Bryan Bishop) Recorded 11-08-2010 – Release Date 11-09-2010 Hosted by Superfan Giovanni Request clips: Classics@adamcarolla.com Subscribe and Watch Clips on YouTube: https://www.youtube.com/@AdamCarollaCorner

#1 ACS #2054 (feat. Jay Chandrasekhar, Vinnie Tortorich, Gina Grad and Bryan Bishop) Recorded 04-17-2017 – Release Date 04-18-2017 #2 ACS #2138 (feat. Jerry Rocha, Dave Dameshek, Gina Grad and Bryan Bishop) Recorded 08-09-2017 – Release Date 08-10-2017 #3 ACS #1057 (feat. Harris Goldberg, David Garrett, Dave Dameshek, Alison Rosen and Bryan Bishop) Recorded 04-15-2013 – Release Date 04-16-2013 #4 CS #1919 (feat. Steve Luthaker, John Resig, David Wild, Gina Grad and Bryan Bishop) Recorded 10-04-2016 – Release Date 10-05-2016 #5 ACS #442 (feat. Ed Asner, Matt Asner, Shira Lazar and Bryan Bishop) Recorded 11-08-2010 – Release Date 11-09-2010 Hosted by Superfan Giovanni Request clips: Classics@adamcarolla.com Subscribe and Watch Clips on YouTube: https://www.youtube.com/@AdamCarollaCorner

Guest: Sal Khan, founder of Khan AcademyAI is poised to change nearly every business, but few are changing as quickly as education. And Sal Khan, who has spend more than a decade manually creating more than 7,000 educational videos, says that's a good thing. He's encouraged Khan Academy to focus on “disrupt[ing] ourselves ... more than almost any other organization that I know of.” The reason is backed up by the data: Personalized tutors — designed to help students achieve mastery in a subject, but previously thought to be unscalable — could shift the educational bell curve “significantly to the right,” Sal says.Chapters:(00:52) - John and Ann Doerr (05:20) - Khan Academy's origins (07:42) - What it is now (12:43) - Emotional fortitude (15:25) - Generating revenue (19:36) - The two-sigma “problem” (21:31) - OpenAI and Sam Altman (24:47) - What AI can do (27:56) - Cheating and other fears (30:06) - Video production (34:08) - Standardized tests (38:36) - AI tutors' tone (40:22) - Not leaving the closet (43:20) - Who Khan Academy is hiring (45:58) - What “grit” means to Sal Mentioned in this episode: Nasdaq, Dan Wohl, Vedic and Buddhist literature, Microsoft, Benjamin Bloom, ChatGPT, the Turing Test, Greg Brockman, Donald Trump, Bing Chat and Sydney, Khanmigo, the SAT and ACT, Schoolhouse.world, Craig Silverstein and Google, John Resig and jQuery, and Angela Duckworth.Links:Connect with SalTwitterLinkedInConnect with JoubinTwitterLinkedInEmail: grit@kleinerperkins.com Learn more about Kleiner PerkinsThis episode was edited by Eric Johnson from LightningPod.fm

In episode 800 of Syntax, Scott and Wes sit down with John Resig, the creator of jQuery, to discuss the current state of React and TypeScript. They dive into the evolution of frontend frameworks, the challenges of server-side rendering, and the tech stack at Khan Academy. Show Notes 00:00 Welcome to Syntax! 00:59 Brought to you by Sentry.io. 01:32 What is jQuery? 05:31 Did you anticipate the success jQuery had? 07:16 allow-discrete, @starting-style. Install Nothing: App UIs With Native Browser APIs - Scott Tolinski. 07:54 Building the community around jQuery. 11:16 jQuery plugins. 13:00 Did you ever make money from jQuery? 16:13 What is your role at Khan Academy. 17:58 What is the tech stack at Khan Academy? 21:56 Why do you want to change your CSS and JS framework? 24:03 TypeScript vs Flow. 25:25 GraphQL federation. 28:08 What was your frontend framework journey? 30:23 Is there any part of React you wish would improve? 32:37 Reservations using React Router. 33:14 Khan Academy web platform vs native platform. 35:21 What do you use for state management? 38:48 What's harder than it should be on the web today? Kilian's Question On X. Polypane.app. 42:46 Opinions on JavaScript Sprinkles. 44:04 What's with the $ sign in jQuery? 45:29 The challenges of having your name in such a widely used software. 51:06 Challenges with server-side rendering in React. 52:42 Sick Picks & Shameless Plugs. 54:48 What are the performance issues associated with internationalization? 56:57 Back to Sick Picks & Shameless Plugs. Sick Picks John: Biome, Remix, Lingui. Shameless Plugs John: Khan Academy. Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

When making mokuhanga and producing The Unfinished Print, I have looked towards various online tools for research and inspiration. One of these tools is ukiyo-e.org. A Japanese woodblock print database which collects and archives woodblock print collections from around the world.  John Resig is the chief software architect at the Khan Academy who, in 2013, for his love of mokuhanga and the Japanese woodblock print, and through his own  collection, developed ukiyo-e.org.  Those researching, collecting, and making mokuhanga can explore some of the best Japanese print collections at the click of a button. In this episode of The Unfinished Print, I speak with ukiyo-e.org developer John Resig about why he decided to create the website and how his collecting of mokuhanga and making mokuhanga affected that decision. We also discuss the evolution of the humanities in mokuhanga, archiving prints, tradition, and the copywriting of images, as well as John's work with the Japanese Art Society of America.  Please follow The Unfinished Print and my own mokuhanga work on Instagram @andrezadoroznyprints or email me at theunfinishedprint@gmail.com  Notes: may contain a hyperlink. Simply click on the highlighted word or phrase. Artists works follow after the note. Pieces are mokuhanga unless otherwise noted. Dimensions are given if known. John Resig  - Ukiyo-e.org, Digital Humanities Research, John's personal mokuhanga collection on Airtable,   Sky Above Clouds IV: After Georgia O'Keefe (2019) Utagawa Kuniyoshi (1798-1861) - is considered one of the last “masters” of the ukiyo-e genre of Japanese woodblock printmaking. His designs range from landscapes, samurai and Chinese military heroes, as well as using various formats for his designs such as diptychs and triptychs.  Five portraits of the actor Ichikawa Danjuro VIII (1823-1854) in various roles (1849) yakusha-e - (役者絵) is the Japanese term for actor prints in mokuhanga.  Utagawa Kunisada (1786-1865) Tsukioka Yoshitoshi  1839-1892 (月岡 芳年) was a mokuhanga designer who is famous for his prints depicting violence and gore. His work is powerful, colourful, and one of the last vibrant moments of the ukiyo-e genre of woodblock prints. More information about Yoshitoshi's life and his copious amount of work can be found, here.   Iga no Tsubone and the Ghost of Fujiwara Nakanari, from the series One Hundred Ghost Stories from China and Japan (1865) Annie Bissett - is an American mokuhanga printmaker and graphic designer based in Rhode Island, USA. Her work touches on politics, and beauty. Her interview with The Unfinished Print can be found, here. Annie's work can be found, here. Irene (2023) Onchi Kōshirō (1891-1955) - originally designing poetry and books Onchi became on of the most I important sōsaku hanga artists and promotor of the medium. His works are saught after today. More info, here. Portrait of a Poet: Hagiwara Sakutarō (1886-1942) Meiji Era Prints - The Meiji Era of Japan was between 1868-1912 CE. This was a period of immense modernization and industrialization in Japan, where the Japanese economy was booming. New ideas within mokuhanga was occurring as well. Perspective, colour, through new pigments (gamboge, certain yellows), the advancement of photography, and new topics and themes (war, industry, architecture), the Meiji era print designer and publisher had a lot of choice when producing their prints.  Shigeru Kuriyama (1912-2010) - was a sōsaku hanga  printmaker who worked with Onchi Kōshirō (1891-1956), and U'nichi Hiratsuka (1895-1997). He founded the print magazine Yukari and Kasuri. His prints were focused on folk arts.   Fragrance of Lavender (1996) sōsaku-hanga - or creative prints, is a style of printmaking which is predominantly, although not exclusively, prints made by one person. It started in the early twentieth century in Japan, in the same period as the shin-hanga movement. The artist designs, carves, and prints their own works. The designs, especially in the early days, may seem rudimentary but the creation of self-made prints was a breakthrough for printmakers moving away from where only a select group of carvers, printers and publishers created woodblock prints.  Your First Print: David Bull - this was the first DVD I ever purchased on how to make mokuhanga. This was in and around 2007. While I look back at that time thinking about why I didn't take it up as seriously as I do now, I sometime wonder, "Where would I be now in my Mokuhanga journey?" I realize that that is a redundant way of thinking. I am where I am now today, and to be happy with just that. You can still find this product on Dave's website.  Takuji Hamanaka - printmaker based in Brookly, NY. Uses bokashi,  a printmaking technique, predominately in his works. Unique and powerful. website Instagram Collapse (2016) April Vollmer - is an established artist who works predominantly in mokuhanga. Her book Japanese Woodblock Print Workshop is one of the most authoritative books on the subject and has influenced many mokuhanga artists. April's interview with The Unfinished Print can be found, here. Wood Like Matsumura - is an online and brick and mortar store, for woodblock printmaking, located in Nerima City, Tōkyō. Yoshida Hiroshi (1876-1950) - a watercolorist, oil painter, and woodblock printmaker. Is associated with the resurgence of the woodblock print in Japan, and in the West. It was his early relationship with Watanabe Shōzaburō, having his first seven prints printed by the Shōzaburō atelier. This experience made Hiroshi believe that he could hire his own carvers and printers and produce woodblock prints, which he did in 1925.  Kiso River (1927) kabuki - is a traditional form of Japanese theatre which started in Kyoto on the banks of the Kamo River in the 17th Century. Today it is a multi million dollar business and is almost exclusively run, professionally, by The Shochiku Company. Kabuki, the word, is separated into three different sounds; ka - meaning to sing, bu - meaning to dance, and ki- meaning skill. There are various families in kabuki which generate actors, passing down tradition throughout the lineage. For more information please read this fine article from Nippon.com. There are many books written on the subject of kabuki, but in my opinion, to begin, one needs to read Leonard Pronko's work Theatre East & West, Kawatake Toshio's Kabuki, and Earl Ernst's The Kabuki Theatre. Online, please visit Kabuki21.com, who's site is unparalleled. On YouTube there is the new(ish) Kabuki In-Depth which is updated regularly on kabuki information and history, and is very well done.  Georgia O'Keeffe (1887 – 1986) was a renowned American artist, known for her pioneering contributions to modern American art, particularly in the realm of abstract and contemporary art. Lake George Reflection (1921) bokashi - is a mokuhanga technique, where the pigment fades from a heavy colour to a softer, broad colour. Made famous by prints designed by Hokusai and Hiroshige, this technique is, for me, the most popular technique utilized by  mokuhanga printmakers. There are various types: Ichimoji-bokashi or straight line graduation, used in the above mentioned Hiroshige and Hokusai prints. Ichimoji-mura-bokashi or straight line gradation with uneven edge. Ō-bokashi or wide gradation, Ate-nashi-bokashi or gradation without definition. Futa-iro-bokashi or two tone gradation, and ita-bokashi or softer-edge gradation, where the block is cut in a specific way to achieve this style of gradation. All of these styles of bokashi technique take practice and skill but are very much doable.  Bertha Lum (1869-1954) - was born in Iowa. Having begun travelling to Japan in 1903, Bertha Lum noticed the decline of the Japanese woodblock print in Japan in the early 20th Century, deciding to take up the medium. Lum began making woodblock prints after learning in Japan from an unknown teacher during her first trip to Japan. Japan, Lafcadio Hearn (1850-1904), and China influenced Bertha Lum's prints. Lum's work focused on these themes through an American lens.  Winter (1909) Frances Gearhart (1869-1958) - Born in Illinois, Gearhart was a self-taught artist who spent most of her life in California. Originally a watercolorist, Frances Gearhart began experimenting with Japanese woodblock and linoleum in and around 1913. The themes of her work are predominately landscapes of the Pacific Coast and other areas of California. Her work is associated with the Arts and Crafts movement in California. A fine article on Frances Gearhart's life can be found, here.  In The Sun (1930) Fujio Yoshida (1887-1997) - the wife of Hiroshi Yoshida and the mother of Tōshi Yoshida (1911-1995) and Hodaka Yoshida (1926-1995). Fujio was so much more than a mother and wife. She had a long and storied career as a painter and printmaker. Fujio's work used her travels and personal experiences to make her work. Subjects such as Japan during The Pacific War, abstraction, portraits, landscapes, still life, and nature were some of her themes. Her painting mediums were watercolour and oil. Her print work was designed by her and carved by Fujio.  Roses (1925) TinEye - is an image search and recognition company. They use technology which allows the user to search an image creating a reverse image match. More information can be found, here.  The Metropolitan Museum of Art - is the largest art museum in North and South America. It began to be assembled by John Jay (1817-1894) in the late 19th century. Incorporated in 1870, the museum has collected many essential pieces, such as the works of Henri Matisse (1869-1954) and Pierre-Auguste Renoir (1841-1919). For more information about the MET, you can find it here. Waseda University  - is a private research university located in Tōkyō, Japan. It was established in 1882. Waseda has one of the largest woodblock print databases in the world, and are free to use. More information can be found, here.  Ristumeikan - is a university founded in 1869, and located in Kyoto and Ōsaka. Like Waseda it holds one of the largest collection of Japanese woodblock prints. You can search their database, here.  Mike Lyon  -  is an American artist. His medium has been varied throughout his career such as "square tiles," or "pixels," through to making mokuhanga, monoprinting, and machine-assisted etching, drawing and mezzotint. Mike Lyon also has a large woodblock print collection which he has curated for the public, here. More information about his work can be found, here.  Linda In Black (2019) Frick Reference Library - is a reference library in the Frick Museum in New York City. The museum was once the mansion of wealthy American industrialist Henry Clay Frick (1849-1919). The museum houses some of the finest pieces of sculpture, paintings, and art in the United States. There is also the public Frick Reference Library located on 10E 71st Street in New York City. More information can be found, here.  Hokusai: Inspiration and Influence - was an exhibition held from March 26 - July 16, 2023 at the Museum of Fine Arts Boston. More information can be found, here.  Japanese Art Society of America (JASA) - Starting in 1973 by a small group of collectors of ukiyo-e in New York City, JASA has expanded to cover many Japanese arts. Their magazine Impressions is a biannual magazine that discusses in a scholarly way various Japanese arts. More information can be found, here.  Utagawa Hiroshige (1797-1858) - born in Edo, Hiroshige is famous for his landscape series of that burgeoning city. The most famous series being, One Hundred Famous Views of Edo (1856-1859), and the landcape series, Fifty-Three Stations of the Tōkaidō (1833-1834). His work highlights bokashi, and bright colours. More info about his work can be found, here. Below is, Coastal Landscape In Moonlight (1857) Kingfisher and Iris Scholten Japanese Art - is a mokuhanga-focused art gallery in midtown Manhattan. René Scholten, an avid collector of the Japanese print, founded it. You can find more info here. Katherine Martin is the managing director of Scholten Japanese Art. Katherine has written extensively for the gallery and conducted lectures about Japanese prints. Her interview with The Unfinished Print can be found, here.  International Mokuhanga Conference - is a bi-yearly conference dedicated to mokuhanga which started in 2011 by the International Mokuhanga Association. Each conference is themed. The latest conference was in 2021, delayed a year because of the pandemic. More information can be found, here.   Cameron Bailey - is a mokuhanga woodblock printmaker based in Queens, New York. His work is predominantly reduction woodblock. Camerons work has shown around the world. You can listen to one of his earliest interviews on The Unfinished Print, here. His work can be found, here.  Reflection (2020) sumo - while sumo wrestling has been known to Western audiences for quite some time, it is only in the past several years that the Japan Broadcasting Corporation (NHK) has created content for Western audiences to watch tournaments and engage with wrestlers through videos, such as YouTube.  Sumo prints were being produced in the Edo Period (1603-1868), with the Kastukawa school of artists beginning to create prints in the vein of actor prints of the day (yakusha-e).  Utagawa Kunisada (1786-1865) A portrait of Inoyama Moriemon (1846) Acolytes of The Baren  - is the Facebook group dedicated to Dave Bull and Mokuhankan. It can be found, here. Emerging Hanga - is a Facebook group dedicated to new mokuhanga, and sharing information. It can be found, here.   Brush & Baren  - is a Facebook group dedicated to sharing the history of mokuhanga of the late 19th and early 20th Century. It can be found, here.  Friends of Baren Forum - is a Facebook group dedicated to those interested in mokuhanga and woodblock printing in general. it can be found, here.  © Popular Wheat Productions opening and closing musical credit - Flowers & Fire by BLITZ. From the album Second Empire Justice (1983), first released on Future Records.  logo designed and produced by Douglas Batchelor and André Zadorozny  Disclaimer: Please do not reproduce or use anything from this podcast without shooting me an email and getting my express written or verbal consent. I'm friendly :) Слава Українi If you find any issue with something in the show notes please let me know. ***The opinions expressed by guests in The Unfinished Print podcast are not necessarily those of André Zadorozny and of Popular Wheat Productions.***                    

Join Lee and Glenn as they Keep Calm and Boom On!  You won't want to miss this chat with co-founder of The Chive and Atmosphere TV, friend of Bill Murray and brother of Leo, John Resig.  Hear how the brothers founded Chive.com in Silicone Beach , CA, creating the wildly t-shirt business coining the phrase and selling Keep Calm and Chive On t-shirts, moving to Austin almost 10 years ago setting up shop with one of the wildest office buildings downtown, creating Atmosphere TV to provide short form content to bars and restaurants across the globe and oh so much more! From John Daly to Bill Murray shenanigans, bourbon interview secrets, office showers sweating beer, a Banksy museum in Austin, and so many other great nuggets it is obvious John is living the dream in Austin, Keeping Calm and Chiving On to the fullest every day!This episode is such a great reminder that Austin is full of characters and BoomATX is on a mission to interview them all!  

Leo Resig is the Chief Executive Officer & Co-Founder at Atmosphere, the world's leading streaming TV service for businesses.  A graduate of Indiana University with a degree in Management, Leo tested a range of career paths -- everything from screenwriting to personal banking -- before discovering digital advertising in its nascent stages in 2002. He cut his teeth on the agency side as a digital media Ad Ops manager in Hollywood at Crew Creative. He then joined Gorilla Nation (now Evolve Media), on the publisher side with roles in ad operations and graphic design.  Leo and his brother, John Resig, started theCHIVE.com in 2008 as a one-stop shop for viral photos and videos. theCHIVE became a global lifestyle movement and CHIVE Media Group became the umbrella company for theCHIVE.com, their ecommerce business The Chivery, a 501c3 non-profit called Chive Charities, and streaming OTT app, CHIVE TV.  The brothers spun the idea for Atmosphere TV over beers at a local bar, after realizing that the experience of consuming content on TV's outside the home could be elevated. This was the birth of CHIVE TV, which became the flagship channel within Atmosphere's streaming platform, which now houses over 50 TV channels.  Along the way, Leo also went on to co-found a golf apparel company called William Murray Golf with Bill Murray and his brother John. He also launched a top 50 US-brewery called Resignation Brewery in 2014 selling KCCO Beer. Philanthropy has always been important to Leo and he and his brother established Chive Charities in 2011 which has helped raise and donate over $20M to help individuals with rare medical disorders, veterans and first responders.  Family has always come first for Leo. He is a proud father to two amazing children and husband to his wife, Tiffany. Hailing from Fort Wayne, Indiana, Leo now resides in Austin, TX by way of Chicago and Venice Beach

Prepare for one of the most entertaining, candid, irreverent and down-to-earth episodes of TBM as Chive's John Resig checks in with ABJ Managing Editor Will Anderson. From Day #1, The Chive and its offspring have followed a simple, successful formula: Give the audience what traditional media and tech giants can't, spoon feed it- often times for free, and find creative ways to monetize the ever-changing business model.  And don't hit the eject button early because Chive Media Group is hiring, and John reveals the surefire strategy to get a call back.

Loren Sands-Ramshaw: https://lorensr.me/The GraphQL Guide (coming soon): https://graphql.guide/TranscriptLoren Sands-Ramshaw: [00:00:00] So welcome Shawn to the GraphQL Guide interview with Shawn Swyx Wang. Is that swyx: [00:00:04] it? I pronounce that, right. It's it's my Chinese and English initials. And it's just a branding that I'm leaned into because it's unique. Yeah. I think it's great. Loren Sands-Ramshaw: [00:00:11] Yeah, definitely unique. So for those of our readers who don't yet know you, swyx: [00:00:15] Who are you, what do you do?Cool. I'm Shawn. I guess I work on developer experience at Temporal. I should be more assertive. I am head of developer experience at Temporal.io. It's a Small startup that does microservices orchestration, which is a very, very fancy name that basically runs an open-source framework spun out of Uber that we can go into more details, but really, I've done.I sort of migrated from finances, which is my first career. Then I went into Front end. So I did a JavaScript bootcamp then went into front end D started doing some speaking and writing in 2017 and got noticed by Netlify. And that's how I got into developer education, which is what we're here to talk about, I guess, and then started getting into graph QR because it was all tied into the react world.At the time. You could not ignore graph QL and Gatsby and Apollo and all the other ecosystem in, in, in place. I did. Then I then went to AWS to do the same job, essentially where they have amplify an app sync apps think is AWS has graph QL gateway as a service, which we can talk about. And I recently left to join Temporal.Loren Sands-Ramshaw: [00:01:18] Going back to when you were getting noticed you were like writing blogs and doing talks and getting out a spot Netlify how did you decide to get into developer education? swyx: [00:01:25] I didn't, there wasn't actually a decision. It was just like, let's just try this. And see what happens. So that the context was that the boot, the first job I got out of bootcamp was at Two Sigma, which is a well-known Quant hedge fund in New York.The problem was that I was in a, I didn't know it, but I got into a bad part of Two Sigma where they were severely underusing their engineers to the point where four days out of five, we were not doing anything like specifically not standing on our desk. Cause we had stand up desks. And.Explicitly given to have the okay. To do whatever we wanted, whatever because we just didn't have work. And that was, it's a, it's an enviable position, right. For for a lot of people like, Oh yeah. Paid around and do whatever you want. That's that sounds like a great job, but I don't think it's a very good job for a junior.Like someone just starting out. Right. You're not going to grow up very much. So it's like frustration. Really that I was like, okay, I'm not getting any learning at work. My, my team lead was like not doing his job. So I just started blogging and, making my own mentors, like, externally New York city has a pretty vibrant meetup scene.So I just, started doing my own talks, even though I didn't feel like an expert. And then I started doing blogging and I think the first one that really picked up for me was. When react announced that it was working on async react like concurrent mode as it is known today, but back then it was async react.So it was announced at a conference in JS conf on March in March, 2018. And I remember that night because it was a big shock to the react ecosystem and it was like a sweeping change. They touching every single part of react. So I just stayed up all night to write a walkthrough of the talk, the demo, and just really like went through everything at it.And that was the first blog post that. We've got really some notice for me and that really still bald since then. And since then I've kind of enveloped everything into this principle I've learned in public. Like when you find something interesting write it up in your own words and share it with people.And at least the people involved in working on the thing will probably read it. And if you're saving some work and if you have some unique perspective than other people will find it helpful as well. Loren Sands-Ramshaw: [00:03:26] Was there a moment where you were like, I'm going to write my own blog posts instead of reading other people's.swyx: [00:03:32] I've been doing it, unsuccessfully for like the two years prior. So there was no one single moment. It was just like focusing it on something that people actually cared about. It turns out that, you want to write things that people want to read. And that's that was a pretty big insight for me.It's not, it didn't seem like that big of an insight until you look at it. The vast quantities of developer blogs out there. And a lot of them are sort of very inward facing. They don't really answer the question of why should you care? And so I, I definitely had my mentality changed around like, okay.Like it has to be an intersection of things you're very interested in and things that other people are interested in and you can't just have one or two. Loren Sands-Ramshaw: [00:04:07] Speaking of things that people are interested to read, you have a great book on the coding careers. That's called the coding career handbook.One of your first. Customers really like the parts of it that I read. What was that like coming with the idea of the book and writing it and swyx: [00:04:20] publishing it. So there's a fun story for the reason the name is so awkward. I still don't like the name, but I just had to go with it because I didn't have anything of anything else.The reason was the original name was cracking the coding career because there was a successful technical interviews book called cracking the coding interview. And the whole point was that it w I wanted it to be apparent in the title that once you're done with the interview, once you landed the job.There's a huge gaping hole of what's next. And this th this book is targeted at the what's next. Unfortunately, Gail McDonald, the author cracking Cody career actually got in touch with me and mentioned lawyers. So I had to change the name before lunch. So, by the time, like I already had my Twitter handle up and all that, and I was just like, all right, I'll just stick with this thing.But it is an acronym. Yeah the. Point I think is that people, I think my most successful writing, like it or not has been my non-technical writing which the learning public essay has reached, hundreds of thousands of people. And I constantly get shout outs every single day about people starting to own journeys.And it's something that I really. Believe it, even though I hate, I'm not like the Tony Robbins type, I don't want to be like a lifetime life coach or anything. I just think that this worked for me and it will work for a lot more other people. So I was like, okay. I just, I should probably just write down some more advice on, on, on what I think that people need, because.I think what really crystallized it for me was when you look at career ladder. So I did a study of every public career ladder out there. So career ladders are these things where it's like, all right you're junior, you're expected have these qualities or senior, you expected these qualities, staff, principal, whatever.And and everyone has some version of these in some companies are actually brave enough to publish them. And so if you just study all of them and you realize something really interesting, which is that when you look at the way that people are promoted and graded about 75% of the grading criteria is non-technical.Seventy-five right. It's like, all right, you can call it. Great. But what about your communication? What about your business impact your mentorship and all that, which is like surprisingly not the type of thing that you learn in college or bootcamp. And no one tells you to do it, but suddenly it's 75% of your evaluation, like, well, okay.And I think that just reflects the reality that we are less coders and more code enabled humans and we can code, but we're humans first. And so we need to apply all these sort of soft skills. I hate the word soft skills, but that's the common commonly accepted terms. So I use it Two two, we need to teach each other, lessons from these things.I am not saying I'm the world's foremost expert at them. I have things to work on myself and it's a very difficult thing to, to come on and say like, I have something worthwhile for you, even though I'm imperfect. But I don't base my advice on myself. I also base my advice on.Hundreds of other people that I've interviewed and collect collected the book has like 1400 references to people smarter and wiser and more accomplished than I have. And that, that's just what research does for you. And hopefully you can decide yourself which of these ideas you agree with and which are not.And that's all I ask really, I think it's really hard to write a soft skills book. Because your sort of character has to be impeccable. Like the moment you're like, Oh, I had a bad interaction with this person. Therefore, the entire book is wrong. Like, I'm sure, if you want to take that view that's fine for you.But I view ideas as sort of independent, you can sort of pick and choose. And if this book, has 40 chapters and three of them make sense for you then that, that would be a good investment of time for me. Loren Sands-Ramshaw: [00:07:39] I liked it like the field of life coaches and career coaches and therapy and stuff.And I really appreciate the knowledge that you've put into the world with that book. So thank you swyx: [00:07:49] for writing. Well, yeah. Thanks for asking about it. It's kind of, it's still awkward that you can hear me like being very hesitant about like, talking about this thing, but people like it.I think that, everyone wants to hire seniors. That's the truth. There's a huge glut of bootcamps producing juniors. There's lots of people self-teaching. And then from junior to senior, somehow you magically, hope to. Find something that works. And then once you're seeing her every once a hi, everyone wants to hire you.So I guess if I had to narrow it down, like I need to make it. Easier for people to up-level whether or not they can use the book as a guide or they can join the discord that I have and interact with me directly and ask me questions and all that. These are all passed into upscaling, more people from junior to senior.And I think people don't do it. It's just, it's a very awkward thing to do. But that's an interesting challenge. I really Loren Sands-Ramshaw: [00:08:37] liked the boot camps. There were like nine months. You can go really deep. It'd be cool if I was like a graduate school version of boot camp. So you go to the bootcamp one, and then later on you go to the boot camp two.swyx: [00:08:46] Oh, there is a Recurse center, which is the self guided one in New York. Yeah. A lot of pretty famous people have come out of the recur center because they do it's essentially like graduate school. Like you propose your topic and then you sit in a room with a bunch of other people who are very self motivated as well.And you produce something to impress each other and the kind of people that actually self-select to go there are very intellectually curious themselves. So they work on pretty cool stuff. And it turns out that once they graduate, they will actually go on to do some pretty interesting things as well.So, that's a comparison, but like the thing is that doesn't scale. Like they, they admit like maybe a few dozen people there's tens of thousands who will never do it. Loren Sands-Ramshaw: [00:09:23] Also. There are a couple more ideas in that area that I have where like, Having it be more of a norm for companies of like even medium size to have like a junior teaching mentorship program.swyx: [00:09:37] Yeah. Yup. More apprenticeships, especially for people from non-traditional backgrounds. I find, I see so many companies that have, Campus recruiting for colleges. But actually, what about everyone else? So, yeah. And then in the mentorships, it, th the thing is like, it's perceived to be a cost.And we need to turn that around and turn the tenant equation around and say like, actually you're getting. To upskill talent, there's that cheap, that becomes very valuable once you put, once you invested in them. And I think some companies are getting into this mindset. So Stripe is having direct integration with the university of Waterloo.And I think shop, sorry. Stripe is integrating with the university of Limerick, I think in Ireland. And Shopify is. Has a has a degree offering with the university of Waterloo. And it's just amazing to see all these innovations, but they're just sort of piecemeal. And then, they'll improve a few dozen people, a few hundred people at a time, but it's a slow process for sure.Loren Sands-Ramshaw: [00:10:28] I would think of it makes sense for there to be like a lower part of the market where like, like the, maybe under the entry-level for expected junior does, there's like a gap where people can do like. Traditional apprenticeships where it's more of a stipend or like an internship kind of thing where you're not being paid like a normal dead salary, but you are learning a lot.Yeah. And maybe like that would be low enough that it would be profiled. swyx: [00:10:52] They are doing that at they are doing that at Lambda school, which is the online bootcamp. The problem is Whenever you talk about paying people perhaps less than an average developer salary the, there people online who get very angry about that.And I, it's not my place to say. Who's right and who's wrong. I defend the right of consenting adults to agree to whatever contract they want, even though, some, some of them may be exploitative in retrospect, but we have to let people make mistakes. And we have to let people experiment with new forms because all we know is the current system.Doesn't work well in, in some way we need to try new ideas. We need to make it safe to try new ideas. And and so Atlanta school was really trying. And I think what they have right now is they'll guarantee you they'll give you a student for a month.And they'll pay the full month of it. So it's totally cost free to you, except that you have to give them, stuff to do. And I think that's a really beautiful experiment. So I don't know, some people get angry about that. I'm like, you're, you don't know what it's like to be a bootcamp student.I would've killed for that. When I was a BlueCat student, Loren Sands-Ramshaw: [00:11:51] I have friends who haven't found a job after boot camp. So, hope that swyx: [00:11:56] system works fine. Yeah. Nothing is better than sort of just getting into a real work scenario and like, stop jumping on the artificial hoops with like in video binary or whatever.And just get into the real work. And after three months, six months, nine months, you're a dev. And. You know that w yeah. Every, everything else is just gate keeping. So whatever. Loren Sands-Ramshaw: [00:12:14] So you think of algorithm, coding interviews? I had an interview with Toptal, and I didn't know they were going to do data structures and algorithms.So I didn't study and like, I haven't studied it in over 10 years. And I got an a in my courses at Dartmouth, so like I knew it at one point. swyx: [00:12:30] But I totally did you burn, did they give you a grade? Did they give you a number? Like how bad? I know they just like stop Loren Sands-Ramshaw: [00:12:35] asking your questions. swyx: [00:12:36] Yeah.Yeah, yeah. So tail, the reason that'd be so stringent is the marketing, right? They're like we, they have to have a rejection rate to, to show off. Because that's part of the marketing appeal. I totally get it from their angle, but then also, like you don't need them. So, whatever.Loren Sands-Ramshaw: [00:12:49] What are your thoughts around different education mediums? Like how did you decide to do a book versus a video course? And do you have any plans for doing books or courses or. swyx: [00:12:59] Inefficient. That's an interesting question. The reason I did a book was because the MVP of a book is a blog post, and I already done like three, four years of blogging prior, and people already knew me from my blogging.So it was very natural progression. So I didn't really question it. I also know that I take a lot more time to do video than I do writing or, yeah. No, let's just put it, let's put it the other way. Like, I don't think I'm ever on the world's most natural speaker. I have a lot of false starts.I've thought I'm sinners and I'm still working on it as you can probably tell. But yeah. And so when it comes to writing, it's SEO, searchable, it's you can edit it anytime and reformat things, and it's not it's super cheap. You can add hyperlinks, which I love dropping references.Right? Like when I. Have references in a podcast or a talk. I can't drop a hyperlink in my mouth and you can click on it and it just leads you right to the source. I really liked that. And it annoys me when podcasts say, like, we'll put it in the show notes on any deal. They don't it's really super annoying anyway.So writing solves all of that. It's it's perfect. Medium. It's very scalable. In fact, I have a whole chapter on why writing is great. Everyone, every developer should write. So yeah, I mean, no, no contest on mediums. That's it. One of the downsides of writing is that the moment you call anything, a book, what's the normal price of a book it's nine to nine to $59 or something like that.Like you can go to maybe 99 or whatever, actually, I don't know how much theYeah, got it. Yeah, there's a range. Right. And it's basically constrained by the format rather than the value of the knowledge contained in the book. So if my book happens to. Yeah. Increase your the slope of your career by $10,000 a year. The Mexican charge is 59, which is what I charge that's absurd.Right. And other formats, like video courses, that's automatically like 200 to $300. Irrespective of like the actual value of the delivers to you. And so that's a really bizarre way to do things. So that, that was one, that's one argument for why you might want to do other formats.So apart from this book, I actually considered doing a reactant types, of course, because my other one of my other side gigs is that I run the react and TypeScript cheat sheet, which is. The de facto community docs for react and TypeScript. And it's a, it's a much bigger deal now with them back when I started.So I teach, a thousand people a day react to TypeScript and it's been a completely volunteer behavior volunteer activity. And if I, sold 1% of those on a video course, I probably make a living.It's something that I thought about. Th the only reason I don't do it is because I don't want to be a teacher. I don't think I'm a, I've a very ever temperament to be a good teacher. I don't think I have the patients. I want to do other things with my life apart from teaching.So I think I'll just leave it to someone else, or maybe collaborate with someone. Loren Sands-Ramshaw: [00:15:44] Let's move to the backfield topic. What is your swyx: [00:15:47] take on evacuation? Greatest thing since sliced bread. Is that what I'm supposed to say? So I had a talk about this Hawaii where like kinda compared it to like, I hate I wish that people would start comparing graph QL to risk.Like we have to, because that's kind of what we. What the paradigms are and how people mentally place them. But rest doesn't go away at Graco has a protocol over rest. And so it was like, it's, it's not either, or it's like one and the other. That's it. My sort of galaxy brief summary of graph you all is that instead of creating a dozen different end points that are all kind of dumb you create one smart end point and then you have contracts that can specify whatever that end point does sort of on, on request.And I think that's a really simplified take, but it really. You were there at Apollo day. And I think the Apollo folks have a really good present explanation of this. It really starts to come into its own when you start having multiple devices to support. So you have mobile and desktop and web Sr and, and Sorry.Well, mobile native and desktop and mobile web and on whatever other devices that you may have, these are all have the different data requirements. And there's a combinatorial explosion. They have all these lines crossing over from different services, into different devices that you could simplify by just having one single sort of smart endpoint.And everyone connects to that one smart end point. It speaks to the right contract and that smart endpoint has. The means to resolve all the data from each individual data source then that's essentially graph QL. Like you could do this in a bunch of different other ways as well. And there have been many, many other attempts like graph QL is, is, it's not new.They're there. And I think the creators of graph you all are pretty upfront about like the inspirations that led to. Craft you are like all data, which I never really tried any of these. So outside, I don't have much sympathy. All we know is that graph QL is successful. Now it has the network effects now, and therefore it's a much better bet than the other formats.Which is an argument by like it's success, it's popular. Therefore it should be more popular like that kind of argument, but it's true. There's some amount of validity to betting on things because the ecosystem is better. And so, so that's really smart.I have another take, which kind of combines into one of the questions that we prepped for is what I dislike about it. So, I think that it's very, very easy for front end developers to wax poetic about graph QR, because it makes their lives a lot easier. And the people that we kind of leave behind, or we sort of punt all the tough questions too, are the backend developers for whom It turns out it's not true.It's not always true, but net, it turns out that it's more work for them, whatever it is from like, figuring out how to do off figuring out how to do like rate limiting or like query complexity, limit limitations and like, Inserting all the validation steps or like joining schema is, and the federating them, these are all the tough work that was maybe sometimes shift done on the client side has all been shifted onto the backend.That's really unfortunate for graphical adoption. Like the main bottleneck of graphical adoption is backend. That's it there. And I wish we would stop. Okay. I wish front end developers would stop selling graph QL based on how easy it makes their lives, because it's totally unsympathetic to graph to back in people back.And people are just like, you guys are not thinking about the security risks. They're not thinking they're not talking to them in terms that they are thinking about. And I wish that more evangelism, more graphical individualism was more sympathetic to the backend perspective. Loren Sands-Ramshaw: [00:19:08] What are your personal swyx: [00:19:10] favorite parts?Oh, graphical. I, this is the common answer, right? Like it's I feel like graphical is kind of like the common ground of all of them. Cause like, you can, it's a raffle or it's a postman or whatever it is. It's the common tool and it's so good and actually got a lot better. We graphical Explorer sorry, graphical Explorer.And that's the little side tab that the added and I think, their plans were a graphic for 2.0 in graphical. And it. It's just such a introspective tool that has embedded documentation in it. Like, it's just, it's everything you want out of a documentation tool and of API documentation that  rest never really got to, like the best you got.It was open API and even that's kind of like a sprawl and it doesn't have embedded like try this, it, it does, but like it, it's just not as smooth as graphical. So yeah not really galaxy brain take here. But I think, yeah once you make experimentation and modification a lot easier than you, you move the pace of development faster, at least on the front end.So, I definitely like that a lot. The errors kind of bother me a little bit with, areas being 200. Okay. That's a common sort of gripe among people who don't like graph QL, but you'd learn to deal with it. You just, yeah. Loren Sands-Ramshaw: [00:20:16] Any advice for swyx: [00:20:16] people learning Graco?Nice. We're learning people that are in graph. Y'all I think the thing that you do in the book where like you explain the validation and set it, set things up from scratch you should do that. You should go through the exercise. Actually even set up a server using just pure graph LGS without all the fanciness that maybe Apollo server does for you.And just, yeah. Fundamentally understand like, or, so like, I guess the advice would be like stripped down the tooling as much as possible and build your way back up instead of just starting at the tooling and never going down the stack a little bit. So, did you know that you can query Aggreko end points just with fetch?Do you know how to do that? If so then great. Then what's the next step after fetch? What does caching actually do for you? So on and so forth, like these are all this, these are the steps that you knew you need to sort of work through to, to build up to a complete understanding of graph you are so that when things go wrong, you know how to fix it.And that's one thing which I really encourage because graphene is a complex system. It's client side is service side and there's like, This complex chain of events that go through it. And sometimes the errors can be a bit too loose. If you don't really know what's going on under the hood.Loren Sands-Ramshaw: [00:21:19] Yeah. I don't a friend who I was a junior dev working at a company that like had a Apollo in place and like their view of craft kill was if I add this like fragment or this query to this component, then. I'm going to get the data. And so they don't have the understanding of like what's happening, how it's all getting collected, where the cash is doing.Which is definitely helpful. When things go wrong. swyx: [00:21:47] Yeah. Yeah. Loren Sands-Ramshaw: [00:21:48] What are your, yeah. So you had a chance to read parts of the guide. Thank you so much for being here. I really valued your feedback. What swyx: [00:21:55] were your favorite parts of the book? So I noticed that you do something unique, which I don't see a lot in a lot of other books, which is every code sample has like a good tag.Is that what you do? And you can just view the defer or go straight to the, get, get tag from that sample. And I actually really liked that. Sorry. So this is really tiny detail, but then like, I appreciate that. Cause I read a bunch of other books as well. Like I got another, a book here.And on top of this monitor that I'm looking at you on, I have a bunch of other techniques as well. I really enjoy reading technical books as a way to level up. And so like when you can actually follow through on the code and download it and run it yourself, that's a really nice detail.Overall, like, I think it's, I think it's a very comprehensive, like 500 something pages, which is huge guide, and it's the kind of detail that you would take months to really pick up on. And, you get it within a Yeah. Within a few days of just reading this book.And so I just really appreciate it, like all the research and all the piecing together of things. Obviously you had to make some tough choices, like, picking on picking Apollo. But I don't think these are controversial at all. These are just like, the industry standard things that, that you would at least expect people to be familiar with.Even if they go with the alternative. And then going into like each individual client and framework, I don't use react native sorry, I don't use Vue or react native, or I think you have some other native iOS, even that you went into there. I don't use any of those platforms. I'm just a web person.But I know that, when the time comes, I can just pick it up and start there. So that's a really good perspective as well as like the broader ecosystem, right? Like, Apollo Federation, which is like a fair, fairly new thing. And then talking a little bit about history as well, which I think is one of the most significant graph your companies out there.So, so yeah, it really like combines, condenses a lot of research that's done by you and John Resig and that's pretty well, this very much worth the sticker price. Loren Sands-Ramshaw: [00:23:36] Thank you. So the tags is particularly difficult because I have a tag for each section of each coding chapter.And those are chapters six through 11, and then for each version of the book has a different tag of version. So it's like the react chapter is maybe 40, 40 tags with each, with a version number. And then each time I changed the code for the next version of the book, I can make another 40 tags. It's a big process.Yeah. swyx: [00:24:05] I was thinking about, is react the best pear to graft you all like, does it, is it an accident of history that it just happened to also come out of Facebook? That's. Which is why we use it together. I always wonder that because, we act it's very weird with its effects and all that.It's kinda clunky to, to use. So you basically have to use a third party library, like, or goal, or Apollo client to wire to that. I don't, I'm not sure how I feel about that. Like I was just like, Ugh. Anyway, we can talk the frame, talk about frameworks in a day, but yeah, I appreciate it that all the guys are in there and you took pains to, to cover other devices.Like, like I said, like, one of the main benefits of adopting graph is that you can support multiple devices, multiple frameworks in paradigms pretty easily. Okay. Loren Sands-Ramshaw: [00:24:47] Any visions swyx: [00:24:48] for the future of death off? OhLoren Sands-Ramshaw: [00:24:51] well just probably like, having the backend story be. More developed. I think it was both pitching them and then swyx: [00:24:56] also the software supporting them. I have a pretty good coverage of this in the book where you talk about differ and idea, the two directors, which I never remember stream yes.Street. So like all these spec level things are very important because once it's in the spec then multiple, different parties can implement them. And we because right now everyone's kind of haphazardly kind of. Hacking their way around it if they need it. And once it's standardized we can really build some rails around it to make it a lot more reasonable and, things like the, for like, they need to be in there just cause once your graph gets big, like you, you need to, query things at different paces and have them all in one quick one single query. Yeah. So, so more standardization of stuff. Like I even, I don't know. I don't know how you feel about this, actually. I should ask you a do, but I think that graphic, I wish that graph y'all had a date time. Standard type. Loren Sands-Ramshaw: [00:25:41] Definitely. I think it's a, swyx: [00:25:43] some stage in the spec. Okay. Super annoying. It doesn't happen.Yeah, so, I think Lee Byron has had arguments for why did kept it out. And definitely simpler is better for the initial success of graph. You would prefer would not be where it is today. If it had done all the things it had to really, really scope down and just solve a specific problem for Facebook and the early adopters.Then it got big and then people want more out of it. This is the natural way of things is how it always goes. That's it. It's super annoying to work with the time in in graph QL and everyone has their own really weird spec. And we should probably standardize on that. I think relay seems to, relay seem kind of dead for a while.And then it had a little bit of resurgence and people really like the the cursor format which which I think you briefly touch on as well. There's, there seems to be some amount of need for standardization of like, the way we do pagination, the way we do a bunch of things like even authorization as well.I don't think it's really it's too. Left to influence that it's too hand-wavy. And so, yeah, which is, which kind of goes back to the solving backend developers, pain points, like having best practices that are sort of, well defended and in production at well-known companies that really gives a lot of assurance to the rest of us who are just trying to figure this out and trying to evaluate like, Oh, Hey, I have this thing that has worked for 15 years.That's that happens to be rested. I can ship faster with that, or I can deal with this cutting-edge thing, which like I might make a critical mistake on. Sorry, my cat and my Comey. Exactly. So, nine times out of 10, the, I was going to say no, because it's just like, are you a dev just trying to play it a new toy or are you trying to ship, do you know how to ship things, which I've always worked in, nothing's broken about it.So you really need to pave the path, which is something that obviously I do for a living, but Graffio has a lot of smart people working on that. Yeah. Did I answer the question about the future?Well, Federation used to be a big sticking point and then they actually, came out with it. So I think it's less of a talking point now. And hopefully I, I haven't used it in any sort of work setting, so I don't know how actually people feel about it. All I know is that it was there were multiple competing solutions and now there's an official one.Loren Sands-Ramshaw: [00:27:48] So, I guess the last thing on graphica was app sync. I'm curious. But what kind of companies you see you saw using it? I guess I quick over here for people. swyx: [00:27:57] Okay. Absolutely. So graph yall tends to end up as a gateway meaning that it starts to wrap around other rest API starts to wrap around your other data services.And then you start to that's as natural. In my view, state of where it should lie in your stack and then your front end sort of starts to query against the graphical gateway rather than your rest or API gateway. In Amazon's terminology, it is literally called API gateway, the most unimaginative name possible.So, the graphical version of that is called app sync. Not graphically I'll get waived for whatever reason. And it really does essentially the same thing. You can define resolvers and resolve against data sources, whether the rest or a third party, or even then I can include a dynamo DB database, which there's a specialized schema for that.We can, which is really intuitive to set up. And I, I think so, people are using that Amazon music, 30 million monthly active users, it's is based on that think there, there are some clients, I, big sort of consumer brand clients. And then there are a bunch of smaller smaller of a well-known names.Like, orange theory is another one that, which we talk about a lot which is a gym that converted to like an online fitness training company during COVID that has like, that does like 2 million, monthly subscribers a month or something like that. And. And yeah, I it's used in production by the kind of companies that use AWS and they may not necessarily be, well-known names to developers, but they are successful businesses in an off their own.Right. We also have a bunch of non-profits, which I really enjoy because it helped them get to market quicker. I feel like I, I still am still performing my role as AWS spokesperson here, but like, it really, I really enjoyed this cause like during COVID, a lot of people had to go online and a lot of nonprofits actually built out their apps using app sync and they got to market in like three weeks and, started serving people.Like some of them were like homeless shelters. Some of them were like sort of critical medical care facilities and and. When you see the pace of development solve by, by, by this, by the service like you, you can get naturally very excited by them. And sorry. So let me get to the point.The point is that you want a service, a graph, your service and either someone at your company is going to build it and it's going to be. Weird and funky and kind of, custom to your company or it's sort of, specked out and developed and scaled by someone like AWS or her Sera or Apollo, w whoever else does the graphic as a gateway service?Because I, it could, because I just said like the backend stuff is the hard part. So when on, let someone else do that for you, that's the SME pitch. So yeah. Sorry. I feel really weirdly passionate about this just cause like it's a really fascinating investment. It'll be, this is the only big cloud to invest in graph you off.As you're in Google and awareness on this and now Facebook is in the cloud. So, so, I feel like it, it has, maybe it doesn't get enough credit for like the amount that is really investing in making graphical a thing and making graphical easier for people to, to put it into production. I would say it's not the easiest thing in the world because it still has to encounter a lot of AWS hurdles, like, how do you deal with IAM policies and billing and all that which has its own sort of nightmares and EWS.Nothing's perfect, but it's a trusted brand and it serves people who are familiar with AWS. It serves them well enough. Oh. One example. I think I really liked was a Yan tweet on Twitter. I don't know if you, if if you come across him he's actually done a bunch of tests and actually helped to help a bunch of clients build with ASIC.And one of the interesting things is that graph Jaan natively has his subscription sort of. Paradigm association method, method which you can implement it with like long polling, whatever. But yeah, the high thing was serverless has been using has been developing serverless, which with WebSockets like having the scalability, serverless with the persistent connections or web sockets absent has this built in.And so it's much easier to to develop sort of live apps, w. With the live reaction functionality that that website has give you with seeing them without, and to go pure serverless with API gateway. I'm sorry, I'm throwing a lot of jargon at you, but if you're in the AWS ecosystem, you know what that means?Loren Sands-Ramshaw: [00:31:42] No, I've. I've used it on one or two. What did they call it? Consulting gigs. And I swyx: [00:31:48] remember not understanding the UI Loren Sands-Ramshaw: [00:31:51] very well, like you're not feeling intuitively, but then being able to do most with like CloudFormation via the amplify CLI. swyx: [00:31:58] So I liked that.Yeah, that's a that's the common starting point which is like, if you just have a pretty common use case, I definitely recommend using a CLI then the more. Custom you get I would recommend checking out co CDK, the CAGR development kit where you can programmatically create confirmation resources to attach onto your API gateway.And that's the migration path. You start with the CLI started out, building something simple, a proof of concept get familiar with the graphical schema definition, language that maps onto your resources. Like. And that's ultimately what you want. Right? You want your, the graphical, SDL SDL that you write to to do as much work for you.So that means provisioning infrastructure in the backend and doing Kojin and the front end. Right. That's what, that's the ultimate dream of like do one thing, one source of truth. And it flows both ways. Right. And that's what I think, is. Building towards I'd definitely say it's not perfect.Like, like exactly AWS will never win any awards, but the bar is very low for AWS. Like, all you have to do is to be in better than existing services that AWS has is not trying to win the world's best API for, compared to all the other startups out there. It just has to serve existing AWS customers.Very well. So, so yeah that's kind of my perspective on that. Like, and like the core gen goes all the way down to the front end. So, EDSS has this sorry. Amplify has this idea of the data stores, which is on-device cache of your remote data, which is powered by your graph, your schema.I remember Loren Sands-Ramshaw: [00:33:16] When Twitter figured out that JB amplify a client was based on a public client, but also had a lots of added things like offline. swyx: [00:33:25] Data. Yeah. And th this kind of thing is only possible with strong typing, right? Like w which is essentially what graph provides for you, strong typing of your backend schema.And so once you have that, you can produce a front end replica of that, and then it works offline which is the kind of thing that you basically only possible by vertical integration. And if you don't, if you piece things together yourself, then you're on the hook for building all of that.Which is pretty rough. So like, I just think it's amazing that they want an investment that's going into this. I feel like it's really rough to make easy and get right, because the surface area is massive, but but I think that the vision is correct. I think the vision of like, let's make this graph, Gail schema do everything.Drive make it the source of truth and drive the whole app. And when you do migrations it's very easy to see what to regenerate the clients regenerate the backend infrastructure. That's the way you want to do things. Because if everything's disconnected, then you're essentially doing a lot of things twice.Like, you change the schema. All right. Then you write the resolver then. Alright. Provision the infrastructure, the backend. These can all be done in one step. If you had tight integration any Loren Sands-Ramshaw: [00:34:25] final message you'd like to give to the readers in the graph? Yoga. swyx: [00:34:28] Enjoy the book and ask the authors for coverage of relay.Cause I feel like there's a lot and no fault to you. Like I think graphic equals ecosystem is big enough and you already did a fantastic job of covering all of these things. I just feel like, Apollo is one perspective on what graft Cal could be. And there are very, very smart people that I really, really respect that love relay and I don't know anything about it and I wish I could read more about it.Loren Sands-Ramshaw: [00:34:51] I planned on adding at least a little bit about relay pursuant to your feedback. So thank you for that. And thank you for joining us today, Shawn.swyx: [00:34:58] Yep. Likewise.

We are a party-themed podcast, so FUN is at the heart of every episode. One way we keep things fun is by mixing it up and trying new things. We play games like JS Jeopardy… (clip from episode #112) debate hot topics like should websites work without JS… (clip from episode #87) discuss and analyze the news… (clip from episode #94) share wisdom we’ve collected over the years… (clip from episode #106) interview amazing devs like John Resig and Amelia Wattenberger… and a whole lot more. Oh, and did I mention we record the show live? You can be part of the hijinx each and every Thursday at changelog.com/live. This is JS Party! Please listen to a recent episode that piques your interest and subscribe today. We’d love to have you with us.

We are a party-themed podcast, so FUN is at the heart of every episode. One way we keep things fun is by mixing it up and trying new things. We play games like JS Jeopardy… (clip from episode #112) debate hot topics like should websites work without JS… (clip from episode #87) discuss and analyze the news… (clip from episode #94) share wisdom we’ve collected over the years… (clip from episode #106) interview amazing devs like John Resig and Amelia Wattenberger… and a whole lot more. Oh, and did I mention we record the show live? You can be part of the hijinx each and every Thursday at changelog.com/live. This is JS Party! Please listen to a recent episode that piques your interest and subscribe today. We’d love to have you with us.

Make sure to subscribe to the podcast and youtube to get all the podcast. The new DAK SAVAGE Discipline GO drink from Origin Labs. All natural Only 95g of caffeine Only 5 calories KETO An energy drink that is actually good for you. Get it on amazon for free shipping or at Originmaine.com and use code DAKSAVE10 on any and all products. BRANDON: IG: @harrellwhitetailranch TWITTER: FB:@HWranch WEBSITE: http://harrellwhitetailranch.com/ DAKOTA: IG: @dakotameyer0317 FB: @sgtdakotameyer TWITTER: @DAKOTA_MEYER WEBSITE: https://dakotameyer.com/ YOUTUBE: Dakota Meyer OWN THE DASH: IG: @ownthedash FB: @ownthedash TWITTER: @ownthedash WEBSITE: https://ownthedash.com FLIPSIDE CANVAS: IG: @flipsidecanvasprints FB: @flipsidecanvas TWITTER: @flipsidecanvas WEBSITE: https://flipsidecanvas.com/   Follow John Resig here: https://www.instagram.com/johnresig/ And Check out The Chive https://www.chivemediagroup.com/about

We continue with the #InsightsPodcast series, and on this edition, we have Ritesh Arora, Co-Founder and CEO of Browser Stack, a mobile and web testing platform. In this podcast you will hear about Ritesh's journey as a young engineer how he pivoted through a few startup ideas before landing on the BrowserStack idea. And how he bootstrapped the startup to more than $20M in revenue - a humongous achievement for any founder. Ritesh comes from a family background in business, and always had an eye for venturing on the entrepreneurial journey. Teaming up with his roommate from IIT Bombay, Ritesh started his first startup in final year of college: building a product for sentiment analysis in 2005, which involved him picking up machine learning and natural language processing way before AI/ML became fashionable. “I read probably about every research paper published on the topic at that time, about 76 of them. Went through them multiple times and came up with our own algorithm.” Unable to come up with a go-to-market for the product, Ritesh and Nakul decided to take up jobs, but the desire to build something consumer-facing got them started soon on their second venture, in the space of information aggregation on the internet. This time around they were even able to gain traction, but monetization and identifying the right business model proved to be a challenge. Ritesh and Nakul spent a year brainstorming before stumbling on the problem that BrowserStack solves today, while consulting with companies that were seeking their help in building machine learning solutions. ‘Testing website on internet browsers' was a challenge for thousands of developers globally and something that Ritesh and Nakul experienced first hand as developers . Ritesh and Nakul, set out to simplify the journey of developers by helping them test and debug their website on different browsers (mainly Internet Explorer at that time). The traction they got this time around was explosive, starting with 10K beta users in three weeks (thanks to John Resig's tweet), moving to a paid offering soon that grew to $20K monthly revenues in about 4-5 months and $1M annual recurring revenue at the end of year one- all this when they were just a team of two, working out of a coffee shop in Mumbai! The focus on global market from day one helped them scale to $20M annual recurring revenue in a span of four years with just a 50 member team. They realised the need to scale up the organization to be able to sustain the growth and decided to get advisors on board who can help mentor the team in the right direction. The fund-raise for BrowserStack was more about finding the right partner than about raising money. Ritesh speaks about the value that a good investor brings on board especially in the scaling phase, because the founder is always doing it for the first time while the VCs have helped many such companies scale. Apart from talking about the journey of choosing the right investor, Ritesh shares learnings for younger entrepreneurs, from the early days and emphasizes on focussing towards solving large problems, getting feedback from customers, not solving for monetizing in early days and building a great product that makes the customer's journey frictionless. “When your customers use your product, they should feel that it has changed their life” he says. Tune in to the podcast to hear Ritesh's phenomenal journey which has become an epitome of bootstrapping your way to success.

On this week's episode of the freeCodeCamp podcast, Quincy interviews Shawn Wang (@swyx). We talk about "learning in public" and his transition into tech from finance, where he left behind a job that paid him US $350,000 per year. Shawn grew up in Singapore and came to the US as a college student. He worked in finance, but at age 30, he burned out. So he decided to learn to code. He used freeCodeCamp and a ton of other resources, and since then he's worked as a freelance developer, and at several companies including Netlify. Follow Shawn on Twitter: https://twitter.com/swyx Follow Quincy on Twitter: https://twitter.com/ossia Here are some links we discuss in the interview. Shawn's Projects: The official React subreddit that Shawn moderates: https://reddit.com/r/reactjs Shawn's article on No Zero Days: https://www.freecodecamp.org/forum/t/no-zero-days-my-roadmap-from-javascript-noob-to-full-stack-developer-in-12-months/164514 Job Search / Salary Negotation articles: Cracking the Coding Interview: https://fcc.im/2UihbNm Hasseeb Qureshi's story of getting a $250K/y developer job at Airbnb: https://haseebq.com/farewell-app-academy-hello-airbnb-part-i Steve Yegge's "Get that job at Google" essay: http://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html Patrick McKenzie on Salary Negotiation https://www.kalzumeus.com/2012/01/23/salary-negotiation/ Quincy's recommended article: I spent 3 months applying to jobs after a coding bootcamp. Here's what I learned: https://medium.freecodecamp.org/9a07468d2331 Algorithm Expert: https://www.algoexpert.io Full Stack Academy https://www.fullstackacademy.com Shawn's Learn In Public movement: Shawn's Learn In Public essay https://gist.github.com/sw-yx/9720bd4a30606ca3ffb8d407113c0fe5‌‌ Kent C Dodds' Zero to 60 in Software Development: How to Jumpstart Your Career https://www.youtube.com/watch?v=-qPh6I2hfjw&app=desktop‌‌ Cory House on Becoming an Outlier: https://vimeo.com/97415346‌‌ Brad Frost on Creative Exhaust: http://bradfrost.com/blog/post/creative-exhaust/‌‌ Patrick McKenzie on the origin of the word "friendcatcher": https://news.ycombinator.com/item?id=511089‌‌ Chris Coyier on "Working In Public": https://chriscoyier.net/2012/09/23/working-in-public/ Links to other things we discuss: Shawn's Software Engineering Daily Interview with Sacha Greif: https://softwareengineeringdaily.com/2017/08/09/state-of-javascript-with-sacha-greif/‌‌ The origin of No Zero Days: https://www.reddit.com/r/getdisciplined/comments/1q96b5/i_just_dont_care_about_myself/cdah4af/‌‌ John Resig, creator of jQuery, telling his team to rip out jQuery: http://bikeshed.fm/180 ‌‌Jeff Bezos' Two Pizza Team rule: https://buffer.com/resources/small-teams-why-startups-often-win-against-google-and-facebook-the-science-behind-why-smaller-teams-get-more-done‌‌ Shawn's "You can learn so much on the internet for the low, low price of your ego" quote draws from Paul Graham's Keep Your Identity Small: http://paulgraham.com/identity.html‌‌ Shawn's Impostor Syndrome Bootcamp Podcast: https://player.fm/series/impostor-syndrome‌‌ TypeScript's growth via npm surveys: https://mobile.twitter.com/seldo/status/1088240877107965953

On this episode of the Bike Shed, we're thrilled to welcome special guest John Resig, creator of jQuery and front-end architect at Khan Academy. The conversation begins with a discussion around John's work on jQuery, one of the most influential libraries in the history of the web. From there the discussion shifts to John's role as front-end architect at Khan Academy and how he balances feature development and paying down tech debt or exploring new technologies. John and Chris then discuss the rate of change of front-end technologies, and John provides wonderfully pragmatic guidance distinguishing the rate of innovation from the perceived needed rate of adoption. The conversation also ventures into discussions around the trade-offs involved in open sourcing internal projects. Lastly, they touch briefly on the topic of GraphQL based on John's work at Kahn Academy, as well as his in-progress book, The GraphQL Guide. A little bit of everything with one of the most influential web developers of the past 15 years. What more could you ask for? jQuery Khan Academy Removing jQuery from GitHub.com frontend React hooks Webpack Aphrodite styling library from Khan Academy Event Stream NPM Package Security Issue The GraphQL Guide Sangria GraphQL Framework in Scala John's personal site John on twitter

In this special rebroadcast of JS Party, Jerod and Suz talk with John Resig about how he’s using GraphQL at Khan Academy, some of the mistakes and successes using GraphQL, John’s feelings on jQuery, and community Q&A.

In this special rebroadcast of JS Party, Jerod and Suz talk with John Resig about how he’s using GraphQL at Khan Academy, some of the mistakes and successes using GraphQL, John’s feelings on jQuery, and community Q&A.

John Resig is the Co-Founder and President theCHIVE, the media company that's behind CHIVE TV. In this podcast we go behind the scenes of this brand and get insight into the businesses success. Keep Calm Chive On.

Jerod and Suz talk with John Resig about how he’s using GraphQL at Khan Academy, some of the mistakes and successes using GraphQL, John’s feelings on jQuery, and community Q&A.

Jerod and Suz talk with John Resig about how he’s using GraphQL at Khan Academy, some of the mistakes and successes using GraphQL, John’s feelings on jQuery, and community Q&A.

Mariko Kosaka さんをゲストに迎えて、JavaScript コミュニティ、Chrome, HTTPS, 標準化、Unicode などについて話しました。 Show Notes OneSignal - Multi-platform Push Notification Service Jed Schmidt on Twitter: "headed to meet the legendary @miyagawa in a few" BrooklynJS John Resig - JavaScript Programming Khan Academy John Resig - search.cpan.org ECMAScript 5 Strict Mode, JSON, and More Chromium Blog: A secure web is here to stay Chrome will mark all HTTP sites as ‘not secure’ starting in July Yahoo! JAPANサービスは常時SSL（AOSSL）に対応します Let's Encrypt - Free SSL/TLS Certificates Issue with TLS-SNI-01 and Shared Hosting Infrastructure Dave Winer on HTTPS People sometimes wonder why the @googlechrome team pushes HTTPS so hard EV Cert is Broken TC39 - ECMAScript Automatic Semicolon Insertion Editorial: Add Automatic Semicolon Insertion hazard clause Brendan Eich JavaScript Standard Style semistandard Kebab Case Flag Symbols ドコモの絵文字、MoMAに収蔵 ユニコード戦記 ─文字符号の国際標準化バトル | 小林龍生 Han unification UTS #37: Unicode Ideographic Variation Database Inside Frontend O'Reilly Velocity Glimmer 超速! Webページ速度改善ガイド Stimulus: A modest JavaScript framework for the HTML you already have. YouTube for Apple TV overhauled with cross-platform design Safari Technology Preview 46 brings Service Workers to Apple’s browser Podcasting Guide 2017 – Tatsuhiko Miyagawa’s Blog

Ever wonder how to walk away from the open source project you've built, loved and maintained? John Resig, the creator of jQuery, joins us to talk about how to say goodbye. We'll look at what leaving your project feels like, how to do it in a healthy way and what moving on can bring to your life.

John Resig is the co-founder and CEO of Resignation Media, responsible for the wildly-popular and creative humor website called theCHIVE.com. During this lively discussion with Dave, John shares the story of how he started the family business with his brother, their entrepreneurial formula for success, what he does to foster his company’s culture, and what this super-chill guy actually stresses out about. Discover how the simple idea of storytelling and sharing funny photos -- and selling Bill Murray t-shirts -- ultimately created a thriving online community with a sense of humor and a heart.

John Resig is the co-founder and CEO of Resignation Media, responsible for the wildly-popular and creative humor website called theCHIVE.com. During this lively discussion with Dave, John shares the story of how he started the family business with his brother, their entrepreneurial formula for success, what he does to foster his company’s culture, and what this super-chill guy actually stresses out about. Discover how the simple idea of storytelling and sharing funny photos -- and selling Bill Murray t-shirts -- ultimately created a thriving online community with a sense of humor and a heart.

This week the TNQ Podcast is proud to welcome John Resig, founder of The Chive, the world’s largest entertainment website. This master entrepreneur’s Never Quit story takes place in the ultra competitive world of digital entertainment, where you must “innovate…or die.” Join former Navy SEALs, Marcus Luttrell, and TNQ Podcast producer, Wizard, as they unlock the mindset behind how you grow a startup into a massive digital presence, highly engaged community and charitable organization, all while never quitting when the times got tough. This episode of the TNQ Podcast is a great combination of being highly entertaining, while also packed full of truly actionable advice you can apply today in your own life. One minute there will be a story of Marcus alligator wrestling or being struck by lightning, and the next minute full of hard-truth advice to millennials about what it means to be a productive citizen, or how the keys to modern day success are still rooted in old-school work ethic. Also, find out how Resig’s unusual balance of work and play, or willingness to experiment and fail, are key elements behind his extraordinary success. Once again this week, Marcus, Wizard, and the TNQ Podcast team, deliver on their mission to bring you some of the world’s most inspiring and impactful #NeverQuit stories. Help spread the word by sharing the show with friends and family. “Great Stories Ignite Legends” Support the show.

In this episode, Leah Silber, CEO of Tilde, Inc. and Ember.js core team member talks about what she's learned building communities, organizing events, and running a business. We talk about how people can move from "observer" to "participant" and grow their own healthy communities and companies. Links: Leah Silber: EmberConf 2016: The Morning-After Post-Mortem Event Driven: How to Run Memorable Tech Conferences Transcript: CHARLES: Hello everybody and welcome to the Frontside Podcast, Episode 43. I am Charles Lowell. I'm here with Brandon Hays, and a very, very special guest. Brandon, do you want to introduce her? BRANDON: Yeah, we're here with Leah Silber. She runs Tilde? 'Tild'? I always say this incorrectly. LEAH: You can't be saying it incorrectly. When we named the company, we knew we were choosing one of those names where people are going to say it and you just have to accept it. That's fate and that's how it goes. We usually say 'til-de' here. BRANDON: Okay, I'll say Tilde, and you can say 'Frontsi-de'. CHARLES: The way you say Tilde says more about you, than it does about us. BRANDON: Yeah, it's a verbal Rorschach test. We were really, really glad to have your time. We know that people actually work with you as a consultant for these kinds of things to help with communities, conferences, build their businesses. So, you have a lot of gathered expertise around these things. Would you tell us a little bit about yourself, about your background, what you do and kind of how you got involved in tech and running businesses? LEAH: Sure, not unlike an elevator pitch but I have been working in open source startups and companies, I want to say it's probably been like 10 years now or crazy something like that. But my first open source project that I was seriously involved in was jQuery, and that was a long time ago and it was pretty magical in retrospect because jQuery was, at the time, it was like coming out of nowhere. Nobody thought it was going to really make a dent in technology. John Resig was this clearly brilliant but still this nobody, sort of working on this project in his spare time, and Yehuda Katz jumped in and a bunch of other people earlier at the beginning. It was a time in the ecosystem where they were a little bit laughed at the room. In retrospect, there was a time when the ecosystem was a little more rude, like some of the competitive behaviors that happened back then. Thankfully, it just wouldn't fly right now. But it's been super cool to be involved with something and be able to witness something at the ground floor where this little idea and project that nobody takes seriously because there are these seemingly massive projects and landscape, and then just sort of watch it take over the world. It was a process obviously that took a little while. But again, in retrospect, it didn't take all that long, so that was really an amazing experience to watch. It was also my first really intense open source community learning experience. Everything from witnessing what kind of personalities got involved and how they did it, to watching John who sort of -- I want to say he's a consummate politician, but he's not a political person. I guess what I mean, he's just really good at people. CHARLES: He's like a diplomat? LEAH: He is. But like the sort of diplomat where you're in a battle and then suddenly a treaty happens and you just don't even know what happened but everybody's happy and you vaguely remember that you all hated each other a few minutes ago. He's really talented. Obviously, also having the technical chops to build something impressive helps with that. But watching how different personalities in open source interacted with each other, and even just for myself, like learning how to be a good open source citizen and learning how to contribute to a project and finding a way as a non-coder at the time to be useful in an open source project was really amazing. That was something I was involved with for a number of years. Then, slowly as time went on, I got involved in other projects and other events. And along the way, I was like, "This is really fun. Why am I working not in technology but doing this at night." Well pretty early on, I moved out from New York to California which is, I guess, the rite of passage or at least was. Got a job at my first startup, spent a couple years there, sort of again learning everything in fast forward because that's how startups work. I've done that a couple of different times over the years, thankfully not that many. I've managed to have what I consider impressive stability in a startup land where people can end up needing to change jobs, projects and positions very rapidly. Nowadays, I mostly focus on Ember work. There was a big chunk of time in the middle where I was focused on Ruby on Rails work. I do events, conferences, meet up groups, community management. A lot of the less glamorous stuff involved in once a project does become more successful, like figuring out a governance strategy, and figuring out how you protect your brand and what happens when lawyers and PR people and all these other different industry people start coming at you with all these questions that you hadn't thought about. How much infrastructure is too much infrastructure? What happens when the project starts having money? All these sorts of things. I feel like I've lived through a bunch of projects and their growing pains, and have a really solid understanding of the different routes. I'm still learning every day, and that's kind of why I love it. I started with my co-founders, I started my own company about five years ago which I'm always pleased and astonished to still be existing. Obviously, I watched companies spin up and die down overnight in the fast-paced technology sector. So, I'm a fan of stability and continuing to exist, is basically the top of my list. But that was about five years ago now, and it's been really great. I would never previously have identified myself as an entrepreneur. I had this, I want to say now, misconception that I was a support person, that I was the perfect second-in-command that I needed somebody at the top of the food chain who had these brilliant ideas and then I would be the person who would come in and say, "Great idea. Let me make it happen for you," and like operations and execution. At some point, I realized that that's not real. There's no reason that the person who has ideas has to be more in-charge than the person who makes ideas happened, like these two skill sets, if they're not in the same person are equally necessary. I think that was probably a little bit of standard sort of impostor syndrome kind of stuff. And also, there's a lot of pressure involved in thinking about yourself as in-charge of something important with high stakes. But I don't know. At some point, I think I watched enough people do the job and I served as that second-in-command or upper management kind of role for a lot of people. I realized that primarily, the difference between the people who were running the show as figureheads and the people who were actually running the show day to day, the difference primarily was just boldness. Like one of them had the audacity to say, "I can be in charge. I'm going to start a company. I'm going to do this." And that's not actually that big of delta so 'fake it until you make it'. BRANDON: I kind of want to lock in on that concept a little bit. I don't want to let that just float by on the river. That is something that has been such a profound lesson in my life over the last six months or a year that I think, a lot of us that wind up running companies kind of fall into that by accident or happenstance or something. You always have this weird left over hope from times where you work for other people, that somebody will step in and be in charge. It's a deal where everybody stands on the line and like, "Okay, whoever wants to step forward, step forward, and everybody steps back but you." And that feeling of being the last person standing when everybody else has backed, just by nature of not stepping back, you realized, "Oh, you know what --” Like there is such a thing as an operationally oriented CEO. So it really is the idea that you just said, it really is a matter of boldness and being willing to be the person, where the buck stops, is really the only difference between a person that feels like a really great second-in-command versus the person that feels like they could be running things. LEAH: There's just this magical myth of the big important idea person. Anything that's going to be successful or most things are going to be successful I guess, they're rarely just one person sitting on a mountain. One person starts with a shred of an idea, and then everybody around them sort of helps turn it into something real. So it could really be anybody who has that first instinct that it doesn't mean that that person has to be in-charge. CHARLES: I'm wondering, if there's any parallels there between, "Have you borrowed any of that boldness through community?" Or has there been any bouncing back and forth about lesson in terms of somebody has to take the lead on something. LEAH: Actually, it's harder a little bit in community stuff because taking a lead typically means or we think it typically means making a decision. I think that's where in open source, a lot of people go wrong, and a lot of open source projects end up with a top down management strategy where somebody is in-charge and that person tells them what's going to happen and then everybody, for example, freaks out about backwards compatibility. Then they're like, "Oh, yeah. I got a plan for this." But part of that is like you see a power vacuum and you think like, "Okay, I can step up and take this." But in open source, that's not really the ideal way or at least not in the philosophy of most of the projects that I've been in which is you only need to ask people what they think along the way, differently than in a professional environment. Like in Ember, we have the RFP process where we source a feedback before we make massive changes. That just makes everything, like you can even really say, "This is the exact thing I want to do," and you can lay out a really great plan and take that leadership role. But in a framework where it's not an edict, in a framework where it's like, "Okay, now everybody else, what do you think about it? How can you improve my idea?" And there's a whole bunch of things that happen. The first and most obvious is your idea gets better because people point out things that you didn't think of or don't necessarily personally have the experience or have noticed. But also, people just feel consulted in a way that is more critical. I like to think people want to feel consulted in work environments also. But I guess when you're the boss, you can get away with just saying, "This is the policy. I made the policy." In open source, people won't really let that fly. You can't just say, "This is a feature set. I've made this. That's the rule." Certainly not if you want them to use your project and contribute to your project and help you be successful. There are some similar things to think about when running a company versus running an open source project. But essentially, the project has to be a significantly more collaborative environment that makes people feel invested in the project and want to stick around and want to become other contributors so that the project can grow, succeed, and have a lot of people involved rather than just one-idea person. BRANDON: I was listening to a podcast recently that I can't remember which one it was but the people were talking about a different tech community and their definition of community really surprised me and it made me realize that people have different definitions for what a community is. LEAH: Wildly. BRANDON: Yeah, and so I'm curious about what your definition, in terms of an open source community, what it is and what it's job is for that open source project? LEAH: I don't have a dictionary definition and in a lot of cases, it's kind of a feel. Like I like to talk about sometimes how the different communities I've been involved with had a different feel. In an indirect fashion, a lot of what your community is comes from the people who are theoretically in charge, be that your core team, or your benevolent dictator, or whoever sort of the thought leader. That person or people really influence the kind of community that you create with their behavior. For example, the kind of community where the person in charge just tells you what the project is going to do next and does it, has a very different feel where the person in charge says, "Here are my thoughts. What do you guys think about it? How do you want us to do this? Do you have suggestions? Did I miss anything?" I think if there's enough premeditation and consideration that goes into the decisions that that person makes, that he or she can really shape a positive community, a collaborative community, and a supportive community. In Ember, we have managed to collect a group of amazing people who want to help each other, want to support each other, and who are enthusiastic about what's happening, and on most good days who don't freak out when they get a little worried that something isn't happening the way they want it to because they can trust that they're going to have a period of input and their needs are going to at least be considered. You don't always get the exact thing that you want. But it's a lot better if you know that your concerns were heard, evaluated, and maybe there's some other plan or way to sort of not completely screw you, basically. Ember's been really good at taking care of people and their needs even as the user base is more needy in different changing ways. I guess a community is a living breathing thing. For sure, it changes. I'm oftentimes sort of paying attention to the undercurrent of what happened, what's going to be the outcome of this? Having chats with people, especially people in theoretical leadership roles, about different ways to handle different situations that will keep as many people as possible, happy and supported. BRANDON: As you were describing that, to me, it feels like you've highlighted something interesting about communities, which is, you can use a theme and not be a part of its community. Somebody could use Ember and not choose to be a part of the Ember community. But participating in a community is kind of the desire to influence that thing in some way. Like, when you say they want to have their needs represented and they want to be a part of the RFC process, there is some part of it where I guess a lot of it has to do with just any kind of connection with other people who do the same thing or probably do the textbook one. But I also feel for a lot of people, there's a desire to be able to have their needs represented and met and feel like they are somehow a part of the direction of this thing, as well. LEAH: Yeah. It totally varies based on your personality. Some people just want to feel like they are a part of it. Even if they feel like their interests are well represented, you see people all the time looking for small ways to contribute because it's fun. It's exciting. There's progress happening, there's success, it's something that isn't like a lot of other opportunities that you have especially if you've been in some other industry, or some other kind of job. You don't always have this thing where you can sort of be part of an organism and a community and watch something evolve and maybe even have input in it, or just have 40 friends around the world who want to chat with you about it at any given time. It's fun. BRANDON: A question that I have in terms of following up on that is your role on the Ember side of things, I'm assuming and I want you to clarify if I'm not hitting it properly. My understanding of your role in the Ember ecosystem, in addition to handling a lot of the unglamorous logistical components is to help kind of grow and foster that style of community and Ember's become pretty well-known for having a unique focus on quality of community. I'm wondering if that's intentional or if there are things that you do or if it's sort of been luck. I don't know how much intentionality has gone into that or how much the community design has gone into that. LEAH: For sure, it's mixed. There's a lot of things where select events are really good example of setting the tone. And there's like an evolution of events that I like to follow in some of my newer growing communities that I'm focusing on where you start out with a little more of a campy feel, it's a little scrappy. And slowly, you iterate to get into a much more professional feel. But all along the way at those stages, having that event, the logistically top quality really sort of changes the tone of everything. If you show up to an event and it sort of haphazard and no one knows what's happening, you might all love each other and you probably will have a good time. But it's a different experience than one where it's sort of run like a well-oiled machine where you get a sense of people take this seriously. This is real. This is impressive. We're building big, amazing things together. We can accomplish together. So some of it is just on all the little things. Event is just one sort of example. But all the little things that go into the well-rounded ecosystem, I try and focus on quality so that obviously, there's a whole bunch of people focusing on the quality of the code. But I also want to focus on the quality of the events and the website and helping meet ups run quality events around the world and helping people show off that they use Ember and are proud. Any sort of these peripheral things -- the better you execute them, the more of an overall, "Wow! This is real. This is serious. I can stake my professional future on this." The more of that kind of a feeling that you're going to get. Community growth is organic in a lot of ways, obviously. But there are certainly things that you can do along the way to help foster the community growth. There's like personality things like making sure everyone's actually welcoming, and that people want to come and get to know you and work with you and get involved in your technology. There's things like the tactical processes of our RFC. Making sure there are ways for people technically to get involved. There's things like a focus on documentation, which again just makes it easy. So, it's really an overall quality thing every step along the way, and a lot of community overlook the parts of building community that aren't code. You can do that but you end up on a different trajectory than a project where you pay attention to all the peripheral things. CHARLES: So, I'm actually curious because I've witnessed the things that you've done like on a grand scale which definitely have had that air of quality that you're talking about. But I'm curious about these kind of nascent communities that you're talking about and kind of just, one, just curious about what they are because I'm curious. Then the second is, for people who might be speaking of doing something similarly, like starting something small that they want to grow into something huge, but actually that concrete, small scope. What are the things you can do with limited resources, if you have limited resources and you've got a small scope, what can you do to imbue it with that sense of quality that will carry you to higher places? LEAH: I guess the first thing to think about, and I hope this does not sound bad, but is whether or not your project actually needs a community. By that I mean I certainly think open source projects should all be actual open source projects. So you should accept pull requests, you should let people file issues, you should have collaborators, etcetera. But there have been a lot of projects along the way that I've been involved with helping with where we looked at it and said this doesn't need to be a community. This doesn't need to have a conference every year, or it'll have some sort of community right just amongst people who contribute but it doesn't need to be like Ember, like Rails. We're a whole giant ecosystem that spins up. For example, over the years, there have been projects like Handlebars, Bandler, and Thor. These are projects that tremendous numbers of people use. You don't run into anyone who says like, "I'm a member of the Thor community." And that's perfectly fine, right? There's sort of a version of a project where you have an MVP, you have a good website, you have good docs, you have a bunch of contributors, and that's all you really need. Then there's the version where you want it to be a much bigger, more involved setup. So one community that, I would say, in a nascent stage right now is the Rust community, which I've been peripherally involved with. I'm not on the team. I'm not doing significant community masterminding but I have been working with some people in the project to do agree with me on the value of this quality. And so, I've helped them. We just ran Rust Conf this last weekend which was their first conference. It was 250 people in Portland. It was really, really fantastic. I've worked with them on, for example, making quality swag over the years and trying to figure out what level of control over their brand. It's not too much but still protects the brand enough, things like that. They've also modeled some of their governance kind of stuff after the Ember community which makes sense. Yehuda is involved in both projects and he's a big proponent of a lot of that stuff. But it's been really cool to watch. Like first Rust was saying, "Oh, this how Ember does it. Let's crib some of that stuff." Now, in a lot of cases, Ember is saying, "Oh, wow! Look how Rust is doing that. Let's take that back." It's been a very good symbiotic back and forth relationship. But it really just does take the people who are leading intellectually to decide that they care about quality, to decide that they care about a collaborative community environment, to decide that they care about diversity, to decide that they care about all of these little things along the way. The earlier people recognize that these are things you need to care about, the better job that you can do. You can always sort of ride the ship most of the time. But if you start out on the right path to begin with, you're going to be able to accomplish so much more because you don't have that much course correcting to do. There is obviously, also always course correcting in Ember, in Rust, in Rails, everywhere, where somebody not speaking about code but somebody takes a misstep and the whole community sort of has to figure out like, "Okay, this is not the way we want. This is the kind of interaction to go. How are we going to fix this?" Or, "This is not the way we want. There's kind of major technical decisions to be made. How are we going to fix this?" It's an evolution. It's a collaboration. I'm absolutely a fan of the core team entity and of that core team being a medium sized group. Not tiny but a medium sized group of people who bring really, really different things to the table in terms of who they are, their backgrounds and their skills. For example, this serves me well but I am a fan of core teams that have non-coders on the core team. There's a lot of stuff that can get done for a project that doesn't involve writing a line of code. Now, obviously you want to have somebody around who understands open source and the strategy. It is in fact challenging to find people who don't have to be coders but also appreciate all this other stuff and want to be involved in it. But when you can find people like that, that's the really magical key to this more well-rounded community. I like to say, engineers are basically superheroes. They can sort of think of something and then create it and that is the power that most other kinds of people don't have. I mean, maybe contractors and welders, but if you are working at a desk job somewhere, there's not really much that you can conceive of where you have an idea, you write it down, you spend a couple months then it exists, it works, it actively changes your life. One of the downsides of that amazing superpower is that engineers can oftentimes get into a position where they think anything is possible and they don't recognize that just because they can figure out how to do something doesn't necessarily mean that they are the best people to do that thing. That comes into play a lot with these other qualitative things in an ecosystem. So, you can go to a lot of technical conferences and wonder, sort of, why is the quality not quite there? In a lot of cases, the answer is because the person in charge is not particularly skilled in this area. They are coder. They can write brilliant code but do they know how to think about where the lunch line is going to queue up and make sure that it's going to go through the phase, and that there's enough bathrooms and stuff like that. These are very vastly different skill sets. One of the past successes there is to sort of realize, "Yes, I can probably pull this off." But if I can find somebody for whom this is a natural area of expertise and I can focus on my area of expertise. Like, wow. We'll be able to accomplish so much more and everything will be better all around. BRANDON: I think you've hit on something there again that I've seen since moving into technology from -- I come from a non-technology background and there is a sense outside of this industry that people kind of have different areas of expertise. When you are an engineer, your job -- I actually think a lot of it stems from the fact that your job is to become an expert in the field of other people's jobs. So, your job is to automate something so you have to know enough about marketing to do marketing software. Then you have to know about enough about this other thing to do this other thing. So you think that you can learn anything and it's true that you can learn anything but there's a skill tree associated with each of those things. You don't realize, you're a junior level conference organizer, and maybe it might be worth talking to a senior level conference organizer. We've definitely fallen victim to that many times where we thought, "Oh, you know what? I'm pretty good at the technology side. I can give a conference talk. I must be probably pretty good at education." And it turns out that education is a multi-thousand year old skill tree that is pretty well-defined. LEAH: One of the hard parts in thinking about this for me is, I really like the MVP concept that I have taken from technology, which is you don't have to get it right. Get something out there. Figure out what the bare minimum version of whatever it is you're trying to accomplish is. Ship it, iterate. I like that and I talk about a lot of things in my life in that frame which is kind of weird when I talk to my parents about iterating on things and what not. For example, in a decision about child rearing. "Oh, my God. The first one is this way." It's a very useful way of thinking about things and I am a fan in many things of actually applying it to areas all over your life. But for something like how to run a small conference, you oftentimes don't need an MVP. You don't need to go through the stage of that level of quality because you can just work with somebody who's already learned all those lessons and already done those things. It's not like a greenfield code project where somebody has to actually start from the baseline every time it's a new project and build up all the infrastructure. You can just skip right to the front of the line. Find someone who's good at this and start out initially at a much higher level of quality. BRANDON: I want to kind of dig into that a little bit and ask about you wrote a really great blog post earlier this year about your experiences running Ember Conf. It's so obvious the amount of effort and kind of thought, not just effort, but like directed effort and thought that goes into building a really great experience for people. I'm wondering if you have like certain areas that you look for and noticing whether somebody has really put a lot of thought into designing a good conference experience for somebody. If somebody were hoping to do something like that, what are some of the areas that tell you that you're dealing with like a really good, thoughtfully designed conference? Or where does that effort go basically when you run through the process? You only have so much time and effort you can put into this thing to create that experience, not the minimum viable conference, but the conference when you look at the division of your time and doing conference stuff. I think people wind up being surprised how much goes toward one thing or another. LEAH: I'm not entirely sure how to answer that question because you don't usually get insights into what people are doing along the way. I go to fewer conferences these days because I find myself irritated. I don't even like the way it sounds but it's kind of true, where I go to a conference and I'm really trying to focus on the content and I'm really trying to focus on the goodwill of the people who are organizing it. Oftentimes, it's just so many moments where I'm like, "That should be better quality." Like it is very easy to get that right. You just need to have thought about that. You just need to plan for that. I don't think there's many opportunities to sort of figure out those things ahead of time from somebody else to make an assessment of how a show is going to go. I can say that there are sometimes things that I see on just the websites where I'm like, "Oh, that is not a good sign." There are tools around for most of the things that you would want to do like selling your tickets and collecting information, and the online pre- event functionality. It's rarely a good sign when you see someone build their own. It's sort of another engineer foible kind of thing. You don't need to reinvent the wheel. It takes substantial energy to reinvent the wheel. If you go with something that already exists, you can focus for example, on all this other quality stuff. But there's also sort of the way in which people build the content of their conference, like that's super telling. Maybe not even so much about logistics but it is pretty telling about the community or at least the people running a show as a representation of the community. For example, I think it's pretty much conventional wisdom these days that you want to have blind call for papers. It's not reasonable to me when I see someone not do it that way. I understand that small events maybe just go invitation in the first year or two. I think that's actually a pretty justifiable thing. We don't have the critical mass yet to get enough submissions in for a program, or we're not really sure how to execute on that, and our community has these specific people who we know are really talented and will do a good job. I think you end up with usually a subpar roster that way because you don't have the variety of experience that you'd be able to attract in a call for papers. But what's super weird to me is, yes, we're going to do a call for papers but we're not going to go the classic extras steps that open source and technology as a whole has learned that will really help this task go better and help eliminate latent biases and things like that. That's kind of weird. I still see it sometimes. I find myself confused by it. I suspect more than anything that people just haven't thought of it or don't know how to execute on the strategy that a lot of other conferences has figured out a successful. I don't know, part of the reason I don't like to go to conferences so much is I remember when I was making all these mistakes, and I don't want to be that person who's really critical of someone who's trying to do something good but it's hard. Once you have that experience and once you sort of know better, it's hard to watch somebody else stumble over the same things you stumbled over. You feel like, "You should know that. I know that." CHARLES: So, is there a community of conference organizers? It seems like they need to be some sort of meta conference or some sort of meta community of community organizers. BRANDON: There is Conf Conf. CHARLES: Are you serious? LEAH: I might not be impressive enough to go to something called Conf Conf. I don't know. A lot of those things actually when you get to, "Oh, it's industry, upper-tier collaborator events." They're often times invitation kind of things and I'm not very cool. I don't know. I see things like that sometimes. There's this conference about speakers. It's like speakers conf – CHARLES: Oh, speakers conf, yeah, and it's like in Aruba. LEAH: It seems cool but I'm always like, "How do you get invited to that?" CHARLES: Yeah, that's the part -- BRANDON: How do you get into that club? LEAH: I know people who should be there and don't know it exists, or people who should be there but just - I don't know, no one has invited them, and it's invitational. It's hard to say. But I guess what I was going to say is over the years, I have at times belonged to different online forums that were trying to scratch that itch. The most successful one was probably for a good five, six years. There was a very active community of conference organizers in the Ruby space. But I think most of those people have either stopped doing conferences or gotten to a place where they just don't need that much help anymore, and there hasn't been like an influx of new people doing it. So there isn't really any strong community like that that I belong to today. That's a challenge in anything you face, where once you don't need the help anymore, people don't stick around to help the other people and it's hard to sort of organize that way. BRANDON: That sounds like a big opportunity to me. But it sounds like an opening or a hole for providing something like that. Do you do any consulting for people on this? Do people hire you to help design a conference experience? Because I know that the ones you've put together -- you're pretty well-known for being one of the best in the business for this. LEAH: Thank you, I think. No pressure at all. I do consulting, though obviously, that's mostly for companies and not communities because communities don't typically have money for that sort of thing. In communities, you need to create your own experts, and in an ideal world, there are people who recognize that when they're at the beginning of the learning curve, they should reach out to people who are further along and benefit from their experience and do things like read blog post and books and what not. The blog post that you mentioned earlier, it was absurdly long. I was surprised that anybody read it and then a lot of people read it. I was surprised because of the length but I was also surprised in the way that it's difficult to come up with a conference talk where you're sort of like, "I know all this stuff," but I don't know what amongst this knowledge base is interesting to other people, and I don't know what other people don't know and I know the stuff so obviously, it's not impressive. But I sort of forced myself to write it anyway because it was just such a big endeavor and there were thoughts even for myself that I wanted to preserve for later. Then I was pleasantly surprised by how many people read it and had comments and had useful things to say, or even just like, "I appreciate how much thought went into XYZ. I wouldn't have thought that. It was value that came out of that blog post that I didn't think of at the beginning. The value of other people getting a chance to recognize what kind of thought and planning needs to go into having something like that execute flawlessly, or dealing with things when they don't execute flawlessly. BRANDON: One thing that that was an obvious expenditure of effort, because you started so early in the process, many months before the conference was the Women Helping Women Initiative. I saw that really early on. I actually don't think that was precedented in conference organizing. Can you tell us a little bit about that? I don't remember how far in advance it was, I just remember thinking it was absurdly far in advance and very well thought out and very well designed. LEAH: Well, it was early. For example, I actually have to email the Women Helping Women group today with a long list of thoughts and activities for next year. I feel like I'm super behind because it's September 15th and the conference is at the end of March. Last year, I think we were already talking basically like 2, 3 weeks after the previous year's conference had ended. So basically, I looked at the conference in 2015 and it was great. I was really happy with most areas of it but I was not happy with the representation of women. There's so many groups that in fact, the conference would benefit from that representation of, but women was obviously a target that I thought I could potentially bring something to the table on being a woman in technology and in Ember. I spent some time thinking about all the various women in tech efforts. I have been involved over the years in a lot of things that felt good and said good things but at the end of the day didn't seem to accomplish very much. Right from the beginning, I wanted it to be a tactical effort. I wanted it to be like a short term pipeline of, "We put this in one end and we get this out the other end, and we have accomplished XYZ." Because it's important to have lots of organizations that make people who are under-represented in any community feel good and feel welcome. But it's also just as important and a little bit less prominent, in most cases, to have those same people then become leaders in that community. That' sreally sort of a signal to everybody else that they're welcome and that they can accomplish things. I looked at our community and I thought there are already, actually, really awesome women here. Not as many as I'd like. But I know a lot of women who are impressive and who are like, "Why aren't they on stage?" So, I sort of approached the effort last year from the perspective of there's a lot of organizations out there working on the women in technology pipeline problem, and it's a very real problem. Hopefully, they're going to do a solid job. There's a lot of insights and I'm watching and it's cool. But I want to focus on the problem of -- let's not call it a problem -- but I want to focus on the situation of the people who are already here and helping them take those leadership roles and step up and really join the community at every level. Not just at the entry level. We've come in through the fix the pipeline problem setup. CHARLES: And then hope everything kind of magically works itself out from there. LEAH: Yeah, which shockingly, it doesn't. I don't know... We spent many, many months basically supporting people at every step along the way from, "I want to go to this conference," to, "I'm a speaker at this conference." And we did things like brainstorming about what kind of proposals people could submit. We helped each other once we had a critical mass of a bunch of talented women. We helped each other with our proposals. We helped each other with our ideas. I organized podcasts where the program committee did question and answer sessions with the women. We did some hangouts where women who had more experience than the rest of us came and talked about their first time speaking or their experience getting to know a community or their experience learning to code and we encourage each other in a lot of ways. It's just a really positively pushy support group. We encourage each other. It's funny because it was hard along the way sometimes because you don't want to be too pushy. I was always worried and sort of dancing on that line of, "I want to repeat to you, you can clearly do this. You have said things. You have accomplished things, look at your education, look at your career. You are obviously, obviously good enough and impressive enough to be on the stage and I want to keep reminding you of that so you do it. But I also don't want you to feel like you are being bullied into it." Not everybody wants to be a leader. Not everybody wants to be in a role of getting up on stage and giving a talk. I had a couple of the participants come talk to me or email me after the program saying, "That was really helpful. That was the nudge that I needed." So that made me feel good about the various interactions along the way and it's always just going to be something that you have to do in a very sensitive manner. But there are women that I knew that were here that were talented and then so many women that just came out of the woodwork where I was sort of like, "I know your name or I didn't know you at all," and like, "Why don't I know your name? You're incredible. You're better than half the people I see on stage at a conference." And so we worked on this for months and months and months. I got a bunch of women in the community who were in sort of transitional leadership roles which is I thought, "Hey, you're a community leader," but they weren't sure they were a community leader yet. I got a lot of people like that involved to help nudge along all the other people who could potentially be our next batch of community leaders. I don't know... It was really amazing and you have to pad the numbers every step along the way and at the end of the day, you actually want a conference with impressive representation of anyone. So you have to get significantly more than you need into the pipeline thinking about it, and then significantly more than you need actually submitting and then hopefully at the end of the tunnel when everything shakes out, you'll get a reasonable number of people right. Because obviously things get filtered out and at every step of the way. There's a lot of other people that you're competing with. Overall, the quality of the proposals from the women was astonishing. It was a blind call for papers process in terms of the program committee. But as the administrator, who doesn't get a vote in these things, I was managing the app that handle the voting during the process of picking our speaker and all that kind of stuff. I was just astonished by watching quietly in the background how all these ratings came in and nobody knew they were doing this but the proposals from the women were on average, like dramatically better than everybody else. I'm not like saying, "Oh, yay! We're better." I'm sure a lot of that had to do with the amount of thought that went into it because even a seasoned conference submitter who spoke in a lot of conferences might get to a point where they're sort of cranking out a proposal in a week or even a month, and a lot of these women spent six months thinking about it. But all that hard work showed in the proposals, all that hard work showed in the roster, and I really want that hard work to show around the community. Part of what I'm trying to focus on this year is how do we take that from being the EmberConf Women Helping Women program to being the general Ember Women Helping Women program. Because after EmberConf, I felt like I could really help other conferences change their way that their rosters grew. Specifically before that EmberConf, you did have a lot of well-meaning organizer saying, "I want more women represented at my conference but I can't find them." Now, I think there's certainly ways to do it and there's a lot of clever ways to meet people and encourage people. But when push comes to shove, and it's in that moment, you would just run into a lot of organizer saying, "Well, I don't know what to do. It's an open process. Anyone can submit." And now, they could look at our conference and see there's a dozen women who are clearly talented and capable. I'm going to go to all 12 of those people and ask them to submit to my conference. Maybe some of them will and maybe that will help. It's a small step but I started seeing the women who spoke at EmberConf who a lot of them hadn't spoken anywhere beforehand, pop up at conferences all over the place. So, I sort of felt like the effect was magnified and we were able to really... I don't want to say like we, all of us women together, were able to help each other not just at Ember Conf but in a larger way. We're focusing a lot on that this year or I should say, we're going to start on how can we expand the program to be a resource that helps women take leadership roles and speaking opportunities across the JavaScript ecosystem so that Ember is really truly well represented by the people who actually make up the community. BRANDON: I think it's super clear that the thought process that you put into this was well designed enough and the work that went into it was consistent enough that you both got a huge uptick in the number of women represented at the conference. But also actually overall, the quality of conference talks went up year every year as a result of all of that additional preparation. And the encouraging people from backgrounds that had something to say that maybe felt like they didn't have something to say, instead of seeing the same faces over and over again, they went all the way across the board and it ended up showing and being a better quality conference experience for attendees for that. LEAH: It turns out the diversity is actually awesome. It's not just the thing that you should talk about and put on a list because it's politically correct. But in fact, things will be better if there are more people represented from different backgrounds with different experiences, different skills, different everything. You felt it everywhere you went and felt like you were hearing new things, interesting things, and perspectives that maybe weren't always as well represented. My biggest sad point about things is I'm trying to tackle the community of women but there are so many other communities that could also be better represented in Ember and in technology at large. And I would really love for more people to step up and sort of focus. It's hard to get involved in an effort like this because it's hard to get any traction and also because honestly, there's a lot of concern about, "Am I going to do it right? Am I going to make the problem worse?" All those sorts of self-doubt issues that are legit and based on having seen other people out in the world make a good faith effort trying to fix a problem but like say something wrong and get in huge trouble. It's just challenging and it requires a lot of thought. Even me, as I talk about this right now, I'm stressed out and I'm like, "Am I using the right words? Am I going to say the wrong thing?" But it's still worth doing. And if you're persistent and you work hard, you can really, really change things and have a positive impact. BRANDON: Well, I think it sets forward a lot of good patterns for other people trying to do this thing and I think when you talk about this being scary, the point is that it's not going to be scary. It's very scary so it makes it super brave that you're attempting that stuff. I think the impact is certainly on me. I found that pretty inspiring. Certainly at the Frontside, we found it inspiring. I hope it inspires other people in other communities to follow the same patterns. LEAH: Yeah, I hope so. I mean if there are women or anybody else that feels like they have something to contribute to really improving the landscape of who our leadership is and making sure each they are represented, I guess I would encourage those people to step up. It's the same thing as being a CEO or being the second-in-command. You just need to have the boldness to decide that you're going to try and make a difference. In the Women Helping Women program specifically, I've been talking to a lot of the women that I met last year about how can you take more of a leadership role in the program? For example, I was talking a week ago to somebody who's a student in the Women Helping Women program and I was like, "I can't represent your concerns as well as you can." I was in college at some point but that was a very long time ago, and there are just perspectives that you're going to have that I'm not going to have. Even within the women's group, there's like different perspectives and I've been working with people and encouraging them to try and work with me on taking leadership roles within the program itself. So many well-meaning programs like this, by the way, like spin up, have some success and then go away because the person-in-charge got busy and that's the end of that. It's similar to a community in that if it's going to be a long term successful effort, or at least as long term as it's necessary, I'm really going to need other people in the community to step up and find ways to be involved so that I'm not actually important to the success of this anymore. Instead, it's a whole group of people and there's no one single point of failure. BRANDON: When that happens, I can't wait to read that particular blog post. When you're able to kind of demonstrate the process for other people to be able to follow and, "Hey, look at this thing. It kind of runs itself now." That sounds really awesome and you're definitely -- LEAH: Fingers crossed. BRANDON: Yeah, you're kind of off road because you're helping to find some of the things that may influence other communities, as well. So, I think that's super cool. LEAH: I hope so. BRANDON: All right. We need to get let you get back to CEO-ing. You have a company to run and you have a whole life and everything. LEAH: I'm going to put on my business jacket as soon as I hang up on you and get back to work. BRANDON: You're in Portland. It would be a like a business hoodie probably, right? LEAH: Sort of. I have this really nice blazer. It literally changes my mind some days. I'm like, "Oh, I'm not getting enough done." I'm going to put out my business blazer. Then, they shift into over drive. BRANDON: All right. We'll get your business blazer and get to business-ing. That actually sounds like a cool little business life hack. LEAH: Yeah. BRANDON: Well, thank you so much for your time on this stuff. We got about halfway through the questions I want to talk to you about so I hope we get a shot at doing this again. I really love learning from you on this stuff. I've learned a ton from your writing. I've learned a ton from watching you work and I really appreciate all you do for the Ember community, the JavaScript community, all the stuff you've done for the Ruby community. You've had a really big impact, and so it's really great to talk to somebody that kind of sets a pattern of how these things are possible. I hope that good fortune continues to follow you as you're bold in doing these things. So, thank you for all the stuff that you do. LEAH: Thank you. I hope so, as well. It's been fun. CHARLES: Thank you. All right, goodbye everybody. BRANDON: So, bye everybody. If you have any questions or anybody else that you'd like us to talk to, let us know. If you have any additional questions for Leah, hit us up on Twitter at the Frontside. CHARLES: We usually ask for people's contact information. Where can youl be found on Twitter? LEAH: I do have a Twitter account. I'm not super active because I'm busy wearing my business blazer. But my handle is @Wifelette and I try to be as responsive as I can certainly to people who reach out to me, even if I'm not broadcasting all that much. BRANDON: Awesome. Okay, well thank you again Leah, and thanks Charles. I hope everybody listening has an awesome week.

02:43 - Dave Rupert Introduction Twitter GitHub Blog Paravel 03:42 - Chris Coyier Introduction Twitter GitHub Blog CSS-Tricks CodePen 06:24 - The ShopTalk Show and Podcasting @shoptalkshow “What do I learn next?” => “Just Build Websites!” Question & Answers Aspect 23:19 - Tech Is A Niche Paul Ford: What is Code? 29:51 - Balancing Technical Content for All Levels of Listeners Community Opinion 38:42 - Learning New CSS Tricks (Writing Blog Posts) Code Golf 41:54 - The Accessibility Project Adventures in Angular Episode #027: Accessibility with Marcy Sutton Anne Gibson: An Alphabet of Accessibility Issues 56:02 - Favorite & Cool Episodes ShowTalk Show Episode #091: with Jamison Dance and Merrick Christensen ShopTalk Show Episode #101: with John Resig ShopTalk Show Episode #157: with Alex Russell   ShopTalk Show Episode #147: with Tom Dale ShopTalk Show Episode #123: Special Archive Episode from 2004 ShopTalk Show Episode #166: with Lisa Irish ShopTalk Show Episode #161: with Eric Meyer Picks FIFA Women's World Cup (Joe) Winnipeg (Joe) The Martian by Andy Weir (Joe) Zapier (Aimee) SparkPost (Aimee) dev.modern.ie/tools/vms (AJ) remote.modern.ie (AJ) Microsoft Edge (AJ) StarFox Zero for Wii U (AJ) Hot Plate (AJ) untrusted (AJ) Skiplagged (Dave) Judge John Hodgman (Dave) Wayward Pines (Chris) Sturgill Simpson (Chris) The Economic Value of Rapid Response Time (Dave) The Adventure Zone (Dave) React Rally (Jamison) Matsuoka Shuzo: NEVER GIVE UP (Jamison) DESTROY WITH SCIENCE - Quantum Loop (Jamison) Serial Podcast (Chuck) Ruby Remote Conf (Chuck)

02:43 - Dave Rupert Introduction Twitter GitHub Blog Paravel 03:42 - Chris Coyier Introduction Twitter GitHub Blog CSS-Tricks CodePen 06:24 - The ShopTalk Show and Podcasting @shoptalkshow “What do I learn next?” => “Just Build Websites!” Question & Answers Aspect 23:19 - Tech Is A Niche Paul Ford: What is Code? 29:51 - Balancing Technical Content for All Levels of Listeners Community Opinion 38:42 - Learning New CSS Tricks (Writing Blog Posts) Code Golf 41:54 - The Accessibility Project Adventures in Angular Episode #027: Accessibility with Marcy Sutton Anne Gibson: An Alphabet of Accessibility Issues 56:02 - Favorite & Cool Episodes ShowTalk Show Episode #091: with Jamison Dance and Merrick Christensen ShopTalk Show Episode #101: with John Resig ShopTalk Show Episode #157: with Alex Russell   ShopTalk Show Episode #147: with Tom Dale ShopTalk Show Episode #123: Special Archive Episode from 2004 ShopTalk Show Episode #166: with Lisa Irish ShopTalk Show Episode #161: with Eric Meyer Picks FIFA Women's World Cup (Joe) Winnipeg (Joe) The Martian by Andy Weir (Joe) Zapier (Aimee) SparkPost (Aimee) dev.modern.ie/tools/vms (AJ) remote.modern.ie (AJ) Microsoft Edge (AJ) StarFox Zero for Wii U (AJ) Hot Plate (AJ) untrusted (AJ) Skiplagged (Dave) Judge John Hodgman (Dave) Wayward Pines (Chris) Sturgill Simpson (Chris) The Economic Value of Rapid Response Time (Dave) The Adventure Zone (Dave) React Rally (Jamison) Matsuoka Shuzo: NEVER GIVE UP (Jamison) DESTROY WITH SCIENCE - Quantum Loop (Jamison) Serial Podcast (Chuck) Ruby Remote Conf (Chuck)

02:43 - Dave Rupert Introduction Twitter GitHub Blog Paravel 03:42 - Chris Coyier Introduction Twitter GitHub Blog CSS-Tricks CodePen 06:24 - The ShopTalk Show and Podcasting @shoptalkshow “What do I learn next?” => “Just Build Websites!” Question & Answers Aspect 23:19 - Tech Is A Niche Paul Ford: What is Code? 29:51 - Balancing Technical Content for All Levels of Listeners Community Opinion 38:42 - Learning New CSS Tricks (Writing Blog Posts) Code Golf 41:54 - The Accessibility Project Adventures in Angular Episode #027: Accessibility with Marcy Sutton Anne Gibson: An Alphabet of Accessibility Issues 56:02 - Favorite & Cool Episodes ShowTalk Show Episode #091: with Jamison Dance and Merrick Christensen ShopTalk Show Episode #101: with John Resig ShopTalk Show Episode #157: with Alex Russell   ShopTalk Show Episode #147: with Tom Dale ShopTalk Show Episode #123: Special Archive Episode from 2004 ShopTalk Show Episode #166: with Lisa Irish ShopTalk Show Episode #161: with Eric Meyer Picks FIFA Women's World Cup (Joe) Winnipeg (Joe) The Martian by Andy Weir (Joe) Zapier (Aimee) SparkPost (Aimee) dev.modern.ie/tools/vms (AJ) remote.modern.ie (AJ) Microsoft Edge (AJ) StarFox Zero for Wii U (AJ) Hot Plate (AJ) untrusted (AJ) Skiplagged (Dave) Judge John Hodgman (Dave) Wayward Pines (Chris) Sturgill Simpson (Chris) The Economic Value of Rapid Response Time (Dave) The Adventure Zone (Dave) React Rally (Jamison) Matsuoka Shuzo: NEVER GIVE UP (Jamison) DESTROY WITH SCIENCE - Quantum Loop (Jamison) Serial Podcast (Chuck) Ruby Remote Conf (Chuck)

John Resig, creator of jQuery, talks about what it was like to build the most popular javascript library and then walk away from it five years later to follow his passion for education. We unpack what it’s like to maintain such a popular toolkit, how he feels about books, how he takes on his own learning, and why he made the Women Who Code twitter list. Show Links Digital Ocean (sponsor) MongoDB (sponsor) Heroku (sponsor) TwilioQuest (sponsor) jQuery Pamela Fox jQuery Foundation Khan Academy Labs Women Who Code Twitter List Jenn Schiffer's Interview on CodeNewbie Codeland Conf Codeland 2019

John Resig, Co-Founder & President of the massively popular, trendsetting website theChive.com joins Kevin & Steve.  They talk about how the Chive came to life, the origins of the name, how you get eyeballs, KCCO, Chivers & Chivettes,  Bill Murray, True Blood, Austin TX and MUCH MORE. Get ready for an AWESOME CHEW!

This talk will cover how the jQuery project has worked to provide the best possible experience for its users and has fostered a community around contributing back to the project. We'll look at what the project has done to create this environment and see how it can apply to other projects or companies. More info at: https://fronteers.nl/congres/2011/sessions/jquery-and-the-open-source-process-john-resig

This talk will cover how the jQuery project has worked to provide the best possible experience for its users and has fostered a community around contributing back to the project. We'll look at what the project has done to create this environment and see how it can apply to other projects or companies. More info at: https://fronteers.nl/congres/2011/sessions/jquery-and-the-open-source-process-john-resig

This talk will be a comprehensive look at what you need to know to properly test your web applications on mobile devices. We’ll look at the different mobile phones that exist, what browsers they run, and what you can do to support them. Additionally we’ll examine some of the testing tools that can be used to make the whole process much easier. John Resig is a JavaScript Tool Developer for the Mozilla Corporation and the author of the book Pro JavaScript Techniques. He’s also the creator and lead developer of the jQuery JavaScript library. Currently, John is located in Boston, MA. He’s hard at work on his second book, Secrets of the JavaScript Ninja, due in bookstores in 2009. Follow John on Twitter: @jeresig Licensed as Creative Commons Attribution-Share Alike 3.0 (http://creativecommons.org/licenses/by-sa/3.0/).

Refreshed from relaxing, post-TXJS hiatus, the Yay Queries return with a trio of ultra-hot HTML5 sites, with varying levels of usefulness. We'll throw down the book on on jQuery (Fundamentals) and get in touch with jqTouch ExtJS Sencha! And when the team returns to dreamland with John Resig, who knows what you'll hear, and what will be drowned out by the drone of cheap plastic horns!?

Refreshed from relaxing, post-TXJS hiatus, the Yay Queries return with a trio of ultra-hot HTML5 sites, with varying levels of usefulness. We'll throw down the book on on jQuery (Fundamentals) and get in touch with jqTouch ExtJS Sencha! And when the team returns to dreamland with John Resig, who knows what you'll hear, and what will be drowned out by the drone of cheap plastic horns!?

Adam and Wynn caught up with John Resig at TXJS and talked about mobile web development with jQuery and TestSwarm, a continuous integration project from Mozilla Labs.

Adam and Wynn caught up with John Resig at TXJS and talked about mobile web development with jQuery and TestSwarm, a continuous integration project from Mozilla Labs.

Despite Alex's vivid account of his adventures in the world of RequireJS, Adam, exhausted from many late nights of dancing 'till dawn, takes a snooze right in the middle of a perfectly good episode of yayQuery. In his dream, a mysterious guest named John Resig reveals information about the future of jQuery and mobile browsers.

Despite Alex's vivid account of his adventures in the world of RequireJS, Adam, exhausted from many late nights of dancing 'till dawn, takes a snooze right in the middle of a perfectly good episode of yayQuery. In his dream, a mysterious guest named John Resig reveals information about the future of jQuery and mobile browsers.

On this special episode of Doctype, Nick and Jim go behind the scenes of FOWA Miami 2010 and talk to some of the best in the biz, like Gary Vaynerchuk, Alex Hunter, Steve Huffman, John Resig, Alex Payne, and more.

This week we have an interview an interview with Brennan Stehling a developer and author from Milwaukee, WI.  Brennan and Larry talk about jQuery.  Brennan blogs at http://brennan.offwhite.net/blog/. After the interview Larry talks about with Dave about his finishing up on his special assignment in Redmond.  Larry then asks Dave which technology he leans towards: AJAX or RIA. Show Notes ASP.NET AJAX John Resig – creator of jQuery Pro JavaScript Techniques by John Resig cssQuery Project Learning jQuery by Jonathan Chaffer Javascript the good parts by Douglas Crockford Running JSLINT from within Visual Studio jQuery in Action by Bear Bibeault A Website you should know Dave’s pick: Clemens Vaster’s Blog Larry’s pick: W3C Validator for HTML and CSS Download / Listen to the Show http://shows.thirstydeveloper.com/TD059.mp3 New Twitter Feed Thirsty Developer has a twitter feed, friend us at http://twitter.com/thirstyd

An impressive presentation by jQuery JavaScript library creator John Resig at our January 2009 WebPub meeting. John put a lot of work into preparing what was truly a lesson plan, and he delivered it very well. It was accessible to anyone in the audience, regardless of skill or experience level. Please visit this podcast at http://webpub.mit.edu/2009/01/jquery-john-resig-video/

In this week's show we talk with John Resig on javaScript libraries and address the question what is more important when we release an app: speed or quality?