Software tool which flags suspicious and non-portable constructs in source code
POPULARITY
4 episodes with linting
4 episodes with linting
2 episodes with linting
2 episodes with linting
4 episodes with linting
2 episodes with linting
2 episodes with linting
2 episodes with linting
2 episodes with linting
Josh Goldberg joins Amy and Brad to unpack the recent ESLint V9 release and its impact on the TypeScript ecosystem. From explaining the nuances of flat config migration to debating the proper separation between Prettier and ESLint, Josh offers practical advice for improving developer workflows. The conversation covers Josh's journey as a full-time open source maintainer, the Open Source Pledge initiative, and best practices for implementing linting in CI/CD pipelines. Plus, Josh shares behind-the-scenes details from the inaugural SquiggleConf event.Chapter Marks00:00 - Intro00:48 - Welcome Josh Goldberg01:06 - Working in open source and getting paid03:10 - The Open Source Pledge04:49 - ESLint V9 and flat config changes07:25 - Migration challenges with flat config09:52 - Understanding ESLint config format11:50 - How most people use ESLint16:20 - Prettier vs ESLint responsibilities18:47 - Conflict between Prettier and ESLint21:26 - TypeScript's role in ESLint25:01 - TypeScript ESLint packages explained27:43 - Linters for other languages29:31 - ESLint in CI/CD pipelines32:03 - Auto-fixing in different environments37:14 - AI's role in linting and formatting41:45 - SquiggleConf discussion44:15 - Conference tooling and Q&A system46:33 - Future SquiggleConf plans47:13 - Picks and PlugsBrad GarropyPick: Philips Hue smart lighting system - Set up Christmas lights with Hue smart outlets for easy control via phone or voice commandsPlug: Brad's BlueSky account - @bradgarropy.comJosh GoldbergPick: BlueSky social network - Appreciates how it feels like early Twitter without spam bots and complicated server setupsPlug: SquiggleConf - Web development tooling conference returning in September 2025Amy DuttonPick: The Inheritance Games (book) - Describes it as an easy-to-read young adult fiction with puzzles, similar to Knives OutPlug: Amy's BlueSky account - @selfteachmeLinksMentioned in the EpisodeTypeScript ESLintESLint v9 migration docsESLint Config InspectorSentry Grave $750k to Open Source MaintainersOpen Source Pledge initiativeSquiggle Conf websitePrisma PulsePhilips Hue smart lightingThe Inheritance Games (book mentioned by Amy)Social Media AccountsBrad's BlueSky account: @bradgarropy.comAmy's BlueSky account: @selfteachmeJosh Goldberg's BlueSky Account: @joshuakgoldberg.comRelated ResourcesESLint Stylistic projectESLint Config PrettierESLint Plugin Prettier"Create TypeScript Apps" project (Josh's tooling package)Awesome ESLint repo (collection of ESLint plugins)Manual to Magical: AI in Developer Tooling: Tobbe's talk on using AI to write code modsNicholas Zakas discussing the ESLint config system on Syntax podcastTools MentionedHuskyLint-stagedCursorBiome and OXLint (Rust-based linters)GitHub Actions
Scott and Wes dive into the State of Frontend 2024 Survey, breaking down the latest trends, tools, and frameworks shaping the developer ecosystem. Tune in as they react to hot takes on frameworks, state management, hosting, and what's next for frontend devs! Show Notes 00:00 Welcome to Syntax! 00:53 Brought to you by Sentry.io. 01:15 About the survey. Follow along! State of Frontend Survey 02:10 Frameworks. 06:15 Rendering frameworks. 07:35 State management. 09:14 Other libraries. Just: Dependency-free Utilities. 13:34 Data. Syntax Episode 453. Syntax Episode 833. 16:39 Hosting. AWS Amplify. 19:51 Continuous Integration. 21:30 Micro-frontends. 23:25 Package Managers. pnpm Link Workspace Packages. Corepack. 28:35 JS Runtimes. 29:47 Typescript. 33:13 Browser Technologies. 35:05 What is app property? 38:20 Progressive Web Apps. 40:11 Styling tools. 43:17 Testing. 45:39 Code editors. 49:02 Build tools. 49:17 Linting tools. 50:26 Operating systems. 51:17 The future trends. 54:14 Sick Picks + Shameless Plugs. Sick Picks Scott: Candle Warmer. Wes: Flighty iOS App. Shameless Plugs Scott: Syntax on Bluesky Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads
HTML All The Things - Web Development, Web Design, Small Business
Code quality matters! When developers write better, cleaner, and safer code - their deliverables improve significantly. When code is safer, there are less problems with crashes and unintended errors. When code is cleaner, team members find it easier to read, peer review, and add on to down the line. Improving the quality of your code is easier said than done, however, as it takes more than just "getting good" at coding. In this episode, Matt and Mike discussed the importance of and how to improve your code quality by keeping coding styles consistent with your team, refactoring, writing good tests, using prettier formatting, and linting. Show Notes: https://www.htmlallthethings.com/podcasts/why-code-quality-matters-testing-linting-refactoring Thanks to Wix Studio for sponsoring this episode! Check out Wix Studio, the web platform tailored to designers, developers, and marketers via this link: https://www.wix.com/studio
Show DescriptionWe've got follow up on Cloudflare and Cara from last episode, a question about setting up Prettier and auto linting, a cool tool from a listener on comparing colors, a question about using tooling like Craft or more user friendly apps like Webflow when working with clients, and our takes on accessibility overlays. Listen on Website →Links Cloud Application Hosting for Developers | Render Prettier · Opinionated Code Formatter Biome, toolchain of the web Vetur Compare colors Craft CMS Webflow: Create a custom website | Visual website builder Accessibility Overlay Decision Sponsors
Linting is the process of checking source code for programmatic as well as stylistic errors. Ruff is a highly popular Python linter written in Rust. It was developed by Charlie Marsh, who also founded Astral, which is focused on next-generation Python tooling. Charlie joins the podcast to talk about open source development, Ruff, the UV The post Ruff and Next-Generation Python Tooling with Charlie Marsh appeared first on Software Engineering Daily.
Linting is the process of checking source code for programmatic as well as stylistic errors. Ruff is a highly popular Python linter written in Rust. It was developed by Charlie Marsh, who also founded Astral, which is focused on next-generation Python tooling. Charlie joins the podcast to talk about open source development, Ruff, the UV The post Ruff and Next-Generation Python Tooling with Charlie Marsh appeared first on Software Engineering Daily.
Vi forklarer sånn cirkus hva påskekrimmen vår handler om i år. En lytter lurer på hvordan påskekrimmen er laga, og Jørgen forklarer sånn cirkus.Jørgen er veldig begeistra for mobilspillet McPixel 3.Ole Petter har fått igjen på skatten og lurer på hva han skal kjøpe seg.Vi ringer Vemund M. Santi og hører hvorfor han mener ChatGPT har gjort norske studenter dårligere på Python-syntaks.Million Lint, er det noe som heter, men hvorfor heter det egentlig linting, og ikke delinting? Det snakker vi mye om.Musk har opensourca Grok, og vi gjør et halvhjerta forsøk på å finne ut hvorfor det heter Grok.Devin er verdens første AI-utvikler, men hvorfor heter det Devin? Det snakker vi også mye om. kode24-klubben lager AI-barnebøker.Arild har skrevet en vits vi forsøker å gjøre litt bedre, som vanlig. Hosted on Acast. See acast.com/privacy for more information.
في الحلقة دي بنتكلم مشكلة رئيسية بتواجهنا اثناء كتابة الكود سواء لوحدك او مع فريق، ازاي كلنا نكتب كود شبه بعضه في الشكل والجودة بالرغم من اختلاف خبرات وتجارب افراد الفريق. ودا يجيبنا للـ Formatting و الـ Linting ويفرقو ايه عن بعض وازاي ممكن تستعملهم في شغلك في شركتك علي اكثر من مستوي بحيث تضمن مفيش كود غير متناسق يندمج مع باقي الكود. روابط مفيدة: ESlint JSLint JS Standard Prettier TypeScript ESLint Husky lint-staged
Python at Meta is huge. Not only does it famously power Instagram's backend, but it underpins our configuration systems, much of our AI work and many services. Amethyst joins Pascal for this episode of the Meta Tech Podcast to talk about how the Python Foundation Team works to improve the developer experience of everyone working with Python at Meta and Fixit 2, the freshly open-sourced linter framework built on top of libcst. Got feedback? Send it to us on Threads (https://threads.net/@metatechpod), Twitter (https://twitter.com/metatechpod), Instagram (https://instagram.com/metatechpod) and don't forget to follow our host @passy (https://twitter.com/passy, https://mastodon.social/@passy, and https://threads.net/@passy_). Fancy working with us? Check out https://www.metacareers.com/. Links Fixit 2 announcement post: https://engineering.fb.com/2023/08/07/developer-tools/fixit-2-linter-meta/ Fixit: https://fixit.readthedocs.io µfmt: https://ufmt.omnilib.dev µsort: https://usort.readthedocs.io LibCST: https://libcst.readthedocs.io 5 Things You Didn't Know About Buck2: https://engineering.fb.com/2023/10/23/developer-tools/5-things-you-didnt-know-about-buck2/ Scheduling Jupyter Notebooks at Meta: https://engineering.fb.com/2023/08/29/security/scheduling-jupyter-notebooks-meta/ Timestamps Intro 0:06 Intro Amethyst 1:57 Production vs Software Engineering 3:41 PE for language teams 5:40 Python at Meta 6:58 Python3 migration 10:15 Projects on the Python Foundation Team 16:30 libcst and codemods 21:55 What Python looks like at Meta 25:53 Meta's involvement in the Python community 30:30 The importance of lints at Meta 35:13 Why another linter? 39:11 Favourite lint 46:26 Outro 48:17 Bloopers 48:54
In this episode, our guest Josh Nesbitt, CTO of Glean a Leeds EdTech startup, shares his insights on securing the data of vulnerable people, the importance of accessibility and compliance in production-ready products, and the challenges of achieving usability, functionality, and security in concert. Join us as we debunk common misconceptions around agile and explore how security teams can be more creative in their approach. We'll talk about how to use tooling and engagement to get engineers and security teams on the same page. Links to everything Josh discussed in this episode can be found in the show notes and if you liked the show, please do leave us a review and share on LinkedIin or in your teams, it really helps us spread the word and get high-quality guests, like Josh, on future episodes. We hope you enjoyed this episode - See you next time, keep secure, and don't forget to ask yourself, ‘Am I a compromising position here?' SHOW NOTESGreat blogs on how Shopify do engineering: https://shopify.engineering/The ‘curse of knowledge' Jeff mentioned came from our discussions with Christian Hunt - Check out his episodes hereGithub ActionsNice guide on how to get started with Linting (a tool the analyses source code to flag programming errors and bugs)Rubocop - A Ruby static code analyser About JoshJosh is a software engineer and technical leader based in the UK. He's been working on the web for the last 17 years, and during that time, he's worked with a wide range of clients, from indie start-ups to some of the largest organisations in the world. His work spans from hands-on projects building large platforms to leading some of the best-performing teams in our industry.Alongside his work as a consultant, he also runs an internationally recognised conference called All Day Hey!, which brings people from all over the world to the heart of Leeds to learn, inspire and share stories.Links Related to Josh Nesbitt:Josh on Linkedin: linkedin.com/in/josh-nesbittJosh at Hey! Including his amazing conference ALL DAY HEY!: https://heypresents.com/Josh's podcast: https://heypresents.com/podcast
We're talking how we stay online - or not - on vacation, is create-guten-block the future for us WP developers? Can we get a state of the web component address from the President of web components? Have we seen the last new browser engine? And deciding whether to add features or remove them from your app.
In dieser Episode sprechen wir über das Thema Linting und stellen die Werkzeuge eslint und stylelint vor, die Entwicklern helfen, Code-Qualitätsprobleme im Frontend-Bereich zu vermeiden. Zu Beginn erklären wir, was Linting ist und wie es bei der Entwicklung von Webanwendungen eingesetzt wird. Wir diskutieren auch die Vorteile von Linting, wie z.B. die Verbesserung der Code-Lesbarkeit, Fehlervermeidung und die Einhaltung von Code-Standards. Anschließend stellen wir die beiden Linting-Tools eslint und stylelint vor und erklären, wie diese Werkzeuge funktionieren. Des Weiteren diskutieren wir verschiedene Konfigurationsmöglichkeiten für eslint und stylelint und zeigen auf, wie man diese Tools in den Entwicklungsprozess integrieren kann. Zusammenfassend bietet diese Episode eine umfassende Einführung in das Thema Linting und die Verwendung von eslint und stylelint als wichtige Werkzeuge für die Verbesserung der Code-Qualität in Frontend-Projekten.
Linting and static code analysis in general are important tools in software engineering. Making sure the code builds and works is all very well. But a consistent coding style minimises maintenance efforts and future development. In this episode I'll introduce several tools that can make your code analysis easier: pylint https://www.pylint.org flake8 https://flake8.pycqa.org/en/latest/index.html black https://black.readthedocs.io/en/stable/index.html pre-commit https://pre-commit.com pre-commit hooks https://pre-commit.com/hooks.htmlOther links you may find interesting and have been mentioned in the episodePEP8 https://peps.python.org/pep-0008/ Google Python Style Guide https://google.github.io/styleguide/pyguide.html YAML file format https://yaml.org Stephen C. Johnson's paper on lint https://web.archive.org/web/20220123141016/https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.56.1841&rep=rep1&type=pdf Definition of spaghetti code (yes there is one) https://en.wikipedia.org/wiki/Spaghetti_code Not mentioned in the episode, but you might be interested in this linter written in Rust https://github.com/charliermarsh/ruff Byte-sized RSE is presented in collaboration with the UNIVERSE-HPC project.https://www.imperial.ac.uk/computational-methods/rse/events/byte-sized-rse/ByteSized RSE link to Imperial CollegeSupport the Show.Thank you for listening and your ongoing support. It means the world to us! Support the show on Patreon https://www.patreon.com/codeforthought Get in touch: Email mailto:code4thought@proton.me UK RSE Slack (ukrse.slack.com): @code4thought or @piddie US RSE Slack (usrse.slack.com): @Peter Schmidt Mastadon: https://fosstodon.org/@code4thought or @code4thought@fosstodon.org LinkedIn: https://www.linkedin.com/in/pweschmidt/ (personal Profile)LinkedIn: https://www.linkedin.com/company/codeforthought/ (Code for Thought Profile) This podcast is licensed under the Creative Commons Licence: https://creativecommons.org/licenses/by-sa/4.0/
Brad and Amy discuss the great features of Remix and some of their favorite ways to utilize it.SponsorsHashnodeCreating a developer blog is crucial in creating an online presence for yourself. It's proof of work for your future employer. Hashnode makes it easy to start a blog in seconds on your custom domain for free. It's fully optimized for developers and supports writing in Markdown, rich embeds, publishing from GitHub repository, syntax highlighting, and edge caching with Next.js blogs deployed on Vercel. On top of these, Hashnode is free from paywall, ads, and sign-up prompts.Hashnode is a community of developers, engineers, and people in tech. Your article gets instant readership from their growing community.Check out Hashnode, and join the community.Daily.devdaily.dev is where developers grow together. It provides a community-based feed of the best developer news, helping you stay up-to-date. daily.dev aggregates hundreds of sources every few minutes and creates a personal feed for you according to your interests, whether it's web dev, data science, or Elixir. Anything you might be interested in, it has the content for you.Check out daily.devShow Notes00:00 Introduction01:12 Getting into Remix05:54 Remix History08:23 Sponsor: Hashnode13:25 Nesting Routing19:12 How Links Work24:15 Server Side Generation25:01 File Location28:15 Input28:59 Writing Code39:53 Form States40:54 Boundary Components45:26 Remix Frustration54:04 Help from Tailwind57:46 Authentication00:00 Database Solutions00:00 Modeling00:00 Sponsor: Daily.dev00:00 Testing00:00 Linting and Formatting00:00 Deploying00:00 Projects for Remix00:00 Grab Bag Questions00:00 Picks and Plugs
In this episode, Amy and James explain Github Actions: what they are, how they work, use cases, and more. Amy also shares some of her personal experience in setting up Github Actions in a recent project.SponsorsZEALZEAL is a computer software agency that delivers “the world's most zealous” and custom solutions. The company plans and develops web and mobile applications that consistently help clients draw in customers, foster engagement, scale technologies, and ensure delivery.ZEAL believes that a business is “only as strong as” its team and cares about culture, values, a transparent process, leveling up, giving back, and providing excellent equipment. The company has staffers distributed throughout the United States, and as it continues to grow, ZEAL looks for collaborative, object-oriented, and organized individuals to apply for open roles.For more information visit codingzeal.comVercelVercel combines the best developer experience with an obsessive focus on end-user performance. Their platform enables frontend teams to do their best work. It is the best place to deploy any frontend app. Start by deploying with zero configuration to their global edge network. Scale dynamically to millions of pages without breaking a sweat.For more information, visit Vercel.comDatoCMSDatoCMS is a complete and performant headless CMS built to offer the best developer experience and user-friendliness in the market. It features a rich, CDN-powered GraphQL API (with realtime updates!), a super-flexible way to handle dynamic layouts and structured content, and best-in-class image/video support, with progressive/LQIP image loading out-of-the-box."For more information, visit datocms.comShow Notes00:00:00 - Intro00:05:27 - What are GitHub actions?00:12:59 - Sponsor: DatoCMS00:13:53 - Linting or Formatting00:24:34 - Sponsor: Vercel00:30:03 - Sponsor: Zeal00:30:56 - Other Use Cases00:37:12 - Grab Bag Questions00:44:00 - Picks and PlugsLinksLearn Github Actions - https://docs.github.com/en/actions/learn-github-actionsQuickstart for Github Actions - https://docs.github.com/en/actions/quickstartLevel Up Tutorials Course on Github Actions from Brian Douglass - https://leveluptutorials.com/tutorials/code-automation-with-github/introduction(James Pick) Rode Wireless Go - https://www.amazon.com/Rode-Microphones-Wireless-Channel-Microphone/dp/B08XFQ6KP9(James Plug) YouTube Channel - https://www.youtube.com/c/jamesqquick(Amy Pick) ELOH IPhone Game - https://apps.apple.com/us/app/eloh/id1406382064(Amy Plug) Learn Build Teach Discord - https://learnbuildteach.com/
Today on the show, Charles and Subrat interview Miroslav Jonas to discuss various approaches related to monorepos, linting and CI. Enjoy this broad conversation as the panel shares their industry insights on these various topics and strategies you can start to implement today. In this episode… What are monorepos? Migrating and linting engines Nx and monorepos Utilizing plug ins Integration libraries and linting Benefits of Nx Front end vs back end communications Sponsors Top End Devs Raygun | Click here to get started on your free 14-day trial Coaching | Top End Devs Links Imgur Taming Code Organization with Module Boundaries in Nx | by Miroslav Jonaš | Nrwl Smart, Fast and Extensible Build System Github: meeroslav Twitter: @meeroslav Picks Charles- Quiddler Charles - Top End Devs Conferences Charles- Watch Dan Brown's The Lost Symbol Streaming (2021-) | Peacock Miro- Watch The Sandman | Netflix Official Site Miro- Nx Conf 2022 - October 17th, 2022 Subrat- The Pragmatic Programmer: From Journeyman to Master
Today on the show, Charles and Subrat interview Miroslav Jonas to discuss various approaches related to monorepos, linting and CI. Enjoy this broad conversation as the panel shares their industry insights on these various topics and strategies you can start to implement today. In this episode… What are monorepos? Migrating and linting engines Nx and monorepos Utilizing plug ins Integration libraries and linting Benefits of Nx Front end vs back end communications Sponsors Top End Devs Raygun | Click here to get started on your free 14-day trial Coaching | Top End Devs Links Imgur Taming Code Organization with Module Boundaries in Nx | by Miroslav Jonaš | Nrwl Smart, Fast and Extensible Build System Github: meeroslav Twitter: @meeroslav Picks Charles- Quiddler Charles - Top End Devs Conferences Charles- Watch Dan Brown's The Lost Symbol Streaming (2021-) | Peacock Miro- Watch The Sandman | Netflix Official Site Miro- Nx Conf 2022 - October 17th, 2022 Subrat- The Pragmatic Programmer: From Journeyman to Master
Questions? Comments? Find out more on our site podcast.unrulysoftware.com (https://podcast.unrulysoftware.com). You can join our discord (https://discord.gg/NGP2nWtFJb) to chat about tech anytime directly with the hosts.
Hello and welcome to CHAOSScast Community podcast, where we share use cases and experiences with measuring open source community health. Elevating conversations about metrics, analytics, and software from the Community Health Analytics Open Source Software, or short CHAOSS Project, to wherever you like to listen. Today, our special guest is Matt Van Itallie, who's the Founder and CEO of Sema, a software company focused on code quality. Today, we find out about Sema's tools, one being an analytics tool to understand open source, the other one helps developers build a portfolio of their work, and we learn how these tools relate to the work CHAOSS is doing. Also, Matt goes in depth about “code is a craft,” using Sonar for Linting, and ScanCode, and some things he would like to make better in the future. Download this episode now to find out much more, and don't forget to subscribe for free to this podcast on your favorite podcast app and share this podcast with your friends and colleagues! [00:01:42] Matt tells us his background and what brought him to CHAOSS. [00:03:17] We hear Matt's thoughts on the various paradoxes and complexities when evaluating code quality in open source, Sean asks Matt if anyone has cataloged the available Linters, and we hear about an open source project called ScanCode. [00:07:21] Sean brings up the language agnostic code quality analysis tool, and Matt explains how it works, what the benefits are, and some constraints that he's discovered in his work. [00:09:54] Georg wonders how detailed Matt gets looking at the process analysis. [00:12:37] Matt talks about explaining quality measurement to executives and non-technical executives. [00:15:19] Since security is always a concern, Sean tells us about a challenge they have in the Risk working group at CHAOSS with identifying various declared recognized risks, and Matt explains how this relates to the work he's doing. [00:21:10] Georg wonders if there's anything Matt wants to make better in the future and if the CHAOSS Community can help him with it. He explains an automated tool to understand the health of the guild. [00:26:40] Matt talks about a tool from Sema that makes it easier and faster to write code reviews and using ScanCode. [00:29:33] Find out where you can follow Matt online. Quote: [00:19:29] “Code is a craft means that creators matter a ton because there's so much institutional knowledge in their heads about how things fit together and the meaning of it. Crafts people create meaning that is incredibly hard to transfer.” Value Adds (Picks) of the week: [00:30:29] Georg's pick is moving into a new house. [00:30:46] Matt's pick are two extraordinary open source community leaders, Kunal and Eddie. [00:31:30] Sean's picks are being back on his bicycle, TREK 520 with Schwalbe tires, and to thank Google, Red Hat, and VMware for all the support they've provided for CHAOSS Project. Panelists: Georg Link Sean Goggins Guest: Matt Van Itallie Sponsor: SustainOSS (https://sustainoss.org/) Links: CHAOSS (https://chaoss.community/) CHAOSS Project Twitter (https://twitter.com/chaossproj?lang=en) CHAOSScast Podcast (https://podcast.chaoss.community/) podcast@chaoss.community (mailto:podcast@chaoss.community) Ford Foundation (https://www.fordfoundation.org/) Georg Link Twitter (https://twitter.com/GeorgLink) Sean Goggins Twitter (https://twitter.com/sociallycompute) Matt Van Itallie Twitter (https://twitter.com/vanitallie_matt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Matt Van Itallie LinkedIn (https://www.linkedin.com/in/mvi?original_referer=https%3A%2F%2Fwww.google.com%2F) Sema (https://www.semasoftware.com/) Sonar (https://www.sonarsource.com/) ScanCode toolkit-GitHub (https://github.com/nexB/scancode-toolkit) Kunal Kushwaha Twitter (https://twitter.com/kunalstwt) Eddie Jaoude Twitter (https://twitter.com/eddiejaoude) TREK 520 (https://www.trekbikes.com/us/en_US/bikes/bikepacking-touring-bikes/520/520/p/24000/) Schwalbe tires (https://www.schwalbetires.com/) Special Guest: Matt Van Itallie.
When you are teaching someone web development skills, when is the right time to start teaching code quality and testing practices? Karl Stolley believes it's never too early. Let's hear how he incorporates code quality in his courses. Our discussion includes: starting people off with good dev practices and tools linting html and css validation visual regression testing using local dev servers, including https incorporating testing with git hooks testing to aid in css optimization and refactoring Backstop Nightwatch BrowserStack the tree legged stool of learning and progressing as a developer: testing, version control, and documentation Karl is also writing a book on WebRTC, so we jump into that a bit too. Special Guest: Karl Stolley.
Mit Frederik Braun (Github, Twitter), Firefox-Security-Großmeister und Workingdraft-Dauergast (bekannt aus den Revisionen 447 und 452) beleuchteten Schepp und Peter diverse Aspekte rund um ASTs und Security. Schaunotizen [00:01:02] Linting und AST Zu Beginn klären wir erst mal, was ein Abstract Syntax Tree überhaupt ist und wie wir ihn mit dem AST explorer erforschen können. Es […]
Unedited live recording on YouTube (Ep 146) Datree Kubeconform pre-commit https://github.com/yannh/kubeconform https://pre-commit.com/ Eyar's article about K8s schema validation Open an issue for questions on k8s schema kubectl --dry-run=client bug Datree's CLI tool to ensure K8s manifests and Helm charts follow best practices Check CRDs and schema with Datree ★ Support this podcast on Patreon ★
In this episode, My Development Machine Set-Up CompileSwift.live Working With Server-Sent Events Memory Leaks on M1 Macs How to Write a Good Commit Message WatchOS 8.1.1 fixes slow charging Let's Connect https://bio.link/peterw --- Send in a voice message: https://anchor.fm/compileswift/message
I'd like to learn more about paypal-scripts. What tasks did the package cover: linting, transpiling, CI, deploy, etc. Please share any advice you can about starting a similar toolkit. Tools without config Concerning Toolkits
Facebook has a unique recruitment model. Instead of being assigned to one team, you first end up in Bootcamp, where you learn how the company functions and our tools and frameworks work. Then you get to look for teams, work with them and decide which one to join. Because the team selection is decoupled from hiring, switching teams is easy. In this episode, we're talking to Sash who has been taking advantage of internal mobility by switching teams every year almost on the dot. Over the course of his career at Facebook, he has worked on iOS animations, Android hardware and most recently the Wrist-based human-computer interaction interface that is being developed by FRL Labs. Links: Inside Facebook Reality Labs: Wrist-based interaction for the next computing platform: https://tech.fb.com/inside-facebook-reality-labs-wrist-based-interaction-for-the-next-computing-platform/ Boz To The Future: https://www.facebook.com/boztothefuturepod Keyframes Animation Library: https://github.com/facebookarchive/Keyframes IFBM 30: Linting for Design Quality with Elle: https://pca.st/episode/1e22130d-88a5-4ea9-a968-692cac232a78 IFBM 31: Intentional Architecture with Yuan and Dustin: https://pca.st/episode/2199bc68-2287-41b7-aa45-ab52595e1c62 Richie's Plank Experience: https://www.oculus.com/experiences/quest/1642239225880682/ Timestamps: Intro 0:06 Joining FB 1:52 News Feed Delight 4:20 Switch to Hardware 13:25 Hackamonth 19:27 AOSP Engineering 22:07 Hardware Prototyping at FRL 24:50 Developing for VR and Favourite Experiences 30:35 Outro 36:52 Bloopers 37:44
For the third and final episode focusing on UI quality, Pascal is joined by Sara, Patrik and Aaron to discuss how design reviews happen at Facebook. Instead of looking at static screenshots alongside the code, reviews now include a dynamic representation of the view hierarchy that not only allows for inspection of properties but also directly highlights violations of Facebook's design standards for accessibility and usability. Learn how all of this grew out of a tool suite originally built for the web and much more in episode 32 of Inside Facebook Mobile. Got feedback? Send it to us on Twitter (https://twitter.com/insidefbmobile), Instagram (https://instagram.com/insidefbmobile) and don't forget to follow our host @passy (https://twitter.com/passy). Fancy working with us? Check out http://fb.com/careers. Links: Podcast: Boz to the Future - https://tech.fb.com/introducing-boz-to-the-future-a-new-podcast-series-from-facebook-reality-labs/ Facebook Open Source on YouTube - https://www.youtube.com/channel/UCCQY962PmHabTjaHv2wJzfQ IFBM 29: Design Systems with Sriram - https://pca.st/u8r4u6h6 IFBM 30: Linting for Design Quality with Elle - https://pca.st/q336vyxe Sapienz: https://engineering.fb.com/2018/05/02/developer-tools/sapienz-intelligent-automated-software-testing-at-scale/ Jest - https://jestjs.io/ Timestamps: Intro 0:05 News: Boz To The Future 0:43 News: FBOSS ELI5 on YouTube 1:26 Interview Teaser 1:50 Interview Greeting 2:48 Sara Intro 3:10 Aaron Intro 4:15 Patrik Intro 4:43 UI Quality Team Mission 5:39 Shift Left Initiative 6:40 History of Quality Linting 8:08 Linting on Mobile 9:29 UIQR 15:17 Designer Diff Review 18:17 E2E Testing with Jest 25:55 Sapienz 27:12 UI Quality Scoring 29:17 Outro 41:16 Blooper 41:57
In this Hasty Treat, Scott and Wes talk about Stylelint, what it is and why you should use it! Sanity - Sponsor Sanity.io is a real-time headless CMS with a fully customizable Content Studio built in React. Get a Sanity powered site up and running in minutes at sanity.io/create. Get an awesome supercharged free developer plan on sanity.io/syntax. Sentry - Sponsor If you want to know what's happening with your code, track errors and monitor performance with Sentry. Sentry's Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. Cut your time on error resolution from hours to minutes. It works with any language and integrates with dozens of other services. Syntax listeners new to Sentry can get two months for free by visiting Sentry.io and using the coupon code TASTYTREAT during sign up. Show Notes 03:15 - What is a linter anyway? Why do you want to lint your CSS? Does stylelint fix errors or just tell you errors? 04:42 - Getting setup .stylelintrc stylelint extension Sass High perf animations stylelint order Max nesting depth Declaration strict value { "extends": [ "stylelint-config-standard", "stylelint-config-sass-guidelines" ], "plugins": [ "stylelint-high-performance-animation", "stylelint-declaration-strict-value", "stylelint-order" ], "rules": { "selector-no-qualifying-type": [ true, { "ignore": [ "attribute" ] } ], "plugin/no-low-performance-animation-properties": [ true, { "ignoreProperties": [ "color", "background-color", "box-shadow" ] } ], "indentation": "tab", "order/order": [ "custom-properties", "declarations" ], "order/properties-alphabetical-order": null, "declaration-block-no-duplicate-custom-properties": true, "declaration-empty-line-before": null, "scale-unlimited/declaration-strict-value": [ [ "/color$/", "z-index", "font-size" ] ], "scss/dollar-variable-pattern": "^[a-z][a-zA-Z0-9]+$", "max-nesting-depth": 3, "selector-pseudo-class-no-unknown": null } } Links https://github.com/stylelint/awesome-stylelint JSLint JSHint ESLint VS Code Tweet us your tasty treats! Scott's Instagram LevelUpTutorials Instagram Wes' Instagram Wes' Twitter Wes' Facebook Scott's Twitter Make sure to include @SyntaxFM in your tweets
Even if you have been modeling processes and workflows for a long time, you're creating processes from a human perspective. It would help if you made sure that your customers understand what's happening and that your models represent the logical flow of how the system operates. Unfortunately, BPM engines do not always comprehend this. These engines interpret your models without guiding heuristics which can lead to performance issues. Moreover, as a modeling expert, you have more experience parsing a model. You're more fluent in the BPM language than the average business user, and a model that makes sense to you may leave them behind.
We are continuing our focus on UI Quality from last episode and are diving deep into design linters. Elle and her team work on Facebook-internal Figma plugins that provide guidance on aspects like colours and usability of user interfaces. In the interview, Elle and Pascal discuss how the plugin leverages Facebook's web architecture to roll out changes quickly and how a shared REST API allows for rules to be used in multiple contexts. Got feedback? Send it to us on Twitter (https://twitter.com/insidefbmobile), Instagram (https://instagram.com/insidefbmobile) and don’t forget to follow our host @passy (https://twitter.com/passy). Fancy working with us? Check out http://fb.com/careers. Links Docusaurus 2.0 Beta - https://docusaurus.io/blog/2021/05/12/announcing-docusaurus-two-beta F8 - https://developers.facebook.com/f8/ Rapid release at massive scale - https://engineering.fb.com/2017/08/31/web/rapid-release-at-massive-scale/ Figma API - https://www.figma.com/developers/api GraphQL - https://graphql.org/ Relay - https://relay.dev/ Timestamps Intro 0:06 News: Docusaurus 2 News: F8 1:59 Elle introduction 2:13 Shift Left Initiative 3:32 UI Layout Linters 6:03 Figma Plugins 14:20 Outro 27:26 Bloopers 28:23
Flake8 is a command-line tool for linting Python projects. By default, it includes lint checks provided Pyflakes, pycodestyle, and McCabe It's also a platform, and allows plugins to extend the checks. Flake8 will run third-party extensions if they are found and installed. But what does all of that mean? Anthony Sottile is a maintainer of flake8 and has kindly offered to explain it to us. Special Guest: Anthony Sottile.
After such a fun conversation last week, we bring Mike back in to discuss applying security at build time and what we can do with infrastructure as code through linting and early analysis. We break down the difference between Linting, Policy as Code, and SaaS and talk about how each of these might fit into your workloads. Plus! As a security practitioner, what you can do to move the ball forward in automated testing and security in your CI/CD pipelines. We got it back down to 30-ish minutes and hope you enjoy the listen. Join us for a conversation from GREP to Hashicorp Sentinel
I denne episoden prater vi løst og fast om Abstrakte Syntakstrær, og forsøker å ta et lite dypdykk ned i hva de er og hva man kan bruke de til.
We have a confession. We had a beautiful (ok, maybe just good) episode 8 lined up a few months ago all nicely recorded with our friend Luke again and it should have just been an easy one to release.But no. Real life stuff gets in the way, the world e...
In part 3 of our Tag 1 Team talks about documentation as code: linting for prose, we demonstrate the Vale linter in action. This open source linter for prose is highly customizable, making it possible for writers with little coding experience or developers with little writing experience to start testing their work. In this Tag1 Team Talk, Michael Meyers (Managing Editor at Tag1) and Lynette Miles (Principal Technical Writer at Tag1) talk about integrating Vale into your workflow on the command line, or as part of an IDE, show a few tests, and demonstrate how quickly you can make changes to your tests, enabling your writers and your developers to work from the same expectations.
eslint-plugin-react@typescript-eslint/eslint-plugineslint-plugin-prettiereslint-config-prettiereslint-plugin-jsx-a11yeslint-plugin-react-hookseslint-plugin-testing-libraryeslint-plugin-jest-domeslint-plugin-importeslint-plugin-react-reduxTools for an evolving Design System - use cases for custom linting rules.
Like developers, many technical writers have tool sets they use in the course of their work. These include IDEs, image editors, transcription software, version control, and so on. One well-known type of tool in the software world, but less so in the writing world is the linter. Software developers often consider their linters to be invaluable in catching or preventing errors, as well as enforcing defined stylistic guidelines before errors get out in front of the world.
PART 1 - WHAT IS IT, WHY USE IT, HOW DOES IT WORK? Documentation is a critical part of any customer-facing product or service. Without it, your customers need hand holding, your support staff struggles to help your users, and your company spends money on unhappy customers instead of creating new products. One of the biggest challenges is creating quality documentation. Treating your documentation as part of your product leads the entire production team towards thinking of users first. Treating your documentation as part of your code lowers the barriers for your development teams to contribute. In this talk, Michael Meyers (Managing Editor at Tag1) and Lynette Miles (Principal Technical Writer at Tag1) dig into what it means to treat your docs like code, and how it can help your teams’ workflows. We’ll also talk about linting - and why it can matter just as much for your writers as it does for your developers, and how a docs-as-code methodology can speed up contributions from everyone working on a product.
Sponsored by Datadog: pythonbytes.fm/datadog Michael #1: PSF / JetBrains Survey via Jose Nario Let’s talk results: 84% of people who use Python do so as their primary language [unchanged] Other languages: JavaScript (down), Bash (down), HTML (down), C++ (down) Web vs Data Science languages: More C++ / Java / R / C# on Data Science side More SQL / JavaScript / HTML Why do you mainly use Python? 58% work and personal What do you use Python for? Average answers was 3.9 Data analysis [59% / 59% — now vs. last year] Web Development [51% / 55%] ML [40% / 39%] DevOps [39% / 43%] What do you use Python for the most? Web [28% / 29%] Data analysis [18% / 17%] Machine Learning [13% / 11%] Python 3 vs Python 2: 90% Python 3, 10% Python 2 Widest disparity of versions (pro 3) is in data science. Web Frameworks: Flask [48%] Django [44%] Data Science NumPy 63% Pandas 55% Matplotlib 46% Testing pytest 49% unittest 30% none 34% Cloud AWS 55% Google 33% DigitalOcean 22% Heroku 20% Azure 19% How do you run code in the cloud (in the production environment) Containers 47% VMs 46% PAAS 25% Editors PyCharm 33% VS Code 24% Vim 9% tool use version control 90% write tests 80% code linting 80% use type hints 65% code coverage 52% Brian #2: Hypermodern Python Claudio Jolowicz, @cjolowicz An opinionated and fun tour of Python development practices. Chapter 1: Setup Setup a project with pyenv and Poetry, src layout, virtual environments, dependency management, click for CLI, using requests for a REST API. Chapter 2: Testing Unit testing with pytest, using coverage.py, nox for automation, pytest-mock. Plus refactoring, handling exceptions, fakes, end-to-end testing opinions. Chapter 3: Linting Flake8, Black, import-order, bugbear, bandit, Safety. Plus more on managing dependencies, and using pre-commit for git hooks. Chapter 4: Typing mypy and pytype, adding annotations, data validation with Desert & Marshmallow, Typeguard, flake8-annotations, adding checks to test suite Chapter 5: Documentation docstrings, linting docstrings, docstrings in nox sessions and test suites, darglint, xdoctest, Sphinx, reStructuredText, and autodoc Chapter 6: CI/CD CI with GithHub Actions, reporting coverage with Codecov, uploading to PyPI, Release Drafter for release documentation, single-sourcing the package version, using TestPyPI, docs on RTD The series is worth it even for just the artwork. Lots of fun tools to try, lots to learn. Michael #3: Open AI Jukebox via Dan Bader Listen to the songs under “Curated samples.” A neural net that generates music, including rudimentary singing, as raw audio in a variety of genres and artist styles. Code is available on github. Dataset: To train this model, we crawled the web to curate a new dataset of 1.2 million songs (600,000 of which are in English), paired with the corresponding lyrics and metadata from LyricWiki. The top-level transformer is trained on the task of predicting compressed audio tokens. We can provide additional information, such as the artist and genre for each song. Two advantages: first, it reduces the entropy of the audio prediction, so the model is able to achieve better quality in any particular style; second, at generation time, we are able to steer the model to generate in a style of our choosing. Brian #4: The Curious Case of Python's Context Manager Redowan Delowar, @rednafi A quick tour of context managers that goes deeper than most introducitons. Writing custom context managers with __init__, __enter__, __exit__. Using the decorator contextlib.contextmanager Then it gets even more fun Context managers as decorators Nesting contexts within one with statement. Combining context managers into new ones Examples Context managers for SQLAlchemy sessions Context managers for exception handling Persistent parameters across http requests Michael #5: nbstripout via Clément Robert In the latest episode, you praised NBDev for having a git hook that strips out notebook outputs. strip output from Jupyter and IPython notebooks Opens a notebook, strips its output, and writes the outputless version to the original file. Useful mainly as a git filter or pre-commit hook for users who don’t want to track output in VCS. This does mostly the same thing as the Clear All Output command in the notebook UI. Has a nice youtube tutorial right in the pypi listing Just do nbstripout --``install in a git repo! Brian #6: Write ups for The 2020 Python Language Summit Guido talked about this in episode 179 But these write-ups are excellent and really interesting. Should All Strings Become f-strings?, Eric V. Smith Replacing CPython’s Parser with a PEG-based parser, Pablo Galindo, Lysandros Nikolaou, Guido van Rossum A Formal Specification for the (C)Python Virtual Machine, Mark Shannon HPy: a Future-Proof Way of Extending Python?, Antonio Cuni CPython Documentation: The Next 5 Years, Carol Willing, Ned Batchelder Lightning talks (pre-selected) What do you need from pip, PyPI, and packaging?, Sumana Harihareswara A Retrospective on My "Multi-Core Python" Project, Eric Snow The Path Forward for Typing, Guido van Rossum Property-Based Testing for Python Builtins and the Standard Library, Zac Hatfield-Dodds Core Workflow Updates, Mariatta Wijaya CPython on Mobile Platforms, Russell Keith-Magee Wanted to bring this up because Python is a living language and it’s important to pay attention and get involved, or at least pay attention to where Python might be going. Also, another way to get involved is to become a member of the PSF board of directors What’s a PSF board of directors member do? video There are some open seats, Nominations are open until May 31 Extras: Michael: Updated search engine for better result ranking Windel Bouwman wrote a nice little script for speedscope https://github.com/windelbouwman/pyspeedscope (follow up from Austin profiler) Jokes: “Due to social distancing, I wonder how many projects are migrating to UDP and away from TLS to avoid all the handshakes?” - From Sviatoslav Sydorenko “A chef and a vagrant walk into a bar. Within a few seconds, it was identical to the last bar they went to.” - From Benjamin Jones, crediting @lufcraft Understanding both of these jokes is left as an exercise for the reader.
Parens * vim-sexp https://github.com/guns/vim-sexp/ (My preferred) * vim parinfer https://github.com/eraserhd/parinfer-rust (Also good) * paredit.vim https://github.com/vim-scripts/paredit.vim # REPL * fireplace https://github.com/tpope/vim-fireplace (My preferred) * cider-nrepl https://github.com/clojure-emacs/cider-nrepl * conjure https://github.com/Olical/conjure (alternative to fireplace) * animation: https://asciinema.org/a/267614 # Linting * ale https://github.com/dense-analysis/ale * syntastic https://github.com/vim-syntastic/syntastic * linting the vanilla way https://cljdoc.org/d/clj-kondo/clj-kondo/2019.10.11-alpha/doc/editor-integration#vanilla-way (based on https://gist.github.com/romainl/ce55ce6fdc1659c5fbc0f4224fd6ad29) * neomake https://github.com/neomake/neomake # Misc * async-clj-omni https://github.com/clojure-vim/async-clj-omni/ * vim jack-in https://github.com/clojure-vim/vim-jack-in * salve https://github.com/tpope/vim-salve * dispatch https://github.com/tpope/vim-dispatch/ * replant https://github.com/SevereOverfl0w/vim-replant # Git * fugitive https://github.com/tpope/vim-fugitive * gitgutter https://github.com/airblade/vim-gitgutter * vimcasts on fugitive http://vimcasts.org/blog/2011/05/the-fugitive-series/ # Refactoring * clj-refactor.nvim https://github.com/clojure-vim/clj-refactor.nvim # Community * clojure-vim https://github.com/clojure-vim/ * #vim on Clojurians https://app.slack.com/client/T03RZGPFR/C0DF8R51A
Jon and Ben review the changes introduced by the Rust 1.38 release. Get in touch with us if you’d like to be interviewed, propose a topic for an episode, or help out! Twitter: @rustaceanfm Discord: Rustacean Station Github: @rustacean-station Email: hello@rustacean-station.org Timestamps & referenced resources [@1:15] - Pipelined compilation [@3:25] - Linting some incorrect uses of mem::uninitialized Rustacean Station episode on Rust 1.36 with discussion on std::mem::MaybeUninit [@6:30] - #[deprecated] attribute on macros Rust reference: Diagnostic attributes [@11:30] - std::any::type_name Security advisory for the destabilization of std::error::Error::type_id in Rust 1.34.2 [@16:00] - slice::{concat, connect, join} now accepts &[T] in addition to &T [@18:10] - *const T and *mut T now implement std::marker::Unpin [@20:55] - New convenience methods for working with std::time::Duration [@22:25] - cargo fix --clippy [@23:40] - Diff-friendly format for Cargo.lock [@25:00] - Looking forward to Rust 1.39 futures v0.3 milestone tokio v0.2 milestone tower v0.1 milestone hyper v0.13 milestone Credits Intro Theme: Aerocity Audio Editing: Zoran Zaric Hosting Infrastructure: Jon Gjengset Show Notes: Ben Striegel Hosts: Jon Gjengset and Ben Striegel
Over the past two decades of working in tech, the use of Continuous Integration (or CI) has become a mainstream approach to product development. Randy and Don discuss the systems they used before (or lack thereof), what they use now, and why Continuous Integration meets the hype.
In what is sure to lead to significant community discussion, there's now a pitch for adding a style guide and formatter to Swift.
Welcome back to The Rabbit Hole Podcast. Today on the show we are addressing the topic of linting your code. Linting is the process of running a program (or linter) that will automatically analyze your code for potential errors and patterns that don't adhere to certain style guidelines.
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
Today we’ll be test talking with Kwo Ding all about his new Sonar WebDriver Plugin which is a static code analysis tool that helps you to follow best practices for writing WebDriver tests. If you're interested in writing clean Selenium code, you don’t want to miss this episode.
Jake and Michael discuss all the latest Laravel releases, tutorials, and happenings in the community.
In this episode, Chris & Spencer discuss their current efforts to migrate the design system (components, colors, typography, etc.) to a dedicated repository covering the various tooling and processes around publishing a package to a private registry, testing, linting, documentation and automated releasing with semantic-release. Show Notes Migrating a design system to a dedicated repository - Medium MDX Docz CODEOWNERS semantic-release commitlint commitizen yarn link
Panel: Dave Kimura Charles (Chuck) Max Wood Nate Hopkins Special Guest: Dan Mayer In this episode of Ruby Rogues, the panel talks with Bozhidar Batsov who is the VP of Engineering at Toptal, and an Emacs fanatic. The panel and the guest talk about RubCop, Emacs, and Komodo, among other topics! Check out today’s episode for more details. Show Topics: 0:00 – Sentry.IO – Advertisement! 1:07 – Chuck lists the panelists and the special guest. 1:37 – Chuck: Why are you famous? 1:41 – Guest gives his background. 2:13 – Guest: I am passionate about Emacs. 2:55 – Chuck. 2:58 – Panel: I have on a few projects. Do you know RUFO? It’s a bit more opinionated than RuboCop. 3:25 – Guest: I am familiar with RUFO and their approach is similar to JavaScript called Pretty or something like that. 4:45 – Guest: 4:49 – Panel: Can you tell us what RuboCop is and why is it important? 5:00 – Guest: There are a few main things that RuboCop is: 1.) Placement for Ruby minor... 2.) Lint tool 3.) Automatic checker for all the best practices outlined in the community 4.) Formatter for Ruby code – you can feed it ugly code and it will spin out beautiful code 7:30 – Panel: What are the origins of the project? Where you interested in the performance and security aspects of it? 7:49 – Guest. The guest talks about RuboCop in detail. 10:59 – Panel: It’s important to remember that these are just guidelines and they are NOT set in stone. Using single or double quotes. As long as the project is consistent and using decent practices then I am okay with the code. I will disable the...in RuboCop. Today with high-resolution monitors it’s one of those things that are an annoyance to me. It’s just my opinion, though. 12:07 – Guest: Why disable it and not...? 13:36 – Panel: You could use VS code instead of Emacs! I am just kidding. 13:51 – Guest: I hope you are kidding! 13:56 – Chuck: I cannot live without this code... 14:06 – Guest. 14:26 – Panel: I was an early adapter from the beginning and it was hella slow. I tried it from sublime text and I got annoyed so I eventually switched to VS code. Once I got over the brand name, I really like it as my main editor. 15:20 – Panel: Maybe it’s more approachable and it’s easier to dip your toes in. 15:35 – Guest. 16:29 – Panel: I haven’t heard of KOMODO in long time. I remember that was one of the first IDs that I had checked out. I tried that then went to Ruby Mine and then tried Sublime text and then VS. 16:57 – Guest: Komodo was a famous editor. 17:17 – Panel: I am curious on RuboCop that the adaption is driven by teaching idiomatic Ruby to people new to the language? 17:40 – Guest: I don’t think it’s much about the stylistic stuff at this point. I also noticed that the main driver of the group was... Guest goes into great detail about this topic. 22:44 – Guest (continues): RuboCop offers a bunch of different structure. 24:27 – Guest (continues): We are wondering how to approach the issue of performance. The performance aspect tended to be trickier than what we had expected. The majority of developers when given the choice to either secure or make something convenient - they will choose the latter option. 25:47 – Panel: That’s why they get hit with a high AWS bill. 26:00 – Guest. 26:30 – Panel: The things you have learned with RuboCop, is it changing the direction with MRI or the design of the language at all? 26:40 – Guest: I would hope so, but I don’t have hard evidence to prove this. If you give people too many options then it could be a waste of time. I don’t care about the nuances. 30:06 – Ad: RubyMine! 30-day trial! 30:38 – Panel: Would you recommend the Rails style guide if you are building a Rails style project? Should we use that as a baseline and then customize it for your team? 30:55 – Guest: The style guide should be good. For a while I was the only editor. Not a lot of the options that are there aren’t my personal opinion, but it’s the general prescription. If you have strong preferences and you have your team agree on those then it’s okay to be modifying it. At the end of the day it’s better to have consistency within a project. You are doing great! 32:57 – Chuck asks a question. 33:44 – Chuck: Could I modify a rule? 33:53 – Guest: There are varying degrees to the rule. 35:56 – Panel: One of your conference talks you talked about the future of Rails and the future of other Ruby frameworks? 36:18 – Guest: I am worried about the future of Ruby b/c I see people talking about the maturity of the system but there isn’t a clear vision to where we are going. There are some cornerstones for Ruby 3 that he is repeating. 41:05 – Guest (continues): I think we need to commit to the module and the API. 45:42 – Chuck: All of those things make sense to me. Is there any desire for people to fork Ruby or pulling / putting some of this in? 46:00 – Guest. 48:18 – Panel: Transition that to Rails and the future of Rails? 48:27 – Panel: There are big companies that are making changes. 48:51 – Guest. 53:33 – Panel: I think that is a common pattern that most companies move towards. 54:12 – Chuck: We did an episode on ElixirMix with Chris McCord. Check that out! 54:35 – Chuck: Picks! 54:40 – Advertisement – Fresh Books! End – Cache Fly! Links: Get a Coder Job Course Ruby Rust Ruby Motion Ruby on Rails Angular Komodo Emacs RuboCop RuboCop – GitHub Stimulus reflex Messages: Share Screens Smittybilt Visual Studio Code: Introducing Visual Studio Live Share VRBO Bozhidar’s GitHub Bozhidar’s Twitter Bozhidar’s Patreon Bozhidar’s Open Collective Past EMx Episode 020 with Chris McCord! Sponsors: Sentry RubyMine Cache Fly Fresh Books Picks: Dave Tire Plugs VS Live Share Nate Share Screen using Messages on Mac Charles VRBO Find opportunities for R&R Rocket League Bozhidar Documentation for Markdown users Bear App
Panel: Dave Kimura Charles (Chuck) Max Wood Nate Hopkins Special Guest: Dan Mayer In this episode of Ruby Rogues, the panel talks with Bozhidar Batsov who is the VP of Engineering at Toptal, and an Emacs fanatic. The panel and the guest talk about RubCop, Emacs, and Komodo, among other topics! Check out today’s episode for more details. Show Topics: 0:00 – Sentry.IO – Advertisement! 1:07 – Chuck lists the panelists and the special guest. 1:37 – Chuck: Why are you famous? 1:41 – Guest gives his background. 2:13 – Guest: I am passionate about Emacs. 2:55 – Chuck. 2:58 – Panel: I have on a few projects. Do you know RUFO? It’s a bit more opinionated than RuboCop. 3:25 – Guest: I am familiar with RUFO and their approach is similar to JavaScript called Pretty or something like that. 4:45 – Guest: 4:49 – Panel: Can you tell us what RuboCop is and why is it important? 5:00 – Guest: There are a few main things that RuboCop is: 1.) Placement for Ruby minor... 2.) Lint tool 3.) Automatic checker for all the best practices outlined in the community 4.) Formatter for Ruby code – you can feed it ugly code and it will spin out beautiful code 7:30 – Panel: What are the origins of the project? Where you interested in the performance and security aspects of it? 7:49 – Guest. The guest talks about RuboCop in detail. 10:59 – Panel: It’s important to remember that these are just guidelines and they are NOT set in stone. Using single or double quotes. As long as the project is consistent and using decent practices then I am okay with the code. I will disable the...in RuboCop. Today with high-resolution monitors it’s one of those things that are an annoyance to me. It’s just my opinion, though. 12:07 – Guest: Why disable it and not...? 13:36 – Panel: You could use VS code instead of Emacs! I am just kidding. 13:51 – Guest: I hope you are kidding! 13:56 – Chuck: I cannot live without this code... 14:06 – Guest. 14:26 – Panel: I was an early adapter from the beginning and it was hella slow. I tried it from sublime text and I got annoyed so I eventually switched to VS code. Once I got over the brand name, I really like it as my main editor. 15:20 – Panel: Maybe it’s more approachable and it’s easier to dip your toes in. 15:35 – Guest. 16:29 – Panel: I haven’t heard of KOMODO in long time. I remember that was one of the first IDs that I had checked out. I tried that then went to Ruby Mine and then tried Sublime text and then VS. 16:57 – Guest: Komodo was a famous editor. 17:17 – Panel: I am curious on RuboCop that the adaption is driven by teaching idiomatic Ruby to people new to the language? 17:40 – Guest: I don’t think it’s much about the stylistic stuff at this point. I also noticed that the main driver of the group was... Guest goes into great detail about this topic. 22:44 – Guest (continues): RuboCop offers a bunch of different structure. 24:27 – Guest (continues): We are wondering how to approach the issue of performance. The performance aspect tended to be trickier than what we had expected. The majority of developers when given the choice to either secure or make something convenient - they will choose the latter option. 25:47 – Panel: That’s why they get hit with a high AWS bill. 26:00 – Guest. 26:30 – Panel: The things you have learned with RuboCop, is it changing the direction with MRI or the design of the language at all? 26:40 – Guest: I would hope so, but I don’t have hard evidence to prove this. If you give people too many options then it could be a waste of time. I don’t care about the nuances. 30:06 – Ad: RubyMine! 30-day trial! 30:38 – Panel: Would you recommend the Rails style guide if you are building a Rails style project? Should we use that as a baseline and then customize it for your team? 30:55 – Guest: The style guide should be good. For a while I was the only editor. Not a lot of the options that are there aren’t my personal opinion, but it’s the general prescription. If you have strong preferences and you have your team agree on those then it’s okay to be modifying it. At the end of the day it’s better to have consistency within a project. You are doing great! 32:57 – Chuck asks a question. 33:44 – Chuck: Could I modify a rule? 33:53 – Guest: There are varying degrees to the rule. 35:56 – Panel: One of your conference talks you talked about the future of Rails and the future of other Ruby frameworks? 36:18 – Guest: I am worried about the future of Ruby b/c I see people talking about the maturity of the system but there isn’t a clear vision to where we are going. There are some cornerstones for Ruby 3 that he is repeating. 41:05 – Guest (continues): I think we need to commit to the module and the API. 45:42 – Chuck: All of those things make sense to me. Is there any desire for people to fork Ruby or pulling / putting some of this in? 46:00 – Guest. 48:18 – Panel: Transition that to Rails and the future of Rails? 48:27 – Panel: There are big companies that are making changes. 48:51 – Guest. 53:33 – Panel: I think that is a common pattern that most companies move towards. 54:12 – Chuck: We did an episode on ElixirMix with Chris McCord. Check that out! 54:35 – Chuck: Picks! 54:40 – Advertisement – Fresh Books! End – Cache Fly! Links: Get a Coder Job Course Ruby Rust Ruby Motion Ruby on Rails Angular Komodo Emacs RuboCop RuboCop – GitHub Stimulus reflex Messages: Share Screens Smittybilt Visual Studio Code: Introducing Visual Studio Live Share VRBO Bozhidar’s GitHub Bozhidar’s Twitter Bozhidar’s Patreon Bozhidar’s Open Collective Past EMx Episode 020 with Chris McCord! Sponsors: Sentry RubyMine Cache Fly Fresh Books Picks: Dave Tire Plugs VS Live Share Nate Share Screen using Messages on Mac Charles VRBO Find opportunities for R&R Rocket League Bozhidar Documentation for Markdown users Bear App
Panel: Chris Fritz Eric Hatchet Divya Sasidharan Charles Max Wood Special Guest: Benjamin Hong In this episode, the panel talks with Benjamin Hong who is a Senior Fullstack Engineer at GitLab, Inc. who currently resides in the Washington D.C. metro area. Ben and the panel talk about Politico and the current projects that Ben is working on. The panelists talk about topics, such as Vue, Vuex, VuePress, Nuxt, among others. Check out today’s episode! Show Topics: 0:00 – Advertisement – Kendo UI 0:32 – Panel: Hi! Welcome – our panel today is live at Park City, UT. 1:34 – Benjamin introduces himself. 1:41 – Panel: Politico is a well trafficked website and it’s well known. What are your thoughts about working on a well trafficked website? 2:22 – Guest. 2:44 – Panel: Why did you settle on Vue? 2:50 – Guest: ...I came onto the team and was passionate about helping. We built out the component types. I thought Vue was better suited for the team. 3:36 – Panel: That’s a large team – that’s a lot of people 3:45 – Guest: Yeah, at one time I was writing everything. A lot of people on the team right now didn’t know a lot of JavaScript – but having Vue helps everyone to move the project forward. 4:29 – Panel: They can write just HTML, etc. 4:38 – Guest: Yep, exactly. It helps with communication. 4:55 – Panel asks a question. 5:00 – Guest: I use an event bust. 5:20 – Chuck: Did you have to move from an event bust to Vuex and what was that like? 5:30 – Guest: We had to move into module-esque anyways. 5:42 – Panel: You probably have Vuex with modules and...? 5:54 – Guest: We are using your enterprise broiler plate! 6:05 – Panel: Yeah, every team uses their own patterns. What files would I see used within your team? 6:16 – Guest answers the question. 6:55 – Panel asks a question. 7:01 – Guest: We can keep with the recommended packages fairly well! 7:21 – Panel. 7:26 – Guest: Funny enough at London...we are starting to get a lot with our co-coverage. We have a hard time balancing with unit tests and...eventually we want to look at Cypress. 8:12 – Panel. 8:15 – Guest. 8:19 – Chuck. 8:38 – Panel: I always encourage people to test the unit tests. 9:00 – Chuck: As you adopted Vue what was it like to get buy-in from management. Usually they have a strong backend with Rails, and someone comes in and says let’s use X. How do you sell them on: we are going to use this new technology. 9:30 – Guest: We could really use the user-experience better, and also to offload things from the backend developers. Our desire was to control more things like animation and to specialize those things. That was my selling point. 10:32 – Chuck: I tend to do both on the apps that I’m working on. I told Chris that I was going to switch a lot of things to Vue – some of the things you said I am not interested in the backend b/c it’s too painful. 11:01 – Panel. 11:08 – Chuck: There are things that are really, really good on the backend, but... 11:18 – Panel. 11:24 – Panel: You get the benefits of rendering... 11:43 – Chuck: What are your challenges into Vue? 11:50 – Guest: It’s definitely the scale, because we were a team of 5 and now we are a team of 15. Also, the different time changes b/c we have some people who live in India. Getting that workflow and we are looking at STORYBOOK to help with that. 12:30 – Chuck: Every person you add doubles the complexity of the group. 12:40 – Panel: I think that is conservative! 12:49 – Chuck. 12:56 – Panel: I get to see Chuck in person so this is different! 13:09 – Panel: Challenge accepted! 13:18 – Panel: This is the roast! 13:25 – Panel: Are you working, Benjamin, on a component library? Are you working on that alongside your current project? How do you manage that/ 13:38 – Guest: Unfortunately, we have a lot of deadlines and everything is running in parallel! 14:00 – Panel: How do you implement expectations throughout your team? 14:13 – Panel. 14:16 – Guest: It’s for everyone to understand their own expectations and the team’s expectations. I have to be able to parse it out w/o giving them too much guidance. 15:20 – Panel. 15:25 – Guest: Yep! 15:30 – Panel: ...having to edit the same files and the same lines... 15:36 – Guest: We have been able to keep those in their own lanes! 15:44 – Panel: Yeah that’s no fun – I’ve been there! 15:53 – Chuck: You are working in the development branch – and then their thing breaks my thing, etc. 16:08 – Panel: You are doing dimensional travel! It’s almost like reorganizing a complete novel. 16:30 – Guest: You don’t want your work to drag on too long b/c you don’t want to poorly affect the other team members. 16:53 – Panel: Does that mean you use internal docs to help with the workflow? 17:03 – Guest: Yes, we use the common team board. 17:30 – Panel asks a question. 17:39 – Guest: Yes, that’s a challenge. I have setup an internal product called Politico Academy. 18:29 – Chuck: How do you fit into what Politico is doing? 18:45 – Guest: They are giving out cutting edge information regarding policies and that sort of thing. We have tools like compass to track your notes within the team and also bills. Politico Pro is like for lobbyists and those fees are very expensive. 19:23 – Panel: Do you have to create graphs and D3 and stuff like that? 19:35 – Guest: I am itching to do that and we haven’t really done that, yet. I would love to do that, though! 19:42 – Panel: Chris will be talking about that which will air on YouTube! 20:02 – Panel: Ben, you make decisions based on architecture – do the members of the team get to contribute to that or no? 20:27 – Guest: Yeah, I have a democratic approach. I want people to show their opinion, so that way they know that their voice is getting heard. I don’t make all the decisions, but I do give some guidelines. 21:11 – Chris: I like to time box it. I do the same thing, too. 21:49 – Chuck: Yeah someone would propose something to a new feature (or whatnot) and we would want to see if we want to explore it now or later. 21:55 – Panel goes back-and-forth. 23:26 – Panel: On that note- you want to make sure that each developer has submitted a pole request per day. What is universal in regards to coding practices, and code comments, and stuff like that and code style? 23:55 – Guest: We do PREMIER across the board right now. 24:55 – Panel asks a question. 25:08 – Guest: I like having more...if it can show WHY you did it a certain way. 25:33 – Panel: It’s good not to save the data. 25:40 – Chris: Sometimes a SQUASH can be helpful. 25:50 – Divya: I try to commit often and my work is a work in-progress. 26:08 – Chris. 26:13 – Chuck comments. 26:24 – Panel goes back-and-forth! 26:43 – Guest: They will write their code and then use Prettier and it will look terrifying b/c it’s like what did you just do. I want them to see the 2 lines they changed rather than the whole file. 27:13 – Panelist talks about Linting. 27:34 – Chuck. 27:39 – Chris: If it’s not the default then... 27:55 – Divya: When you manually setup your project you can run a prettier pre-commit. 28:00 – Chris: My pre-commits are much more thorough. 28:37 – Panel goes back-and-forth! 29:26 – Advertisement – Get A Coder Job! 30:02 – Panel: Can you talk about VuePress, please? 30:06 – Guest: Yeah! The guest talks about VuePress in-detail! 31:21 – Chuck. 31:25 – Panel. 31:44 – Chuck: I am curious about this – what’s the difference between VuePress and Nuxt? 31:58 – Guest answers the question. 32:19 – Chris adds his comments into this topic (VuePress and Nuxt). 32:47 – Guest. 33:02 – Divya. 34:24 – Chuck: If they are fluent in English and native in another language and it’s easy to figure where to put everything. 34:41 – Chris: Yeah they have a clear path for to clear up any documentation potential problems. 35:04 – Chris: ...the core docs and the impending libraries and the smaller ones, too. 35:17 – Divya: When you are creating the docs and you are thinking about NTN it’s important to think about the English docs. They say that it’s best to think of the language if that doc was to be translated into another language. 35:50 – Chris: Definition: “A function that returns another function” = higher function. 36:19 – Chuck: We are running out of time, and let’s talk about user-scripts. You have co-organized a group in Washington D.C. I tell people to go to a group to help like Meetups. What do you recommend? 37:00 – Guest: A lot of it is to be that community leader and show-up. To figure out let’s go ahead and meet. I know a lot of people worry about the “venue,” but go to a public library or ask an office for space, that’s an option, too. 38:15 – Panel: We have these different Meetups and right now in my area we don’t have one for Vue. 38:37 – Guest: Yeah, I recommend just getting it going. 39:04 – Chris: Yeah, just forming a community. 39:16 – Chuck: D.C. is a large area, so I can see where the larger market it would be easier. But even for the smaller communities there can be 10 or so people but that’s a great start! 39:48 – Guest: Yeah, once it gets started it flows. 40:02 – Chuck: What are the topics then at these meetings? 40:05 – Guest: I like to help people to code, so that’s my inspiration. 40:50 – Divya: I help with the Chicago Meetup and tons of people sign-up but not a lot of people to show – that’s our challenge right now! How do you get people to actually GO! 41:44 – Guest: I tell people that it’s a free event and really the show up rate is about 30%. I let the people to know that there is a beginning section, too, that there is a safe place for them. I find that that is helpful. 42:44 – Chris: Yeah, even the language/vocabulary that you use can really deter people or make people feel accepted. 43:48 – Chuck: Let’s talk about the idea of ‘new developers.’ They would ask people for the topics that THEY wanted to talk about. 44:37 – Divya: From an organizer’s perspective... 46:10 – Chuck: If you want people to show-up to your Meetups just do this...a secret pattern! I did a talk about a block chain and we probably had 3x to 4x a better turnout. 46:55 – Panel. 47:00 – Divya: The one event that was really successful was having Evan and Chris come to Chicago. That event was eventually $25.00 and then when Evan couldn’t come the price dropped to $5.00. 48:00 – Panel goes back-and-forth. 48:22 – Chuck: Where can they find you? 48:30 – Guest: BenCodeZen! 48:40 – Advertisement – Fresh Books! DEVCHAT code. 30-day trial. Links: Vue React Angular JavaScript DevChat TV Graph QL VuePress Nuxt Meetup 1 Chicago Meetup for Fullstack JavaScript Ben’s LinkedIn Ben’s Website Ben’s Twitter DevChat TV Past Episode with Benjamin Hong (MJS 082) Sponsors: Fresh Books Cache Fly Kendo UI Get A Coder Job! Picks: Divya Creator Summit Chris “Chuck” Take a break when traveling to conferences and such Vue.js in Action Eric Stackblitz Charles The One Thing Self Publishing School Ben Ted Talk by Elizabeth Gilbert Vue.js Meetups
Panel: Dave Kimura Charles (Chuck) Max Wood Nate Hopkins Special Guest: Dan Mayer In this episode of Ruby Rogues, the panel talks with Bozhidar Batsov who is the VP of Engineering at Toptal, and an Emacs fanatic. The panel and the guest talk about RubCop, Emacs, and Komodo, among other topics! Check out today’s episode for more details. Show Topics: 0:00 – Sentry.IO – Advertisement! 1:07 – Chuck lists the panelists and the special guest. 1:37 – Chuck: Why are you famous? 1:41 – Guest gives his background. 2:13 – Guest: I am passionate about Emacs. 2:55 – Chuck. 2:58 – Panel: I have on a few projects. Do you know RUFO? It’s a bit more opinionated than RuboCop. 3:25 – Guest: I am familiar with RUFO and their approach is similar to JavaScript called Pretty or something like that. 4:45 – Guest: 4:49 – Panel: Can you tell us what RuboCop is and why is it important? 5:00 – Guest: There are a few main things that RuboCop is: 1.) Placement for Ruby minor... 2.) Lint tool 3.) Automatic checker for all the best practices outlined in the community 4.) Formatter for Ruby code – you can feed it ugly code and it will spin out beautiful code 7:30 – Panel: What are the origins of the project? Where you interested in the performance and security aspects of it? 7:49 – Guest. The guest talks about RuboCop in detail. 10:59 – Panel: It’s important to remember that these are just guidelines and they are NOT set in stone. Using single or double quotes. As long as the project is consistent and using decent practices then I am okay with the code. I will disable the...in RuboCop. Today with high-resolution monitors it’s one of those things that are an annoyance to me. It’s just my opinion, though. 12:07 – Guest: Why disable it and not...? 13:36 – Panel: You could use VS code instead of Emacs! I am just kidding. 13:51 – Guest: I hope you are kidding! 13:56 – Chuck: I cannot live without this code... 14:06 – Guest. 14:26 – Panel: I was an early adapter from the beginning and it was hella slow. I tried it from sublime text and I got annoyed so I eventually switched to VS code. Once I got over the brand name, I really like it as my main editor. 15:20 – Panel: Maybe it’s more approachable and it’s easier to dip your toes in. 15:35 – Guest. 16:29 – Panel: I haven’t heard of KOMODO in long time. I remember that was one of the first IDs that I had checked out. I tried that then went to Ruby Mine and then tried Sublime text and then VS. 16:57 – Guest: Komodo was a famous editor. 17:17 – Panel: I am curious on RuboCop that the adaption is driven by teaching idiomatic Ruby to people new to the language? 17:40 – Guest: I don’t think it’s much about the stylistic stuff at this point. I also noticed that the main driver of the group was... Guest goes into great detail about this topic. 22:44 – Guest (continues): RuboCop offers a bunch of different structure. 24:27 – Guest (continues): We are wondering how to approach the issue of performance. The performance aspect tended to be trickier than what we had expected. The majority of developers when given the choice to either secure or make something convenient - they will choose the latter option. 25:47 – Panel: That’s why they get hit with a high AWS bill. 26:00 – Guest. 26:30 – Panel: The things you have learned with RuboCop, is it changing the direction with MRI or the design of the language at all? 26:40 – Guest: I would hope so, but I don’t have hard evidence to prove this. If you give people too many options then it could be a waste of time. I don’t care about the nuances. 30:06 – Ad: RubyMine! 30-day trial! 30:38 – Panel: Would you recommend the Rails style guide if you are building a Rails style project? Should we use that as a baseline and then customize it for your team? 30:55 – Guest: The style guide should be good. For a while I was the only editor. Not a lot of the options that are there aren’t my personal opinion, but it’s the general prescription. If you have strong preferences and you have your team agree on those then it’s okay to be modifying it. At the end of the day it’s better to have consistency within a project. You are doing great! 32:57 – Chuck asks a question. 33:44 – Chuck: Could I modify a rule? 33:53 – Guest: There are varying degrees to the rule. 35:56 – Panel: One of your conference talks you talked about the future of Rails and the future of other Ruby frameworks? 36:18 – Guest: I am worried about the future of Ruby b/c I see people talking about the maturity of the system but there isn’t a clear vision to where we are going. There are some cornerstones for Ruby 3 that he is repeating. 41:05 – Guest (continues): I think we need to commit to the module and the API. 45:42 – Chuck: All of those things make sense to me. Is there any desire for people to fork Ruby or pulling / putting some of this in? 46:00 – Guest. 48:18 – Panel: Transition that to Rails and the future of Rails? 48:27 – Panel: There are big companies that are making changes. 48:51 – Guest. 53:33 – Panel: I think that is a common pattern that most companies move towards. 54:12 – Chuck: We did an episode on ElixirMix with Chris McCord. Check that out! 54:35 – Chuck: Picks! 54:40 – Advertisement – Fresh Books! End – Cache Fly! Links: Get a Coder Job Course Ruby Rust Ruby Motion Ruby on Rails Angular Komodo Emacs RuboCop RuboCop – GitHub Stimulus reflex Messages: Share Screens Smittybilt Visual Studio Code: Introducing Visual Studio Live Share VRBO Bozhidar’s GitHub Bozhidar’s Twitter Bozhidar’s Patreon Bozhidar’s Open Collective Past EMx Episode 020 with Chris McCord! Sponsors: Sentry RubyMine Cache Fly Fresh Books Picks: Dave Tire Plugs VS Live Share Nate Share Screen using Messages on Mac Charles VRBO Find opportunities for R&R Rocket League Bozhidar Documentation for Markdown users Bear App
Panel: Chris Fritz Eric Hatchet Divya Sasidharan Charles Max Wood Special Guest: Benjamin Hong In this episode, the panel talks with Benjamin Hong who is a Senior Fullstack Engineer at GitLab, Inc. who currently resides in the Washington D.C. metro area. Ben and the panel talk about Politico and the current projects that Ben is working on. The panelists talk about topics, such as Vue, Vuex, VuePress, Nuxt, among others. Check out today’s episode! Show Topics: 0:00 – Advertisement – Kendo UI 0:32 – Panel: Hi! Welcome – our panel today is live at Park City, UT. 1:34 – Benjamin introduces himself. 1:41 – Panel: Politico is a well trafficked website and it’s well known. What are your thoughts about working on a well trafficked website? 2:22 – Guest. 2:44 – Panel: Why did you settle on Vue? 2:50 – Guest: ...I came onto the team and was passionate about helping. We built out the component types. I thought Vue was better suited for the team. 3:36 – Panel: That’s a large team – that’s a lot of people 3:45 – Guest: Yeah, at one time I was writing everything. A lot of people on the team right now didn’t know a lot of JavaScript – but having Vue helps everyone to move the project forward. 4:29 – Panel: They can write just HTML, etc. 4:38 – Guest: Yep, exactly. It helps with communication. 4:55 – Panel asks a question. 5:00 – Guest: I use an event bust. 5:20 – Chuck: Did you have to move from an event bust to Vuex and what was that like? 5:30 – Guest: We had to move into module-esque anyways. 5:42 – Panel: You probably have Vuex with modules and...? 5:54 – Guest: We are using your enterprise broiler plate! 6:05 – Panel: Yeah, every team uses their own patterns. What files would I see used within your team? 6:16 – Guest answers the question. 6:55 – Panel asks a question. 7:01 – Guest: We can keep with the recommended packages fairly well! 7:21 – Panel. 7:26 – Guest: Funny enough at London...we are starting to get a lot with our co-coverage. We have a hard time balancing with unit tests and...eventually we want to look at Cypress. 8:12 – Panel. 8:15 – Guest. 8:19 – Chuck. 8:38 – Panel: I always encourage people to test the unit tests. 9:00 – Chuck: As you adopted Vue what was it like to get buy-in from management. Usually they have a strong backend with Rails, and someone comes in and says let’s use X. How do you sell them on: we are going to use this new technology. 9:30 – Guest: We could really use the user-experience better, and also to offload things from the backend developers. Our desire was to control more things like animation and to specialize those things. That was my selling point. 10:32 – Chuck: I tend to do both on the apps that I’m working on. I told Chris that I was going to switch a lot of things to Vue – some of the things you said I am not interested in the backend b/c it’s too painful. 11:01 – Panel. 11:08 – Chuck: There are things that are really, really good on the backend, but... 11:18 – Panel. 11:24 – Panel: You get the benefits of rendering... 11:43 – Chuck: What are your challenges into Vue? 11:50 – Guest: It’s definitely the scale, because we were a team of 5 and now we are a team of 15. Also, the different time changes b/c we have some people who live in India. Getting that workflow and we are looking at STORYBOOK to help with that. 12:30 – Chuck: Every person you add doubles the complexity of the group. 12:40 – Panel: I think that is conservative! 12:49 – Chuck. 12:56 – Panel: I get to see Chuck in person so this is different! 13:09 – Panel: Challenge accepted! 13:18 – Panel: This is the roast! 13:25 – Panel: Are you working, Benjamin, on a component library? Are you working on that alongside your current project? How do you manage that/ 13:38 – Guest: Unfortunately, we have a lot of deadlines and everything is running in parallel! 14:00 – Panel: How do you implement expectations throughout your team? 14:13 – Panel. 14:16 – Guest: It’s for everyone to understand their own expectations and the team’s expectations. I have to be able to parse it out w/o giving them too much guidance. 15:20 – Panel. 15:25 – Guest: Yep! 15:30 – Panel: ...having to edit the same files and the same lines... 15:36 – Guest: We have been able to keep those in their own lanes! 15:44 – Panel: Yeah that’s no fun – I’ve been there! 15:53 – Chuck: You are working in the development branch – and then their thing breaks my thing, etc. 16:08 – Panel: You are doing dimensional travel! It’s almost like reorganizing a complete novel. 16:30 – Guest: You don’t want your work to drag on too long b/c you don’t want to poorly affect the other team members. 16:53 – Panel: Does that mean you use internal docs to help with the workflow? 17:03 – Guest: Yes, we use the common team board. 17:30 – Panel asks a question. 17:39 – Guest: Yes, that’s a challenge. I have setup an internal product called Politico Academy. 18:29 – Chuck: How do you fit into what Politico is doing? 18:45 – Guest: They are giving out cutting edge information regarding policies and that sort of thing. We have tools like compass to track your notes within the team and also bills. Politico Pro is like for lobbyists and those fees are very expensive. 19:23 – Panel: Do you have to create graphs and D3 and stuff like that? 19:35 – Guest: I am itching to do that and we haven’t really done that, yet. I would love to do that, though! 19:42 – Panel: Chris will be talking about that which will air on YouTube! 20:02 – Panel: Ben, you make decisions based on architecture – do the members of the team get to contribute to that or no? 20:27 – Guest: Yeah, I have a democratic approach. I want people to show their opinion, so that way they know that their voice is getting heard. I don’t make all the decisions, but I do give some guidelines. 21:11 – Chris: I like to time box it. I do the same thing, too. 21:49 – Chuck: Yeah someone would propose something to a new feature (or whatnot) and we would want to see if we want to explore it now or later. 21:55 – Panel goes back-and-forth. 23:26 – Panel: On that note- you want to make sure that each developer has submitted a pole request per day. What is universal in regards to coding practices, and code comments, and stuff like that and code style? 23:55 – Guest: We do PREMIER across the board right now. 24:55 – Panel asks a question. 25:08 – Guest: I like having more...if it can show WHY you did it a certain way. 25:33 – Panel: It’s good not to save the data. 25:40 – Chris: Sometimes a SQUASH can be helpful. 25:50 – Divya: I try to commit often and my work is a work in-progress. 26:08 – Chris. 26:13 – Chuck comments. 26:24 – Panel goes back-and-forth! 26:43 – Guest: They will write their code and then use Prettier and it will look terrifying b/c it’s like what did you just do. I want them to see the 2 lines they changed rather than the whole file. 27:13 – Panelist talks about Linting. 27:34 – Chuck. 27:39 – Chris: If it’s not the default then... 27:55 – Divya: When you manually setup your project you can run a prettier pre-commit. 28:00 – Chris: My pre-commits are much more thorough. 28:37 – Panel goes back-and-forth! 29:26 – Advertisement – Get A Coder Job! 30:02 – Panel: Can you talk about VuePress, please? 30:06 – Guest: Yeah! The guest talks about VuePress in-detail! 31:21 – Chuck. 31:25 – Panel. 31:44 – Chuck: I am curious about this – what’s the difference between VuePress and Nuxt? 31:58 – Guest answers the question. 32:19 – Chris adds his comments into this topic (VuePress and Nuxt). 32:47 – Guest. 33:02 – Divya. 34:24 – Chuck: If they are fluent in English and native in another language and it’s easy to figure where to put everything. 34:41 – Chris: Yeah they have a clear path for to clear up any documentation potential problems. 35:04 – Chris: ...the core docs and the impending libraries and the smaller ones, too. 35:17 – Divya: When you are creating the docs and you are thinking about NTN it’s important to think about the English docs. They say that it’s best to think of the language if that doc was to be translated into another language. 35:50 – Chris: Definition: “A function that returns another function” = higher function. 36:19 – Chuck: We are running out of time, and let’s talk about user-scripts. You have co-organized a group in Washington D.C. I tell people to go to a group to help like Meetups. What do you recommend? 37:00 – Guest: A lot of it is to be that community leader and show-up. To figure out let’s go ahead and meet. I know a lot of people worry about the “venue,” but go to a public library or ask an office for space, that’s an option, too. 38:15 – Panel: We have these different Meetups and right now in my area we don’t have one for Vue. 38:37 – Guest: Yeah, I recommend just getting it going. 39:04 – Chris: Yeah, just forming a community. 39:16 – Chuck: D.C. is a large area, so I can see where the larger market it would be easier. But even for the smaller communities there can be 10 or so people but that’s a great start! 39:48 – Guest: Yeah, once it gets started it flows. 40:02 – Chuck: What are the topics then at these meetings? 40:05 – Guest: I like to help people to code, so that’s my inspiration. 40:50 – Divya: I help with the Chicago Meetup and tons of people sign-up but not a lot of people to show – that’s our challenge right now! How do you get people to actually GO! 41:44 – Guest: I tell people that it’s a free event and really the show up rate is about 30%. I let the people to know that there is a beginning section, too, that there is a safe place for them. I find that that is helpful. 42:44 – Chris: Yeah, even the language/vocabulary that you use can really deter people or make people feel accepted. 43:48 – Chuck: Let’s talk about the idea of ‘new developers.’ They would ask people for the topics that THEY wanted to talk about. 44:37 – Divya: From an organizer’s perspective... 46:10 – Chuck: If you want people to show-up to your Meetups just do this...a secret pattern! I did a talk about a block chain and we probably had 3x to 4x a better turnout. 46:55 – Panel. 47:00 – Divya: The one event that was really successful was having Evan and Chris come to Chicago. That event was eventually $25.00 and then when Evan couldn’t come the price dropped to $5.00. 48:00 – Panel goes back-and-forth. 48:22 – Chuck: Where can they find you? 48:30 – Guest: BenCodeZen! 48:40 – Advertisement – Fresh Books! DEVCHAT code. 30-day trial. Links: Vue React Angular JavaScript DevChat TV Graph QL VuePress Nuxt Meetup 1 Chicago Meetup for Fullstack JavaScript Ben’s LinkedIn Ben’s Website Ben’s Twitter DevChat TV Past Episode with Benjamin Hong (MJS 082) Sponsors: Fresh Books Cache Fly Kendo UI Get A Coder Job! Picks: Divya Creator Summit Chris “Chuck” Take a break when traveling to conferences and such Vue.js in Action Eric Stackblitz Charles The One Thing Self Publishing School Ben Ted Talk by Elizabeth Gilbert Vue.js Meetups
Panel: Charles Max Wood Chris Fritz Erik Hanchett Divya Sasidharan Special Guests: Hassan Djirdeh In this episode of Views on Vue, the panelists discuss state management with Vue.js with Hassan Djirdeh. Hassan is a front-end engineer developer based out of Toronto, Canada and works for the ecommerce company Shopify as his full-time job. In his free-time he does anything and everything related to Vue and has also recently helped publish a book called Fullstack Vue. They talk about Vue CLI 3.0, state management patterns, his talk The Importance of State Management in Vue, and more! In particular, we dive pretty deep on: Hassan intro Vue Recently started using the Vue CLI 3.0 How is Vue CLI 3.0 different from 2.0? More obvious to understand what people need for their application Vuex and Vue Router Great way to get things started What if you’re using a configuration from Vue CLI 2.0? Webpack or Browserify Making things easier and better for new Vue developers Further configuring your projects Have you found anything you haven’t been able to configure with Vue CLI 3? Git integration Vuex Modules Linting Can you create your own templates with the CLI? How much should the CLI tool walk the developer through the process? Integrating ESLint into a project Runtime errors Pre-commit hook The Importance of State Management in Vue – Hassan’s Talk And much, much more! Links: Shopify Fullstack Vue Vue CLI 3.0 Vue Vuex Vue Router Webpack Browserify Vuex Modules The Importance of State Management in Vue – Hassan’s Talk ESLint Hassan’s Medium Hassan’s GitHub @djirdehh hassandjirdeh.com Sponsors: Kendo UI FreshBooks Picks: Charles GDPR Solo Movie Chris Sarah Drasner Repo - loldash Jean-Claude Van Johnson Dark Primer Erik Wallabyjs.com Divya Gatsby.js SmooshGate blog Hassan Avengers: Infinity War Lambda School
Panel: Charles Max Wood Chris Fritz Erik Hanchett Divya Sasidharan Special Guests: Hassan Djirdeh In this episode of Views on Vue, the panelists discuss state management with Vue.js with Hassan Djirdeh. Hassan is a front-end engineer developer based out of Toronto, Canada and works for the ecommerce company Shopify as his full-time job. In his free-time he does anything and everything related to Vue and has also recently helped publish a book called Fullstack Vue. They talk about Vue CLI 3.0, state management patterns, his talk The Importance of State Management in Vue, and more! In particular, we dive pretty deep on: Hassan intro Vue Recently started using the Vue CLI 3.0 How is Vue CLI 3.0 different from 2.0? More obvious to understand what people need for their application Vuex and Vue Router Great way to get things started What if you’re using a configuration from Vue CLI 2.0? Webpack or Browserify Making things easier and better for new Vue developers Further configuring your projects Have you found anything you haven’t been able to configure with Vue CLI 3? Git integration Vuex Modules Linting Can you create your own templates with the CLI? How much should the CLI tool walk the developer through the process? Integrating ESLint into a project Runtime errors Pre-commit hook The Importance of State Management in Vue – Hassan’s Talk And much, much more! Links: Shopify Fullstack Vue Vue CLI 3.0 Vue Vuex Vue Router Webpack Browserify Vuex Modules The Importance of State Management in Vue – Hassan’s Talk ESLint Hassan’s Medium Hassan’s GitHub @djirdehh hassandjirdeh.com Sponsors: Kendo UI FreshBooks Picks: Charles GDPR Solo Movie Chris Sarah Drasner Repo - loldash Jean-Claude Van Johnson Dark Primer Erik Wallabyjs.com Divya Gatsby.js SmooshGate blog Hassan Avengers: Infinity War Lambda School
We talk Lint, Linters and Linting with Tor Norbye along with what the news about Google officially supporting Kotlin means for Android Studio. For links to show notes, please visit talkingkotlin.com
Grizzly bear facts. Baby talk. Henning is team-lead now. JSON API + Swagger =
03:08 - Benjamin Dunphy Introduction Twitter GitHub 04:07 - Berkeley Martinez Introduction Twitter GitHub Free Code Camp 04:19 - Ian Sinnott Introduction Twitter GitHub Blog TruSTAR Technology 05:19 - The React Codebase 12:38 - Other Important Parts of the React Ecosystem 14:22 - The Angular vs the React Ecosystem and Community The Learning Curve create-react-app 22:07 - Community Developer Experience Functional Programming 26:56 - Getting Connected to the React Community Meetup: Real World React @rwreact ReactJS San Francisco Bay Area Meetup Meetup Eventbrite Calagator Twitter Dan Abramov: My React List 29:34 - Conferences React.js Conf React Rally ReactNext ReactiveConf ReactEurope 33:28 - Technology From the Community redux ThunderCats.js 38:23 - Choices Are Expanding; Not Shrinking Linting 40:19 - The Future of React 42:39 - Starting More Communities Picks This Developing Story (Aimee) Nashville (Aimee) Nodevember (Aimee) egghead.io: React in 7 Minutes (Ben) Lee Byron: Immutable User Interfaces @ Render 2016 (Ben) Nick Schrock: React.js Conf 2016 Keynote (Ben) create-react-app (Ian) Functional Programming Jargon (Ian) The Serverless Framework (Ian) Ben's Blog (Berkeley) Isaac Asimov’s Robot Series (Berkeley) Vsauce: The Zipf Mystery (Berkeley) Kinesis Advantage for PC & Mac (Dave)
03:08 - Benjamin Dunphy Introduction Twitter GitHub 04:07 - Berkeley Martinez Introduction Twitter GitHub Free Code Camp 04:19 - Ian Sinnott Introduction Twitter GitHub Blog TruSTAR Technology 05:19 - The React Codebase 12:38 - Other Important Parts of the React Ecosystem 14:22 - The Angular vs the React Ecosystem and Community The Learning Curve create-react-app 22:07 - Community Developer Experience Functional Programming 26:56 - Getting Connected to the React Community Meetup: Real World React @rwreact ReactJS San Francisco Bay Area Meetup Meetup Eventbrite Calagator Twitter Dan Abramov: My React List 29:34 - Conferences React.js Conf React Rally ReactNext ReactiveConf ReactEurope 33:28 - Technology From the Community redux ThunderCats.js 38:23 - Choices Are Expanding; Not Shrinking Linting 40:19 - The Future of React 42:39 - Starting More Communities Picks This Developing Story (Aimee) Nashville (Aimee) Nodevember (Aimee) egghead.io: React in 7 Minutes (Ben) Lee Byron: Immutable User Interfaces @ Render 2016 (Ben) Nick Schrock: React.js Conf 2016 Keynote (Ben) create-react-app (Ian) Functional Programming Jargon (Ian) The Serverless Framework (Ian) Ben's Blog (Berkeley) Isaac Asimov’s Robot Series (Berkeley) Vsauce: The Zipf Mystery (Berkeley) Kinesis Advantage for PC & Mac (Dave)
03:08 - Benjamin Dunphy Introduction Twitter GitHub 04:07 - Berkeley Martinez Introduction Twitter GitHub Free Code Camp 04:19 - Ian Sinnott Introduction Twitter GitHub Blog TruSTAR Technology 05:19 - The React Codebase 12:38 - Other Important Parts of the React Ecosystem 14:22 - The Angular vs the React Ecosystem and Community The Learning Curve create-react-app 22:07 - Community Developer Experience Functional Programming 26:56 - Getting Connected to the React Community Meetup: Real World React @rwreact ReactJS San Francisco Bay Area Meetup Meetup Eventbrite Calagator Twitter Dan Abramov: My React List 29:34 - Conferences React.js Conf React Rally ReactNext ReactiveConf ReactEurope 33:28 - Technology From the Community redux ThunderCats.js 38:23 - Choices Are Expanding; Not Shrinking Linting 40:19 - The Future of React 42:39 - Starting More Communities Picks This Developing Story (Aimee) Nashville (Aimee) Nodevember (Aimee) egghead.io: React in 7 Minutes (Ben) Lee Byron: Immutable User Interfaces @ Render 2016 (Ben) Nick Schrock: React.js Conf 2016 Keynote (Ben) create-react-app (Ian) Functional Programming Jargon (Ian) The Serverless Framework (Ian) Ben's Blog (Berkeley) Isaac Asimov’s Robot Series (Berkeley) Vsauce: The Zipf Mystery (Berkeley) Kinesis Advantage for PC & Mac (Dave)
Ed and Eric Bishard cover the latest news in the development community including: Linting, Ad-Blocking, NativeScript, and Angular Migrations.
01:49 - Erik Michaels-Ober Introduction Twitter GitHub Ruby Rogues Episode #127: Erik Michaels-Ober 02:07 - The Crystal Programming Language and Statically Typed Programming Languages Erik Michaels-Ober: An Introduction to Crystal @ PolyConf 15 06:54 - Type Inference Union Types Duck Typing Monkey Patching Sandi Metz Blog Post on the Wrong Abstraction 15:06 - Crystal vs Rust or Go 20:10 - Linting Rubocop 20:44 - Type Annotations and Perimeters Keyword Arguments 22:53 - The History of Crystal and its Development as a Language Crystal Docs Crystal GitHub Repo The Future of Crystal (Christmastime Blog Post) 24:41 - Annotation and Return Value 25:35 - Type Inferencing (Cont’d) 28:24 - Crystal REPL (ICR) 32:15 - Getting Involved with Crystal and the Development of the Language Crystal to_proc 40:08 - Threading and Concurrency 44:28 - Crystalshards Crystal Weekly 49:30 - Use Cases and Benchmarks Crystal Standard Library wc.cr 01:03:15 - Compile Errors More on Crystal Erik Michaels-Ober: Crystal Programming Language @ RubyC 2015 Interview for RubyC-2015 with Erik Michaels-Ober Built-in formatting tool Issue Picks Easy Bash Prompt Generator (Jessica) Logitech Wireless Headset Dual H820e Double-Ear Stereo Business Headset (David) Ruby Rogues Episode #127: Erik Michaels-Ober (Erik) fish shell (Erik) Rails Girls Summer of Code (Erik) RescueTime (Avdi) The 7 Habits of Highly Effective People: Powerful Lessons in Personal Change by Stephen R. Covey (Avdi) Whiplash White IPA (Avdi)
01:49 - Erik Michaels-Ober Introduction Twitter GitHub Ruby Rogues Episode #127: Erik Michaels-Ober 02:07 - The Crystal Programming Language and Statically Typed Programming Languages Erik Michaels-Ober: An Introduction to Crystal @ PolyConf 15 06:54 - Type Inference Union Types Duck Typing Monkey Patching Sandi Metz Blog Post on the Wrong Abstraction 15:06 - Crystal vs Rust or Go 20:10 - Linting Rubocop 20:44 - Type Annotations and Perimeters Keyword Arguments 22:53 - The History of Crystal and its Development as a Language Crystal Docs Crystal GitHub Repo The Future of Crystal (Christmastime Blog Post) 24:41 - Annotation and Return Value 25:35 - Type Inferencing (Cont’d) 28:24 - Crystal REPL (ICR) 32:15 - Getting Involved with Crystal and the Development of the Language Crystal to_proc 40:08 - Threading and Concurrency 44:28 - Crystalshards Crystal Weekly 49:30 - Use Cases and Benchmarks Crystal Standard Library wc.cr 01:03:15 - Compile Errors More on Crystal Erik Michaels-Ober: Crystal Programming Language @ RubyC 2015 Interview for RubyC-2015 with Erik Michaels-Ober Built-in formatting tool Issue Picks Easy Bash Prompt Generator (Jessica) Logitech Wireless Headset Dual H820e Double-Ear Stereo Business Headset (David) Ruby Rogues Episode #127: Erik Michaels-Ober (Erik) fish shell (Erik) Rails Girls Summer of Code (Erik) RescueTime (Avdi) The 7 Habits of Highly Effective People: Powerful Lessons in Personal Change by Stephen R. Covey (Avdi) Whiplash White IPA (Avdi)
01:49 - Erik Michaels-Ober Introduction Twitter GitHub Ruby Rogues Episode #127: Erik Michaels-Ober 02:07 - The Crystal Programming Language and Statically Typed Programming Languages Erik Michaels-Ober: An Introduction to Crystal @ PolyConf 15 06:54 - Type Inference Union Types Duck Typing Monkey Patching Sandi Metz Blog Post on the Wrong Abstraction 15:06 - Crystal vs Rust or Go 20:10 - Linting Rubocop 20:44 - Type Annotations and Perimeters Keyword Arguments 22:53 - The History of Crystal and its Development as a Language Crystal Docs Crystal GitHub Repo The Future of Crystal (Christmastime Blog Post) 24:41 - Annotation and Return Value 25:35 - Type Inferencing (Cont’d) 28:24 - Crystal REPL (ICR) 32:15 - Getting Involved with Crystal and the Development of the Language Crystal to_proc 40:08 - Threading and Concurrency 44:28 - Crystalshards Crystal Weekly 49:30 - Use Cases and Benchmarks Crystal Standard Library wc.cr 01:03:15 - Compile Errors More on Crystal Erik Michaels-Ober: Crystal Programming Language @ RubyC 2015 Interview for RubyC-2015 with Erik Michaels-Ober Built-in formatting tool Issue Picks Easy Bash Prompt Generator (Jessica) Logitech Wireless Headset Dual H820e Double-Ear Stereo Business Headset (David) Ruby Rogues Episode #127: Erik Michaels-Ober (Erik) fish shell (Erik) Rails Girls Summer of Code (Erik) RescueTime (Avdi) The 7 Habits of Highly Effective People: Powerful Lessons in Personal Change by Stephen R. Covey (Avdi) Whiplash White IPA (Avdi)
The HOBI Gang is all alone in the studio with no guests this week but they do have enough content to fill a fourth seat! The guys discuss their past week including the heartbreaking loss of not only the Bengals but also David Bowie! The gang discuss more theories of Star Wars: The Force Awakens and try to figure out what Nickel has to bribe HOBI with to win a Floppy outright. Blake has 25 selections for this week's Top 5, the most Favorite Films of the 1990s while Jason decides to change his picks as he goes along!
02:28 - Sebastian McKenzie Introduction Twitter GitHub Blog 02:53 - Babel (Pronunciation Clarification) 05:56 - History Learn ES2015 - Babel 09:14 - The State of Babel 09:59 - Babel and the TC39 Process 11:54 - Features That Can’t Be Transpiled Weak Maps and Proxies 13:45 - Readability and Performance Output Traceur 18:12 - Plugin Architecture 19:58 - ES6/2015 Feature Implementation Blockscoping Labels Exceptions Destructuring 25:49 - The Birth of Babel 26:45 - Babel vs Traceur 28:08 - Future Babel Features Code Optimization Minification Linting 30:15 - The Status of ES2015 and ES2016 31:01 - Browser Support 35:03 - Marketing 35:59 - TypeScript 37:24 - Babel Development and Labor Picks Primitive.io (Joe) Armada: The Novel by Ernest Cline (Joe) How to Win Friends & Influence People by Dale Carnegie (AJ) Web Security Warriors Podcast (AJ) Nodevember (Aimee) The Hitchhiker's Guide to the Galaxy by Douglas Adams (Dave) Yellowstone National Park (Dave) React Rally (Dave) Iterativ: AngularJS Kurs (Chuck) Hire Thom Parkin! (Chuck) The Martian by Andy Weir (Sebastian) Five Guys Burgers and Fries (Sebastian)
02:28 - Sebastian McKenzie Introduction Twitter GitHub Blog 02:53 - Babel (Pronunciation Clarification) 05:56 - History Learn ES2015 - Babel 09:14 - The State of Babel 09:59 - Babel and the TC39 Process 11:54 - Features That Can’t Be Transpiled Weak Maps and Proxies 13:45 - Readability and Performance Output Traceur 18:12 - Plugin Architecture 19:58 - ES6/2015 Feature Implementation Blockscoping Labels Exceptions Destructuring 25:49 - The Birth of Babel 26:45 - Babel vs Traceur 28:08 - Future Babel Features Code Optimization Minification Linting 30:15 - The Status of ES2015 and ES2016 31:01 - Browser Support 35:03 - Marketing 35:59 - TypeScript 37:24 - Babel Development and Labor Picks Primitive.io (Joe) Armada: The Novel by Ernest Cline (Joe) How to Win Friends & Influence People by Dale Carnegie (AJ) Web Security Warriors Podcast (AJ) Nodevember (Aimee) The Hitchhiker's Guide to the Galaxy by Douglas Adams (Dave) Yellowstone National Park (Dave) React Rally (Dave) Iterativ: AngularJS Kurs (Chuck) Hire Thom Parkin! (Chuck) The Martian by Andy Weir (Sebastian) Five Guys Burgers and Fries (Sebastian)
02:28 - Sebastian McKenzie Introduction Twitter GitHub Blog 02:53 - Babel (Pronunciation Clarification) 05:56 - History Learn ES2015 - Babel 09:14 - The State of Babel 09:59 - Babel and the TC39 Process 11:54 - Features That Can’t Be Transpiled Weak Maps and Proxies 13:45 - Readability and Performance Output Traceur 18:12 - Plugin Architecture 19:58 - ES6/2015 Feature Implementation Blockscoping Labels Exceptions Destructuring 25:49 - The Birth of Babel 26:45 - Babel vs Traceur 28:08 - Future Babel Features Code Optimization Minification Linting 30:15 - The Status of ES2015 and ES2016 31:01 - Browser Support 35:03 - Marketing 35:59 - TypeScript 37:24 - Babel Development and Labor Picks Primitive.io (Joe) Armada: The Novel by Ernest Cline (Joe) How to Win Friends & Influence People by Dale Carnegie (AJ) Web Security Warriors Podcast (AJ) Nodevember (Aimee) The Hitchhiker's Guide to the Galaxy by Douglas Adams (Dave) Yellowstone National Park (Dave) React Rally (Dave) Iterativ: AngularJS Kurs (Chuck) Hire Thom Parkin! (Chuck) The Martian by Andy Weir (Sebastian) Five Guys Burgers and Fries (Sebastian)
02:27 - Alex Eagle Introduction Twitter GitHub Google 02:54 - Jonathan Turner Introduction Twitter GitHub Microsoft [Talk] Jonathan Turner: TypeScript and Angular 2 @ ng-conf 2015 [Talk] Jonathan Turner: TypeScript and Angular 2 @ Angular U 2015 03:30 - What is TypeScript? 04:40 - Google + Microsoft =
02:27 - Alex Eagle Introduction Twitter GitHub Google 02:54 - Jonathan Turner Introduction Twitter GitHub Microsoft [Talk] Jonathan Turner: TypeScript and Angular 2 @ ng-conf 2015 [Talk] Jonathan Turner: TypeScript and Angular 2 @ Angular U 2015 03:30 - What is TypeScript? 04:40 - Google + Microsoft =
02:27 - Alex Eagle Introduction Twitter GitHub Google 02:54 - Jonathan Turner Introduction Twitter GitHub Microsoft [Talk] Jonathan Turner: TypeScript and Angular 2 @ ng-conf 2015 [Talk] Jonathan Turner: TypeScript and Angular 2 @ Angular U 2015 03:30 - What is TypeScript? 04:40 - Google + Microsoft =
02:15 - Jamund Ferguson Introduction Twitter GitHub Blog PayPal Jamund Ferguson: JavaScript Linting for Code Quality & ESLint Overview 02:47 - Lint (Background) JSLint Douglas Crockford JSHint ESLint [GitHub] eslint Nicholas Zakas [Gitter] eslint 04:48 - Keeping ESLint Up-to-date Esprima Ariya Hidayat espree Babel babel-eslint ES6 (ECMAScript 6) 08:09 - Abstract Syntax Tree (ASTs) Jamund Ferguson: Don’t be scared of abstract syntax trees Minification UglifyJS 13:28 - Using Lint Tools Context Switching Aspects to Linting: Code Standardization Catching Bad Mistakes JSCS (JavaScript Code Style) “Extends” 20:42 - Are there a downsides to linting? The Social Problem 23:40 - Establishing Rules Bikeshedding Consistency 25:12 - Cool ESLint Features handle-callback-err Not Throwing Literals No Restricted Modules Jamund Ferguson: Error Handling in Node.js @ MountainWest JavaScript 2014 30:45 - How ESLint Works Internally eslint-plugin-angular Configuration and Defaults 40:07 - Getting Started with Linting 43:03 - Autofixer 44:41 - Plugins 46:47 - Linter Feedback From the Panel Picks Mozilla (AJ) We Will All Be Game Programmers (Aimee) Search Inside Yourself: The Unexpected Path to Achieving Success, Happiness (and World Peace) by Chade-Meng Tan (Aimee) Good Mythical Morning (Dave) Salt Lake City (Dave) BB King Calls This One Of His Best Performances (Jamison) json-server (Jamison) Austenland (Joe) Supergirl (Joe) A Short History of Nearly Everything by Bill Bryson (Jamund) The Book of Mormon (Jamund)
02:15 - Jamund Ferguson Introduction Twitter GitHub Blog PayPal Jamund Ferguson: JavaScript Linting for Code Quality & ESLint Overview 02:47 - Lint (Background) JSLint Douglas Crockford JSHint ESLint [GitHub] eslint Nicholas Zakas [Gitter] eslint 04:48 - Keeping ESLint Up-to-date Esprima Ariya Hidayat espree Babel babel-eslint ES6 (ECMAScript 6) 08:09 - Abstract Syntax Tree (ASTs) Jamund Ferguson: Don’t be scared of abstract syntax trees Minification UglifyJS 13:28 - Using Lint Tools Context Switching Aspects to Linting: Code Standardization Catching Bad Mistakes JSCS (JavaScript Code Style) “Extends” 20:42 - Are there a downsides to linting? The Social Problem 23:40 - Establishing Rules Bikeshedding Consistency 25:12 - Cool ESLint Features handle-callback-err Not Throwing Literals No Restricted Modules Jamund Ferguson: Error Handling in Node.js @ MountainWest JavaScript 2014 30:45 - How ESLint Works Internally eslint-plugin-angular Configuration and Defaults 40:07 - Getting Started with Linting 43:03 - Autofixer 44:41 - Plugins 46:47 - Linter Feedback From the Panel Picks Mozilla (AJ) We Will All Be Game Programmers (Aimee) Search Inside Yourself: The Unexpected Path to Achieving Success, Happiness (and World Peace) by Chade-Meng Tan (Aimee) Good Mythical Morning (Dave) Salt Lake City (Dave) BB King Calls This One Of His Best Performances (Jamison) json-server (Jamison) Austenland (Joe) Supergirl (Joe) A Short History of Nearly Everything by Bill Bryson (Jamund) The Book of Mormon (Jamund)
02:15 - Jamund Ferguson Introduction Twitter GitHub Blog PayPal Jamund Ferguson: JavaScript Linting for Code Quality & ESLint Overview 02:47 - Lint (Background) JSLint Douglas Crockford JSHint ESLint [GitHub] eslint Nicholas Zakas [Gitter] eslint 04:48 - Keeping ESLint Up-to-date Esprima Ariya Hidayat espree Babel babel-eslint ES6 (ECMAScript 6) 08:09 - Abstract Syntax Tree (ASTs) Jamund Ferguson: Don’t be scared of abstract syntax trees Minification UglifyJS 13:28 - Using Lint Tools Context Switching Aspects to Linting: Code Standardization Catching Bad Mistakes JSCS (JavaScript Code Style) “Extends” 20:42 - Are there a downsides to linting? The Social Problem 23:40 - Establishing Rules Bikeshedding Consistency 25:12 - Cool ESLint Features handle-callback-err Not Throwing Literals No Restricted Modules Jamund Ferguson: Error Handling in Node.js @ MountainWest JavaScript 2014 30:45 - How ESLint Works Internally eslint-plugin-angular Configuration and Defaults 40:07 - Getting Started with Linting 43:03 - Autofixer 44:41 - Plugins 46:47 - Linter Feedback From the Panel Picks Mozilla (AJ) We Will All Be Game Programmers (Aimee) Search Inside Yourself: The Unexpected Path to Achieving Success, Happiness (and World Peace) by Chade-Meng Tan (Aimee) Good Mythical Morning (Dave) Salt Lake City (Dave) BB King Calls This One Of His Best Performances (Jamison) json-server (Jamison) Austenland (Joe) Supergirl (Joe) A Short History of Nearly Everything by Bill Bryson (Jamund) The Book of Mormon (Jamund)
© 2020-2025 Ivy Podcast Discovery LLC
