Podcasts about Zakas

Kai kurie darbdaviai siūlo apmokamas laisvas dienas tiems savo darbuotojams, kurie yra krašto apsaugos savanoriai ar Šaulių sąjungos nariai. Ar tokia priemonė gali paskatinti žmones aktyviau jungtis į pilietiškas organizacijas? Kuo tai gali būti naudinga verslui?Taip pat, domėsimės politikos vieta Eurovizijoje.Lietuvoje naminės katės kasmet nužudo milijonus paukščių. Taip skaičiuoja ornitologai ir piktinasi, kad paukščiai žūsta dėl to, kad žmonės palieka savo gyvūnus be priežiūros, tad specialistai ragina bent pavasarį, paukščių perėjimo metu, laikyti kates namie, o lauke vedžioti su pavadėliais. Taip pat, dalis gamtininkų ir mokslininkų atkreipia dėmesį, kad laisvai gamtoje būnančios naminės katės gali tapti pavojingų virusų nešiotojomis, pavyzdžiui, paukščių gripo.Gero nusiteikimo nestokojanti Zakų šeima jau ne vieną dešimtmetį puoselėja daržininkystės ūkį, augina ir perdirba paklausiausias lietuviškas daržoves: bulves, morkas, kopūstus, agurkus ir dar daugybę kitų. Ūkio įkūrėjas Kęstutis Zakas atsimena: veiklos pradžioje darbui teko pasikinkyti ir arklį, o dabar - dalis procesų robotizuoti. Į ūkio plėtojimą įsitraukusi visa šeima. Tuo netruksite įsitikinti. Zakų šeimos ūkyje Šiaulių rajone, Jauniūnų kaime, lankėsi LRT Radijo laidos „Gimtoji žemė“ vedėja Rūta Simanavičienė.Ved. Darius Matas

Patirties ir šeimos vienybės Zakų šeimos aruode netrūksta. Ūkio pradininkas Kęstutis Zakas sako, kad žemę pradėjo dirbti su arkliu, o štai dabar gali pasidžiaugti ir ūkyje dirbančiu robotu, kuris leidžia išvengti sunkaus rankinio darbo. Zakai augina mėgstamiausias lietuvių daržoves: bulves, morkas, agurkus, kopūstus ir kita bei jas perdirba. Lietuvos daržovių augintojų asociacijos direktorė Indrė Lukoševičienė pabrėžia investavimo į technologijas svarbą.10 metų seniausią Spelta kviečių veislę auginantis biodinaminio ūkio savininkas Arūnas Martinėlis iš Levandiškio kaimo, Širvintų rajone, įsirengė ir malūną. Iš Spelta miltų galima iškepti ekologiškas bei visavertę maistinę vertę turinčias bandeles, blynus, duoną.Rubrika „Gamtininko komentaras“. Aukštaitijos nacionalinis parkas ir Labanoro regioninis parkas pasižymi labai turtinga laumžirgių fauna. Šiuose parkuose gyvena 61 laumžirgių rūšis iš 69 aptiktų Lietuvoje. Kuo laumžirgiai svarbūs stebint klimato kaitos procesus papasakos aplinkosaugininkas Andrejus Gaidamavičius.Ved. Rūta Simanavičienė

ABOUT OUR GUEST:  Martie Edmunds Zakas has been Mueller Water Products' CEO since August 2023 and served as President and CEO from August 2023 to May 2024. She previously served as the Executive Vice President and Chief Financial Officer of Mueller Water Products since 2018. She has directed Mueller's strategic planning, corporate development, investor relations and corporate communications activities since joining the Company in 2006. Prior to joining Mueller, Martie spent five years with Russell Corporation where she held a variety of positions culminating in her role as Corporate Vice President, Chief of Staff, Business Development and Treasurer, until its 2006 acquisition by Berkshire Hathaway. From 1993 to 2000, Martie served as Corporate Vice President, Director of Investor Relations and Corporate Secretary for Equifax, Inc., a global data, analytics and technology company. She began her career as an investment banker at Morgan Stanley. Martie earned a Bachelor of Arts degree from Randolph-Macon Woman's College (now Randolph College), a MBA from the University of Virginia Darden School of Business and a Juris Doctor from the University of Virginia School of Law. She is a Director of Mueller Water Products and BlueLinx Holdings, Inc., and is a former Director of Atlantic Capital Bancshares, Inc. She serves on the Board of Trustees of the University of Virginia Darden School Foundation. CONNECT WITH MARTIE  LinkedIn   CONNECT WITH MUELLER WATER PRODUCTSWebsite   X (Twitter)  LinkedIn YouTube EPISODE AND EMPOWERING WOMEN IN INDUSTRY LINKSEmpowering Women in Industry Conference RegistrationEmpowering Women in Industry MembershipEmpowering Women in Industry MagazineEmpowering Women in Industry WebsiteEmpowering Women in Industry Virtual Events QUOTES AND KEY TAKEAWAYS“I am really honored to be a female leading a manufacturing company in the U.S. because you do not see as many female CEOs of public manufacturing companies.  By seeing the unexpected, I think it will help us all move forward and hopefully in the future we will see more female CEOs in the manufacturing industry. Then it becomes expected.”Inclusion: “Importantly, if you feel included and feel part of that team then I think we then are going to get the benefits of hearing all the different voices, ideas, and backgrounds such that we can have collective success.”“You want to feel that the contributions you are making or the organization you are working with are making important contributions.”“You need to have your own personal set of values.  As you go through this, ensure you have your baseline of what your values are and you ensure that is an integral part of the work that you are doing.”Most important skill: “Be adaptable and be curious. Because whatever the headlines are today, they are going to change.”“Observe what you see that you like and that you may want to emulate.  As importantly, see what you don't like. You can take that and say I do not want that to be part of my toolkit.” 

Cindy Elgan glanced into the lobby of her office and saw a sheriff's deputy waiting at the front counter. “Let's start a video recording, just in case this goes sideways,” Elgan, 65, told one of her employees in the Esmeralda County clerk's office. She had come to expect skepticism, conspiracy theories and even threats related to her job as an election administrator. She grabbed her annotated booklet of Nevada state laws, said a prayer for patience and walked into the lobby to confront the latest challenge to America's electoral process.The deputy was standing alongside a woman that Elgan recognized as Mary Jane Zakas, 77, a longtime elementary schoolteacher and a leader in the local Republican Party. She often asked for a sheriff's deputy to accompany her to the election's office, in case her meetings became contentious.“I hope you're having a blessed morning,” Zakas said. “Unfortunately, a lot of people are still very concerned about the security of their votes. They've lost all trust in the system.”After the 2020 election, former President Donald J. Trump's denials and accusations of voter fraud spread outward from the White House to even the country's most remote places, like Esmeralda County. Elgan knew most of the 620 voters in the town. Still, they accused her of being paid off and skimming votes away from Trump. And even though their allegations came with no evidence, they wanted her recalled from office before the next presidential election in November.

Back when I was starting my planning business in 2010, things were a lot different than today.  Community over competition wasn't a thing. Instagram wasn't a thing yet. TikTok obviously wasn't around. Podcasts weren't around. And you know what else hadn't taken off yet? The coaching boom.Back then, we didn't have wedding pros telling us what they had done to grow their businesses, which was a challenge because we had to learn from failing.But now, you have sooooo many voices to choose from, and so many different opinions on how to grow your business the right way.  I've heard from you that it's completely overwhelming.So what can we do about it? And where should we be spending our time?-----Our guest is Steph Zakas, coach and photographer, and host of the Your Next Breakthrough Podcast.-----(00:00:00) Navigating Coaching Overload in Business(00:06:06) Empowering Entrepreneurs Through Core Issue Coaching(00:10:37) Entrepreneurial Impact of External Marketing Messages(00:24:16) Client-Centered Sales Approach for Efficiency(00:26:38) "Embracing Safety through Rest and Mindfulness"(00:38:59) Personalized Morning Routines for Optimal Energy(00:39:55) Personalized Daily Routines for Peak Productivity(00:44:46) Maximizing High-Level Thinking Through Delegating---Today's episode is brought to you by The Planner's Vault. The doors are currently closed for The Planner's Vault, but join the wait list now so you can be the first to know when the doors re-open.Weddings for Real on Social Media:Instagram: @weddingsforrealFacebook: @weddingsforrealtwitter: @weddingsforrealHosted by Megan Gillikin, Weddings for Real is presented by The Planner's Vault, and is produced by Earfluence. ----Podcast Production or Podcast Guesting Services - https://www.earfluence.com/wfr

20 Vanessa Zakas Reflections On Glory by Golden Hills

Steph ranks #1 for "Iceland Elopement Photographer", but her marketing and digital marketing is so much more than that! She's a Master Coach, Sales Expert, Photographer, and Podcast Host. Check out her free guide "25 Ways to Market Your Business As An Introvert, without relying on social media" https://www.stephzakas.com/25-introvert-marketing-freebie and more info about her Iceland Retreat https://www.stephzakas.com/iceland-retreat It's a 2-month experience starting with a group coaching micromind on June 1st to shift your money confidence and ending in a 3-day Adventure Retreat in Iceland July 17-19.  It's a metamorphosis of shedding the layers holding you down, finding clarity on your next level, and becoming radically confident it will happen. The experience will transform the top 3 reasons blocking you from your next level:  Deepening your self-confidence & what's possible for you  Shifting your relationship to money coming into your life And elevating your brand, packages, and sales skills to convey the value to the dreamy aligned clients you want to work with.   The doors to join close May 31st and the ticket includes accommodation, food during the Retreat, VIP Excursion, Planning help & coaching from Steph, and a 5-week Group Coaching Micromind. Steph's Podcast: Alchemize Your Weird

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.

Steph Zakas is an adventure elopement photographer living in Iceland and a business coach for high achieving entrepreneurs. She turned $300 in saved barista tips into a multi-six figure photography company and broke all the rules along the way. In this interview, we chat about her journey in photography, from her beginnings in Ohio and the path that took her to Iceland. We'll discuss what life is like for her as an adventure wedding photographer, her unique approach to working with clients, and how she sets herself apart in a competitive market. COACHING & EDUCATION SITE: https://www.bossitbrave.com/ COURSES FOR ELOPEMENT PHOTOGRAPHERS: https://www.bossitbrave.com/business-courses WEBSITE: https://www.zakasphotography.com/ CLUBHOUSE: @stephzakas IG: https://www.instagram.com/icelandadventureweddings/ Facebook: https://www.facebook.com/groups/thebravecave Have you heard? A game-changer in the preset world has arrived. Introducing QUEST. Quest is a subscription-based platform with exclusive access to new signature presets & profiles for only $8/month. Subscribers also get access to great bonus content & tutorials, live edit sessions and Q&As, and the chance to connect with a community in our Quest Facebook group. www.archipelagoquest.com Podcasts listeners can get their first month of Quest membership FREE with code: PODCAST30 This is a limited time offer, available until the end of March, 2021.

“You don’t want to do something that will impact the environment after you leave” On the first episode of the Creative Wedding Podcast I talk to Stephanie Zakas about Iceland and Leave No Trace. Stephanie recently moved to Iceland after flying back and forth for a few years and has some great insight about safety and the do's and dont's of Iceland. You can find her work at: https://www.zakasphotography.com/ https://www.instagram.com/icelandadventureweddings/ Other helpful links: Leave No Trace: LNT.org Icelandic Pledge: https://www.inspiredbyiceland.com/icelandicpledge Environmental Funds for Iceland: https://www.mountainguides.is/environmental-fund AND A HUGE SHOUTOUT TO CASSIE LOPEZ! She wrote and recorded the intro song for me. She's also an amazing wedding photographer! https://www.cassielopez.com/ AND https://www.instagram.com/cassielopezphotography/ My Work: https://www.brandipotterphoto.com Education: https://www.brandipotterlearn.com Instagram: https://www.instagram.com/brandipotterphoto

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Joined By Special Guest: Jeremy Fairbank Episode Summary Jeremy is a Software Developer at Test Double and the author of Programming Elm book. Even though Jeremy majored in Chemistry in college, he was always interested in programming since middle school. After he graduated from college he went to work as a web developer at Plastic Industries and relied on blog posts and other online resources to teach himself how to code. Gradually as the company’s needs changed, Jeremy transitioned into an application developer. He taught himself JavaScript using the book Professional JavaScript for Web Developers . He then attented a Coursera classto learn on principles of functional programming and gained experience with many front end frameworks and libraries, including Elm, React, Redux, Backbone.js, and Marionette.js. Jeremy is based out of Hawaii and when he isn't coding, he spends his time playing his guitar and hiking and going to the beach with his family. Links JSJ 325: Practical functional programming in JavaScript and languages like Elm with Jeremy Fairbank Jeremy’s GitHub Jeremy's LinkedIn Jeremy’s Blog Professional JavaScript for Web Developers by Nicholas C. Zakas Professional JavaScript for Web Developers by Matt Frisbie https://knockoutjs.com/ https://marionettejs.com/ https://www.coursera.org/ https://www.coursera.org/learn/programming-languages elm-lang.org https://www.facebook.com/javascriptjabber https://twitter.com/JSJabber https://www.facebook.com/DevChattv Picks Jeremy Fairbank: Programming Elm The Umbrella Academy Beyond Burger Charles Max Wood: Orphan Black https://devchat.tv/ https://www.netlify.com/ https://www.11ty.io/ https://github.com/cmaxw/devchat-eleventy JavaScript Jabber - Devchat.tv

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Joined By Special Guest: Jeremy Fairbank Episode Summary Jeremy is a Software Developer at Test Double and the author of Programming Elm book. Even though Jeremy majored in Chemistry in college, he was always interested in programming since middle school. After he graduated from college he went to work as a web developer at Plastic Industries and relied on blog posts and other online resources to teach himself how to code. Gradually as the company’s needs changed, Jeremy transitioned into an application developer. He taught himself JavaScript using the book Professional JavaScript for Web Developers . He then attented a Coursera classto learn on principles of functional programming and gained experience with many front end frameworks and libraries, including Elm, React, Redux, Backbone.js, and Marionette.js. Jeremy is based out of Hawaii and when he isn't coding, he spends his time playing his guitar and hiking and going to the beach with his family. Links JSJ 325: Practical functional programming in JavaScript and languages like Elm with Jeremy Fairbank Jeremy’s GitHub Jeremy's LinkedIn Jeremy’s Blog Professional JavaScript for Web Developers by Nicholas C. Zakas Professional JavaScript for Web Developers by Matt Frisbie https://knockoutjs.com/ https://marionettejs.com/ https://www.coursera.org/ https://www.coursera.org/learn/programming-languages elm-lang.org https://www.facebook.com/javascriptjabber https://twitter.com/JSJabber https://www.facebook.com/DevChattv Picks Jeremy Fairbank: Programming Elm The Umbrella Academy Beyond Burger Charles Max Wood: Orphan Black https://devchat.tv/ https://www.netlify.com/ https://www.11ty.io/ https://github.com/cmaxw/devchat-eleventy JavaScript Jabber - Devchat.tv

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Joined By Special Guest: Jeremy Fairbank Episode Summary Jeremy is a Software Developer at Test Double and the author of Programming Elm book. Even though Jeremy majored in Chemistry in college, he was always interested in programming since middle school. After he graduated from college he went to work as a web developer at Plastic Industries and relied on blog posts and other online resources to teach himself how to code. Gradually as the company’s needs changed, Jeremy transitioned into an application developer. He taught himself JavaScript using the book Professional JavaScript for Web Developers . He then attented a Coursera classto learn on principles of functional programming and gained experience with many front end frameworks and libraries, including Elm, React, Redux, Backbone.js, and Marionette.js. Jeremy is based out of Hawaii and when he isn't coding, he spends his time playing his guitar and hiking and going to the beach with his family. Links JSJ 325: Practical functional programming in JavaScript and languages like Elm with Jeremy Fairbank Jeremy’s GitHub Jeremy's LinkedIn Jeremy’s Blog Professional JavaScript for Web Developers by Nicholas C. Zakas Professional JavaScript for Web Developers by Matt Frisbie https://knockoutjs.com/ https://marionettejs.com/ https://www.coursera.org/ https://www.coursera.org/learn/programming-languages elm-lang.org https://www.facebook.com/javascriptjabber https://twitter.com/JSJabber https://www.facebook.com/DevChattv Picks Jeremy Fairbank: Programming Elm The Umbrella Academy Beyond Burger Charles Max Wood: Orphan Black https://devchat.tv/ https://www.netlify.com/ https://www.11ty.io/ https://github.com/cmaxw/devchat-eleventy JavaScript Jabber - Devchat.tv

Healthy, hurt, or injured? Gamblers are often left guessing about injury reports provided by sports franchises. Matt Brown and Brett Collson talk with Virginia Zakas, head of operations at Inside Injuries, about injury transparency and why leagues should be holding teams accountable. Plus, a recap of the Preakness Stakes and PGA Championship, and thoughts on the new marketing code released by the American Gaming Association (https://www.americangaming.org/wp-content/uploads/2019/05/Responsible-Marketing-Code-for-Sports-Wagering.pdf)

Gregg Sussman and Frank Stampfl open the show tipping their cap to video producer Martino Puccio, who was in the room, and recording, the moment Mariano Rivera found out he was unanimously elected to the Baseball Hall of Fame. Virginia Zakas joins the show to talk about about the latest injuries around the NBA. The guys stick with the NBA, and look at the top fantasy players to pick off the waiver wires this week, as well as the insane scoring run by James Harden.  #FNTSY #MLB #NBA #MarianoRivera #MartinoPuccio #JamesHarden #InsideInjuries Learn more about your ad-choices at https://news.iheart.com/podcast-advertisers

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

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

Gregg Sussman and Frank Stampfl open the show getting you ready for tonight's Jets-Browns game, with Frank excited to watch the game with former BFF, Mike Florio. Looking back at the Steelers, Gregg talks about Antonio Brown getting punished for missing practice, and how Gregg may be involved in a trade involving Antonio Brown, Melvin Gordon, Alvin Kamara and Julio Jones. Virginia Zakas of Inside Injuries joins the show to update the guys on injuries to Marlon Mack, Dalvin Cook, and Jarvis Landry. #FNTSY #NFL #Week3 #InsideInjuries #Jets #Browns #JarvisLandry #JulioJones #Bucs #RonaldJones #PeytonBarber #MelvinGordon Learn more about your ad-choices at https://news.iheart.com/podcast-advertisers

Gregg Sussman and Frank Stampfl reminisce about their old BFF, Mike Florio, and tell stories of how he would take their computers and send direct messages to random people. The guys look at some running back rankings for Week 2, ad both love the rise of Matt Breida. Virginia Zakas of Inside Injuries joins the show to give updates on Aaron Rodgers, Leonard Fournette and Rex Burkhead, just to name a few. #FNTSY #NFL #fantasyfootball #Week2 #MattBreida #LeonardFournette #InsideInjuries #SammyWatkins Learn more about your ad-choices at https://news.iheart.com/podcast-advertisers

Gregg Sussman and Frank Stampfl look at the best 3rd wide receivers to pick as you get lower in drafts. Looking at the Broncos, Gregg and Frank discuss where to take the big duo of Demaryius Thomas and Emmanuel Sanders, with Frank saying Thomas is still a safe bet, but Sanders is the "slightly" better fantasy value. The guys chat with Virginia Zakas of Inside Injuries, as they look at some big injuries around NFL training camps, including a big hit to the Cowboys offensive line.  #FNTSY #NFL #fantasyfootball #Broncos #EmmanuelSanders #DemaryiusThomas #Cowboys #Zeke #DelanieWalker #TYHilton #LeSeanMcCoy #AJMcCarron #Bills Learn more about your ad-choices at https://news.iheart.com/podcast-advertisers

When I started to edit the conversation, I had with peter back in June of this year, I realized there was a chunk of information about his brother Spiros Zakas who founded the design firm Zakaspace, that didn’t quite fit into the 30 minutes or so I had allotted for the podcast. Now I realize the first rule of podcasting is that there are no rules, but be that as it may, I wanted to keep some sort of structure.Spiros was a very large influence in restaurant designs starting in the mid 70’s not only in Chicago with the work he did lettuce entertain you and others, but around the country as well. He had a sense of place and purpose in his restaurant designs that not only created a great experience for the guest, but also provided a practical approach to operations as well. Elements that all too often in a lot of restaurants I’ve seen and worked with don’t co-exist as well as they should. Too many designers today are more focused on form than function which may create a beautiful environment for the guest but presents inherent operating difficulties that get in the way of good service.Well anyway, I’m not sure I want to call Spiros a pioneer or a visionary, but he was a designer who listened to the needs of the operator and was able to provide beautiful and workable environments. A true rare commodity that his brother peter, Silvia Milic and now peter’s son P.J. are keeping alive in their firm, Z-Space design

Gregg Sussman and Frank Stampfl review the latest injury reports on Chris Thompson, Rishard Matthews, Donald Penn and more with Virginia Zakas of InsideInjuries.com. Then, they break down the latest changes to rules and scoring for FanDuel football games as well as their preferred players for FanDuel lineups. #FNTSY #FNTSYRadio #NFL #FantasyFootball #Injuries #ChrisThompson #RishardMatthews #DonaldPenn #FanDuel Learn more about your ad-choices at https://news.iheart.com/podcast-advertisers

021218 Zakas

Panel: Charles Max Wood Aimee Knight Corey House Joe Eames Special Guests:  In this episode, JavaScript Jabber speaks with Dirk Hohndel about Open Source Software. Dirk is the Chief Open Source Officer at VMWare and has been working with open source for over 20 years. Dirk duties as the Chief Open Source Officer is to engage with the open source community and help promote the development between the community, companies, and customers. Dirk provides historical facts about open sources to current processes. The discussion covers vision and technological advances with languages, security, and worries of using open source software, view/consumption and burnout on maintaining a project. This is a great episode to learn about more different avenues of Open Source. In particular, we dive pretty deep on: What does the Chief Open Source Officer do? What is really different and has stayed the same in open source? Technological advances Good engineering and looking ahead or forward 100 million lines of code running a car… This is in everything.. Production environments Security Bugs in the software and the security issues Scaling and paying attention Where should we be worried about open source Notation and data sets Write maintainable software How does VMWare think about open source? View and Consumption of open source The burnout of open source projects - how to resolve this abandonment To much work to maintain open source  - not a money issue Scaling the team workload not the money Contribution and giving back Companies who do and don’t welcome open source What to do to make a project open source? Adopting an API And much more! Links: @_drikhh VMWare Drikhh - everywhere! https://github.com/dirkhh Picks: Aimee De Contact  Dodow  Dirk Track This Critical Thinking Charles Nicholas Zakas - Books  Corey Fun Fun Function Show Joe Dice Forge Concept of empathy    

Panel: Charles Max Wood Aimee Knight Corey House Joe Eames Special Guests:  In this episode, JavaScript Jabber speaks with Dirk Hohndel about Open Source Software. Dirk is the Chief Open Source Officer at VMWare and has been working with open source for over 20 years. Dirk duties as the Chief Open Source Officer is to engage with the open source community and help promote the development between the community, companies, and customers. Dirk provides historical facts about open sources to current processes. The discussion covers vision and technological advances with languages, security, and worries of using open source software, view/consumption and burnout on maintaining a project. This is a great episode to learn about more different avenues of Open Source. In particular, we dive pretty deep on: What does the Chief Open Source Officer do? What is really different and has stayed the same in open source? Technological advances Good engineering and looking ahead or forward 100 million lines of code running a car… This is in everything.. Production environments Security Bugs in the software and the security issues Scaling and paying attention Where should we be worried about open source Notation and data sets Write maintainable software How does VMWare think about open source? View and Consumption of open source The burnout of open source projects - how to resolve this abandonment To much work to maintain open source  - not a money issue Scaling the team workload not the money Contribution and giving back Companies who do and don’t welcome open source What to do to make a project open source? Adopting an API And much more! Links: @_drikhh VMWare Drikhh - everywhere! https://github.com/dirkhh Picks: Aimee De Contact  Dodow  Dirk Track This Critical Thinking Charles Nicholas Zakas - Books  Corey Fun Fun Function Show Joe Dice Forge Concept of empathy    

Panel: Charles Max Wood Aimee Knight Corey House Joe Eames Special Guests:  In this episode, JavaScript Jabber speaks with Dirk Hohndel about Open Source Software. Dirk is the Chief Open Source Officer at VMWare and has been working with open source for over 20 years. Dirk duties as the Chief Open Source Officer is to engage with the open source community and help promote the development between the community, companies, and customers. Dirk provides historical facts about open sources to current processes. The discussion covers vision and technological advances with languages, security, and worries of using open source software, view/consumption and burnout on maintaining a project. This is a great episode to learn about more different avenues of Open Source. In particular, we dive pretty deep on: What does the Chief Open Source Officer do? What is really different and has stayed the same in open source? Technological advances Good engineering and looking ahead or forward 100 million lines of code running a car… This is in everything.. Production environments Security Bugs in the software and the security issues Scaling and paying attention Where should we be worried about open source Notation and data sets Write maintainable software How does VMWare think about open source? View and Consumption of open source The burnout of open source projects - how to resolve this abandonment To much work to maintain open source  - not a money issue Scaling the team workload not the money Contribution and giving back Companies who do and don’t welcome open source What to do to make a project open source? Adopting an API And much more! Links: @_drikhh VMWare Drikhh - everywhere! https://github.com/dirkhh Picks: Aimee De Contact  Dodow  Dirk Track This Critical Thinking Charles Nicholas Zakas - Books  Corey Fun Fun Function Show Joe Dice Forge Concept of empathy    

Panel:  Joe Eames Charles Max Wood Special Guest: Justin Schwartzenberger In the episode of Adventures in Angular the panel welcome Justin Schwartzenberger to talk about Angular Air. Justin is a podcaster, product manager, and educator at Narwhal Technologies. Justin talks about his experience working with customers and contributing to the Angular community. Justin discusses the content of his podcast, Angular Air, and how it helps the Angular community learn all about Angular. This is a great episode for learning about other podcast platforms that focus on all things Angular. In particular, we dive pretty deep on: •What do you do at Narwhal and with Angular Air? Angular Air podcast History Hosting and Topics on Angular Air video podcast Favorite episodes on Angular Air How to figure out what to discuss on the podcast Using the community to figure great topics Competition for listening time Things to learn - Angular Animations, GraphQL, etc. Influences Performances, Character, with the intros and hosting Difficulties and Challenges - Scheduling and finding guests Youtube videos recording and cueing up Dealing with episodes notes on Youtube Views on the Video platform vs. Audio platform What is the future of Angular Air podcast? Automation, Sponsorships, etc What is the present and future of Angular overall? Are people still doing Angular? •and much more! Links:  Angular Air  @angularair Narwhal Technologies (nrwl.io) @schwarty @jschwarty schwarty.com Picks: Charles The Way of Kings  Artimus Nicolas Zakas -Books Open Collectives Hyper Drive Hub Joe JavaScript Journey with Only Six Characters  5 year old MacBook Pro  Justin Reactive.how Mr. Robot Episode 8 Star Wars    

Panel:  Joe Eames Charles Max Wood Special Guest: Justin Schwartzenberger In the episode of Adventures in Angular the panel welcome Justin Schwartzenberger to talk about Angular Air. Justin is a podcaster, product manager, and educator at Narwhal Technologies. Justin talks about his experience working with customers and contributing to the Angular community. Justin discusses the content of his podcast, Angular Air, and how it helps the Angular community learn all about Angular. This is a great episode for learning about other podcast platforms that focus on all things Angular. In particular, we dive pretty deep on: •What do you do at Narwhal and with Angular Air? Angular Air podcast History Hosting and Topics on Angular Air video podcast Favorite episodes on Angular Air How to figure out what to discuss on the podcast Using the community to figure great topics Competition for listening time Things to learn - Angular Animations, GraphQL, etc. Influences Performances, Character, with the intros and hosting Difficulties and Challenges - Scheduling and finding guests Youtube videos recording and cueing up Dealing with episodes notes on Youtube Views on the Video platform vs. Audio platform What is the future of Angular Air podcast? Automation, Sponsorships, etc What is the present and future of Angular overall? Are people still doing Angular? •and much more! Links:  Angular Air  @angularair Narwhal Technologies (nrwl.io) @schwarty @jschwarty schwarty.com Picks: Charles The Way of Kings  Artimus Nicolas Zakas -Books Open Collectives Hyper Drive Hub Joe JavaScript Journey with Only Six Characters  5 year old MacBook Pro  Justin Reactive.how Mr. Robot Episode 8 Star Wars    

Panel:  Joe Eames Charles Max Wood Special Guest: Justin Schwartzenberger In the episode of Adventures in Angular the panel welcome Justin Schwartzenberger to talk about Angular Air. Justin is a podcaster, product manager, and educator at Narwhal Technologies. Justin talks about his experience working with customers and contributing to the Angular community. Justin discusses the content of his podcast, Angular Air, and how it helps the Angular community learn all about Angular. This is a great episode for learning about other podcast platforms that focus on all things Angular. In particular, we dive pretty deep on: •What do you do at Narwhal and with Angular Air? Angular Air podcast History Hosting and Topics on Angular Air video podcast Favorite episodes on Angular Air How to figure out what to discuss on the podcast Using the community to figure great topics Competition for listening time Things to learn - Angular Animations, GraphQL, etc. Influences Performances, Character, with the intros and hosting Difficulties and Challenges - Scheduling and finding guests Youtube videos recording and cueing up Dealing with episodes notes on Youtube Views on the Video platform vs. Audio platform What is the future of Angular Air podcast? Automation, Sponsorships, etc What is the present and future of Angular overall? Are people still doing Angular? •and much more! Links:  Angular Air  @angularair Narwhal Technologies (nrwl.io) @schwarty @jschwarty schwarty.com Picks: Charles The Way of Kings  Artimus Nicolas Zakas -Books Open Collectives Hyper Drive Hub Joe JavaScript Journey with Only Six Characters  5 year old MacBook Pro  Justin Reactive.how Mr. Robot Episode 8 Star Wars    

Descripcion del programa José Manuel es ingeniero de software, trabaja como desarrollador web en Estocolmo para Spotify. Especializado en web performance optimization, SEO y accesibilidad. Con él nos adentraremos en el mundo de las Progressive Web Apps, y veremos como gracias al nuevo Catálogo de Apis podemos realizar acciones tales como notificaciones push, almacenamiento local y ejecución offline entre muchas otras. ¡Esperamos que os guste el episodio y como siempre nos vemos al final! ¿Queréis participar? ¿Queréis participar y ayudarnos a decidir que grabar en WeCodeSign y proponer invitad@s? Aquí podéis participar en WeCodeSign. Recomendaciones Preguntas rápidas: José Manuel Quién me ha inspirado: Alberto Quién me ha inspirado: Davide Mendolia Quién me ha inspirado: Felipe Ribeiro Quién me ha inspirado: Steve Souders Quién me ha inspirado: Nicholas C. Zakas Quién me ha inspirado: Addy Osmani Quién me ha inspirado: Dan Abramov Quién me ha inspirado: Stoyan Stefanov Recomiéndanos un recurso: Frontend Focus Recomiéndanos un recurso: JavaScript Weekly Recomiéndanos un recurso: Chrome and Web at Google I/O 2017 Recomiéndanos un recurso: JS Conf Recomiéndanos un recurso: CSS-Tricks Recomiéndanos un recurso: Smashing Magazine Recomiéndanos un recurso: High Performance Browser Networking Recomiéndanos a un invitado o invitada: Jaume Sanchez Elias ¿Qué tema te gustaría que tratásemos?: Web Performance Contacta con: José Manuel Twitter de José Manuel Web de José Manuel Links del programa Hilo sobre cómo aparecieron las PWA, por Alex Russell Progressive Web Apps: Great Experiences Everywhere (Google I/O '17) Production Progressive Web Apps With JavaScript Frameworks (Google I/O '17) PWA Directory Progressive Web Apps La guía sin conexión by Jake Archibald The Service Worker Cookbook Service Worker Tools Service Worker Pre Cache Tu primera Progressive Web App by Pete LaPage Building Progressive Web Apps A big list of progressive web app tips and tricks The State of Progressive Web Apps Production Progressive Web Apps with JavaScript Frameworks Qué son las Aplicaciones Web Progresivas o "Progressive Web Apps" Progressive web apps PWA: Para Webs Asombrosas Recomendaciones de Ignacio Progressive Web App questions Progressive Web App Checklist The PWA Resource list Lighthouse Patrocinadores Fictizia.com Contacta con Ignacio Web de WeCodeSign Twitter de WeCodeSign eMail de WeCodeSign Web de Ignacio Villanueva Twitter de Ignacio Villanueva

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,

022213 Zakas

011712 Zakas

Mit dem seltenen Überraschungsgast Peter starten Rodney und Hans in eine neue Revision voller Spiel, Spaß und Abenteuer! [00:00:10] News MySQL 5.6.6 ist da Mit memcached an Bord! Schaunotizen [00:00:40] Neue Syntax in ECMAScript 6 Die nächste Version von JavaScript wird allerlei neue Syntax einführen, wovon Nicholas C. Zakas ein großer Teil ganz und gar […]

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/).