Podcast appearances and mentions of nicholas zakas

ESLint is a static code analysis tool for identifying and fixing problems in JavaScript code. It helps developers maintain code quality and consistency by enforcing coding standards and detecting issues such as syntax errors, stylistic problems, and bugs. Nicholas Zakas is the creator of ESLint. He joins the show to talk about working at Yahoo The post Creating ESLint with Nicholas Zakas appeared first on Software Engineering Daily.

ESLint is a static code analysis tool for identifying and fixing problems in JavaScript code. It helps developers maintain code quality and consistency by enforcing coding standards and detecting issues such as syntax errors, stylistic problems, and bugs. Nicholas Zakas is the creator of ESLint. He joins the show to talk about working at Yahoo The post Creating ESLint with Nicholas Zakas appeared first on Software Engineering Daily.

This week we're delighted to have Nicholas Zakas on the show to talk about ESLint. ESLint is a tool that helps you find and fix problems in your JavaScript code by writing plugins that check for patterns in your code's AST. We talk about the history of ESLint, the challenges of building a linter, and the future of of ESLint. https://x.com/slicknet https://eslint.org/ Episode sponsored By MUX (https://mux.com) Become a paid subscriber our patreon, spotify, or apple podcasts for the full episode. https://www.patreon.com/devtoolsfm https://podcasters.spotify.com/pod/show/devtoolsfm/subscribe https://podcasts.apple.com/us/podcast/devtools-fm/id1566647758 https://www.youtube.com/@devtoolsfm/membership

Hello, Kent! My name is Petar and I'm from Bulgaria. I'd like to ask your opinion on this question: Do you think that the "Epic Stack" is relevant for people who are relatively new to web development? Here's some information about me: my interest in web development started about a year ago. Currently, I feel really confident in HTML, CSS, JavaScript, React, and TypeScript. I have read a lot of books and completed numerous courses on these topics, including the HTML course on web.dev, the CSS course by Josh Comeau, the books by Nicholas Zakas on JavaScript, the JS course by Dan Abramov, Epic React, and the "Learning TypeScript" book by Josh Goldberg. I also purchased your testing course but haven't had the chance to complete it yet. Currently, I don't have a job, but I'm planning to land one soon.My question to you, again, is whether you think sticking with the Epic Stack would be beneficial for me, or if it's better to focus on already established technologies in the market such as Redux, Next.js, etc. I just want to hear your honest opinion, even if it may be (or become) wrong. The Epic Stack (blog post) The Epic Stack (announcement talk) epicweb-dev/epic-stack (github) Is Epic Stack beneficial for new developers?

In this supper club episode of Syntax, Wes and Scott talk with Nicholas Zakas about his creation of ESLint, what's coming up in ESLint, and his work as a coach and mentor for programmers. Show Notes 00:34 Welcome 01:20 Guest introduction Human Who Codes Nicholas C. Zakas (@nzakas@fosstodon.org) Twitter @slicknet nzakas on GitHub @humanwhocodes) on Instagram Human Who Codes on YouTube 04:24 Why did you want to build ESLint? 09:08 How does ESLint work? 13:25 How do you work on a project for a decade? 17:12 At what point do you pay attention to JavaScript proposed changes? 20:37 Config systems in JavaScript 31:18 ESLint in Rust? 41:07 Are we going to see ESLint for more languages? 47:06 What kind of coaching do you do for programmers? 02:46 SIIIIICK ××× PIIIICKS ××× ××× SIIIIICK ××× PIIIICKS ××× Apollo Neuro Shameless Plugs Understanding JavaScript Promises Tweet us your tasty treats Scott's Instagram LevelUpTutorials Instagram Wes' Instagram Wes' Twitter Wes' Facebook Scott's Twitter Make sure to include @SyntaxFM in your tweets

Web development has changed a lot since the release of ESLint in 2013. Nicholas Zakas, the creator of ESLint, joins us to talk about the complete rewrite of ESLint, goals for the rewrite, and how the rewrite will leverage Rust. Links https://eslint.org https://twitter.com/geteslint https://twitter.com/humanwhocodes https://twitter.com/slicknet https://humanwhocodes.com Tell us what you think of PodRocket We want to hear from you! We want to know what you love and hate about the podcast. What do you want to hear more about? Who do you want to see on the show? Our producers want to know, and if you talk with us, we'll send you a $25 gift card! If you're interested, schedule a call with us (https://podrocket.logrocket.com/contact-us) or you can email producer Kate Trahan at kate@logrocket.com (mailto:kate@logrocket.com) Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket combines frontend monitoring, product analytics, and session replay to help software teams deliver the ideal product experience. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Special Guest: Nicholas Zakas.

Guest Ali Nehzat Panelists Richard Littauer | Justin Dorfman Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. Get ready for an exciting guest today as we welcome, Ali Nehzat, who's a Software Engineer with a preference for embedded systems and Founder of thanks.dev. Ali's been around for a while, and he realized that the open source ecosystem needs some help, and his focus is specifically on the OSS funding problem. Today, we'll learn more about Ali's story of why he started thanks.dev, what motivated him, people that inspired him through his journey, and he reveals his mission for OSS developers. But it doesn't stop there! Ali dives into different aspects he's experimenting for funding, he tells us how payouts are supported so developers get paid, and how he's planning on making this more sustainable. Download this episode now to find out more! [00:02:53] We find out the difference between thanks.dev and the other platforms, and Ali tells us his story about being motivated by Brian Carlson from the Node.js community, who's behind node-postgres. [00:08:13] Ali talks about thanks.dev's approach with helping to convince people to give money to open source. [00:11:20] We hear the tools that thanks.dev offers to its engineers to help them figure out how to sell giving back to open source. [00:14:07] After having conversations with OSPO companies, Ali explains how everything is a learning experience currently with thanks.dev, and he states the reason for thanks.dev not getting involved with code of conduct right now and what the mission is. [00:17:51] Licensing landscape is brought up by Ali and the conversations happening around it. [00:20:51] Ali fills us in on the insightful conversations he had with Joel Wasserman who really helped him in his journey, as well as other people, with thanks.dev, as well as some ideas to solve the funding with open source and make sure thanks.dev is sustainable going forward. [00:23:05] As far as projects go, Ali tells us who's he's worked with to get more funding. [00:26:06] Justin wonders if there's any papers Ali's read dealing with the complexities and edge cases, he explains how he would like to publish blog posts he wrote, and the testing and the experiments he's been doing, and the impact Duane O'Brien from Indeed has made. [00:29:28] Richard brings up payment payouts and wonders how Ali is making sure the money actually gets to the developers and that helps the sustainability of those projects. [00:33:50] Ali is currently not getting a salary for this, but he tells us how fundraising through family and friends helped him, and how he's planning to make this sustainable for him. [00:35:37] Find out where you can follow Ali on the web. Quotes [00:03:20] “Currently, thanks.dev is focusing on an experiment if you make it super easy for companies to donate to their dependency trees, what would be the outcome of that?” [00:04:41] “When I got interested in the funding space and in the challenges that open source maintainers face, it was actually all motivated by Brian Carlson in the Node.js community, who's the person behind node-postgres.” [00:06:35] “It's not just funding, it's project management and it's community management. There's a whole array of other problems that can be attacked.” [00:09:12] “When I hit that barrier, the approach I took was to add a line item to my invoices for the OSS ecosystem.” [00:22:02] “The biggest learning is that to solve the funding problem in open source, you have to look at it from the perspective of the marketplace.” [00:23:50] “Then there's a whole cohort of donors on GitHub and Open Collective that are engineering managers that are going to their own organizations and getting donations done and figuring out the motivations and actions behind these people.” [00:26:52] “The input that Duane O'Brien has had on thanks.dev has made such a huge impact.” Spotlight [00:37:32] Justin's spotlight is CodeMirror. [00:38:19] Richard's spotlight is Atom. [00:39:04] Ali's spotlight is Brian Carlson. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Justin Dorfman Twitter (https://twitter.com/jdorfman?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Ali Nehzat LinkedIn (https://au.linkedin.com/in/ali-nehzat-75428a7) Ali Nehzat Twitter (https://mobile.twitter.com/nehzata) thanks.dev Twitter (https://mobile.twitter.com/thanks_dev) ali@thanks.dev (mailto:ali@thanks.dev) thanks.dev (https://thanks.dev/home) Sustain Podcast-Episode 58: Joel Wasserman on Flossbank and Sustainably Giving Back to Dependencies (https://podcast.sustainoss.org/58) Sustain Podcast-Episode 96: Chad Whitacre and how Sentry is giving $150 to their OSS Dependencies (https://podcast.sustainoss.org/96) Sustain Podcast- 2 episodes featuring guest, Duane O'Brien (https://podcast.sustainoss.org/guests/duane-obrien) Sustain Podcast-2 episodes featuring guest, Nicholas Zakas (https://podcast.sustainoss.org/guests/zakas) CodeMirror (https://codemirror.net/) Atom (https://atom.io/) Brian Carlson-GitHub (https://github.com/brianc) node-postgres (https://github.com/brianc/node-postgres) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Ali Nehzat.

Guest Simon Minton Panelists Richard Littauer | Justin Dorfman Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. Richard and Justin are super excited to have as their guest today, Simon Minton, who's the CEO of Ringer, which we'll hear all about. Simon tells us how Ringer is different by the ways they provide for their maintainers, how they give back to projects, handle consultancy with projects, and he explains their recruitment process. Simon shares his long-term plan for Ringer, and a new tool they are building to help the ecosystem in the long-term. Go ahead and download this episode now to hear more! [00:01:54] Simon tells us how Ringer was born, what it is, and how many people use it. [00:05:00] Find out how Ringer is different. [00:08:59] Besides a payment gateway, we hear about some other infrastructure and services Simon is providing for the maintainers. [00:12:01] How does Ringer make sure that the money doesn't just flow to the people on the top of the projects, but also to the projects as a whole? [00:14:16] Richard wonders how Simon teaches the next generation to become the next generation of Ringer HQ/maintainers besides the 5%. [00:15:19] Richard brings up a concern around consulting and Simon explains how they handle this with larger and smaller projects. [00:17:32] We learn about some projects where Ringer will be their consultancy platform. [00:19:19] Ringer's recruitment process is explained. [00:21:33] Justin thinks the Ringer site is really cool and Simon shares where the inspiration came from. [00:23:30] Richard wonders if Simon has a long-term plan, and as he scales up his team if services will be provided to the consultants., and he tells us about the educational services he offers. [00:30:58] Simon informs us about a tool they are building right now to help the ecosystem in the long-term. [00:33:20] Justin brings up thanks.dev and the founder, Ali Nehzat. [00:35:58] We learn the meaning of Ringer and where you can follow Simon online. Spotlight [00:37:04] Justin's spotlight is NextAuth.js. [00:37:30] Richard's spotlight is Wikiquote and the works of Seneca the Younger. [00:38:13] Simon's spotlight is Spatie and Freek Van der Herten. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Justin Dorfman Twitter (https://twitter.com/jdorfman?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Simon Minton LinkedIn (https://uk.linkedin.com/in/minton) Simon Minton Twitter (https://twitter.com/simonminton) Ringer (https://www.ringerhq.com/) filament (https://filamentphp.com/) Sustain Podcast-Episode 142: Nicholas Zakas on Sponsoring Dependencies, All the Way Down (https://podcast.sustainoss.org/142) Electron (https://www.electronjs.org/) Ali Nehzat Twitter (https://twitter.com/nehzata) thanks.dev (https://thanks.dev/home) NextAuth.js (https://next-auth.js.org/) Wikiquote-Seneca the Younger (https://en.wikiquote.org/wiki/Seneca_the_Younger) Spatie-GitHub (https://github.com/spatie) Freek Van der Herten-GitHub (https://github.com/freekmurze) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Simon Minton.

Guest Nicholas Zakas Panelists Richard Littauer | Justin Dorfman Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. Our guest today is a returning guest that we've had on before. We are excited to have joining us, Nicholas Zakas, who's one of the maintainers on ESLint, which is a tool that helps you find and fix problems in your JavaScript code. Today, we'll learn all about ESLint, the maintainers, contributors, and how they get paid. Also, we'll find out the success behind ESLint, and a post about sponsoring dependencies that Nicholas wrote on his blog. Go ahead and download this episode now to learn more! [00:02:23] Nicholas tells us all about ESLint, their maintainers that work on the project, and how many people have contributed to the project on GitHub. [00:07:29] Nicholas tells us how maintainers get paid as part of his governance strategy. [00:10:04] Justin asked about the fact that ESLint not only pays contributors, but also pays downstream dependencies. [00:12:04] Richard wonders where all the money comes from that gave ESLint this huge surplus, and Nicholas explains how they raised so much and what it is about ESLint that makes that possible. [00:16:10] We hear some reflections from Richard as he congratulates Nicholas and makes some important points about the success of ESLint. [00:20:19] Nicholas fills us in on the OpenJS Foundation Project. [00:23:57] Richard talks about a blog post Nicholas wrote on his blog about sponsoring dependencies, and Nicholas explains the difference between large charismatic projects and smaller projects and how he sees the role of large projects in funding the smaller ones. [00:31:41] We hear what ESLint did with sponsoring dependencies, and Nicholas tells us about some projects that they wanted to support financially, but turned them down. [00:38:06] Find out where you can follow Nicholas and ESLint online. Quotes [00:07:43] “Everybody on the team, the committers, reviewers, technical steering committee, gets paid an hourly rate for their contributions.” [00:07:53] “Contributions can be anything that contributes to the project, reviewing issues and pull requests, attending meetings, helping people on discord, helping people on GitHub discussions, and if people ever go to conferences or meetings representing the team, they can also charge for that.” [00:10:15] “We made a decision the beginning of last year that it was time to start supporting our dependencies.” [00:12:28] “I do think we are lucky in a lot of ways that we've had champions inside of companies who were working within their company to get ESLint's support.” [00:13:13] “In the beginning, we were hesitant to start spending the money because we didn't know how reliable that source of income would be, and we were worried we wouldn't be able to pay a living wage.” [00:21:25] “Being in a foundation is one type of a reputational check mark that an open source project can get.” [00:26:15] “I think OpenSSL is a great example of [the funding problem]. It's a foundational piece of internet infrastructure.” [00:28:31] “We went on backyourstack.com and started looking for the projects that we were depending on that had Open Collective pages and said, as a project, what is good for open source in general, is also good for ESLint.” [00:29:20] “Open source, in general, is this collective of projects that are built on top of projects that are built on top of projects that are built on top of projects, and we have no problem giving that recognition when we're talking about what the project is built upon.” Spotlight [00:39:47] Justin's spotlight is the new book, What if? 2 by Randall Munroe. [00:40:31] Richard's spotlight is David Troupes, Buttercup Festival comic strips. [00:41:03] Nicholas's spotlight is the book, WebAssembly: The Definitive Guide by Brian Sletten Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Justin Dorfman Twitter (https://twitter.com/jdorfman?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Nicholas Zakas Twitter (https://twitter.com/slicknet) Nicholas Zakas GitHub (https://github.com/nzakas) ESLint (https://eslint.org/) ESLint Twitter (https://twitter.com/geteslint?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) ESLint GitHub (https://github.com/eslint/eslint) ESLint-Open Collective (https://opencollective.com/eslint) Sustain Podcast-Episode 101: Nicholas Zakas and ESLint (https://podcast.sustainoss.org/guests/zakas) Sponsoring dependencies: The next step in open source sustainability (Human Who Codes Blog) (https://humanwhocodes.com/blog/2022/06/sponsoring-dependencies-open-source-sustainability/) Sustain Podcast-Episode 117: Mike McQuaid of Homebrew on Sustainably Working on OSS Projects (https://podcast.sustainoss.org/117) Sustain Podcast-Episode 126: GitHub Maintainer Month with Mike McQuaid of Homebrew and Nina Breznik of DatDot (https://podcast.sustainoss.org/126) BackYourStack (https://backyourstack.com/) Securing Open Source Software Act of 2022 (Sustain) (https://discourse.sustainoss.org/t/securing-open-source-software-act-of-2022/1098) What if? 2 by Randall Munroe (https://xkcd.com/what-if-2/) David Troupes-Buttercup Festival comic strips (Patreon) (https://www.patreon.com/buttercupfestival) WebAssembly: The Definitive Guide by Brian Sletten (https://www.oreilly.com/library/view/webassembly-the-definitive/9781492089834/) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Nicholas Zakas.

On today's episode, Sarah Dayan discusses open source sustainability with Nicholas Zakas, creator of ESLint. ESLint is a widely popular JavaScript linter with a giant ecosystem of third-party plugins. If you have a JavaScript project with a continuous integration, you are certainly using ESLint and you do not want it to fail. Nicholas is also a seasoned author who wrote several books about JavaScript since the early 2000s and more blog posts that you can probably afford to read.A recurring meme is that all modern digital infrastructure somehow depends on a project that some random person has been thanklessly maintaining for decades. Sustaining open source projects that support countless enterprise products has been a particularly hot topic in tech for the last couple of years.- How do you actively maintain a project that others rely on but doesn't bring revenue?- How do you deal with stress and fatigue?- Is the promise of open source still holding?Nicholas Zakas: @slicknet / humanwhocodes.comSarah Dayan: @frontstuff_io / sarahdayan.devESLint: @geteslint / eslint.orgAlgolia: @algolia / algolia.com

Guest Duane O'Brien | Mandy Grover Panelists Richard Littauer | Justin Dorfman | Ben Nichols Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. On today's episode we have two excellent guests, Duane O'Brien and Mandy Grover. Duane is the Head of Open Source at Indeed and Mandy is a Technical Content Architect III, as well as manages a team within the Technical Content organization at Indeed. They are here to talk about the FOSS Fund and the recently released FOSS Fund report. Duane and Mandy go in detail on the report and expand on who it is for, how to use it, tools they used, and things they'll be writing about in the second report. We also learn the ups and downs of writing, but more importantly how Duane and Mandy built their friendship and trust in the process of writing this report successfully. Go ahead and download this episode now to learn more! [00:03:11] Mandy and Duane fill us in on the FOSS Fund report titled, Investing in Open Source: The FOSS Contributor Fund. [00:04:57] We learn more about how the FOSS Contributor Fund started, what it is, and how the response has been so far. [00:09:06] Justin wonders if Duane and Mandy ever thought this would become the blueprint, and then we hear the story how the Sentry thing came about. [00:16:08] Learn about some new things coming out in the second report. [00:19:24] Duane explains how you can still use this report even if your organization is not huge. [00:20:56] Richard wonders if you were a coder, how could you make yourself more eligible to be a recipient of funds. [00:24:19] Find out about a few of the tools they talk about in the report, one which is called Starfish. [00:26:28] Mandy fills us in on how everything went when they released the report and how they set expectations with each other. Duane also brings up about asking maintainers to write things. [00:33:54] Find out where you can find this report and where you can find Duane and Mandy online. Quotes [00:13:56] “We had this moment where we were like, it's certainly projects, it's certainly money, it's certainly all these things, but at the heart of it is people.” [00:21:17] “The biggest problem that we don't talk about is this: You are a single project in a sea of thousands that organizations may depend on.” [00:26:48] “We set expectations early, we knew the goal, and we were always there supporting each other and holding each other accountable.” [00:33:12] “Let's temper our expectation of what we want maintainers to do when it comes to documenting things because it's not easy.” Spotlight [00:35:15] Justin's spotlight is Opensourcestories.org. [00:35:35] Ben's spotlights are 24 Pull Requests and The Good Docs Project. [00:36:37] Richard's spotlight is John Hill. [00:37:08] Mandy's spotlight is to watch all movies. [00:38:29] Duane's spotlight is the book, A Psalm for the Wild- Built by Becky Chambers. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) Duane O'Brien Twitter (https://twitter.com/DuaneOBrien) Duane O'Brien Linkedin (https://www.linkedin.com/in/duaneobrien) Mandy Grover Twitter (https://twitter.com/mandyegrover) Mandy Grover Twitter (Indeed) (https://twitter.com/agrover_indeed) Mandy Grover Linkedin (https://www.linkedin.com/in/mandygrovermatc/) Indeed Open Source (https://opensource.indeedeng.io/) Investing in Open Source: The FOSS Contributor Fund-(EBOOK) (https://opensource.indeedeng.io/Investing-in-Open-Source/) Sustain Podcast-Episode 80: Emma Irwin and the FOSS Fund Program (https://podcast.sustainoss.org/guests/emma-irwin) Sustain Podcast-Episode 96: Chad Whitacre and how Sentry is giving $150k to their OSS Dependencies (https://podcast.sustainoss.org/guests/chad-whitacre) Sustain Podcast- Episode 38: Working Group Updates with Justin & Javi (https://podcast.sustainoss.org/38) Sustain Podcast-Episode 101: Nicholas Zakas and ESLint (https://podcast.sustainoss.org/101) FOSS Contributor Fund (https://engineering.indeedblog.com/blog/2019/11/foss-fund-adopters/) Starfish-GitHub (https://github.com/indeedeng/starfish) Open Source Stories (https://www.opensourcestories.org/) 24 Pull Requests (https://24pullrequests.com/) The Good Docs Project (https://thegooddocsproject.dev/) John Hill (https://about.me/jpjhill) John Hill Twitter (https://twitter.com/jpjhill?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Sunset Blvd (https://www.imdb.com/title/tt0043014/) All the President's Men (https://www.imdb.com/title/tt0074119/) David Lynch movies (https://www.imdb.com/name/nm0000186/) A Psalm for the Wild-Built (Monk & Robot #1) by Becky Chambers (https://www.otherscribbles.com/#/a-psalm-for-the-wild-built/) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guests: Duane O'Brien and Mandy Grover.

Guest Nicholas C. Zakas Panelists Richard Littauer Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. You may know my guest today, Nicholas Zakas, because he is the creator of a very popular JavaScript project called ESLint, which has been downloaded 13 million times each week. Nicholas is an independent software engineer, consultant, and coach, and has written numerous books including, Understanding ECMAScript 6, The Principles of Object-Oriented JavaScript, and Maintainable JavaScript. With over sixteen years of web application development experience and speaking at conferences around the world, he's putting his focus now on mentoring and coaching the next generation of JavaScript engineers. Nicholas brings us on his journey sharing his story of becoming a developer, starting ESLint, and what he's doing to make sure everybody in the ESLint community is able to benefit from the money they are bringing in. We also learn more about an interesting blog post he wrote, how contributors get paid, and other open source projects ESLint donates to. Why should you use ESLint? Go ahead and download this episode now to find out! [00:01:39] Nicholas shares his story with us starting out as a developer and how it led him to starting ESLint. [00:03:01] What did Nicholas mean when he said he fell in love with JavaScript? [00:03:47] We find out how long ESLint has been around, how many people are working full-time, and how he keeps himself in funds. [00:05:04] Nicholas talks about the Open Collective and GitHub sponsors they set up for donations. [00:07:42] Richard brings up a blog post Nicholas wrote on, “How to talk to your company about sponsoring an open source project” and he tells us what iterations he's gone through with ESLint. [00:10:59] Nicholas talks about the difficulties in multi-tasking, and he tells us the next thing they tried with paying a straight per hour rate for team members. [00:17:15] Richard wonders where Nicholas came up with the less than standard rate for hourly work which is not really a Silicon Valley salary, and he also tells us how many hours per month he is paying out and for the people that have been paid, how they feel about it, and having no caps on what people can make. [00:20:43] Nicholas mentions using Tidelift, how much money it brings in, and the money going to TSC members. [00:22:04] Find out what else Nicholas is doing with the money besides paying contributors. He mentions several other open source projects they are donating to, and one person in particular he mentions is Sindre Sorhus. [00:27:58] Richard wonders more about the governance process and how Nicholas feels about it. [00:31:52] Nicholas dives deep as he explains three things that would convince him that ESLint would be a project that he would want to use. [00:34:20] We learn some future plans for what Nicholas would do with funds to make the project more sustainable. [00:38:09] Find out where you follow Nicholas online. Quotes [00:03:26] “And I see ESLint as really, this will sound cheesy, as an act of love on your code that we aren't trying to change what it does.” [00:04:24] “We found that people who have kids are looking for something to do after the kids go to bed.” [00:05:52] “And so, if that is your starting point where even folks who are just coming right out of college are getting 120k each year, that means that's the minimum that you need to raise in order to hire someone full-time if they're in a major metropolitan area in the United States.” [00:22:17] “The first thing is we have what's called a contributor pool, which is money that we set aside every month to pay non-team members for contributions to ESLint.” [00:22:46] “Generally, anything that is of benefit to the project we will potentially pay you for.” [00:24:43] “So, one of the things that we were looking at in terms of sustainability is we're bringing in a certain amount of money each month.” [00:24:53] “We are building on top of the work of others. And so, why shouldn't we be spreading that money to those others, because without them ESLint either wouldn't exist or be a lot harder to maintain.” [00:28:17] “Well, what's interesting is that when I started ESLint, in my mind this was like a one-year project.” [00:29:16] “And I just kept coming back to, what's in it for them?” [00:30:44] “And so, how can I ensure the future survival of the project outside of me working on it?” Spotlight [00:38:52] Richard's spotlight is StandardJS. [00:39:27] Nicholas's spotlight is a project called Release Please. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) Nicholas C. Zakas Twitter (https://twitter.com/slicknet?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Human Who Codes (http://humanwhocodes.com/) Open Collective- ESLint (https://opencollective.com/eslint) How to talk to your company about sponsoring an open source project by Nicholas C. Zakas- Human Who Codes (https://humanwhocodes.com/blog/2021/05/talk-to-your-company-sponsoring-open-source/) Reading List-Human Who Codes (https://humanwhocodes.com/reading/) Deep Work: Rules for Focused Success in a Distracted World by Cal Newport (https://www.amazon.com/Deep-Work-Focused-Success-Distracted/dp/1455586692/ref=sr_1_1?crid=20RZZIIP2GWVG&dchild=1&keywords=deep+work+cal+newport&qid=1634932822&qsid=140-9480495-9312539&sprefix=deep+work%2Caps%2C101&sr=81&sres=0349411905%2C9123832355%2C9123781467%2C912411412X%2CB07DBRBP7G%2C1401962122%2C0735211299%2C9123963255%2C0525536558%2C1443460710%2CB009CMO8JQ%2C1544512279%2CB00IWYP5NI%2CB07SBX56MC%2C0374533555%2CB08817M9SS&srpt=ABIS_BOOK) A year of paying contributors (ESLint) (https://eslint.org/blog/2020/10/year-paying-contributors-review) Sindre Sorhus (https://sindresorhus.com/) ESLint (https://eslint.org/) Standard JS-GitHub (https://github.com/standard/standard) Release Please-GitHib (https://github.com/googleapis/release-please) [Understanding ECMAScript 6: The Definitive Guide for JavaScript Developers by Nicholas C. Zakas](https://www.amazon.com/Understanding-ECMAScript-Definitive-JavaScript-Developers/dp/1593277571/ref=sr15?crid=299FWWAJ52K4H&dchild=1&keywords=nicholas+Zakas+books&qid=1634926017&qsid=140-9480495-9312539&sprefix=nicholas+zakas+book%2Caps%2C86&sr=85&sres=059680279X%2CB00I87B1H8%2C1593277571%2C1449327680%2C1118026691%2C0470109491%2CB011DBHZ2K%2C3944540573%2CB011DB19KE%2CB088P9Q6BB%2CB00BQ7RMW0%2CB01A65ALSY%2CB01A64IRUY%2CB00HK37CXS%2C0470227818%2CB089LJTMPJ&srpt=ABISBOOK)_ [The Principles of Object-Oriented JavaScript by Nicholas C. Zakas](https://www.amazon.com/Principles-Object-Oriented-JavaScript-Nicholas-Zakas-dp-1593275404/dp/1593275404/ref=mtother?encoding=UTF8&me=&qid=1634926112) [Maintainable JavaScript: Writing Readable Code by Nicholas C. Zakas](https://www.amazon.com/Maintainable-JavaScript-Writing-Readable-Code/dp/1449327680/ref=sr15?crid=299FWWAJ52K4H&dchild=1&keywords=nicholas+Zakas+books&qid=1634926112&qsid=140-9480495-9312539&sprefix=nicholas+zakas+book%2Caps%2C86&sr=85&sres=059680279X%2CB00I87B1H8%2C1593277571%2C1449327680%2C1118026691%2C0470109491%2CB011DBHZ2K%2C3944540573%2CB011DB19KE%2CB088P9Q6BB%2CB00BQ7RMW0%2CB01A65ALSY%2CB01A64IRUY%2CB00HK37CXS%2C0470227818%2CB089LJTMPJ&srpt=ABISBOOK)_ Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Nicholas Zakas.

Sponsors Triplebyte offers a $1000 signing bonus Sentry use the code “devchat” for $100 credit CacheFly Panel AJ O’Neal Joe Eames Aimee Knight Charles Max Wood Chris Ferdinandi Joined by Special guest: Nicholas Zakas Summary Nicholas Zakas discusses the overuse of JavaScript and the underuse of HTML and CSS. The panel contemplates the talk Nicholas Zakas gave 6 years ago about this very same topic and how this is still a problem in the development community. Nicholas expounds on the negative effects overusing Javascript has on web applications and the things that using HTML and CSS do really well. The panel talks about the need for simplicity and using the right tool to build applications. Nicholas recommends the methods he uses to build greenfield applications and to improve existing applications. Links https://www.youtube.com/watch?v=li4Y0E_x8zE https://www.slideshare.net/nzakas/enough-withthejavascriptalready https://twitter.com/slicknet https://humanwhocodes.com/ https://www.facebook.com/javascriptjabber https://twitter.com/JSJabber Picks Chris Ferdinandi: The Umbrella Academy Official Trailer https://github.com/features/actions AJ O’Neal: Jurassic Park Terminator 2 E6000 adhesive Aimee Knight: https://www.reebok.com/us/reebok-legacy-lifter/BD4730.html https://www.holloway.com/g/equity-compensation Charles Max Wood: https://podfestexpo.com/ http://charlesmaxwood.com/ https://www.11ty.io/ https://www.netlify.com/ Joe Eames: https://www.mysteryscenemag.com/blog-article/5905-tom-straw-the-author-behind-castle Richard Castle books https://vanillajslist.com/ Nicholas Zakas: The Power of Full Engagement: Managing Energy, Not Time, Is the Key to High Performance and Personal Renewal by Jim Loehr and Tony Schwartz https://opencollective.com/eslint

Sponsors Triplebyte offers a $1000 signing bonus Sentry use the code “devchat” for $100 credit CacheFly Panel AJ O’Neal Joe Eames Aimee Knight Charles Max Wood Chris Ferdinandi Joined by Special guest: Nicholas Zakas Summary Nicholas Zakas discusses the overuse of JavaScript and the underuse of HTML and CSS. The panel contemplates the talk Nicholas Zakas gave 6 years ago about this very same topic and how this is still a problem in the development community. Nicholas expounds on the negative effects overusing Javascript has on web applications and the things that using HTML and CSS do really well. The panel talks about the need for simplicity and using the right tool to build applications. Nicholas recommends the methods he uses to build greenfield applications and to improve existing applications. Links https://www.youtube.com/watch?v=li4Y0E_x8zE https://www.slideshare.net/nzakas/enough-withthejavascriptalready https://twitter.com/slicknet https://humanwhocodes.com/ https://www.facebook.com/javascriptjabber https://twitter.com/JSJabber Picks Chris Ferdinandi: The Umbrella Academy Official Trailer https://github.com/features/actions AJ O’Neal: Jurassic Park Terminator 2 E6000 adhesive Aimee Knight: https://www.reebok.com/us/reebok-legacy-lifter/BD4730.html https://www.holloway.com/g/equity-compensation Charles Max Wood: https://podfestexpo.com/ http://charlesmaxwood.com/ https://www.11ty.io/ https://www.netlify.com/ Joe Eames: https://www.mysteryscenemag.com/blog-article/5905-tom-straw-the-author-behind-castle Richard Castle books https://vanillajslist.com/ Nicholas Zakas: The Power of Full Engagement: Managing Energy, Not Time, Is the Key to High Performance and Personal Renewal by Jim Loehr and Tony Schwartz https://opencollective.com/eslint

Sponsors Triplebyte offers a $1000 signing bonus Sentry use the code “devchat” for $100 credit CacheFly Panel AJ O’Neal Joe Eames Aimee Knight Charles Max Wood Chris Ferdinandi Joined by Special guest: Nicholas Zakas Summary Nicholas Zakas discusses the overuse of JavaScript and the underuse of HTML and CSS. The panel contemplates the talk Nicholas Zakas gave 6 years ago about this very same topic and how this is still a problem in the development community. Nicholas expounds on the negative effects overusing Javascript has on web applications and the things that using HTML and CSS do really well. The panel talks about the need for simplicity and using the right tool to build applications. Nicholas recommends the methods he uses to build greenfield applications and to improve existing applications. Links https://www.youtube.com/watch?v=li4Y0E_x8zE https://www.slideshare.net/nzakas/enough-withthejavascriptalready https://twitter.com/slicknet https://humanwhocodes.com/ https://www.facebook.com/javascriptjabber https://twitter.com/JSJabber Picks Chris Ferdinandi: The Umbrella Academy Official Trailer https://github.com/features/actions AJ O’Neal: Jurassic Park Terminator 2 E6000 adhesive Aimee Knight: https://www.reebok.com/us/reebok-legacy-lifter/BD4730.html https://www.holloway.com/g/equity-compensation Charles Max Wood: https://podfestexpo.com/ http://charlesmaxwood.com/ https://www.11ty.io/ https://www.netlify.com/ Joe Eames: https://www.mysteryscenemag.com/blog-article/5905-tom-straw-the-author-behind-castle Richard Castle books https://vanillajslist.com/ Nicholas Zakas: The Power of Full Engagement: Managing Energy, Not Time, Is the Key to High Performance and Personal Renewal by Jim Loehr and Tony Schwartz https://opencollective.com/eslint

Sponsors Netlify Sentry use the code "devchat" for $100 credit Clubhouse Panel: Charles Max Wood AJ O’Neal Aimee Knight Aaron Frost Chris Ferdinandi Joe Eames Tim Caswell Notes: This episode of JavaScript Jabber has the panelists reminiscing on the past. First, they discuss the projects they’re working on. Tim has joined MagicLeap doing JavaScript and C++. Aaron Frost is one of the founders of HeroDevs. AJ works at Big Squid, a company that takes spreadsheets and turns them into business actions, and is expecting a daughter. Aimee has been exploring developer advocacy, but wants to focus primarily on engineering. She is currently working at MPM. Joe has taken over the CEO position for thinkster.io, a company for learning web development online. Chris switched from being a general web developer specializing in JavaScript and has started blogging daily rather than once a week, and has seen an increase in sales of his vanilla JavaScript educational products. Charles discusses his long term goal for Devchat.tv. He wants to help people feel free in programming, and help people find opportunities though the Devchat.tv through empowering content. Next, the panelists discuss their favorite episodes. Some of the most highly recommended episodes are JSJ 124: The Origin of Javascript with Brendan Eich (1:44:07) JSJ 161: Rust with David Herman (1:05:05) JSJ 336: “The Origin of ESLint with Nicholas Zakas” (1:08:01) JSJ 338: It’s Supposed To Hurt, Get Outside of Your Comfort Zone to Master Your Craft with Christopher Buecheler (43:36) JSJ 218: Ember.js with Yehuda Katz (42:47) Last, the panelists discuss what they do to unwind. Activities include working out, reading, playing Zelda and Mario Kart, studying other sciences like physics, painting miniatures, and Dungeons and Dragons. Picks: Charles Max Wood Villainous Board Game Joe Eames Azul Stained Glass Board Game AJ O’Neal https://www.digikey.com/ Magnetic Hourglass: Amazon | Hobby Lobby $6  Aimee Knight https://www.nytimes.com/2018/12/24/well/mind/work-schedule-hours-sleep-productivity-chronotype-night-owls.html Aaron Frost Matrix PowerWatch https://twitter.com/ChloeCondon Chris Ferdinandi https://learnvanillajs.com/ Tim Caswell https://www.magicleap.com/ https://textonascreen.rocks/ https://history.lds.org/saints

Sponsors Netlify Sentry use the code "devchat" for $100 credit Clubhouse Panel: Charles Max Wood AJ O’Neal Aimee Knight Aaron Frost Chris Ferdinandi Joe Eames Tim Caswell Notes: This episode of JavaScript Jabber has the panelists reminiscing on the past. First, they discuss the projects they’re working on. Tim has joined MagicLeap doing JavaScript and C++. Aaron Frost is one of the founders of HeroDevs. AJ works at Big Squid, a company that takes spreadsheets and turns them into business actions, and is expecting a daughter. Aimee has been exploring developer advocacy, but wants to focus primarily on engineering. She is currently working at MPM. Joe has taken over the CEO position for thinkster.io, a company for learning web development online. Chris switched from being a general web developer specializing in JavaScript and has started blogging daily rather than once a week, and has seen an increase in sales of his vanilla JavaScript educational products. Charles discusses his long term goal for Devchat.tv. He wants to help people feel free in programming, and help people find opportunities though the Devchat.tv through empowering content. Next, the panelists discuss their favorite episodes. Some of the most highly recommended episodes are JSJ 124: The Origin of Javascript with Brendan Eich (1:44:07) JSJ 161: Rust with David Herman (1:05:05) JSJ 336: “The Origin of ESLint with Nicholas Zakas” (1:08:01) JSJ 338: It’s Supposed To Hurt, Get Outside of Your Comfort Zone to Master Your Craft with Christopher Buecheler (43:36) JSJ 218: Ember.js with Yehuda Katz (42:47) Last, the panelists discuss what they do to unwind. Activities include working out, reading, playing Zelda and Mario Kart, studying other sciences like physics, painting miniatures, and Dungeons and Dragons. Picks: Charles Max Wood Villainous Board Game Joe Eames Azul Stained Glass Board Game AJ O’Neal https://www.digikey.com/ Magnetic Hourglass: Amazon | Hobby Lobby $6  Aimee Knight https://www.nytimes.com/2018/12/24/well/mind/work-schedule-hours-sleep-productivity-chronotype-night-owls.html Aaron Frost Matrix PowerWatch https://twitter.com/ChloeCondon Chris Ferdinandi https://learnvanillajs.com/ Tim Caswell https://www.magicleap.com/ https://textonascreen.rocks/ https://history.lds.org/saints

Sponsors Netlify Sentry use the code "devchat" for $100 credit Clubhouse Panel: Charles Max Wood AJ O’Neal Aimee Knight Aaron Frost Chris Ferdinandi Joe Eames Tim Caswell Notes: This episode of JavaScript Jabber has the panelists reminiscing on the past. First, they discuss the projects they’re working on. Tim has joined MagicLeap doing JavaScript and C++. Aaron Frost is one of the founders of HeroDevs. AJ works at Big Squid, a company that takes spreadsheets and turns them into business actions, and is expecting a daughter. Aimee has been exploring developer advocacy, but wants to focus primarily on engineering. She is currently working at MPM. Joe has taken over the CEO position for thinkster.io, a company for learning web development online. Chris switched from being a general web developer specializing in JavaScript and has started blogging daily rather than once a week, and has seen an increase in sales of his vanilla JavaScript educational products. Charles discusses his long term goal for Devchat.tv. He wants to help people feel free in programming, and help people find opportunities though the Devchat.tv through empowering content. Next, the panelists discuss their favorite episodes. Some of the most highly recommended episodes are JSJ 124: The Origin of Javascript with Brendan Eich (1:44:07) JSJ 161: Rust with David Herman (1:05:05) JSJ 336: “The Origin of ESLint with Nicholas Zakas” (1:08:01) JSJ 338: It’s Supposed To Hurt, Get Outside of Your Comfort Zone to Master Your Craft with Christopher Buecheler (43:36) JSJ 218: Ember.js with Yehuda Katz (42:47) Last, the panelists discuss what they do to unwind. Activities include working out, reading, playing Zelda and Mario Kart, studying other sciences like physics, painting miniatures, and Dungeons and Dragons. Picks: Charles Max Wood Villainous Board Game Joe Eames Azul Stained Glass Board Game AJ O’Neal https://www.digikey.com/ Magnetic Hourglass: Amazon | Hobby Lobby $6  Aimee Knight https://www.nytimes.com/2018/12/24/well/mind/work-schedule-hours-sleep-productivity-chronotype-night-owls.html Aaron Frost Matrix PowerWatch https://twitter.com/ChloeCondon Chris Ferdinandi https://learnvanillajs.com/ Tim Caswell https://www.magicleap.com/ https://textonascreen.rocks/ https://history.lds.org/saints

Panel: Charles Max Wood Guest: Nicholas Zakas This week on My JavaScript Story, Charles talks with Nicholas Zakas who is a blogger, author, and software engineer. Nicholas’ website is titled, Human Who Codes – check it out! You can find him on Twitter, GitHub, and LinkedIn among other social media platforms. Today, Nicholas and Chuck talk about Nicholas’ background, JavaScript, and current projects. In particular, we dive pretty deep on: 0:00 – Advertisement: Get A Coder Job! 1:00 – Chuck: Welcome! Give us a background, please, Nicholas! 1:14 – Guest: I am probably best known for making ESLint and I have written a bunch of books, too! (See links below.) 1:36 – Chuck: JSJ 336 and JSJ 075 episodes are the two past episodes we’ve had you on! (See links below.) Let’s go back and how did you get into programming? 1:58 – Guest: I think the first was written in BASIC, which was on a Laser computer. It was a cheaper knockoff version. I think I was into middle school when I got into BASIC. Then when I got into high school I did this computer project, which was the first time someone else used one of my programs. 4:02 – Chuck: Was it all in BASIC or something else? 4:13 – Guest: Just BASIC, but then transferred to something else when we got our first PC. 5:13 – Chuck: How did you get to use JavaScript? 5:18 – Guest: 1996 was my freshman year in college. Netscape 3 got into popularity around this time. I had decided that I wanted to setup a webpage to stay in-touch with high school friends who were going into different directions. I got annoyed with how static the [web] pages were. At the time, there was no CSS and the only thing you could change was the source of an image (on webpages). On the you could do... 8:35 – Chuck: You get into JavaScript and at what point did you become a prolific operator and author? 8:52 – Guest: It was not an overnight thing. It definitely was fueled by my own curiosity. The web was so new (when I was in college) that I had to explore on my own. I probably killed a few trees when I was in college. Printing off anything and everything I could to learn about this stuff! 10:03 – Guest (continues): Professors would ask ME how to do this or that on the departmental website. When I was graduating from college I knew that I was excited about the WEB. I got a first job w/o having to interview. 12:32 – Guest (continues): I got so deep into JavaScript! 13:30 – Guest (continued): They couldn’t figure out what I had done. That’s when I got more into designing JavaScript APIs. About 8 months after graduating from college I was unemployed. I had extra time on my hands. I was worried that I was going to forget the cool stuff that I just developed there. I went over the code and writing for myself how I had constructed it. My goal was to have an expandable tree. This is the design process that I went through. This is the API that I came up with so you can insert and how I went about implementing it. At some point, I was on a discussion with my former colleagues: remember that JavaScript tree thing I wrote – I wrote a description of how I did it. Someone said: Hey this is really good and you should get this published somewhere. Huh! I guess I could do that. I went to websites who were publishing articles on JavaScript. I went to submit the article to one of them. I think it was DevX or WebReference. 18:03 – Guest: A book is a compilation of different articles?! I can do that. I wanted to write a book that would fill in that next step that was missing. I didn’t know what the book was going to be, and I decided to start writing. Once I’ve had enough content I would take a step back and see what it was about. (Check out Nicholas’ books here!) 19:01 – Chuck: Oh you can turn this into a book! 19:10 – Guest: There was very little that I had planned out ahead of time. Anything that happened to me that was exciting had stumbled into my lap! 19:37 – Chuck: That’s how I felt about podcasting – it fell into my lap/life! 19:50 – Chuck: Listeners – check out the past episodes with Nicholas, please. Nicholas, what are you proud of? 20:10 – Guest: In 2006, I was at Yahoo and started off with My Yahoo Team. This was the first time that I was exposed to a massive amount of JavaScript in a single web application. 26:21 – Chuck: Can you talk about your health issues? People would definitely benefit from your example and your story. 26:44 – Guest: I think it is something important for people to understand. The guest talks about Lyme Disease. 35:49 – Chuck: Yep taking care of yourself is important! 36:00 – Guest: Yes to enjoy time with friends and explore other hobbies. Help yourself to de-stress is important. Cognitive work is very draining. When you aren’t getting the right amount of sleep your body is going to get stressed out. Take the time to do nonsense things. You need to let your brain unwind! I love these adult coloring books that they have! 38:07 – Chuck: I love to take a drive up the canyon. 38:12 – Guest. 38:24 – Chuck: Yeah to focus on ourselves is important. 38:36 – Guest: Your body will make it a point to say: pay attention to me! Your body goes into flight or fight mode and your systems shut-off, which of course is not good. You don’t want your body to stay in that state. New parents get sick frequently with newborns, because they aren’t getting enough sleep. 41:08 – Guest: Get some R&R! 41:20 – Chuck: This is great, but I have another call! Let’s do some Picks! 41:35 – Advertisement – Fresh Books! 30-Day Trial! END – Cache Fly Links: React Angular Vue.js JavaScript Ember Elm jQuery Node DevX WebReference Nicholas C. Zakas’ Books ESLint NPM – ESLint Signs and Symptoms of Untreated Lyme Disease Lyme Disease Nicholas’ Twitter JSJ 336 Episode with Zakas JSJ 075 Episode with Zakas Sponsors: Cache Fly Get A Coder Job Fresh Books Picks: Charles Max Wood Wall Calendars – 6 ft. x3 ft. Nicholas Zakas Book: The Better Angels of Our Nature: Why Violence Has Declined by Steven Pinker Adult Coloring Books

Panel: Charles Max Wood Guest: Nicholas Zakas This week on My JavaScript Story, Charles talks with Nicholas Zakas who is a blogger, author, and software engineer. Nicholas’ website is titled, Human Who Codes – check it out! You can find him on Twitter, GitHub, and LinkedIn among other social media platforms. Today, Nicholas and Chuck talk about Nicholas’ background, JavaScript, and current projects. In particular, we dive pretty deep on: 0:00 – Advertisement: Get A Coder Job! 1:00 – Chuck: Welcome! Give us a background, please, Nicholas! 1:14 – Guest: I am probably best known for making ESLint and I have written a bunch of books, too! (See links below.) 1:36 – Chuck: JSJ 336 and JSJ 075 episodes are the two past episodes we’ve had you on! (See links below.) Let’s go back and how did you get into programming? 1:58 – Guest: I think the first was written in BASIC, which was on a Laser computer. It was a cheaper knockoff version. I think I was into middle school when I got into BASIC. Then when I got into high school I did this computer project, which was the first time someone else used one of my programs. 4:02 – Chuck: Was it all in BASIC or something else? 4:13 – Guest: Just BASIC, but then transferred to something else when we got our first PC. 5:13 – Chuck: How did you get to use JavaScript? 5:18 – Guest: 1996 was my freshman year in college. Netscape 3 got into popularity around this time. I had decided that I wanted to setup a webpage to stay in-touch with high school friends who were going into different directions. I got annoyed with how static the [web] pages were. At the time, there was no CSS and the only thing you could change was the source of an image (on webpages). On the you could do... 8:35 – Chuck: You get into JavaScript and at what point did you become a prolific operator and author? 8:52 – Guest: It was not an overnight thing. It definitely was fueled by my own curiosity. The web was so new (when I was in college) that I had to explore on my own. I probably killed a few trees when I was in college. Printing off anything and everything I could to learn about this stuff! 10:03 – Guest (continues): Professors would ask ME how to do this or that on the departmental website. When I was graduating from college I knew that I was excited about the WEB. I got a first job w/o having to interview. 12:32 – Guest (continues): I got so deep into JavaScript! 13:30 – Guest (continued): They couldn’t figure out what I had done. That’s when I got more into designing JavaScript APIs. About 8 months after graduating from college I was unemployed. I had extra time on my hands. I was worried that I was going to forget the cool stuff that I just developed there. I went over the code and writing for myself how I had constructed it. My goal was to have an expandable tree. This is the design process that I went through. This is the API that I came up with so you can insert and how I went about implementing it. At some point, I was on a discussion with my former colleagues: remember that JavaScript tree thing I wrote – I wrote a description of how I did it. Someone said: Hey this is really good and you should get this published somewhere. Huh! I guess I could do that. I went to websites who were publishing articles on JavaScript. I went to submit the article to one of them. I think it was DevX or WebReference. 18:03 – Guest: A book is a compilation of different articles?! I can do that. I wanted to write a book that would fill in that next step that was missing. I didn’t know what the book was going to be, and I decided to start writing. Once I’ve had enough content I would take a step back and see what it was about. (Check out Nicholas’ books here!) 19:01 – Chuck: Oh you can turn this into a book! 19:10 – Guest: There was very little that I had planned out ahead of time. Anything that happened to me that was exciting had stumbled into my lap! 19:37 – Chuck: That’s how I felt about podcasting – it fell into my lap/life! 19:50 – Chuck: Listeners – check out the past episodes with Nicholas, please. Nicholas, what are you proud of? 20:10 – Guest: In 2006, I was at Yahoo and started off with My Yahoo Team. This was the first time that I was exposed to a massive amount of JavaScript in a single web application. 26:21 – Chuck: Can you talk about your health issues? People would definitely benefit from your example and your story. 26:44 – Guest: I think it is something important for people to understand. The guest talks about Lyme Disease. 35:49 – Chuck: Yep taking care of yourself is important! 36:00 – Guest: Yes to enjoy time with friends and explore other hobbies. Help yourself to de-stress is important. Cognitive work is very draining. When you aren’t getting the right amount of sleep your body is going to get stressed out. Take the time to do nonsense things. You need to let your brain unwind! I love these adult coloring books that they have! 38:07 – Chuck: I love to take a drive up the canyon. 38:12 – Guest. 38:24 – Chuck: Yeah to focus on ourselves is important. 38:36 – Guest: Your body will make it a point to say: pay attention to me! Your body goes into flight or fight mode and your systems shut-off, which of course is not good. You don’t want your body to stay in that state. New parents get sick frequently with newborns, because they aren’t getting enough sleep. 41:08 – Guest: Get some R&R! 41:20 – Chuck: This is great, but I have another call! Let’s do some Picks! 41:35 – Advertisement – Fresh Books! 30-Day Trial! END – Cache Fly Links: React Angular Vue.js JavaScript Ember Elm jQuery Node DevX WebReference Nicholas C. Zakas’ Books ESLint NPM – ESLint Signs and Symptoms of Untreated Lyme Disease Lyme Disease Nicholas’ Twitter JSJ 336 Episode with Zakas JSJ 075 Episode with Zakas Sponsors: Cache Fly Get A Coder Job Fresh Books Picks: Charles Max Wood Wall Calendars – 6 ft. x3 ft. Nicholas Zakas Book: The Better Angels of Our Nature: Why Violence Has Declined by Steven Pinker Adult Coloring Books

Panel: Charles Max Wood Guest: Nicholas Zakas This week on My JavaScript Story, Charles talks with Nicholas Zakas who is a blogger, author, and software engineer. Nicholas’ website is titled, Human Who Codes – check it out! You can find him on Twitter, GitHub, and LinkedIn among other social media platforms. Today, Nicholas and Chuck talk about Nicholas’ background, JavaScript, and current projects. In particular, we dive pretty deep on: 0:00 – Advertisement: Get A Coder Job! 1:00 – Chuck: Welcome! Give us a background, please, Nicholas! 1:14 – Guest: I am probably best known for making ESLint and I have written a bunch of books, too! (See links below.) 1:36 – Chuck: JSJ 336 and JSJ 075 episodes are the two past episodes we’ve had you on! (See links below.) Let’s go back and how did you get into programming? 1:58 – Guest: I think the first was written in BASIC, which was on a Laser computer. It was a cheaper knockoff version. I think I was into middle school when I got into BASIC. Then when I got into high school I did this computer project, which was the first time someone else used one of my programs. 4:02 – Chuck: Was it all in BASIC or something else? 4:13 – Guest: Just BASIC, but then transferred to something else when we got our first PC. 5:13 – Chuck: How did you get to use JavaScript? 5:18 – Guest: 1996 was my freshman year in college. Netscape 3 got into popularity around this time. I had decided that I wanted to setup a webpage to stay in-touch with high school friends who were going into different directions. I got annoyed with how static the [web] pages were. At the time, there was no CSS and the only thing you could change was the source of an image (on webpages). On the you could do... 8:35 – Chuck: You get into JavaScript and at what point did you become a prolific operator and author? 8:52 – Guest: It was not an overnight thing. It definitely was fueled by my own curiosity. The web was so new (when I was in college) that I had to explore on my own. I probably killed a few trees when I was in college. Printing off anything and everything I could to learn about this stuff! 10:03 – Guest (continues): Professors would ask ME how to do this or that on the departmental website. When I was graduating from college I knew that I was excited about the WEB. I got a first job w/o having to interview. 12:32 – Guest (continues): I got so deep into JavaScript! 13:30 – Guest (continued): They couldn’t figure out what I had done. That’s when I got more into designing JavaScript APIs. About 8 months after graduating from college I was unemployed. I had extra time on my hands. I was worried that I was going to forget the cool stuff that I just developed there. I went over the code and writing for myself how I had constructed it. My goal was to have an expandable tree. This is the design process that I went through. This is the API that I came up with so you can insert and how I went about implementing it. At some point, I was on a discussion with my former colleagues: remember that JavaScript tree thing I wrote – I wrote a description of how I did it. Someone said: Hey this is really good and you should get this published somewhere. Huh! I guess I could do that. I went to websites who were publishing articles on JavaScript. I went to submit the article to one of them. I think it was DevX or WebReference. 18:03 – Guest: A book is a compilation of different articles?! I can do that. I wanted to write a book that would fill in that next step that was missing. I didn’t know what the book was going to be, and I decided to start writing. Once I’ve had enough content I would take a step back and see what it was about. (Check out Nicholas’ books here!) 19:01 – Chuck: Oh you can turn this into a book! 19:10 – Guest: There was very little that I had planned out ahead of time. Anything that happened to me that was exciting had stumbled into my lap! 19:37 – Chuck: That’s how I felt about podcasting – it fell into my lap/life! 19:50 – Chuck: Listeners – check out the past episodes with Nicholas, please. Nicholas, what are you proud of? 20:10 – Guest: In 2006, I was at Yahoo and started off with My Yahoo Team. This was the first time that I was exposed to a massive amount of JavaScript in a single web application. 26:21 – Chuck: Can you talk about your health issues? People would definitely benefit from your example and your story. 26:44 – Guest: I think it is something important for people to understand. The guest talks about Lyme Disease. 35:49 – Chuck: Yep taking care of yourself is important! 36:00 – Guest: Yes to enjoy time with friends and explore other hobbies. Help yourself to de-stress is important. Cognitive work is very draining. When you aren’t getting the right amount of sleep your body is going to get stressed out. Take the time to do nonsense things. You need to let your brain unwind! I love these adult coloring books that they have! 38:07 – Chuck: I love to take a drive up the canyon. 38:12 – Guest. 38:24 – Chuck: Yeah to focus on ourselves is important. 38:36 – Guest: Your body will make it a point to say: pay attention to me! Your body goes into flight or fight mode and your systems shut-off, which of course is not good. You don’t want your body to stay in that state. New parents get sick frequently with newborns, because they aren’t getting enough sleep. 41:08 – Guest: Get some R&R! 41:20 – Chuck: This is great, but I have another call! Let’s do some Picks! 41:35 – Advertisement – Fresh Books! 30-Day Trial! END – Cache Fly Links: React Angular Vue.js JavaScript Ember Elm jQuery Node DevX WebReference Nicholas C. Zakas’ Books ESLint NPM – ESLint Signs and Symptoms of Untreated Lyme Disease Lyme Disease Nicholas’ Twitter JSJ 336 Episode with Zakas JSJ 075 Episode with Zakas Sponsors: Cache Fly Get A Coder Job Fresh Books Picks: Charles Max Wood Wall Calendars – 6 ft. x3 ft. Nicholas Zakas Book: The Better Angels of Our Nature: Why Violence Has Declined by Steven Pinker Adult Coloring Books

Recording date: 2018-09-20 Tweet John Papa https://twitter.com/john_papa Ward Bell https://twitter.com/wardbell Dan Wahlin https://twitter.com/danwahlin (0:01:51) John reads the mailbag about browser support, service workers performance imapc,t and adding home screens to PWAs. (0:01:51) Mailbag https://twitter.com/RealTalkJS/status/1042572672025194496 (00:2:15) Maxim describes PWA support in the browsers (0:03:10) Ward points out that Addy Osmani https://twitter.com/addyosmani says: "It's important to remember that Progressive Web Apps work everywhere but are supercharged in modern browsers. Progressive enhancement is a backbone of the model." (0:03:42) Service worker support in "Can I Use" https://caniuse.com/#feat=serviceworkers (0:03:50) Maxim recommends using the PWA feature detector https://github.com/tomayac/pwa-feature-detector (0:04:10) Maxim answers John's question about how PWAs have changed over the past few years (0:05:45) Maxim answers what a PWA is and the value to developers and users (0:07:00) Ward asks "What problem does PWA solve?" (0:07:43) Dan asks what he benefits of PWA are to an enterprise business (0:08:50) Maxim points out how low wifi (LiFi) can be hard to deal with (0:09:22) What is a PWA https://developers.google.com/web/progressive-web-apps/ (0:09:30) Ward asks if a PWA magically knows if its offline or not (0:11:50) Maxim talks about LiFi as really low connectivity (0:13:20) John clarifies with Maxim that PWAs uses browser APIs to check their connectivity (0:14:00) Ward asks if he should use the raw service worker protocol (0:15:15) Dan and Ward asks Maxim what makes this easier (0:16:57) Maxim talks about the Workbox project https://developers.google.com/web/tools/workbox/ (0:18:15) John asks Maxim what else besides Service Workers, that is a part of PWAs (0:18:30) Maxim discusses web app manfiest https://developer.mozilla.org/en-US/docs/Web/Manifest (0:21:10) Maxim talks about Service Worker precache https://github.com/GoogleChromeLabs/sw-precache (0:22:22) Ward asks Maxim to tell a story about one of Maxim's successful experiences with PWAs (0:28:26) mobile era rocks PWA https://mobileera.rocks/ (0:28:46) Ward raises how conferences are notorious for low wifi (0:33:00) John asks Maxim when not to do a PWA (0:38:00) Ward, John and Maxim discuss security concerns with PWAs (0:44:30) Lighthouse tool for PWAs https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk (0:45:30) Maxim mentions the Web Hint tool for PWAs https://webhint.io/ (tip: npx hint https://example.com ) (0:46:50) Someone to follow: Nicholas Zakas https://twitter.com/slicknet https://humanwhocodes.com/ (0:47:38) Someone to follow: Simona Cotin https://twitter.com/simona_cotin?lang=en (0:48:10) Someone to follow: Arthur Stolyar https://twitter.com/nekrtemplar Additional Resources PWA Checklist https://developers.google.com/web/progressive-web-apps/checklist Curated list of PWA news by Maxim: https://twitter.com/progwebnews/ PWA Feature Detector https://tomayac.github.io/pwa-feature-detector/ Mobile Era PWA: https://mobileera.rocks/ Workbox: https://workboxjs.org Webhint: https://webhint.io PWA Get Started: https://developers.google.com/web/progressive-web-apps/ https://developer.microsoft.com/en-us/windows/pwa Excellent post on PWA: https://developers.google.com/web/updates/2015/12/getting-started-pwa

Panel: Aimee Knight Charles Max Wood (DevChat TV) Christopher Ferdinandi (Boston) Cory House (Kansas City) Joe Eames Special Guests: Nicholas Zakas In this episode, the panel talks with Nicholas Zakas who writes on his site, Human Who Codes. He is the creator of ESLint, also the author of several books, and he blogs, too. He was employed through Box and today he talks about ESLint in full detail! Check it out!  Show Topics: 0:05 – Advertisement: KENDO UI 0:37 – Hello! The panel is...(Chuck introduces everyone). 1:04 – Nicholas who are you? 1:17 – Nicholas: Yeah it’s been about 5 years and then you invited me again, but I couldn’t come on to talk about ESLint back then. That’s probably what people know me most for at this point. I created ESLint and I kicked that off and now a great team of people is maintaining it. 1:58 – Chuck: What is it? 2:04 – It’s a Linter for JavaScript. It falls into the same category as JSLint. The purpose of ESLint is to help you find problems with your code. It has grown quite a bit since I’ve created it. It can help with bugs and enforcing style guides and other things. 2:53 – Where did it come from? 2:57 – Guest: The idea popped into my head when I worked at Pop. One of my teammates was working on a bug and at that time we were using... Nothing was working and after investigating someone had written a JavaScript code that was using a native code to make an Ajax request. It wasn’t the best practice for the company at the time. For whatever reason the person was unaware of that. When using that native XML...there was a little bit of trickiness to it because it was a wrapper around the... We used a library to work around those situations and add a line (a Linter) for all JavaScript files. It was a text file and when you tried to render code through the process it would run and run the normal expression and it would fail if any of the...matched. I am not comfortable using normal expressions to write code for this. You could be matching in side of a string and it’s not a good way to be checking code for problems. I wanted to find a better way. 6:04 – Why did you choose to create a product vs. using other options out there? 6:15 – Guest: Both of those weren’t around. JSHint was pretty much the defector tool that everyone was using. My first thought was if JSHint could help with this problem? I went back to look at JSHint and I saw that on their roadmap you could create your own rules, and I thought that’s what we need. Why would I build something new? I didn’t see anything on GitHub and didn’t see the status of that. I wanted to see what the plan was, and they weren’t going to get to it. I said that I really needed this tool and I thought it would be helpful to others, too. 8:04 – My history was only back when it was customizable. 8:13 – Aimee: It’s interesting to see that they are basing it on regular expressions. 8:32 – Guest: Interesting thing at Box was that there was...I am not sure but one of the engineers at Box wrote... 9:03 – Aimee: I was going to ask in your opinion what do you think ES Lint is the standard now? 9:16 – Guest: How easy it is to plug things in. That was always my goal because I wanted the tool not to be boxed in – in anyway. The guest continues to talk about how pluggable ESLint is and the other features of this tool. 13:41 – One thing I like about ESLint is that it can be an educational tool for a team. Did you see that being an educational tool? 14:24 – Guest: How do you start introducing new things to a team that is running at full capacity? That is something that I’ve wondered throughout my career. As a result of that, I found that a new team there were some problems I the code base that were really hard to get resolved, because when one person recognizes it there isn’t a god way to share that information within a team in a non-confrontational way. It’s better to get angry at a tool rather than a person. Guest goes into what this can teach people. 18:07 – Panelist: I am not surprised. Is there a best practice to get a team to start with ESLint? Do you get the whole team in a room and show them the options or take the best guess and turn it on? 18:34 – Guest: The thing I recommend is that first and foremost get ESLint in your system with zero rules on. It starts that mindset into your development process. We can do something to automatically check... Get Syntax checking and you will se improvements on the number of bugs that are getting out of production. I recommend using the default the ESLint configuration. This has all of the things that we have found that are most likely errors and runtime errors vs. syntax errors. You can go through with those and sometimes it is easier to run that check with... Using those ESLint rules will clean up a lot of problems that you didn’t know you had with your code. There are too many problems with those rules. I recommend instead of turning them off then put the severity to warning and not error. That is something we started with in the beginning. We turned on as many rules as we could and it drove people crazy. They didn’t feel like when they were committing to a file why should I be... The idea with the different scenario levels you don’t’ want to turn off rules so people don’t know there is a problem. There can be a rule on so people will know that there is a problem, but... Doing that alone will give you a lot of benefit in using ESLint. How do you decide as a team on the rules that are maybe not for finding errors but for stylistic in error? Do we use four spaces, semi-colons, etc. To figure that out I am a big component on finding a pre-existing style guide and adapting it. Get everyone to agree. There is no right or wrong when it comes to stylistic preferences. It really is just getting everyone to do the same thing. I think it was Crawford that said: Whether you drive on the right side of the left side of the road – it doesn’t matter as long as everyone is dong the same thing. I agree with that and it applies to style guides. It can get heated but for the best thing for the team is stick with a guide and work together. 24:36 – Aimee: I can go through the options to pick one of the style guides out there and then it will automatically create my configuration for me is helpful. Question: If you had to pick 2 or 3 rules that you are super helpful what would they be? 25:30 – Guest: To touch briefly on indentation. Whether you like four spaces or whether you are wild and like tabs, I think the indent rule is very helpful. Just for wiping out and eliminating that discussion through your team. Have your editor setup however they want but on the pre-hook... But my favorite rules I tend to lean towards the ones that saved me. The Guest goes through his favorite rules with ESLint. Check it out! 26:51 – Guest mentions his second favorite rule, here! 28:24 – Guest mentions his third favorite rule, here! 29:03 – Guest mentions the rule that makes him giggle a lot, here! 30:07 – Advertisement – Sentry! 31:22 – What is your take on running Fix? Does it make sense to run Fix? 32:00 – Guest: It depends and the idea behind Fix is the idea of doing a one time (at the start) fix everything that it can find wrong b/c I don’t want to do it by hand. It morphed into a more of a tool that people are using all the time. I too have mixed feelings about it. I think the greatest value you get out of Fix is that when you first install it or when you enable a new rule. I think in those situations you get a lot of value out of Fix. I think that when people were getting aggressive with their code styles it took us down a path where we... As a pre-commit hook it could be to fix things and part of the built system you wouldn’t want... People are probably wondering: Why doesn’t ESLint doesn’t fix all the time? It can be a team decision: do you want to run Fix at the point that the developer is writing the code, do you want to use Fix as running it as a build when you are bundling? It really seems more of a personal preference. I am on the fence about it. Even though I am leaning more towards... 35:16 – Do you run Premier? 35:20 – Guest: No I don’t. I don’t have anything against Premier but I think Prettier uses a very interesting space. 37:50 – Chuck: What is next for ESLint and what is next for you? 37:55 – Guest: Well, to be honest I am not sure what is next for ESLint. I haven’t been involved with keeping it maintained for the last few years. I do help out with feedback with decisions. But in general the ESLint the direction is that let’s add tings that help people avoid language hazards and make sure that ESLint is still pluggable. Lastly, that we will be there to help people and the community. There is this virtuosic cycle and tools like Babble and then tools like ESLint introducing rules adapting new rules and features better. For myself, and the future, I haven’t been involved with ESLint because I am focusing on my health. I was diagnosed with Lyme Disease and it meant that I needed to focus on my health. That’s why, too, I wasn’t able to join a few years ago. I am doing better but I am a few years away for working fulltime and writing books and blogging, again. The trajectory is upward. I want to stress that you need to take care of yourself. There is interesting stuff that we are doing and I love it, but make sure you take care of yourself! If you don’t have your health then nothing will really matter. I want to encourage you all to take care of yourselves better. This industry can take a toll on your body b/c it is high-stressed. If you are stressed your immune system will shut down. For a lot of us we are working too much and there isn’t an off-switch. I would like to encourage people to examine their life and their time. When you take time to turn off your analytic brain, and work on your creative brain then the pathways will connect better. Please save your money! Lyme disease is spread through tick bites. 44:30 – Aimee: Thank you for sharing that! 44:38 – Chuck: It’s encouraging to me that you are still trying to come back even after this disease. I think we take things for granted sometimes. You can’t always count on things going the way you want it to go. 45:19 – Guest: What happened to me was I left work and one Friday afternoon I had a normal weekend. My health was on the decline, and I rested all weekend. And Monday I couldn’t get out of bed. That started this whole period where I stopped leaving the house completely. That’s how quickly things can change for you. I harp on people a lot to save their money. If I didn’t have savings there would be a very different end to my story. I want to encourage people to save. 46:33 – Chuck: I think on that note let’s go to picks. Where can people find you? 46:45 – Guest: My blog is Human Who Codes. 47:10 – Chuck: Anything people can do to help you? Check out his books you won’t regret it! 47:33 – Guest: Buying books is always helpful. I would say that if you can spend some time contributing to ESLint that is always a great help. Anything you can do to help them will help me. I want to make sure that those folks are happy, healthy and productive. For me, personally, I love when people Tweet at me and say HI! I love hearing other people’s stories of how they have overcome past diseases or illnesses. If you want to send monetary gifts – donate to a wonderful organization that helps children with Lyme disease. I would encourage you to support if you feel inclined. 50:49 – Chuck: We appreciate it, and I appreciate you being so open about your personal story. 51:11 – Advertisement – eBook: Get a coder job! Links: JavaScript jQuery React Elixir Elm Vue GitHub – Prettier GitHub – Premier Lyme Light Foundation Inclusive Components ESLint – Disallow Specific Imports State of JS Learn JavaScript Book: Total Recall Goodbye Redux YouTube Channel – Sideways Human Who Codes – Nicholas Zakas Nicholas’ Books Nicholas’ Twitter Nicholas’ GitHub Nicholas’ LinkedIn Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Technical debt Professional JavaScript for Web Developers Chris Inclusive Components Blog CSS Cascade JS Jabber - code Cory No Restricted Imports State of JS Total Recall Charles My JavaScript Story Joe Thought bubbles... Goodbye Redux Sideways Channel Nicholas The Brain that Changes Its Self Ghost Boy Tip - Turn off your Wi-Fi before Bed

Panel: Aimee Knight Charles Max Wood (DevChat TV) Christopher Ferdinandi (Boston) Cory House (Kansas City) Joe Eames Special Guests: Nicholas Zakas In this episode, the panel talks with Nicholas Zakas who writes on his site, Human Who Codes. He is the creator of ESLint, also the author of several books, and he blogs, too. He was employed through Box and today he talks about ESLint in full detail! Check it out!  Show Topics: 0:05 – Advertisement: KENDO UI 0:37 – Hello! The panel is...(Chuck introduces everyone). 1:04 – Nicholas who are you? 1:17 – Nicholas: Yeah it’s been about 5 years and then you invited me again, but I couldn’t come on to talk about ESLint back then. That’s probably what people know me most for at this point. I created ESLint and I kicked that off and now a great team of people is maintaining it. 1:58 – Chuck: What is it? 2:04 – It’s a Linter for JavaScript. It falls into the same category as JSLint. The purpose of ESLint is to help you find problems with your code. It has grown quite a bit since I’ve created it. It can help with bugs and enforcing style guides and other things. 2:53 – Where did it come from? 2:57 – Guest: The idea popped into my head when I worked at Pop. One of my teammates was working on a bug and at that time we were using... Nothing was working and after investigating someone had written a JavaScript code that was using a native code to make an Ajax request. It wasn’t the best practice for the company at the time. For whatever reason the person was unaware of that. When using that native XML...there was a little bit of trickiness to it because it was a wrapper around the... We used a library to work around those situations and add a line (a Linter) for all JavaScript files. It was a text file and when you tried to render code through the process it would run and run the normal expression and it would fail if any of the...matched. I am not comfortable using normal expressions to write code for this. You could be matching in side of a string and it’s not a good way to be checking code for problems. I wanted to find a better way. 6:04 – Why did you choose to create a product vs. using other options out there? 6:15 – Guest: Both of those weren’t around. JSHint was pretty much the defector tool that everyone was using. My first thought was if JSHint could help with this problem? I went back to look at JSHint and I saw that on their roadmap you could create your own rules, and I thought that’s what we need. Why would I build something new? I didn’t see anything on GitHub and didn’t see the status of that. I wanted to see what the plan was, and they weren’t going to get to it. I said that I really needed this tool and I thought it would be helpful to others, too. 8:04 – My history was only back when it was customizable. 8:13 – Aimee: It’s interesting to see that they are basing it on regular expressions. 8:32 – Guest: Interesting thing at Box was that there was...I am not sure but one of the engineers at Box wrote... 9:03 – Aimee: I was going to ask in your opinion what do you think ES Lint is the standard now? 9:16 – Guest: How easy it is to plug things in. That was always my goal because I wanted the tool not to be boxed in – in anyway. The guest continues to talk about how pluggable ESLint is and the other features of this tool. 13:41 – One thing I like about ESLint is that it can be an educational tool for a team. Did you see that being an educational tool? 14:24 – Guest: How do you start introducing new things to a team that is running at full capacity? That is something that I’ve wondered throughout my career. As a result of that, I found that a new team there were some problems I the code base that were really hard to get resolved, because when one person recognizes it there isn’t a god way to share that information within a team in a non-confrontational way. It’s better to get angry at a tool rather than a person. Guest goes into what this can teach people. 18:07 – Panelist: I am not surprised. Is there a best practice to get a team to start with ESLint? Do you get the whole team in a room and show them the options or take the best guess and turn it on? 18:34 – Guest: The thing I recommend is that first and foremost get ESLint in your system with zero rules on. It starts that mindset into your development process. We can do something to automatically check... Get Syntax checking and you will se improvements on the number of bugs that are getting out of production. I recommend using the default the ESLint configuration. This has all of the things that we have found that are most likely errors and runtime errors vs. syntax errors. You can go through with those and sometimes it is easier to run that check with... Using those ESLint rules will clean up a lot of problems that you didn’t know you had with your code. There are too many problems with those rules. I recommend instead of turning them off then put the severity to warning and not error. That is something we started with in the beginning. We turned on as many rules as we could and it drove people crazy. They didn’t feel like when they were committing to a file why should I be... The idea with the different scenario levels you don’t’ want to turn off rules so people don’t know there is a problem. There can be a rule on so people will know that there is a problem, but... Doing that alone will give you a lot of benefit in using ESLint. How do you decide as a team on the rules that are maybe not for finding errors but for stylistic in error? Do we use four spaces, semi-colons, etc. To figure that out I am a big component on finding a pre-existing style guide and adapting it. Get everyone to agree. There is no right or wrong when it comes to stylistic preferences. It really is just getting everyone to do the same thing. I think it was Crawford that said: Whether you drive on the right side of the left side of the road – it doesn’t matter as long as everyone is dong the same thing. I agree with that and it applies to style guides. It can get heated but for the best thing for the team is stick with a guide and work together. 24:36 – Aimee: I can go through the options to pick one of the style guides out there and then it will automatically create my configuration for me is helpful. Question: If you had to pick 2 or 3 rules that you are super helpful what would they be? 25:30 – Guest: To touch briefly on indentation. Whether you like four spaces or whether you are wild and like tabs, I think the indent rule is very helpful. Just for wiping out and eliminating that discussion through your team. Have your editor setup however they want but on the pre-hook... But my favorite rules I tend to lean towards the ones that saved me. The Guest goes through his favorite rules with ESLint. Check it out! 26:51 – Guest mentions his second favorite rule, here! 28:24 – Guest mentions his third favorite rule, here! 29:03 – Guest mentions the rule that makes him giggle a lot, here! 30:07 – Advertisement – Sentry! 31:22 – What is your take on running Fix? Does it make sense to run Fix? 32:00 – Guest: It depends and the idea behind Fix is the idea of doing a one time (at the start) fix everything that it can find wrong b/c I don’t want to do it by hand. It morphed into a more of a tool that people are using all the time. I too have mixed feelings about it. I think the greatest value you get out of Fix is that when you first install it or when you enable a new rule. I think in those situations you get a lot of value out of Fix. I think that when people were getting aggressive with their code styles it took us down a path where we... As a pre-commit hook it could be to fix things and part of the built system you wouldn’t want... People are probably wondering: Why doesn’t ESLint doesn’t fix all the time? It can be a team decision: do you want to run Fix at the point that the developer is writing the code, do you want to use Fix as running it as a build when you are bundling? It really seems more of a personal preference. I am on the fence about it. Even though I am leaning more towards... 35:16 – Do you run Premier? 35:20 – Guest: No I don’t. I don’t have anything against Premier but I think Prettier uses a very interesting space. 37:50 – Chuck: What is next for ESLint and what is next for you? 37:55 – Guest: Well, to be honest I am not sure what is next for ESLint. I haven’t been involved with keeping it maintained for the last few years. I do help out with feedback with decisions. But in general the ESLint the direction is that let’s add tings that help people avoid language hazards and make sure that ESLint is still pluggable. Lastly, that we will be there to help people and the community. There is this virtuosic cycle and tools like Babble and then tools like ESLint introducing rules adapting new rules and features better. For myself, and the future, I haven’t been involved with ESLint because I am focusing on my health. I was diagnosed with Lyme Disease and it meant that I needed to focus on my health. That’s why, too, I wasn’t able to join a few years ago. I am doing better but I am a few years away for working fulltime and writing books and blogging, again. The trajectory is upward. I want to stress that you need to take care of yourself. There is interesting stuff that we are doing and I love it, but make sure you take care of yourself! If you don’t have your health then nothing will really matter. I want to encourage you all to take care of yourselves better. This industry can take a toll on your body b/c it is high-stressed. If you are stressed your immune system will shut down. For a lot of us we are working too much and there isn’t an off-switch. I would like to encourage people to examine their life and their time. When you take time to turn off your analytic brain, and work on your creative brain then the pathways will connect better. Please save your money! Lyme disease is spread through tick bites. 44:30 – Aimee: Thank you for sharing that! 44:38 – Chuck: It’s encouraging to me that you are still trying to come back even after this disease. I think we take things for granted sometimes. You can’t always count on things going the way you want it to go. 45:19 – Guest: What happened to me was I left work and one Friday afternoon I had a normal weekend. My health was on the decline, and I rested all weekend. And Monday I couldn’t get out of bed. That started this whole period where I stopped leaving the house completely. That’s how quickly things can change for you. I harp on people a lot to save their money. If I didn’t have savings there would be a very different end to my story. I want to encourage people to save. 46:33 – Chuck: I think on that note let’s go to picks. Where can people find you? 46:45 – Guest: My blog is Human Who Codes. 47:10 – Chuck: Anything people can do to help you? Check out his books you won’t regret it! 47:33 – Guest: Buying books is always helpful. I would say that if you can spend some time contributing to ESLint that is always a great help. Anything you can do to help them will help me. I want to make sure that those folks are happy, healthy and productive. For me, personally, I love when people Tweet at me and say HI! I love hearing other people’s stories of how they have overcome past diseases or illnesses. If you want to send monetary gifts – donate to a wonderful organization that helps children with Lyme disease. I would encourage you to support if you feel inclined. 50:49 – Chuck: We appreciate it, and I appreciate you being so open about your personal story. 51:11 – Advertisement – eBook: Get a coder job! Links: JavaScript jQuery React Elixir Elm Vue GitHub – Prettier GitHub – Premier Lyme Light Foundation Inclusive Components ESLint – Disallow Specific Imports State of JS Learn JavaScript Book: Total Recall Goodbye Redux YouTube Channel – Sideways Human Who Codes – Nicholas Zakas Nicholas’ Books Nicholas’ Twitter Nicholas’ GitHub Nicholas’ LinkedIn Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Technical debt Professional JavaScript for Web Developers Chris Inclusive Components Blog CSS Cascade JS Jabber - code Cory No Restricted Imports State of JS Total Recall Charles My JavaScript Story Joe Thought bubbles... Goodbye Redux Sideways Channel Nicholas The Brain that Changes Its Self Ghost Boy Tip - Turn off your Wi-Fi before Bed

Panel: Aimee Knight Charles Max Wood (DevChat TV) Christopher Ferdinandi (Boston) Cory House (Kansas City) Joe Eames Special Guests: Nicholas Zakas In this episode, the panel talks with Nicholas Zakas who writes on his site, Human Who Codes. He is the creator of ESLint, also the author of several books, and he blogs, too. He was employed through Box and today he talks about ESLint in full detail! Check it out!  Show Topics: 0:05 – Advertisement: KENDO UI 0:37 – Hello! The panel is...(Chuck introduces everyone). 1:04 – Nicholas who are you? 1:17 – Nicholas: Yeah it’s been about 5 years and then you invited me again, but I couldn’t come on to talk about ESLint back then. That’s probably what people know me most for at this point. I created ESLint and I kicked that off and now a great team of people is maintaining it. 1:58 – Chuck: What is it? 2:04 – It’s a Linter for JavaScript. It falls into the same category as JSLint. The purpose of ESLint is to help you find problems with your code. It has grown quite a bit since I’ve created it. It can help with bugs and enforcing style guides and other things. 2:53 – Where did it come from? 2:57 – Guest: The idea popped into my head when I worked at Pop. One of my teammates was working on a bug and at that time we were using... Nothing was working and after investigating someone had written a JavaScript code that was using a native code to make an Ajax request. It wasn’t the best practice for the company at the time. For whatever reason the person was unaware of that. When using that native XML...there was a little bit of trickiness to it because it was a wrapper around the... We used a library to work around those situations and add a line (a Linter) for all JavaScript files. It was a text file and when you tried to render code through the process it would run and run the normal expression and it would fail if any of the...matched. I am not comfortable using normal expressions to write code for this. You could be matching in side of a string and it’s not a good way to be checking code for problems. I wanted to find a better way. 6:04 – Why did you choose to create a product vs. using other options out there? 6:15 – Guest: Both of those weren’t around. JSHint was pretty much the defector tool that everyone was using. My first thought was if JSHint could help with this problem? I went back to look at JSHint and I saw that on their roadmap you could create your own rules, and I thought that’s what we need. Why would I build something new? I didn’t see anything on GitHub and didn’t see the status of that. I wanted to see what the plan was, and they weren’t going to get to it. I said that I really needed this tool and I thought it would be helpful to others, too. 8:04 – My history was only back when it was customizable. 8:13 – Aimee: It’s interesting to see that they are basing it on regular expressions. 8:32 – Guest: Interesting thing at Box was that there was...I am not sure but one of the engineers at Box wrote... 9:03 – Aimee: I was going to ask in your opinion what do you think ES Lint is the standard now? 9:16 – Guest: How easy it is to plug things in. That was always my goal because I wanted the tool not to be boxed in – in anyway. The guest continues to talk about how pluggable ESLint is and the other features of this tool. 13:41 – One thing I like about ESLint is that it can be an educational tool for a team. Did you see that being an educational tool? 14:24 – Guest: How do you start introducing new things to a team that is running at full capacity? That is something that I’ve wondered throughout my career. As a result of that, I found that a new team there were some problems I the code base that were really hard to get resolved, because when one person recognizes it there isn’t a god way to share that information within a team in a non-confrontational way. It’s better to get angry at a tool rather than a person. Guest goes into what this can teach people. 18:07 – Panelist: I am not surprised. Is there a best practice to get a team to start with ESLint? Do you get the whole team in a room and show them the options or take the best guess and turn it on? 18:34 – Guest: The thing I recommend is that first and foremost get ESLint in your system with zero rules on. It starts that mindset into your development process. We can do something to automatically check... Get Syntax checking and you will se improvements on the number of bugs that are getting out of production. I recommend using the default the ESLint configuration. This has all of the things that we have found that are most likely errors and runtime errors vs. syntax errors. You can go through with those and sometimes it is easier to run that check with... Using those ESLint rules will clean up a lot of problems that you didn’t know you had with your code. There are too many problems with those rules. I recommend instead of turning them off then put the severity to warning and not error. That is something we started with in the beginning. We turned on as many rules as we could and it drove people crazy. They didn’t feel like when they were committing to a file why should I be... The idea with the different scenario levels you don’t’ want to turn off rules so people don’t know there is a problem. There can be a rule on so people will know that there is a problem, but... Doing that alone will give you a lot of benefit in using ESLint. How do you decide as a team on the rules that are maybe not for finding errors but for stylistic in error? Do we use four spaces, semi-colons, etc. To figure that out I am a big component on finding a pre-existing style guide and adapting it. Get everyone to agree. There is no right or wrong when it comes to stylistic preferences. It really is just getting everyone to do the same thing. I think it was Crawford that said: Whether you drive on the right side of the left side of the road – it doesn’t matter as long as everyone is dong the same thing. I agree with that and it applies to style guides. It can get heated but for the best thing for the team is stick with a guide and work together. 24:36 – Aimee: I can go through the options to pick one of the style guides out there and then it will automatically create my configuration for me is helpful. Question: If you had to pick 2 or 3 rules that you are super helpful what would they be? 25:30 – Guest: To touch briefly on indentation. Whether you like four spaces or whether you are wild and like tabs, I think the indent rule is very helpful. Just for wiping out and eliminating that discussion through your team. Have your editor setup however they want but on the pre-hook... But my favorite rules I tend to lean towards the ones that saved me. The Guest goes through his favorite rules with ESLint. Check it out! 26:51 – Guest mentions his second favorite rule, here! 28:24 – Guest mentions his third favorite rule, here! 29:03 – Guest mentions the rule that makes him giggle a lot, here! 30:07 – Advertisement – Sentry! 31:22 – What is your take on running Fix? Does it make sense to run Fix? 32:00 – Guest: It depends and the idea behind Fix is the idea of doing a one time (at the start) fix everything that it can find wrong b/c I don’t want to do it by hand. It morphed into a more of a tool that people are using all the time. I too have mixed feelings about it. I think the greatest value you get out of Fix is that when you first install it or when you enable a new rule. I think in those situations you get a lot of value out of Fix. I think that when people were getting aggressive with their code styles it took us down a path where we... As a pre-commit hook it could be to fix things and part of the built system you wouldn’t want... People are probably wondering: Why doesn’t ESLint doesn’t fix all the time? It can be a team decision: do you want to run Fix at the point that the developer is writing the code, do you want to use Fix as running it as a build when you are bundling? It really seems more of a personal preference. I am on the fence about it. Even though I am leaning more towards... 35:16 – Do you run Premier? 35:20 – Guest: No I don’t. I don’t have anything against Premier but I think Prettier uses a very interesting space. 37:50 – Chuck: What is next for ESLint and what is next for you? 37:55 – Guest: Well, to be honest I am not sure what is next for ESLint. I haven’t been involved with keeping it maintained for the last few years. I do help out with feedback with decisions. But in general the ESLint the direction is that let’s add tings that help people avoid language hazards and make sure that ESLint is still pluggable. Lastly, that we will be there to help people and the community. There is this virtuosic cycle and tools like Babble and then tools like ESLint introducing rules adapting new rules and features better. For myself, and the future, I haven’t been involved with ESLint because I am focusing on my health. I was diagnosed with Lyme Disease and it meant that I needed to focus on my health. That’s why, too, I wasn’t able to join a few years ago. I am doing better but I am a few years away for working fulltime and writing books and blogging, again. The trajectory is upward. I want to stress that you need to take care of yourself. There is interesting stuff that we are doing and I love it, but make sure you take care of yourself! If you don’t have your health then nothing will really matter. I want to encourage you all to take care of yourselves better. This industry can take a toll on your body b/c it is high-stressed. If you are stressed your immune system will shut down. For a lot of us we are working too much and there isn’t an off-switch. I would like to encourage people to examine their life and their time. When you take time to turn off your analytic brain, and work on your creative brain then the pathways will connect better. Please save your money! Lyme disease is spread through tick bites. 44:30 – Aimee: Thank you for sharing that! 44:38 – Chuck: It’s encouraging to me that you are still trying to come back even after this disease. I think we take things for granted sometimes. You can’t always count on things going the way you want it to go. 45:19 – Guest: What happened to me was I left work and one Friday afternoon I had a normal weekend. My health was on the decline, and I rested all weekend. And Monday I couldn’t get out of bed. That started this whole period where I stopped leaving the house completely. That’s how quickly things can change for you. I harp on people a lot to save their money. If I didn’t have savings there would be a very different end to my story. I want to encourage people to save. 46:33 – Chuck: I think on that note let’s go to picks. Where can people find you? 46:45 – Guest: My blog is Human Who Codes. 47:10 – Chuck: Anything people can do to help you? Check out his books you won’t regret it! 47:33 – Guest: Buying books is always helpful. I would say that if you can spend some time contributing to ESLint that is always a great help. Anything you can do to help them will help me. I want to make sure that those folks are happy, healthy and productive. For me, personally, I love when people Tweet at me and say HI! I love hearing other people’s stories of how they have overcome past diseases or illnesses. If you want to send monetary gifts – donate to a wonderful organization that helps children with Lyme disease. I would encourage you to support if you feel inclined. 50:49 – Chuck: We appreciate it, and I appreciate you being so open about your personal story. 51:11 – Advertisement – eBook: Get a coder job! Links: JavaScript jQuery React Elixir Elm Vue GitHub – Prettier GitHub – Premier Lyme Light Foundation Inclusive Components ESLint – Disallow Specific Imports State of JS Learn JavaScript Book: Total Recall Goodbye Redux YouTube Channel – Sideways Human Who Codes – Nicholas Zakas Nicholas’ Books Nicholas’ Twitter Nicholas’ GitHub Nicholas’ LinkedIn Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Technical debt Professional JavaScript for Web Developers Chris Inclusive Components Blog CSS Cascade JS Jabber - code Cory No Restricted Imports State of JS Total Recall Charles My JavaScript Story Joe Thought bubbles... Goodbye Redux Sideways Channel Nicholas The Brain that Changes Its Self Ghost Boy Tip - Turn off your Wi-Fi before Bed

Programmeringsövningar och tips till nybörjare på programmering. Fredrik och Kristoffer snackar att koppla bort på semestern och mer om övningar för programmerare. Vi funderar över upprepningens värde för lärandet och undrar om inte hela utvecklarvärlden byggt upp en missriktad rädsla för upprepning. Har ni fler förslag på bra dagliga problem? Fortsätt skicka in dem! Ludvig Gislason hörde av sig med två tips: “Hackerrank har gjort lite sport av det och där finns tävlingar, ranking osv men framförallt har de en stor drös problem att lösa och stöd för att du laddar upp dina lösningar till dem i en mängd olika språk. För mig som gillar att knacka kod lite som andra tycker om att spela tvspel var det här upptäckandet en riktigt trevlig överraskning. Jag upptäckte sidan genom en inspelad livesession på youtube av en användare som kallar sig SnapDragon. Exercism.io har ett antal problemset utformade som test suites i ett 20-tal språk som du ska få gröna. De har byggt ett CLI-verktyg runt tjänsten för att hantera problem och lösningar där du authar via github. Användare kan sedan “nitpicka” varandras lösningar och komma med förslag så att man kan iterera över sin lösning och submitta eventuella förbättringar. Jag har bara gjort ett par stycken men jag gillar verkligen initiativet och bredden." Fredrik återupptäcker charmen med dataimport - i PHP dessutom. Hur många procent av all kod som skrivs handlar om import och export (och lite massage på vägen) av data? Har det bidragit till uppskattningen av funktionell programmering? Blir alla problem mer lätthanterade av att omformuleras som datamanipulering? Som andra huvudämne snackar vi utifrån lyssnares frågor om utmaningarna kring att komma igång med programmering. Det viktiga är inte vilket språk eller vilka verktyg man väljer utan att man börjar göra saker. Kommer man på att något inte passar en upptäcker man det med tiden, och då går det utmärkt att växla till något annat språk eller andra verktyg. Vi undrar om Javascript är ett bra språk att börja med, för att det är populärt och användbart men kanske ännu mer för att allt man behöver för att börja är en webbläsare och kanske ett textredigeringsprogram och båda delarna redan finns på varenda dator, och konstaterar att vi tyvärr inte har några tips på bra nybörjarböcker. Ett stort tack till Cloudnet som sponsrar vår VPS! Har du kommentarer, frågor eller tips? Vi är @kodsnack, @tobiashieta, @isallmaroon och @bjoreman på Twitter, har en sida på Facebook och epostas på info@kodsnack.se om du vill skriva längre. Vi läser allt som skickas. Gillar du Kodsnack får du hemskt gärna recensera oss i iTunes! Länkar Advent of code Kodsnacks Github-repo för Advent of code-lösningar Kodsnack 136 - avsnittet där Kristoffer efterlyste dagliga övningar för programmerare Kodkator Project Euler Hackerrank - tips från Ludvig Gislason Exercism - tips från Ludvig Gislason Breakout Ecmascript 2015 En liten sida på Kodsnack för kod - inte bara Advent of code Melin - Joacim Melin Björeman // Melin Macpro Exempelskriptet för import av markdownfiler till Wordpress Varför folk som bryr sig om språk inte gillar PHP PHP-dokumentationen Kodcentrum Scratch Peek och poke Squeak Professional Javascript, av Nicholas Zakas. Fredrik hade tydligen första upplagan, den andra var den som började få för mycket att omfamna Javascript the good parts André Lamothe SICP - Structure and interpretation of computer programs The little schemer Metaprogrammering Gerald Sussman Richard Feynman Debug 76 med Melton och Ganatra Titlar Jag kan inte riktigt koppla bort det Daglig övning för programmering Man går alltid vidare till nästa sak Repetitionen som är kärnan i att lära sig Mitt dagliga problem Innan det kan bli ett dagligt problem Ren datamanipulering är ju ganska kul När jag använde PHP så var det väldigt länge sedan Stack overflow i dokumentationen Vad jag tror är ett bra sätt att börja Vem är det som vill börja programmera? En helt annan panik i rösten Tankar som man helst bara skjuter åt sidan Både roligt och begripligt Vilka verktyg ska jag köpa?

02:15 - Jamund Ferguson Introduction Twitter GitHub Blog PayPal Jamund Ferguson: JavaScript Linting for Code Quality & ESLint Overview 02:47 - Lint (Background) JSLint Douglas Crockford JSHint ESLint [GitHub] eslint Nicholas Zakas [Gitter] eslint 04:48 - Keeping ESLint Up-to-date ​​Esprima Ariya Hidayat espree Babel babel-eslint ES6 (ECMAScript 6) 08:09 - Abstract Syntax Tree (ASTs) Jamund Ferguson: Don’t be scared of abstract syntax trees Minification UglifyJS 13:28 - Using Lint Tools Context Switching Aspects to Linting: Code Standardization Catching Bad Mistakes JSCS (JavaScript Code Style) “Extends” 20:42 - Are there a downsides to linting? The Social Problem 23:40 - Establishing Rules Bikeshedding Consistency 25:12 - Cool ESLint Features handle-callback-err Not Throwing Literals No Restricted Modules Jamund Ferguson: Error Handling in Node.js @ MountainWest JavaScript 2014 30:45 - How ESLint Works Internally eslint-plugin-angular Configuration and Defaults 40:07 - Getting Started with Linting 43:03 - Autofixer 44:41 - Plugins 46:47 - Linter Feedback From the Panel Picks Mozilla (AJ) We Will All Be Game Programmers (Aimee) Search Inside Yourself: The Unexpected Path to Achieving Success, Happiness (and World Peace) by Chade-Meng Tan (Aimee) Good Mythical Morning (Dave) Salt Lake City (Dave) BB King Calls This One Of His Best Performances (Jamison) json-server (Jamison) Austenland (Joe) Supergirl (Joe) A Short History of Nearly Everything by Bill Bryson (Jamund) The Book of Mormon (Jamund)          

02:15 - Jamund Ferguson Introduction Twitter GitHub Blog PayPal Jamund Ferguson: JavaScript Linting for Code Quality & ESLint Overview 02:47 - Lint (Background) JSLint Douglas Crockford JSHint ESLint [GitHub] eslint Nicholas Zakas [Gitter] eslint 04:48 - Keeping ESLint Up-to-date ​​Esprima Ariya Hidayat espree Babel babel-eslint ES6 (ECMAScript 6) 08:09 - Abstract Syntax Tree (ASTs) Jamund Ferguson: Don’t be scared of abstract syntax trees Minification UglifyJS 13:28 - Using Lint Tools Context Switching Aspects to Linting: Code Standardization Catching Bad Mistakes JSCS (JavaScript Code Style) “Extends” 20:42 - Are there a downsides to linting? The Social Problem 23:40 - Establishing Rules Bikeshedding Consistency 25:12 - Cool ESLint Features handle-callback-err Not Throwing Literals No Restricted Modules Jamund Ferguson: Error Handling in Node.js @ MountainWest JavaScript 2014 30:45 - How ESLint Works Internally eslint-plugin-angular Configuration and Defaults 40:07 - Getting Started with Linting 43:03 - Autofixer 44:41 - Plugins 46:47 - Linter Feedback From the Panel Picks Mozilla (AJ) We Will All Be Game Programmers (Aimee) Search Inside Yourself: The Unexpected Path to Achieving Success, Happiness (and World Peace) by Chade-Meng Tan (Aimee) Good Mythical Morning (Dave) Salt Lake City (Dave) BB King Calls This One Of His Best Performances (Jamison) json-server (Jamison) Austenland (Joe) Supergirl (Joe) A Short History of Nearly Everything by Bill Bryson (Jamund) The Book of Mormon (Jamund)          

02:15 - Jamund Ferguson Introduction Twitter GitHub Blog PayPal Jamund Ferguson: JavaScript Linting for Code Quality & ESLint Overview 02:47 - Lint (Background) JSLint Douglas Crockford JSHint ESLint [GitHub] eslint Nicholas Zakas [Gitter] eslint 04:48 - Keeping ESLint Up-to-date ​​Esprima Ariya Hidayat espree Babel babel-eslint ES6 (ECMAScript 6) 08:09 - Abstract Syntax Tree (ASTs) Jamund Ferguson: Don’t be scared of abstract syntax trees Minification UglifyJS 13:28 - Using Lint Tools Context Switching Aspects to Linting: Code Standardization Catching Bad Mistakes JSCS (JavaScript Code Style) “Extends” 20:42 - Are there a downsides to linting? The Social Problem 23:40 - Establishing Rules Bikeshedding Consistency 25:12 - Cool ESLint Features handle-callback-err Not Throwing Literals No Restricted Modules Jamund Ferguson: Error Handling in Node.js @ MountainWest JavaScript 2014 30:45 - How ESLint Works Internally eslint-plugin-angular Configuration and Defaults 40:07 - Getting Started with Linting 43:03 - Autofixer 44:41 - Plugins 46:47 - Linter Feedback From the Panel Picks Mozilla (AJ) We Will All Be Game Programmers (Aimee) Search Inside Yourself: The Unexpected Path to Achieving Success, Happiness (and World Peace) by Chade-Meng Tan (Aimee) Good Mythical Morning (Dave) Salt Lake City (Dave) BB King Calls This One Of His Best Performances (Jamison) json-server (Jamison) Austenland (Joe) Supergirl (Joe) A Short History of Nearly Everything by Bill Bryson (Jamund) The Book of Mormon (Jamund)          

Panel Nicholas C. Zakas (twitter github blog) Joe Eames (twitter github blog) AJ O’Neal (twitter github blog) Jamison Dance (twitter github blog) Merrick Christensen (twitter github) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 01:24 - Nicholas Zakas Introduction Box Maintainable JavaScript by Nicholas C. Zakas High Performance JavaScript (Build Faster Web Application Interfaces) by Nicholas C. Zakas Yahoo 02:19 - What Makes Maintainable JavaScript? Code Layout Clever Solutions (“Chicken Blood Solutions”) 04:39 - Formatting Thinking, Fast and Slow by Daniel Kahneman Broken Window Theory 07:33 - Architecture aura Nicholas Zakas: The Scalable JavaScript Application Architecture Feature Encapsulation 14:11 - 'High Performance Javascript' and the balance between short-term and long-term knowledge 19:17 - Important conventions for a team to follow Styles Mini Design Patterns Readability 26:14 - Tools & Techniques Style Guide 28:31 - Breaking the continuous integration build 31:14 - Linting JSLint 32:35 - Developing skills for architecting things Experience Personal Trait of Curiosity Component-based and Systems-based software engineers 37:52 - Architecture and Maintainability Testability Backbone.js 43:28 - Creating common conventions that will apply across projects Picks Domo (Joe) Pluralsight (Joe) Game Dev Tycoon (Joe) The Star Wars (Joe) Foundation Actionscript 3.0 Animation: Making Things Move! by Keith Peters (Merrick) ng-conf (Merrick) Kveikur by Sigur Rós (Merrick) makemeasandwich (AJ) Sleep (AJ) Jekyll Themes (Jamison) Growing Object-Oriented Software, Guided by Tests by Steve Freeman (Jamison) A Canticle For Leibowitz by Walter M. Miller Jr. (Jamison) DevChat.tv (Chuck) Thinking, Fast and Slow by Daniel Kahneman (Nicholas) StePhest Colbchella '013 - Time to Dance (Nicholas) Evolution of Music - Pentatonix (Nicholas) Next Week Meteor.js with Marcus Phillips and Fred Zirdung Transcript [Hosting and bandwidth provided by the Blue Box Group. Check them out at BlueBox.net.]  [This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.]  [This podcast is sponsored by JetBrains, makers of WebStorm. Whether you’re working with Node.js or building the frontend of your web application, WebStorm is the tool for you. It has great code quality and code exploration tools and works with HTML5, Node, TypeScript, CoffeeScript, Harmony, LESS, Sass, Jade, JSLint, JSHint, and the Google Closure Compiler. Check it out at JetBrains.com/WebStorm.] CHUCK:  Hey everybody and welcome to episode 75 of the JavaScript Jabber show. This week on our panel, we have Joe Eames. JOE:  Hey, everyone. CHUCK:  AJ O’Neal. AJ:  I can hit unmute. I'm here. CHUCK:  Jamison Dance. JAMISON:  Hello, friends. CHUCK:  Merrick Christensen. MERRICK:  Hey, guys. CHUCK:  I’m Charles Max Wood from DevChat.TV. This week, we have a special guest, that’s Nicholas Zakas. NICHOLAS:  Yup, you got it. CHUCK:  So, since you haven’t been on the show before, do you want to introduce yourself? NICHOLAS:  Sure. I'm a software engineer that is working for Box currently. I think a lot of people probably know me from the books that I've written, mostly on the topic of JavaScript and the talks that I've given also on that topic. And a lot of that relates back to my work when I was at Yahoo. I was there for about five years and was the lead on the Yahoo homepage redesign. And a lot of what I do is really just try to solve problems in real life and then share what I did with everybody else in whatever way I think is most appropriate - writing or speaking or coming on podcasts. CHUCK:  Yes, you're being modest. You have a book,

Panel Nicholas C. Zakas (twitter github blog) Joe Eames (twitter github blog) AJ O’Neal (twitter github blog) Jamison Dance (twitter github blog) Merrick Christensen (twitter github) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 01:24 - Nicholas Zakas Introduction Box Maintainable JavaScript by Nicholas C. Zakas High Performance JavaScript (Build Faster Web Application Interfaces) by Nicholas C. Zakas Yahoo 02:19 - What Makes Maintainable JavaScript? Code Layout Clever Solutions (“Chicken Blood Solutions”) 04:39 - Formatting Thinking, Fast and Slow by Daniel Kahneman Broken Window Theory 07:33 - Architecture aura Nicholas Zakas: The Scalable JavaScript Application Architecture Feature Encapsulation 14:11 - 'High Performance Javascript' and the balance between short-term and long-term knowledge 19:17 - Important conventions for a team to follow Styles Mini Design Patterns Readability 26:14 - Tools & Techniques Style Guide 28:31 - Breaking the continuous integration build 31:14 - Linting JSLint 32:35 - Developing skills for architecting things Experience Personal Trait of Curiosity Component-based and Systems-based software engineers 37:52 - Architecture and Maintainability Testability Backbone.js 43:28 - Creating common conventions that will apply across projects Picks Domo (Joe) Pluralsight (Joe) Game Dev Tycoon (Joe) The Star Wars (Joe) Foundation Actionscript 3.0 Animation: Making Things Move! by Keith Peters (Merrick) ng-conf (Merrick) Kveikur by Sigur Rós (Merrick) makemeasandwich (AJ) Sleep (AJ) Jekyll Themes (Jamison) Growing Object-Oriented Software, Guided by Tests by Steve Freeman (Jamison) A Canticle For Leibowitz by Walter M. Miller Jr. (Jamison) DevChat.tv (Chuck) Thinking, Fast and Slow by Daniel Kahneman (Nicholas) StePhest Colbchella '013 - Time to Dance (Nicholas) Evolution of Music - Pentatonix (Nicholas) Next Week Meteor.js with Marcus Phillips and Fred Zirdung Transcript [Hosting and bandwidth provided by the Blue Box Group. Check them out at BlueBox.net.]  [This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.]  [This podcast is sponsored by JetBrains, makers of WebStorm. Whether you’re working with Node.js or building the frontend of your web application, WebStorm is the tool for you. It has great code quality and code exploration tools and works with HTML5, Node, TypeScript, CoffeeScript, Harmony, LESS, Sass, Jade, JSLint, JSHint, and the Google Closure Compiler. Check it out at JetBrains.com/WebStorm.] CHUCK:  Hey everybody and welcome to episode 75 of the JavaScript Jabber show. This week on our panel, we have Joe Eames. JOE:  Hey, everyone. CHUCK:  AJ O’Neal. AJ:  I can hit unmute. I'm here. CHUCK:  Jamison Dance. JAMISON:  Hello, friends. CHUCK:  Merrick Christensen. MERRICK:  Hey, guys. CHUCK:  I’m Charles Max Wood from DevChat.TV. This week, we have a special guest, that’s Nicholas Zakas. NICHOLAS:  Yup, you got it. CHUCK:  So, since you haven’t been on the show before, do you want to introduce yourself? NICHOLAS:  Sure. I'm a software engineer that is working for Box currently. I think a lot of people probably know me from the books that I've written, mostly on the topic of JavaScript and the talks that I've given also on that topic. And a lot of that relates back to my work when I was at Yahoo. I was there for about five years and was the lead on the Yahoo homepage redesign. And a lot of what I do is really just try to solve problems in real life and then share what I did with everybody else in whatever way I think is most appropriate - writing or speaking or coming on podcasts. CHUCK:  Yes, you're being modest. You have a book,

Panel Nicholas C. Zakas (twitter github blog) Joe Eames (twitter github blog) AJ O’Neal (twitter github blog) Jamison Dance (twitter github blog) Merrick Christensen (twitter github) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 01:24 - Nicholas Zakas Introduction Box Maintainable JavaScript by Nicholas C. Zakas High Performance JavaScript (Build Faster Web Application Interfaces) by Nicholas C. Zakas Yahoo 02:19 - What Makes Maintainable JavaScript? Code Layout Clever Solutions (“Chicken Blood Solutions”) 04:39 - Formatting Thinking, Fast and Slow by Daniel Kahneman Broken Window Theory 07:33 - Architecture aura Nicholas Zakas: The Scalable JavaScript Application Architecture Feature Encapsulation 14:11 - 'High Performance Javascript' and the balance between short-term and long-term knowledge 19:17 - Important conventions for a team to follow Styles Mini Design Patterns Readability 26:14 - Tools & Techniques Style Guide 28:31 - Breaking the continuous integration build 31:14 - Linting JSLint 32:35 - Developing skills for architecting things Experience Personal Trait of Curiosity Component-based and Systems-based software engineers 37:52 - Architecture and Maintainability Testability Backbone.js 43:28 - Creating common conventions that will apply across projects Picks Domo (Joe) Pluralsight (Joe) Game Dev Tycoon (Joe) The Star Wars (Joe) Foundation Actionscript 3.0 Animation: Making Things Move! by Keith Peters (Merrick) ng-conf (Merrick) Kveikur by Sigur Rós (Merrick) makemeasandwich (AJ) Sleep (AJ) Jekyll Themes (Jamison) Growing Object-Oriented Software, Guided by Tests by Steve Freeman (Jamison) A Canticle For Leibowitz by Walter M. Miller Jr. (Jamison) DevChat.tv (Chuck) Thinking, Fast and Slow by Daniel Kahneman (Nicholas) StePhest Colbchella '013 - Time to Dance (Nicholas) Evolution of Music - Pentatonix (Nicholas) Next Week Meteor.js with Marcus Phillips and Fred Zirdung Transcript [Hosting and bandwidth provided by the Blue Box Group. Check them out at BlueBox.net.]  [This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.]  [This podcast is sponsored by JetBrains, makers of WebStorm. Whether you’re working with Node.js or building the frontend of your web application, WebStorm is the tool for you. It has great code quality and code exploration tools and works with HTML5, Node, TypeScript, CoffeeScript, Harmony, LESS, Sass, Jade, JSLint, JSHint, and the Google Closure Compiler. Check it out at JetBrains.com/WebStorm.] CHUCK:  Hey everybody and welcome to episode 75 of the JavaScript Jabber show. This week on our panel, we have Joe Eames. JOE:  Hey, everyone. CHUCK:  AJ O’Neal. AJ:  I can hit unmute. I'm here. CHUCK:  Jamison Dance. JAMISON:  Hello, friends. CHUCK:  Merrick Christensen. MERRICK:  Hey, guys. CHUCK:  I’m Charles Max Wood from DevChat.TV. This week, we have a special guest, that’s Nicholas Zakas. NICHOLAS:  Yup, you got it. CHUCK:  So, since you haven’t been on the show before, do you want to introduce yourself? NICHOLAS:  Sure. I'm a software engineer that is working for Box currently. I think a lot of people probably know me from the books that I've written, mostly on the topic of JavaScript and the talks that I've given also on that topic. And a lot of that relates back to my work when I was at Yahoo. I was there for about five years and was the lead on the Yahoo homepage redesign. And a lot of what I do is really just try to solve problems in real life and then share what I did with everybody else in whatever way I think is most appropriate - writing or speaking or coming on podcasts. CHUCK:  Yes, you're being modest. You have a book,

Nicholas Zakas is a Front-end guy at Box and recently gave a talk called "Enough with the JavaScript Already!" where he advocates that developers use fewer libraries and write smarter JS. Where do we start? What are the four opportunities to load JavaScript? Is Progressive Enhancement still the right solution? Aren't we supposed to be writing MORE JavaScript? Nicholas educates Scott on all the right moves when writing front ends on today's web.

Today we are talking to Nicholas Zakas. He is a front-end engineer, author, and speaker working at Box, and before that, he worked at Yahoo! for almost five years, where he was front-end tech lead for the Yahoo! homepage and a contributor to the YUI library. He regularly blogs, and for a recent blog-post he conducted a little research on how people use GitHub in a company internal context, so I invited him onto the show to ask about his findings. If you cannot see the audio controls, your browser does not support the audio element. Use the link below to download the mp3 manually. Link to mp3Links:Nicholas' homepage/blog, Google+, Twitter, GitHubHis article about how people are using GitHubBoxUnderscore vs Lo-Dash "controversy" (I heard about it on JavaScript Jabbers)Unfuddle (GitHub alternative with more stuff)Some tools for cleaning up old branchesNicholas' latest project: ESLint Listen to the episode on YouTube

As browsers explode with new capabilities and migrate onto devices users can be left wondering, "what’s taking so long?" Learn how HTML, CSS, JavaScript, and the web itself conspire against a fast-​​running application and simple tips to create a snappy interface that delight users instead of frustrating them. Nicholas C. Zakas is principal front-​​end engineer for the Yahoo! homepage, a contributor to YUI, and an author. Nicholas has written Professional JavaScript for Web Developers, Professional Ajax, and High Performance JavaScript. He has also contributed a chapter to Steve Souders’ Even Faster Web Sites. Nicholas posts regularly at his blog as well as on YUI Blog. Follow Nicholas on Twitter: @slicknet Licensed as Creative Commons Attribution-Share Alike 3.0 (http://creativecommons.org/licenses/by-sa/3.0/).

For much of its existence, JavaScript has been slow. No one complained until developers created complex web applications with thousands of lines of JavaScript code. Although newer JavaScript engines have improved the situation, there's still a lot to understand about what makes JavaScript slow and what you can do to speed up your code. More info at: https://fronteers.nl/congres/2010/sessions/high-performance-javascript-nicholas-zakas

For much of its existence, JavaScript has been slow. No one complained until developers created complex web applications with thousands of lines of JavaScript code. Although newer JavaScript engines have improved the situation, there's still a lot to understand about what makes JavaScript slow and what you can do to speed up your code. More info at: https://fronteers.nl/congres/2010/sessions/high-performance-javascript-nicholas-zakas