Stay current on the latest innovations and technologies in the React community by listening to our panel of React and Web Development Experts.
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up–6102072/support.
php/* */ ?>
Stay current on the latest innovations and technologies in the React community by listening to our panel of React and Web Development Experts.
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up–6102072/support.
Copyright: © 2022 Intentional Excellence Productions, LLC
Welcome to React Roundup, the podcast where we keep you updated on all things React related! In today's episode, we have an enlightening discussion featuring Paige Nedringhaus as host, our panelist TJ Van Toll, and our special guest, Florian Rappel, a solution architect from Munich, Germany. Florian, a noted figure in the web community, especially in TypeScript, React, and Microfrontends, dives deep into a variety of engaging topics.
Throughout the episode, we explore the complexities and benefits of using React, often described as a "black box" for the way it abstracts away many details from developers. We also delve into the intriguing world of Microfrontends, where Florian provides a comprehensive overview of this approach, discussing its practical implementation and the organizational shifts it can entail.
Additionally, Florian introduces his new book, "The Art of Microfrontends," and shares insights on how to manage complex front-end projects more efficiently. Whether you're a seasoned developer or new to the ecosystem, this episode offers a wealth of knowledge and practical advice to enhance your development practices.
So, tune in for an insightful journey through the realms of React and Microfrontends, and get ready to elevate your coding game!
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
On this episode of React Round Up we chatted with Miroslav Nikolov, a UI developer at one.com, about his approach to unit testing React components. Miroslav discussed writing components in a human-friendly way, using the library UnexpectedJS. We also talked about Miroslav’s blog, including how he got started with it, and some of the tools he used, like Gatsby and Mailchimp. This is a great episode if you’re looking to learn more about how to approach unit testing in React.
Links
Eric Simons joins the round-up to discuss the latest advancements made by StackBlitz that enables you to run NodeJS in the browser. Eric expands that to the work they've done with the NextJS team to run NextJS in the browser without the need to have a server in the background.
Links
Returning guest, Ian Lavery from Picovice.ai, joins the hosts to talk all things voice recognition. He dives into new languages the company has tackled over the last year (and what languages it plans to tackle next year), how they train their models, and how Picovoice is actually running speech recognition in the browser instead of in the cloud, making things like captioning live streams and real-time chats possible with some of its newer tech Cheetah and Leopard.
He also shares how he wrote a simple podcast transcription app using Picovoice and Express.js, in addition to Picovoice boasting specific SDKs for React, Angular and Vue.
Listen to Ian's first appearance on RRU here where he and the panel went deep into the specifics of voice recognition like security and privacy, understanding it in general, and using it sans big cloud providers.
Sponsors
In today's episode, Lucas and Peter dive deep into the world of front-end frameworks with a captivating discussion featuring PRANTA Dutta, a seasoned React Native developer. Pranta shares his journey transitioning from Vue to React, highlighting both the challenges and advantages of React's manual configurations and rich third-party ecosystem. They explore the contrasts between frameworks like React, Angular, and Flutter, delving into the trade-offs between their built-in features and flexibility. From the complexities of using Flutter's custom canvas painting to the streamlined utilities for notifications and Firebase, we cover it all. They also tackle the ongoing debate of native versus hybrid mobile app development, with insights into the Kotlin Multiplatform project and the importance of choosing the right tools based on project needs.
Join them as they unravel the intricacies of React's success and shortcomings, discuss the merits of design patterns in both Flutter and React, and examine the responsibilities developers hold in shaping their applications. Stay tuned for a valuable conversation packed with industry insights and practical examples!
Links
In this episode of React Round Up we chatted with James Smith from Bugsnag. We talked about the importance of error monitoring and reporting, and how to actually implement those workflows in your production apps. James shared a number of tips for React developers, like what are the most common errors and how you can help prevent them (hint: linters help a lot). We also got into mobile, and what developers can do to protect against third-party SDK errors.
Picks
Akash Joshi Is a frequent blogger across many of the larger blogs across the internet.
He joins the Round Up to share his opinions on how you should put your React applications together as well as some tips on where you shouldn't put files and where you should avoid putting specific types of files.
Some of this is inspired by projects like Next.js and others by his own experience. Paige and TJ chime in with their experience to help provide more context to the conversation.
Links
Senior Frontend Engineer Kathryn Grayson Nanz joins the React Round Up team to talk about all things component libraries. Kathryn shares her experiences building not one but two component libraries, as well as tips and tricks on the benefits of shared libraries, how to get buy in from product and developer teams, the best way to set up libraries and keeping them up-to-date. She also shares pitfalls to try and avoid when getting started with building a new library. Definitely a good listen for anyone debating whether an existing library or a brand new, custom one is the way to go for a project.
Links
Victory Dumebi Nwani joins the round up to discuss integrating the Dialogflow from Google Cloud into your application to manage voice and chat capabilities for your application.
Victory dives into the stack he used to put together a functioning app using that offering from Google.
Links
Priscila Oliveira and Mark Story join the panel to discuss the recent transition at Sentry from vanilla JavaScript to React and TypeScript.
The show starts out with the panelists nerding out over Sentry and how they use it, then they dive into the code transition and the things that they learned from their conversion to TypeScript.
Links
Despite JavaScript being a single-threaded language, you can now leverage multi-threaded computing thanks to modern browser features such as web workers, workouts and service workers. In this show, Majid explains how these features work and what problems they solve. We also discuss the strategies you can use to introduce them to production codebases and give your users a much more enjoyable experience on your web app.
Links
In today’s episode of React Round Up, Nigerian-based developer Dillion Megida explains how you can create source plugins for Gatsby, the static site generation tool. Gatsby can be used to create landing pages, blogs and e-commerce sites, among other things, and it contains a vast plugin ecosystem that helps developers avoid reinventing the wheel when creating their applications. Dillion also shares his experience blogging for websites such as LogRocket, FreeCodecamp and Dev.to and talks us through his workflow and how he comes up with new article ideas.
Links
In this episode, they dive deep into the world of event sourcing with special guest, Luis Galeas, CEO and founder of Ambar. Lucas Paganini, along with Chris and Peter explore the intricacies of event sourcing, comparing front-end implementations using Redux and back-end approaches, and highlighting the benefits, drawbacks, and practical applications.
Luis shares his expertise on event sourcing, discussing how events act as the primary source of truth and the importance of understanding system boundaries for scalability. The conversation covers essential tools, frameworks, and strategies to effectively implement event sourcing in both your development processes and organizational strategies.
Whether you're new to event sourcing or looking to deepen your understanding, this episode offers invaluable insights and practical advice to help you navigate this complex but rewarding architecture. Tune in to learn more about how event sourcing can transform your approach to managing application changes, ensuring scalability, auditability, and minimizing regressions. Don't miss out on this opportunity to hear from experts in the field and discover how to leverage event sourcing for your next big project!
Socials
This week the panelists dive into their work backgrounds and discuss the ins and outs of working at small and large companies. They aim specifically at whether one is better than the other for building a career.
Picks
React Hook Form is a terrific way to manage state in, from, and through, your forms in React. Since React itself doesn't give you much to manage forms, React Hook Form steps into the gap to help you manage your forms and provide features and functionality to your forms.
Our guest, Vijit Ail worked through several of the options out there for managing states and walks the panel through his decision to use React Hook Form.
Links
In today’s show, frontend engineer Tyler Hawkins shares his tips on how you can write clean, maintainable and readable code. Using the examples from his article on the same subject, he explains the importance of using clean code principles to make it easier for different developers to collaborate on a codebase. Tyler also discusses how you can better structure your tests and have more confidence in how they are written.
Links
In this episode, Lucas, Chris, and Peter are joined by Colby Fayock, the Director of Developer Experience Engineering at Cloudinary and a content creator.
Join them as they dive deep into the world of AI-powered WYSIWYG editors for React. They explore the practicality of running AI models locally versus on remote servers, discover Google's innovative browser-based AI models in Chrome, and discuss the versatility and editor compatibility with formats like JSON and Markdown. They also touch on integrating AI functionalities securely using serverless functions and backend APIs, ensuring solid security without exposing sensitive API keys.
Colby shares his experience with using storage formats like HTML and JSON in richer content editors, the flexibility of customizing styles and commands, and the potential applications outside of just being a Notion alternative. They also delve into UX trends toward integrated editing experiences and the practical challenges it may present.
Towards the end, Colby talks about his upcoming full stack Next.js 15 course featuring authentication, database management, and payment options. This episode is packed with valuable insights for developers aiming to enhance their front-end capabilities and integration of AI functions. Stay tuned as we unravel the future of rich-text editing and AI in modern web development.
Social MediaUnvoid
Chris Laughlin joins the round up to discuss how to use the WebKit Speech Recognition API to interact with your react applications. This opens up a wide range of capabilities for web and React applications.
Links
In today's episode, they dive deep into the intricacies of creating a seamless image zoom functionality with our special guest, Robert Pierce, a seasoned software engineer with 13 years of experience and the mastermind behind the popular React Medium Image Zoom library.
They tackle the challenges of zooming in on images while maintaining quality, elaborate on accessibility concerns, and discuss the technical hurdles, including those pesky Safari issues. They also explore the efforts to make clickable content accessible to all users, converting images into modal elements, and the journey from version 4 to version 5 of the library.
Robert shares his experiences with maintaining this open-source project, the community's role, and his attempts to create a monorepo supporting various frameworks. We touch on the complexities of scaling, customizing dialog elements, and the potential future developments for the project.
Join them as they discuss the blend of native functionalities, accessibility, and the pursuit of a perfect user experience. Whether you're a developer interested in modern technologies, web component integration, or just curious about the behind-the-scenes of an open-source project, this episode has something for you. Let's zoom into the details!
Links
In this episode, they dive deep into the intricacies of deploying server-side rendering applications using Next.js on AWS. Join them as Brandon Bayer, the CEO of Flightcontrol shares insightful experiences on overcoming production challenges with FlightControl.
Discover why FlightControl's infrastructure, cost-saving capabilities, and new build system—including Lambda support—are game changers for developers. They talk about updates and exciting projects from Lucas and Chris, explore the seamless deployment to AWS with FlightControl, and compare its strengths against platforms like Heroku and Vercel.
Get ready for a captivating discussion on hybrid clouds, vendor lock-ins, the ease of using AWS services through FlightControl, and the potential for supporting other cloud providers. Plus, Brandon's passion for flying small planes brings a fascinating real-world perspective to the intricacies of sky-high ambitions versus ground-level developments. Tune in for an episode packed with practical insights, expert opinions, and the latest in cloud deployment technology.
Links
In today's episode, our host Lucas Paganini sits down with special guest Paul Bratslavsky, a seasoned software engineer at Strapi, to explore the powerful synergy between Strapi, a versatile JavaScript-based headless CMS, and the cutting-edge features of Next.js. Dive into the rapid development capabilities these technologies offer, streamlining workflows, and quickly delivering products to clients.
They also delve into the convenience of Strapi Cloud for effortless app deployment and discuss varying perspectives on its pricing. Tune in to hear about the benefits of Remix, the evolving job market post-pandemic, and invaluable career advice for aspiring developers. This episode is packed with practical insights, personal anecdotes, and expert tips that you won't want to miss. Plus, get a sneak peek into upcoming soccer games and learn about Unvoid’s client-friendly approach to software development. Join them for a well-rounded discussion on all things tech, career, and beyond!
Socials
In today's episode, they dive deep into the evolving landscape of mobile development by comparing React Native and Capacitor, two pivotal technologies for transforming web code to run seamlessly on mobile devices. Special guest,
Jamon Holmgren, CTO and co-founder of Infinite Red, brings a wealth of knowledge to the conversation, offering insights and firsthand experiences with these tools.Join them as they thoroughly discuss the considerations for choosing between Capacitor and React Native, based on your team's makeup and business needs. They explore the benefits of using Ionic and Capacitor for organizations that favor Angular, and why React Native might be the go-to for those who work with React. They also share valuable information on the Chain React conference, the various content offerings through Infinite Red, and best practices for integrating over-the-air updates.
Additionally, Jamon touches upon intriguing experiments with Yacht testing, and they highlight the exceptional remote design and software development services provided by Envoy, especially their unique payment model that ensures client satisfaction.
If you're navigating the complexities of mobile development, this episode is packed with expert advice and actionable insight.
Socials
Chris Laughlin joins the round up to discuss how to use the WebKit Speech Recognition API to interact with your react applications. This opens up a wide range of capabilities for web and React applications.
Links
Levan Katsadze is a Software Developer. In this episode, they explore a fascinating project, which offers migration rules for moving websites, emails, and databases between hosts. They talk about the tool's functionality and bugs encountered during testing.
Additionally, they shed light on the user-friendly nature of the software and discuss their VS Code extension block, emphasizing the importance of code structure for developers. They delve into the world of web components and upcoming support for web components in React 19.
The episode features discussions on the release of Angular 18, the state of the HTML survey, and the state of the JavaScript survey, as well as valuable insights from Levon Kasatze, who developed a software package to analyze and clean up Gmail mailboxes. Tune in for an insightful and engaging discussion on software development.
Social Media
Unvoid
Cagatay Civici is the founder of PrimeFaces, PrimeNG, PrimeReact and PrimeVue. In this episode, they delve into the world of UI component libraries and the business of open source. Join them as they explore Primetech's journey from consulting work to a thriving team focused on UI component development and the value of selling a library of components with a premium paid version. They also take a closer look at the tailored features and commercial aspects of the Primary Act library and gain insights into creating and monetizing open-source projects. With a focus on UX, product launch strategies, and ongoing development, this episode offers a wealth of knowledge for developers and entrepreneurs navigating the world of open source and library monetization.
Links
Jamon Holmgren is the Co-founder & CTO at Infinite Red, Inc. They dive into the captivating world of React and React Native, exploring the evolution of these technologies and their implications for developers. They engage in thought-provoking discussions on deployment challenges, user expectations in mobile app development, and the intricate process of integrating React Native into existing apps. Join them as they dissect the nuances of React Native, compare it to other frameworks like Flutter, and unravel the complexities of managing dependencies in React Native projects. From success stories to industry insights, this episode offers a wealth of knowledge for developers navigating the realm of web and native mobile development.
Socials
In this episode, The panelist of React Round-Up, View on Vue, Adventures in Angular, Ruby Rogues, and JavaScript Jabber speak with Sean Merron about Mastermind Groups of Startups and much more. Sean is the founder of today's topic and product “Mastermind Hunt.” This product is design to skillfully find a mastermind to take your business and skills to the next level.
Sponsors
In this episode, the panelists talk with Ben Nelson who is a co-founder and CTO of Lambda School. The panelists and Ben talk about Lambda School, the pros & cons of the 4-year university program for developers, and much more. Check it out!
Sponsors
Evan Rusackas is a UI/UX designer, front-end developer, and data visualizer. They delve into the world of open-source development and commercialization. They explore the differences in managing open source and closed source code bases, the complexities and advantages of selling a commercial version of an open source project, and the challenges and rewards of earning money from open source work.
Evan shares insights into the governance and code base management of the Apache Software Foundation, the creation of preset.io to address the needs of Apache Superset users and the commercial features offered by preset.io. They also touch on the benefits of using Apache Superset for business intelligence and data visualization, as well as the workflow for a related React-centric project.
Join them as they uncover the intricacies of open-source development, the evolution of Apache Superset, and the journey of Preset as they explore the intersection of open-source and commercial software.
Sponsors
In this episode of React Round Up Charles Max Wood hosts a solo podcast sharing his perspective on designing your perfect life. In this episode he addresses finding your dream job, building your dream life, and staying current. Start by deciding where you want to end up. Do you see yourself retiring? Working forever? Charles shares his vision for his future and discusses the retirements of others in his life.
Working back from the end of your life, Charles has you ask yourself what kind of life and career you want. Charles shares his vision for both his personal life and his career. After you pick your goal, build the skills, and knowledge to reach that goal. He uses the example of becoming a speaker at conferences. He also recommends you find a mentor or someone who has done what you want to and get their help.
Charles explains how important it is to get out of your own way mentally. Many people find reasons real or imagined as to why they can’t reach their goals. He agrees that the world is unfair and barriers can be real. The best way to show others they can overcome barriers is by doing it yourself and working towards your goals. You can if you believe you can and you work for it.
Sponsors
Max Stoiber is the CEO at Stellate. They delve into the open-source versus closed source debate, featuring insights from prominent figures in the tech industry. From the challenges and complexities of transitioning from engineering to leadership to the evolution of open-source contributions and community support, this episode covers a wide range of compelling topics. They also explore the success and challenges of open-source businesses, with a focus on their sustainability in a global digital landscape. Get ready for an engaging conversation that delves deep into the world of open source, business models, and the future of technology.
Sponsors
Monica Lent has been interested in software from a very young age, and made her first domain name when she was 9 years old. She left her job and founded a startup, analytic tool designed for bloggers designed around affiliate marketing. She talks about some of the lessons she’s learned, including how to sift through data and how to make it useful for people.
The panel discusses how to distill the priorities from the project manager so you know where to spend your time, something that takes a lot of experience and failure. They also talk about the merits of different practices such as whether or not to deploy on Friday and having engineers on call. Monica explains her opinion on how copying and pasting code instead of adding dependencies is a positive constraint. She prefers this method most of the time but not in all cases because it keeps your code flexible and avoids unnecessary specialization. However, she is not advocating for copy/paste over dependencies in every situation : rather the point comes down to using copy/paste instead of inappropriate coupling.
They also dive into how so much programming deals with other people and the importance of keeping your ego out of it when designing constraints, especially since developers hate other developer’s abstractions. They debate whether pride is a characteristic of junior or senior developers. They note that it is easier to get prideful and opinionated when you’re not working on a team.
Sponsors
Gilad Shoham is a developer and open-source leader at Bit. They dive deep into the world of software development. They share insights on the shift from building R&D structures around applications to focusing on components. Discover the philosophy and methodology behind the transformation of feature development, and explore the technology's language-agnostic nature with specific language features. Alongside discussions about component lifecycles and versioning, learn about the challenges and potential solutions of using design systems, as well as a new type of CI system aimed at component-level testing and propagation of changes. Join them as they explore the plans for supporting non-JavaScript languages and delve into cutting-edge developments in component reuse, speed of development, and consistency.
Sponsors
Lucas, Peter, and Chris delve into a fascinating discussion about functional programming, its application in the industry, and personal experiences working with related tools and technologies. From exploring the knowledge gap in functional programming to sharing anecdotes about learning new languages, they provide valuable insights into the world of functional programming. They also touch on the challenges and benefits of adopting functional programming techniques in development, along with recommendations for resources and tools in this space. Join them as they embark on a deep dive into the world of functional programming.Sponsors
LinksSocial MediaUnvoidMohammad Bagher Abiyat is a senior full-stack developer & consultant. He is the co-founder of XQuad and Pheno Agency. They engage in a detailed discussion about Jotai, a library designed for atomic state management in React. They also delve into comparisons with established state management libraries like Redux, exploring the intricacies of Jotai's organization and architecture.Whether you're a seasoned developer or a tech enthusiast, this episode promises to deliver valuable insights and thought-provoking discussions on the evolving landscape of state management in React applications.Sponsors
Dmitriy Kovalenko is a software engineer. They explore the practical considerations and implications of using UI systems such as Material UI and Radix for various web applications. They engage in insightful discussions about the delicate balance between time, money, and personal preference when selecting a UI system and the potential future concerns for frameworks, shedding light on the challenges and opportunities in the UI development landscape. Join them as they unravel the complexities of UI customization, accessibility, and the essential need for flexibility in choosing the right UI framework.
Sponsors
Today we talk with Chris Frewin, a full-stack software engineer at private experience startup InClub, located in Zurich, Switzerland. Involved with all coding aspects, from the back-end, mobile app, CMS, and everything in-between, we learn about the challenges of being a solo developer at a startup. We learn a lot about Gherkin, the format for cucumber specifications.
Sponsors
Chris, Lucas, and Peter dive into the world of UI libraries and the important considerations when selecting one for web development projects. They discuss the pros and cons of using popular libraries, emphasizing the importance of accessibility, internationalization, and long-term implications when making a choice. They also share their preferred libraries and promote their projects, providing valuable insights for developers navigating the diverse landscape of UI libraries. Stay tuned for an engaging discussion on the challenges and best practices of utilizing UI libraries for web development.
Sponsors
Dean Radcliffe is a senior software engineer at Optum. They explore the groundbreaking new library 𝗥𝘅𝑓𝑥, designed to revolutionize the handling of asynchronous effects in code for enhanced user experience and code stability. They lead a discussion on the significance of cancellation, concurrency, and error recovery for user experience and code stability, drawing analogies to a circuit breaker panel for managing async effects in code. They delve into practical implementations, the framework-agnostic nature, and the potential of 𝗥𝘅𝑓𝑥 in simplifying reactivity features within React.
Sponsors
Chris, Lucas, and Peter engage in a deep technical discussion about package managers, testing tools, and technology preferences in React projects. The conversation emphasizes the extensive tech stacks used in React projects and the importance of functional programming and TypeScript. Additionally, they share valuable insights on UI libraries, JavaScript packages, and software and design team extension services, hinting at the potential for a future follow-up episode dedicated to front-end technologies. Whether you're a seasoned developer or a newcomer to the field, this episode offers in-depth insights into the ever-evolving world of front-end development.
Sponsors
In today's episode, the panel of experts delves into the intricate world of reactivity in JavaScript frameworks. They explore Angular's signal-based approach, React's virtual DOM and hoisting, and how libraries like RxJS and Redux handle reactivity. They also discuss the absence of a universal standard for reactivity in JavaScript and the challenges it presents for developers. Join them as they unravel the complexities of reactivity and its impact on modern application development.
Sponsors
On this episode of React Round Up we chatted with Miroslav Nikolov, a UI developer at one.com, about his approach to unit testing React components. Miroslav discussed writing components in a human-friendly way, using the library UnexpectedJS. We also talked about Miroslav’s blog, including how he got started with it, and some of the tools he used, like Gatsby and Mailchimp. This is a great episode if you’re looking to learn more about how to approach unit testing in React.
Sponsors
Charles, Lucas, and Peter dive deep into the world of software development and React programming. They explore the intersection of artificial intelligence and the daily work of React developers. They discuss the benefits and challenges of using AI tools such as Copilot, the nuances of turning designer files into code, and the potential impact of AI on web development. Stay tuned as they discuss the role of AI as a learning tool, the importance of accessibility, and their recommendations for tools and resources for developers.
Sponsors
They delve into the realm of software development, with a focus on React best practices. In this episode, they dissect the intricacies of component structuring and file management, emphasizing the nuances of design patterns and the prudent use of Redux for state management. Tune in for a deep dive into these critical aspects of development and stay ahead of the curve in your software engineering journey.
Sponsors
Welcome to the new set of panelists for the React Round Up podcast. Chris Frewin is a full-stack software engineer. Peter Osah is a full-stack software engineer. Lucas Paganini is a senior front-end Engineer.They delve into the world of software development and system architecture. They explore the nuances of vendor lock-in, migration strategies, and the diverse perspectives on deploying single-page applications. Additionally, they share their experiences with various tools, platforms, and cloud providers, shedding light on the challenges and best practices in the ever-evolving landscape of software development.
Sponsors
Returning guest Mark Erikson joins the React Round Up team to discuss how he found himself in the position of being an open source maintainer for Redux, how he's helped shepherd/author future versions of Redux (and the complete overhauls that happened when React Hooks were introcuded), and the new examples he's written for Redux Toolkit to make Redux easier for devs to get started with. Mark also addresses some commons misconceptions around React and Redux, such as: is React Context a perfect substitute for Redux (spoiler: it's not), and is Redux still relevant today (it is). Take a listen to hear about getting into open source, where Redux is headed and Mark's broader thoughts on helping the React community document and standardize all the options out there so developers have an easier time choosing the tools needed to solve their particular problems.
Sponsors
Today the panel is discussing how to introduce new tech at work. They agree that it’s important to get input from all teams on the decision, although it will primarily affect the development team. One should also consider the different ways people make decisions, such as through discussion or quiet thinking, and give everyone time to come to a decision. The panel talks about positive and negative examples of how to introduce new tech at work. Thomas believes that it is important to acknowledge your own biases in decision making and to try to avoid them. The React experts discuss the significance of the team dynamic and the necessity of different roles in decision making or if it is better to have an organic discovery phase. This relates to Thomas’ point about personal biases, and he believes that it is important to put people in roles that are opposite of their personality. When making decisions about new technology, it is also important to note that not all decisions require the same amount of input, and they discuss how to measure how much input is required for a decision.
Sponsors
Zain Sajjad is a frontend developer at his company Peekaboo Guru, an app built in React. The show begins with Zain explaining why he chose to build Peekaboo Guru in React. Ultimately, he chose React for its composability and reusability. He talks about how much data is shared between his React and React Native applications.Zain explains what he means by a container since he is not talking about Docker, and how he has the app organized. He talks about the differences between routing and navigation between React and React Native. When approaching these differences, he breaks things down into components, containers, and platform, paying careful attention to how they work together. This differentiation can actually help a lot with testing as well.
Sponsors
In this episode of React Round Up, the panel talks with Kay Plößer, describing their experiences learning React. Kay is a software developer from Stuttgart, Germany and the author of the book React from Zero. They discuss the best approach to learning React from scratch. Kay describes the process of writing and producing his book 'React from Zero'. Initially he started with tutorials and lessons and then turned those into a book. It is constructed in two sections: basic and advanced and it's purpose is to help developers learn React without being overwhelmed. He has received great feedback from the people who have bought the book.Kay then describes his experiences teaching React to developers and talks about his blog post React Hooks Demystified which became really popular. The panel then about how developers can increase and diversify income through writing books and side projects.
Sponsors
David Khourshid is the author of a library called Xstate, He has been a developer for 7 years, currently works for Microsoft, his passion is frontendTalks a. In college, he actually studied piano performance, and so he talks about how he got into programming and where he started. The panel discusses his unique husky animation and how he came up with the idea for it and went about programming it.
The panel discusses what a state is in React. David defines a state as a moment in time. States can change, when they do, that’s a state transition. They talk about the utility of states and thinking about your app as a state machine. They agree that describing your code as a state machine makes it easier to communicate and connect with non developers. The panel discusses the importance of learning from other industries, such as approaching programming the same way construction workers build a house. They debate the Waterfall versus the Agile mindset.
They talk about the advantages of programming in React and focusing on the state machine, especially because it is important to be intentional about dealing with concepts separate from other concepts. They share different ways to switch to state machine thinking, one of which is to look at your event handlers and make sure they are doing anything besides dispatching events. David talks about his library called Xstate and the basics of his library and his inspiration, and who else is working in state machines. The finish by discussing industry standards.
Sponsors
In this week’s episode of React Round Up the panel works their way through a blog post outlining best practices for React. The first is “keeping components small and function-specific”. The panel discusses the pros of using this best practice and how it relates to the single responsibility principle. This best practice also helps with the next, “reusability is important”.The panel considers this second best practice and points out some of its flaws. It recommends avoiding the creation of new components. The panel explains that by avoiding creating new components it saves time but can also cause problems as you adapt components to fit more projects.
Sponsors
Front-end developer Maksim Ivanov talks about working for Mojang, the company behind the ridiculously popular game Minecraft. As it turns out, Maksim uses React to build different pieces of the game, and runs the code through a custom renderer to make it work in the game world. In addition to his day job, he also found time to write a book about TypeScript after realizing how much easier getting familiar with new code bases could be if TypeScript was used instead of JavaScript. The panel has used TypeScript to varying degrees themselves, but nobody's gone all in, and they talk about the pros and cons of it, including the initial learning curve and how it can help prevent bugs in the code. Maksim's book covers many aspects of TypeScript in great detail, and it sounds like a good read for anyone just picking up the language.
Sponsors
Today we talk with Fred Schott, the co-creator of Astro, a web framework focused on improving performance. Built around island architecture, it leverages HTML over javascript where it’s an option. Astro is a great option for those who focus on content, marketing, or personal blogs, and it is a great option to use with React. In this episode, we talk about when it makes sense to use Astro, and how to implement it.
Sponsors
In today's episode, we talk about state management, dependency injection, react hooks, API access best practices and more with Tommy Groshong a React UI architect.
Sponsors
Software Engineer Andrey Goncharov joins the React Round Up crew to discuss how his company Hazelcast has approached visualizing hundreds of data points on potentially hundreds of computers in a way that makes sense to users. Dust off your math skills - it gets a little technical along the way as they discuss graphs, charts, performance optimizations, and bottlenecks, and even handling accessibility of these data-intensive graphs. If you ever have to debug system failures and anomalies, this will be a worthwhile episode to check out.
Sponsors
Tania Rascia joins the round up to discuss how to organize your code across files, directories, components, and repos within your React app. The panel chimes in with what they've seen and clarify how these approaches effect the overall application functionality of your app.
Sponsors
Software engineer Pierre Hedkvist joins the React Round Up panelists to share some spicy (controversial) coding decisions he's made and then written about. The first hot topic is using React state to store filter setting in query parameters with the help of a custom Hook, and the second is migrating an app to rely more heavily on React Query instead of Redux.
If you've been considering doing something similar, give this episode a listen to hear Pierre's strategies and advice for anyone looking to get started.
Sponsors
Collin Pfeifer, writer, software engineer, and student at Indiana University joins the React Round Up panel to discuss the intricacies and pitfalls in Create React App, the roadmap of being a self-taught developer, and how the computer education system has changed over the years.
Sponsors
Jack, Paige, and TJ join this week's panelist episode to talk about Figma. Figma is a web-based design tool. Jack takes the lead as he talks about its new exciting features, how this tool benefits the designers, what sets it apart from competing design tools, and many more!
Sponsors
Peter Osah is a Fullstack Software Engineer, Technical Writer, and a Biochemist & Bioinformatics Enthusiast. He joins the show to talk about his article, " Bootstrap your next Preact application with Bun". He begins by giving the listeners an introduction to Bun and its advantages.
Sponsors
Oluwaseun Raphael Afolayan is the Co-Founder of MyTherapist.ng, Technical Author, Fullstack Mobile Engineer, and eSports Gamer. He joins the show to talk about Firebase. He discusses the services that Firebase offers and why he chose it.
Sponsors
Hosts from the JavaScript Jabber podcast, AJ O'Neal and Dan Shappir join this week's crossover episode. They begin by giving a brief introduction of themselves. They talk about how to become a web developer and their perspective on being a web developer. Additionally, they discuss creating open-source projects.
On YouTubeWhat It Takes To Be A Web Developer: Part 2 - RRU 222
Sponsors
Hosts from the JavaScript Jabber podcast, AJ O'Neal and Dan Shappir join this week's crossover episode. They begin by giving a brief introduction of themselves. They talk about how to become a web developer and their perspective on being a web developer. Additionally, they discuss creating open-source projects.
Sponsors
Chirag Dugar is a Software Development Engineer - II at Javis. He begins the show by talking about transitioning from being a college student to a Software Developer. He also shares his past learnings in coding and making connections during his internship. Moreover, he discusses his React projects, his experiences in creating those and his challenges.
Sponsors
Sami Jaber is a Software Engineer at Builder.io. He joins the show to discuss "Implementing CSS Style Inheritance in React Native". He starts by talking about the inspiration behind the article's concept. He also talks about Mitosis, how to use it, and its features.
Sponsors
Bruce A. Tate is a Founder at Groxio, Elixir Expert, and a Technical Author. He joins the show alongside Charles Max Wood to talk about his book, "Seven Languages in Seven Weeks". He also delves into some of the preparations and anticipations that come with reading the book.
Links
Levan Katsadze is a React.js TypeScript developer and Author of VS Code extension "Blockman". He joins the show alongside Jack, Paige, and TJ to talk about Blockman. He starts off by defining it and describing how it functions. He also talks about the reason why he built the VS Code extension and the process of creating it.
Sponsors
Are you dissatisfied with your job? Sam Feeney helps organizations improve employee engagement, increase retention, and reinvent hiring while helping individuals (re)discover career satisfaction in their current roles. He joins the show alongside Chuck Wood to tackle altering the way you perceive your job and talk about Career satisfaction.
On YouTubeHow Do You Stop Hating Your Job? - BONUS
Socials
Simon Grimm is a Creator, Indie Maker & Solopreneur. He is currently working at The Ionic Academy. He joins the panel to talk about React Native and Capacitor. He starts by explaining how a "Capacitor" contributes to your web application. They talk about how to build web applications with a capacitor and how it differs from using a React Native.
On YouTubeCreating Apps with Capacitor and React Native - RRU 217
Sponsors
Hosts of the Adventures in Angular podcast, Chuck Wood and Lucas Paganini, join the React Round Up Panel on this week's episode crossover. They begin the episode by contrasting the two frameworks and offering their own viewpoints on React and Angular. Additionally, they explain each of the frameworks' strong points.
Sponsors
Sean Austin is the CEO and Co-Founder of Helios. It is pioneering speech analytics for Wall Street. He joins the show to explain more about his company's background, how it got started and some of the factors they consider that have an impact on the company. He also discusses the services they can provide to their clients.
Sponsors
Jack, Paige, and TJ join this week's panelist episode to tackle all things React and their take on different frameworks. They start off by talking about the pros and cons of "Create React App". They also discuss the Typescript 5.0 features and the SvelteKit, which was just released.
On YouTubeThe React Universe - RRU 214
Sponsors
Giulio Zausa is a Software Engineer at Flux. They build next-generation collaborative tools for hardware design. He joins the show to talk about his projects on Flux. He also shares some of his tips and experiences on how to improve your application performance. Moreover, he dives into what the react-three-fiber library is all about and its functions.
About This Episode
Alex Olivier is a Product Lead at Cerbos. It is a self-hosted, open-source authorization layer that separates your authorization logic from your core application code. He joins the show to talk about the company in more detail and what it can offer to its users. Additionally, he explains the process of Testing and Setting it up.
About this Episode
Sam Magura is a Software developer at Spot. He joins the show alongside, Jack and TJ to talk about his article, "Why We're Breaking Up with CSS-in-JS". He was the second most active maintainer of Emotion, a widely-popular CSS-in-JS library for React. But realized it came with a big performance cost and added unnecessary complexity. He describes the specific inefficiencies that he has encountered while using it and how he came to realize them. Moreover, he talks about his solution to these performance problems.
Sponsors
Jack Franklin is working on Chrome DevTools as a Frontend Engineer at Google. He joins the show to talk about his article, "Why I don't miss React: a story about using the platform". He explains why he wrote his article and about his experience working with ChromeDevTools. Additionally, he dives into the advantages of Web components and its difference from React. He tackles all of the key points of his article.
Sponsors
Talking about their 2023 Hot Takes and predictions, Jack, Paige, and TJ tackle this week's Panelist episode. They discuss their hopes for this year as well as potential improvements to the various languages and technologies. Additionally, they also dive into some of the software development tools and share their recommendations and expectations for them.
Sponsors
Collin Pfeifer, writer, software engineer, and student at Indiana University joins the React Round Up panel to discuss the intricacies and pitfalls in Create React App, the roadmap of being a self-taught developer, and how the computer education system has changed over the years.
Sponsors
Chromatic developer experience engineer Shaun Evening joins the React Round Up hosts to talk about all the new features rolling out with the release of Storybook 7.
Have you ever wanted to combine your Storybook integration with Material UI, Ant Design, or any other component library? Well, Storybook's making it easier than ever, and that's just the beginning. A new offering called Integrations allows users to add all sorts of plugins to their Storybook workflows for even more functionality, and has "recipes" to help you get the most out of your Storybook.
Follow Shaun on Twitter for all the latest and greatest happening at Chromatic: https://twitter.com/Integrayshaun
Sponsors
Sebastien Lorber, Docusaurus maintainer at Meta and This Week in React newsletter creator, joins the React Round Up panel to discuss the latest and greatest in React 18, including lesser-known hooks and features that are making the framework more useful and performant than ever before. He also deep dives into why Docusaurus (maintained by Meta/Facebook) has become such a popular static site generator for companies and dev teams in all industries to document their products, APIs, software, and more.
Learn more about the most exciting new developments in the React ecosystem by listening now and stay up to date with new developments by signing up for Sebastien's free This Week in React newsletter.
Sponsors
The React Round Up panel joins the show as Jack takes the lead to talk about the various improvements made in the React Ecosystem. Additionally, they offer their thoughts and insights on these updates and share their potential value to the developers. They also talk about whether these features have an impact when used in apps.
About this Episode
Get the Black Friday/Cyber Monday "Focus Blocks Bundle" Deal Coupon Code: "THRIVE" for a GIANT discount Are you looking at all the layoffs and uncertainty going on and wondering if your company is the next to cut back? Or, maybe you're a freelancer or entrepreneur who is trying to figure out how to deliver more value to gain or retain customers? Mani Vaya joins Charles Max Wood to discuss the one thing that both of them use to more than double their productivity on a daily basis. Mani has read 1,000's of productivity books over the last several years and has formulated a methodology for getting more done, but found that he lacked the discipline to follow through on his plans. The he found the one thing that kept him on track and made him so productive that he is now getting all of his work done and was able to live the life he wants. Chuck also weighs in on how Mani's technique has worked for him and allows him to spend more time with his wife and kids, run a podcast network, and a nearly full time contract. Join the episode to learn how Chuck and Mani get into a regular flow state with their work and consistently deliver at work.
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
Returning guest, Ian Lavery from Picovice.ai, joins the hosts to talk all things voice recognition. He dives into new languages the company has tackled over the last year (and what languages it plans to tackle next year), how they train their models, and how Picovoice is actually running speech recognition in the browser instead of in the cloud, making things like captioning live streams and real-time chats possible with some of its newer tech Cheetah and Leopard.
He also shares how he wrote a simple podcast transcription app using Picovoice and Express.js, in addition to Picovoice boasting specific SDKs for React, Angular and Vue.
Listen to Ian's first appearance on RRU here where he and the panel went deep into the specifics of voice recognition like security and privacy, understanding it in general, and using it sans big cloud providers.
Sponsors
Nirmalya Ghosh joins the React Round Up panelists in this episode to talk about how he migrated a monolithic Ruby on Rails application to React. What was estimated to take 3 -6 months ended up taking about 2 years, and Nirmalya shares all the hard-won lessons he learned along the way for any listeners who might be preparing to make a similar upgrade. Additionally, he talks about the company he currently works for and how they're trying to become the one-stop shop for anyone looking for a good API online. Lots of interesting tidbits are packed into this episode!
Sponsors
Software engineer Pierre Hedkvist joins the React Round Up panelists to share some spicy (controversial) coding decisions he's made and then written about. The first hot topic is using React state to store filter setting in query parameters with the help of a custom Hook, and the second is migrating an app to rely more heavily on React Query instead of Redux.
If you've been considering doing something similar, give this episode a listen to hear Pierre's strategies and advice for anyone looking to get started.
Sponsors
Return guest Vijit Ail joins the cast of React Round Up to talk all things Supabase. If you've ever used Firebase and wished it was open source, this is the episode for you. Vijit espouses all the cool things Supabase offers like schema definitions, edge functions, data streaming, and more. There's so much good info chocked into this episode, listen to learn how to get started with Supabase today.
Sponsors
In our 200th episode of React Round Up, the panelists take a look back at how their first appearances on RRU and how they came to be on the show. In addition to advice on how they got to where they are now, they also highlight some of their favorite guests who've graced RRU with all sorts of great React knowledge over the years and offer advice on how you can get started on your own tech podcast or (hopefully) be invited to join an existing one.
Here's to 200 more episodes!
Sponsors
Gleb Bahmutov, who worked with the Cypress.io team for 4 years, joins the panelists to talk all things testing. You may be familiar with Cypress as a popular JavaScript end-to-end testing framework, but did you know it recently began offering component testing as well? This may be just the incentive you need to ditch Jest and Testing Library for unit/integration tests and go all in on Cypress for all your testing needs. Listen up and let us know if you're convinced.
Sponsors
Today we talk with Fred Schott , the co-creator of Astro, a web framework focused on improving performance. Built around island architecture, it leverages HTML over javascript where it’s an option. Astro is a great option for those who focus on content, marketing, or personal blogs, and it is a great option to use with React. In this episode we talk about when it makes sense to use Astro, and how to implement it.
Sponsors
In today's all panelist episode we address web development controversies: state management tools, CSS in JS, GraphQL or REST, and, of course, tabs versus spaces. And the rule is: there's no saying "It depends." Listen to the panelists take hard line stances on things that matter (and things that don't), and try to defend their choices. It's a fun episode for everyone, and we'd love to hear about your own controversial coding decisions.
Sponsors
Today we talk with Chris Frewin, a full-stack software engineer at private experience startup InClub, located in Zurich, Switzerland. Involved with all coding aspects, from the back-end, mobile app, CMS, and everything in-between, we learn about the challenges of being a solo developer at a startup. We learn a lot about Gherkin, the format for cucumber specifications.
Sponsors
In today’s all-panelist episode, we discuss many ancillary skills that you might be tempted to avoid learning but are very beneficial to know. Included in the conversation are CSS, DNS & HTTP, caching, API styles, knowing how to interact with back ends and databases, and command line.
Sponsors
In today’s episode we talk with Atila Fassina, a developer experience engineer working at Xata. As a fan of both, Atila compares Next.js and Remix, comparing their similarities and differences.
We also talk about how Xata makes dealing with databases more comfortable. This server-less database, which is hidden behind an API, provides users with some nice abstractions, such as instant migrations, and analytics and a search engine right out of the box. Our discussion includes partial routing, Remix mutations, and layout RFC.
Sponsors
Today’s guest, Tommy Groshong, walks us through some questions to consider when thinking about pursuing a higher-level role. After a second go-around into management, we get some insight into how the culture can be very different at higher levels and the importance of having good questions to ask. We talk about two separate tracks you could pursue based on your skills and desires, and how to handle the requirements of management and stay connected with your coding craft and new trends in the industry.
Sponsors
Jack leads us through some of the history of how we got to where we are with client side rendering, and how island architecture helps to reduce the workload handled on the client-side. We talk process and tips on transitioning to Islands Architecture, and in the process talk about BUN, Fresh, and other island architecture frameworks.
Sponsors
Today we talk with Travis Waith-Mair, a senior software engineer at Plex, and creator of Bedrock Layout Primitives library. Bedrock layout allows you to build a complex layout without with reusable components without needing to be an expert at the underlying CSS. We talk about the success of his library, and along the way discuss Lerna, a tool for JS Monorepos, and the AVO (Attributes Verbs and Objects) and method.
Sponsors
Today we talk with Florian Rappl the creator of Piral, a next generation portal applications, which utilizes microfrontend architecture. Piral is all about scalability, allowing easy reusability between multiple teams. We learn of the background of how it was developed, and how out of the box it comes with bundles customized to your industry. We discuss when it makes sense to use microfrontend based on client requests and needs, and give some tips on when to start incorporating it.
Sponsors
Today we talk with Dillion Megida, a developer advocate and content creator originally from Nigeria, but living in the Netherlands. We discuss his blog article about the aspect ratio property in CSS. Much of his effort at a developer advocate is writing articles and creating video content to promote the products for Stream, where he currently works. He gives us his insight on preparing for and pursuing the developer advocate role at a company. We also discuss debouncing in JavaScript, which helps to reduce unnecessary expression executions.
Sponsors
Today Jack and TJ talk with Adam Berg, VP of Engineering at Dubsado. We discuss an article he wrote based on lessons learned while his place of work was transitioning from AngularJS to React, called starting with How to Set Up Server Side Rendering (SSR) With React, express.js, and esbuild. We also discuss several of his other articles, including Hey Siri, We’re Breaking Up, and 3 Lines of Code Shouldn’t Take All Day.
Sponsors
In today’s all-panelist episode, we cover our favorite equipment from keyboards and mouse, to computers and monitors, from webcams to microphones.
Sponsors
Today we have special guest Jennifer Fu, a software engineer who specializes in front end development. Currently working at Domino Data Lab, she comes with 20 years of experience in many programming languages, but loves React! Much of her recent work is with Web3.js and Three.js. We discuss how to work with the 3D JavaScript library, and discuss how easy it is to use. As a bonus, we get some of her insight to excelling during the coding interview process. Make sure to check out her extensive library of articles at medium.com (link below).
Sponsors
In this all-panelist episode, we discuss Design Systems, what they are and why you might want one. As a great way to help companies to standardize the look and feel and behavior of their web applications across the enterprise, we discuss the challenges of implementation.
We also discuss how useEffect gets called twice when in developer mode and strict mode to test your component. It mounts it, un-mounts it, the re-mounts it - looking to see if there are leaks. What do we do about this?
Sponsors
Today we talk with software engineer Shubham Khatri, a front end developer at Meta. As someone who is really passionate about React, we discuss Strict Mode and Flock among other things. We also talk about his experience working for the company, insights on getting hired at Meta, and tips for getting a good response from developer help. Sponsors
LinksToday we talk with Steven Wittens with his personal site acko.net, and get a glimpse inside his creative efforts of taking parts of React to a new level to support his vision for graphics developments. We also talk about Live, his own React runtime, and his upcoming use.gpu. Sponsors
PicksIn this episode we have special guest front-end engineer and technical writer Samaila Bala from Nigeria. We discuss several use cases of the React design patterns he has written about, such as the Compound Components Pattern and Provider Pattern. He also discusses his Send Cash app, and how it allows people to transfer money internationally with more ease. Sponsors
Links PicksIn this special all-panelist episode, we discuss all things on how to stand out! We’ll discuss everything from standing out in a crowd, standing out as a software developer, and how to get your name out there. We also talk about why this is an important topic to delve into. We’ll give you tips on finding success by choosing what you find interesting and fun, as well as tips to help you grow and get noticed. Sponsors
LinksEver wish you had some great advice before you needed it? In this panelists episode we talk all about red flags when interviewing with a new company, and things to look for and be aware of during the process. We look at some red flags in coding, and include some tips on finding good code. We look at red flags while working with teams, managers and difficult people, and the the red flags to look for on special projects. There are even a few red flags thrown in for life in general. Sponsors
Links PicksJack, Paige, and TJ give advice for Junior Developers. They pull from their own experience to break down the areas that Junior Developers may struggle with or not know that they need to focus on. Sponsors
PicksIf you're looking for a way to manage your CSS in JS in a super lightweight framework, check out Goober. The package is exceptionally small and keeps your bundle lean and mean. Cristian Bote joins the round up to wrangle this discussion on how to put CSS into your React application in a novel way. Sponsors
Links PicksThere’s a wild west of open source React out there, so let’s help you prepare. In this episode, the squad talks with Tanner Joseph Linsley, an open source React developer who’s got some wisdom to drop on how to do it right and build your community. “Honestly, a lot of the time, it’s about taking existing tools and shaping them into what I need them to be.”
_- Tanner Joseph Linsley _ In This Episode 1) The BIGGEST tools in React that you oughta know in 2022
2) How to use feedback effectively and fix mistakes quickly
3) The TRUTH around open-source in the dev community (and how to get started) Sponsors
Sometimes, the answer isn’t to code more. In this episode, the crew sits down with Chimezie Innocent, a developer who will show you how to clean up your act with UseEffect, as well as why this ONE thing dramatically improved his coding. “If you want to understand something better, the best advice I would give is ‘Just write about it!’”
- Chimezie Innocent In This Episode 1) Why UseEffect is CRUCIAL for avoiding a world of hurt in your cleanup
2) How to reveal how little you ACTUALLY understand a concept (and how to become a better developer fast!)
3) Some GO-TO tips for improving your writing, helping others, and getting paid to do something other than coding Sponsors
Nx is here to make your life easier. In this episode, Paige and TJ talk with Jack Hsu, a developer whose Nrwl and Nx expertise is blowing us away with how streamlined things can be. “It’s nice for everyone to see what’s going on, not just the core developers.”
- Jack Hsu In This Episode 1) What beginners NEED to know to get started with Nx this year
2) Why you’ll LOVE using a Monorepo in 2022 to maintain your sanity
3) The BIG 2022 trends around Next.js, Nx, and Nrwl you ought to know Sponsors
Let’s help you invest in your new CSS Property. (Get it?) In this episode, Jack and Paige sit down with CSS property extraordinaire, Colby Faycock, for React Roundup Round 2! They all discuss how to make CSS get along with React and others, what awesome things Cloudinary does, and how to properly enter the CSS world if you’re a React user. “React and CSS are two different concepts, but they can definitely play nicely.”
- Colby Fayock In This Episode 1) How to make CSS properties play nice with JavaScript and React
2) The BEST way for React users to enter the CSS world in 2022
3) Why companies like Cloudinary are showcasing THIS awesome part of CSS properties Sponsors
Could a flight attendant or lawyer become a developer? You bet! In this episode, the React Roundup team talks with Mikael (Mickey) Petersen, a flight attendant turned lawyer turned developer who believes your background doesn’t define you. They all discuss what you NEED to know about WebGL and canvasses, the pros and cons of Svelte vs. React, and the biggest developments that you should already be following. “I realized my passion is between problem solving and creativity. Coding is a creative outlet, and I always love learning new stuff.”
- Mikael (Mickey) Petersen In This Episode 1) Why Mickey believes ANYONE can become a developer regardless of their background
2) What you NEED to know about working with WebGL and canvasses in React this year
3) How Svelte is an EXCELLENT choice for starting out (but why React is better at higher levels)
4) The BIGGEST developments in 2022 that you oughta be following by now Links
Wanna forget the back-end and only focus on the front? Too bad. In this episode, the React team sits down with Mike Alche, a developer whose full-stack approach reminds us why you need both ends to succeed. They discuss the power of tRPC, what led Mike to AdonisJS (and why it should be more popular), and Mike’s go-to tips for becoming a master at API testing. “As develops, we love building products, but we need a place to put it. The back end’s not as trendy as the front end. That’s what ‘full stack’ means—everything together.”
- Mike Alche In This Episode
Next JS is next in line, but are you ready for it? In this episode, the Roundup rascals team up with Tom Norton, a software developer who’s as excited about Next JS as they are. They discuss the pros and cons, why it’s superior to apps like Gatsby, and why Tom believes studying accessibility is PARAMOUNT for the future. “Get ready for some opinions.”
- Tom Norton In This Episode
A new year brings new libraries and state machines, so if you’d rather not be confused, this episode’s for you. In this one, the team covers React’s most significant improvements, how to avoid losing your mind over state machines, and what libraries to peruse in 2022. In This Episode Why React’s improvements made THIS feature irrelevant for most cases
The team’s solution for people wanting more than just juggling API’s all day (and why it’s a big win for storage and data migration)
If you’re into spreadsheets, we bet you’ll LOVE using THIS library
Want to learn a new, intuitive library in 2022? Jack’s got you covered
How to avoid the NIGHTMARE of complication with state machines Sponsors
Interested to learn more about this “Great Gatsby”? How does it differ from others, and where is the industry headed? Time for a meeting with the Queen! In this episode, the React team sits down with Queen Benedicte Raae, a software developer and overall coding wizard. They discuss the ONE feature of Gatsby that makes it so beginner friendly, what Queen Raae learned from her years of Wordpress and web building, and where they believe the conversation of “no-code vs code everything” is headed. “If you need something content-heavy, Wordpress can be exactly what you need. But if you’re trying to make an application, you need something more intense. The internet is splitting between no-code vs ‘code everything’ solutions.”
So, you’ve followed up with a recruiter and have an interview scheduled tomorrow. Not sure what to do next besides print your resume? Don’t fret! In this episode, the guys sit down with Paige Niedringhaus to discuss the fundamentals of nailing your interview. They lay out the interview red flags that should scare you to your core, how to escape the “application blackhole”, and why the “STAR Method” is incredible for leaving an awesome impression. “If you don’t feel like you qualify, apply anyway. If it sounds interesting, just apply.”
Atila Fassina joins the Round Up to discuss how he got into Next and what he's doing with it now. The panel dives into the ins and outs of what you can do with Next and some advanced uses for the framework. Panel
Jack Franklin joins the Round Up from Google who wrote a side project using both React and Svelte. He breaks down the differences between the two frameworks and what he likes about each. In many ways, Svelte gets out of your way and is a lot of fun to use. However, React does give you some features that make development very nice. Panel
Giuseppe Gurgone joins the round up to discuss React Native for Web and how you can build one application with React Native and deploy it to the web and mobile. He and the panel go in depth on React Native and the ins and outs of using it to build web applications as well. Panel
Get the Black Friday/Cyber Monday "Double Your Productivity by 5pm Today" Deal
Coupon Code: "DEEP" for a GIANT discount Mani provides us with strategies and tactics to get Deep Work time and how to get our minds into that focused state for hours at a time. He has read hundreds of books that have taught him the secrets to getting more done by getting into this state. He starts by telling us how he was passed over for a promotion at Qualcomm in favor of someone younger and less experienced and how that inspired him to figure out what the other guy was doing differently. He learned that he needed to get more done with the time he was spending on his projects. The trick? Deep Work! Deep Work is the ability to spend uninterrupted, focused time on a task to bend your entire mind toward the goal. Other developers call it "Flow" or "the Zone." Mani provides us with strategies and tactics to get Deep Work time and how to get our minds into that focused state for hours at a time. Get the Black Friday/Cyber Monday "Double Your Productivity by 5pm Today" Deal
Coupon Code: "DEEP" for a GIANT discount
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
Chris Frewin joins the round up to discuss the project he worked on for a month and re-organized the code to bring it up to the state of the art. He discusses how to bring in TypeScript and the process for bringing TypeScript's and React's newer features into the application one step at a time. Panel
Tania Rascia joins the round up to discuss how to organize your code across files, directories, components, and repos within your React app. The panel chimes in with what they've seen and clarify how these approaches effect the overall application functionality of your app. Panel
The panel puts their heads together to discuss the different skills and areas of interest they would like to spend time learning or would recommend that you spend time on this year as the holidays approach. Panel
This week, our very own host Paige Niedringhaus leads the discussion about modernizing enterprise React applications - inspired by a course she's just released on that very subject. Over the course of the episode everyone shares tips, tricks, strategies and war stories when it comes to the struggle most developers will face at some point in their careers of keeping large React applications up to date. There's a lot more to keep in mind than just upgrading the code too: tooling setups, code linting, component refactoring, testing - the list goes on! But with some advice (and the help of courses like Paige's), it's not an impossible task. Panel
Yann Braga is the maintainer of Storybook. He talks about Storybook, how it's used, new features the team is working on, and what it's like to be part of the core team actively maintaining an open source system like Storybook that is widely used to build UI systems in isolation and allow teams to see how components are used. Panel
This week the panel discusses several Do's and Don't's for your React Apps that are lessons they've learned building React applications over the years. Panel
Charles Max Wood from Top End Devs joins the round up to discuss his strategies and tactics to get the career you want by keeping current on technologies and learning new things. He explains how to determine what you want in your career. Going and building things, and continuing your learning journey. Panel
Travis Waith-Mair joins the round up to discuss how to compose layouts in React and the bedrock tools and principles that build up good layouts in React. Panel
Eric Simons joins the round up to discuss the latest advancements made by StackBlitz that enables you to run NodeJS in the browser. Eric expands that to the work they've done with the NextJS team to run NextJS in the browser without the need to have a server in the background. Panel
Victory Dumebi Nwani joins the round up to discuss integrating the Dialogflow from Google Cloud into your application to manage voice and chat capabilities for your application. Victory dives into the stack he used to put together a functioning app using that offering from Google. Panel
Priscila Oliveira and Mark Story join the panel to discuss the recent transition at Sentry from vanilla JavaScript to React and TypeScript. The show starts out with the panelists nerding out over Sentry and how they use it, then they dive into the code transition and the things that they learned from their conversion to TypeScript. Panel
This week the panelists dive into their work backgrounds and discuss the ins and outs of working at small and large companies. They aim specifically at whether one is better than the other for building a career. Panel
Florian Rappl joins the Round Up to discuss React internals and how to make sense of how React works. He leads the panel through the process of understanding what React is doing when you write your JSX. He also deviates into Microframeworks a bit. Panel
Evyatar Alush joins the Round Up to discuss Vest, a form validation library that handles form validation library in a manner similar to the way that a testing library looks. The panel walks through the process of using Vest to build validations for your forms on the web and in your React Applications. Panel
Ian Lavery joins the Round Up to discuss how to add Voice Recognition to your React applications without adding heavyweight cloud solutions from the big cloud providers. Ian guides the Round Up through adding Voice Recognition, providing security and privacy, and how to understand voice recognition in general. Panel
Youssouf EL Azizi joins the round up to talk about the best React Native libraries that allow you to leverage the native features of the platforms you run on. Sometimes it's hard to know how to get native features into your mobile app. Whether they're not well maintained or don't cover the widest breadth of use cases, it's hard to know sometimes which ones to use. Youssouf breaks it all down for you. Panel
Chris Laughlin joins the round up to discuss how to use the WebKit Speech Recognition API to interact with your react applications. This opens up a wide range of capabilities for web and React applications. Panel
In today's episode, we talk about state management, dependency injection, react hooks, API access best practices and more with Tommy Groshong a React UI architect. Panel
React Hook Form is a terrific way to manage state in, from, and through, your forms in React. Since React itself doesn't give you much to manage forms, React Hook Form steps into the gap to help you manage your forms and provide features and functionality to your forms. Our guest, Vijit Ail worked through several of the options out there for managing states and walks the panel through his decision to use React Hook Form. Panel
Let's dive deep into the pros and cons of Utility First CSS and Tailwind CSS in particular as Jack plays defense and Paige and TJ play devils advocates. Let's see who comes out on top and give you some insights into whether or not Tailwind CSS is the right choice for your next project. Panel
Paige, Jack, and TJ discuss the details of the different ways that you can render a React application. They talk about the pros and cons of each approach, how they work, and the common mythos surrounding each one. Panel
In today’s show, frontend engineer Tyler Hawkins shares his tips on how you can write clean, maintainable and readable code. Using the examples from his article on the same subject, he explains the importance of using clean code principles to make it easier for different developers to collaborate on a codebase. Tyler also discusses how you can better structure your tests and have more confidence in how they are written. Panel
Chuck dives into the 3 essentials for getting the next successful outcome you want in your career. Whether that's something simple like a raise or something more complex like going freelance, you can achieve it by working on 3 main areas. First, building skills. The most obvious type of skills you'll need is technical skills. However, don't neglect your people skills and your organizational skills as well since you're often paid for how you work with people and enhance their work and how you put your work together in the most efficient ways. Second, building relationships. Often other people will be able to help you find the opportunities or will be the ones to make the decisions that impact your ability to get the outcome you want. Having good relationships is key to having good outcomes. Third, building recognition. Being known for being valuable in important ways allows you to leverage the skills you have to build better relationships and create opportunities to get what you need to get the outcomes you want by giving people what they want. A podcast is a great way to do all three. Chuck explains exactly how that works in this podcast and goes deeper as part of the Dev Influencers Accelerator. Panel
Akash Joshi Is a frequent blogger across many of the larger blogs across the internet. He joins the Round Up to share his opinions on how you should put your React applications together as well as some tips on where you shouldn't put files and where you should avoid putting specific types of files. Some of this is inspired by projects like Next.js and others by his own experience. Paige and TJ chime in with their experience to help provide more context to the conversation. Panel
Chuck explains what he taught Nathan last week when we asked how to get hired at a FANG (Facebook Apple/Amazon Netflix Google) company. Essentially, it boils down to how to build the skills and knowledge needed to pass the interview. How to build the relationships to get into the door and have the interviewer want you to succeed. And how to build the reputation that has the company wanting you regardless of the outcome.
This approach also works for speaking at conferences, selling courses, and other outcomes as well as it's the core of building a successful career as an influencer. Panel
Chuck explains what he taught Nathan last week when we asked how to get hired at a FANG (Facebook Apple/Amazon Netflix Google) company. Essentially, it boils down to how to build the skills and knowledge needed to pass the interview. How to build the relationships to get into the door and have the interviewer want you to succeed. And how to build the reputation that has the company wanting you regardless of the outcome.
This approach also works for speaking at conferences, selling courses, and other outcomes as well as it's the core of building a successful career as an influencer. Panel
Yash Garudkar joins the Round Up to discuss using AWS Amplify to quickly build production ready applications. Yash also dives into how to use some of the offerings provided by AWS without needing to understand the wide array of offerings in Amazon Web Services. Panel
Chuck was on a strategic call with one of his potential coaching clients talking about cryptocurrencies and realized that this is one of the major reasons that people want to become influencers. Or, rather, that many people aspire to make a difference and/or make money and the best way to do that is to become the person people go to for what you do. So, how do you become the first person people think of when they think of that thing you know how to do? Let Chuck tell you. Panel
Chuck was on a strategic call with one of his potential coaching clients talking about cryptocurrencies and realized that this is one of the major reasons that people want to become influencers. Or, rather, that many people aspire to make a difference and/or make money and the best way to do that is to become the person people go to for what you do. So, how do you become the first person people think of when they think of that thing you know how to do? Let Chuck tell you. Panel
Charles talks about the things that get developers stuck when they're trying to start their podcast or other influencer channel. He explains how to get around having those things hamper your journey. Panel
Charles talks about the things that get developers stuck when they're trying to start their podcast or other influencer channel. He explains how to get around having those things hamper your journey. Panel
Charles Max Wood talks about how to build, grow, and benefit from positive relationships within programming. He talks about how he's built genuine positive relationships with hundreds of programmers and how he and others have grown from those relationships. He also explains that you get out of relationships what you put into them. Finally, he goes into how to begin to build relationships by building a system of influence you can use on behalf of the people you want relationships with. Panel
Charles Max Wood talks about how to build, grow, and benefit from positive relationships within programming. He talks about how he's built genuine positive relationships with hundreds of programmers and how he and others have grown from those relationships. He also explains that you get out of relationships what you put into them. Finally, he goes into how to begin to build relationships by building a system of influence you can use on behalf of the people you want relationships with. Panel
Charles Max Wood discusses several opportunities that came his way early in his podcasting career and other opportunities that have come to other people after only a couple of podcast episodes. He explains why that happens and how you can use this to create more influence as a developer. Panel
In today’s episode of React Round Up, Nigerian-based developer Dillion Megida explains how you can create source plugins for Gatsby, the static site generation tool. Gatsby can be used to create landing pages, blogs and e-commerce sites, among other things, and it contains a vast plugin ecosystem that helps developers avoid reinventing the wheel when creating their applications. Dillion also shares his experience blogging for websites such as LogRocket, FreeCodecamp and Dev.to and talks us through his workflow and how he comes up with new article ideas. Panel
Charles Max Wood started podcasting because it sounded fun and because he wanted to talk about technology. He learned pretty quickly that it got him access to people who understood the things he wanted to learn. The reasons changed over the years, as Charles explains before he talks about the big payoff he gets now from doing the podcasts. Panel
On this episode of React Round Up we chatted with Miroslav Nikolov, a UI developer at one.com, about his approach to unit testing React components. Miroslav discussed writing components in a human-friendly way, using the library UnexpectedJS. We also talked about Miroslav’s blog, including how he got started with it, and some of the tools he used, like Gatsby and Mailchimp. This is a great episode if you’re looking to learn more about how to approach unit testing in React. Panel
Jason Weimann started out as an enthusiast of the Massively Multiplayer Online Role Playing Game, Everquest. After becoming a software developer and building a collaborative community playing the game, learn how he used his connections to get a job working for the company that made the game, even if it wasn't a job working as a game developer and how that led to a career working on one of the most popular online games of the time. Panel
Changing careers into software development is always an interesting story and Rani Zilpelwar's story is no different. In this episode, Rani, the QA developer turned software consultant, talks about how she's held almost every software role at one point or another, and how she's continuing to improve her skills now as a software consultant. The discussion includes books and websites she's found helpful to building up her knowledge, how the company she works for helped set her up for success by pairing her with a more experienced developer as a mentor when she started out, and now how / why she blogs on her own site to give back and solidify the things she's learning. Rani's deep knowledge of testing also lends itself well to her new role and she and the team discuss testing strategies and best practices from her days as a QA engineer. This is a great episode if you're looking to make your own career transition and see how other skills can apply there. Panel
Chuck outlines how he's used his podcasts to find mentors to continue his learning journey over 12 years of podcasting. Some mentors have been long lived relationships while others have lasted only a few months or even days. This episode shares Chuck's experience learning from the top people in the development community as a programmer and podcaster. Panel
Chuck outlines how he's used his podcasts to find mentors to continue his learning journey over 12 years of podcasting. Some mentors have been long lived relationships while others have lasted only a few months or even days. This episode shares Chuck's experience learning from the top people in the development community as a programmer and podcaster. Panel
Jack Herrington joins TJ for a discussion about React, Micro Front-Ends, and Module Federation in Webpack. All of these are things that Jack has show off on his Youtube Channel. They discuss the how and why you'd want to implement this approach to building applications. Panel
Remember the amazing adventure it was to learn a new thing every day as a Junior Developer? It's easy to feel a little stuck or lost as a Senior developer since there aren't roadmaps or people looking to mentor seniors. (Besides Charles Max Wood.) Chuck talks about how he felt that way at different points in his career and how podcasting and connecting with the programming communities helped him get past that. Panel
Returning guest Mark Erikson joins the React Round Up team to discuss how he found himself in the position of being an open source maintainer for Redux, how he's helped shepherd/author future versions of Redux (and the complete overhauls that happened when React Hooks were introcuded), and the new examples he's written for Redux Toolkit to make Redux easier for devs to get started with. Mark also addresses some commons misconceptions around React and Redux, such as: is React Context a perfect substitute for Redux (spoiler: it's not), and is Redux still relevant today (it is). Take a listen to hear about getting into open source, where Redux is headed and Mark's broader thoughts on helping the React community document and standardize all the options out there so developers have an easier time choosing the tools needed to solve their particular problems. Panel
Charles Max Wood explains how he landed his first 4 freelance clients that took him through a few years of freelancing with only 3 years of experience and a few hundred podcast listeners. Funnily enough, they actually came to him, not the other way around. He explains how he made himself attractive to them and then turned it into a mutually profitable relationship once he had their attention. Panel
Charles Max Wood rejoins the show to discuss the things that help people take their careers from a job to a calling. The panel goes into publishing content, how to learn, meeting other people, and working with others. Chuck also advocates for having a plan for your career and taking deliberate steps each day to achieve what you wish for. Panel
This is a repeat episode of the JavaScript Jabber 146. Here's the original link https://devchat.tv/js-jabber/146-jsj-react-with-christopher-chedeau-and-jordan-walke/ Sponsors
John-Daniel Trask, founder and CEO of Raygun, talks about his experience building a monitoring company and about how to measure the speed and quality of your code.
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
John-Daniel Trask, founder and CEO of Raygun, talks about his experience building a monitoring company and about how to measure the speed and quality of your code.
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
This is a repeat episode of Ruby Rogues 485 The Rogues dive into who are top 5% developers, what they're doing and how to recognize them. They start out discussing how mid-level developers can move up and how developers can grow in more ways that technical skills. Panel
Software Engineer Andrey Goncharov joins the React Round Up crew to discuss how his company Hazelcast has approached visualizing hundreds of data points on potentially hundreds of computers in a way that makes sense to users. Dust off your math skills - it gets a little technical along the way as they discuss graphs, charts, performance optimizations and bottlenecks, and even handling accessibility of these data-intensive graphs. If you ever have to debug system failures and anomalies, this will be a worthwhile episode to check out.Panel
On this episode of React Round Up we talked to Dragos Bulugean about starting your own business, and managing really big apps. Dragos created Archbee, a service for helping companies manage documentation. We talked about the tech behind Archbee, as well as how he managed to build a business by himself—and how you can do the same. Panel
This week we chatted with James Quick from Auth0 about all things Jamstack. We discussed what the Jamstack is, and walked through a ton of interesting tools and frameworks–including Gatsby, Next.js, Auth0, Sanity, and a whole lot more. Listen for a number of helpful tips & tricks around building sites with the jam stack and more. Panel
On this episode we chatted with Ben Farrell, author of Web Components in Action, about all things web components. We talked about the status of web components, the best way to get started today, and a whole lot more. Panel
Senior Frontend Engineer Kathryn Grayson Nanz joins the React Round Up team to talk about all things component libraries. Kathryn shares her experiences building not one but two component libraries, as well as tips and tricks on the benefits of shared libraries, how to get buy in from product and developer teams, the best way to set up libraries and keeping them up-to-date. She also shares pitfalls to try and avoid when getting started with building a new library. Definitely a good listen for anyone debating whether an existing library or a brand new, custom one is the way to go for a project. Panel
On this episode of React Round Up we chatted with Joe Karlsson from MongoDB. We talked about all things serverless, from how to get started, to which sort of apps are good fits for serverless services, to how incredibly confusing AWS and Azure’s pricing pages are. It was a fun conversation, and is a great listen if you’re curious about serverless but aren’t sure where to start. Panel
Get the Black Friday/Cyber Monday "Double Your Productivity by 5pm Today" Deal
Coupon Code: "DEEP" for a GIANT discount Mani provides us with strategies and tactics to get Deep Work time and how to get our minds into that focused state for hours at a time. He has read hundreds of books that have taught him the secrets to getting more done by getting into this state. He starts by telling us how he was passed over for a promotion at Qualcomm in favor of someone younger and less experienced and how that inspired him to figure out what the other guy was doing differently. He learned that he needed to get more done with the time he was spending on his projects. The trick? Deep Work! Deep Work is the ability to spend uninterrupted, focused time on a task to bend your entire mind toward the goal. Other developers call it "Flow" or "the Zone." Mani provides us with strategies and tactics to get Deep Work time and how to get our minds into that focused state for hours at a time. Get the Black Friday/Cyber Monday "Double Your Productivity by 5pm Today" Deal
Coupon Code: "DEEP" for a GIANT discount
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
Colby Fayock, lead developer, book author and speaker, joins the React Round Up team to discuss why developers should focus on more than just leveling up their JavaScript skills. Understanding HTML, CSS, config tools that help power applications and more can be really helpful – especially when it comes to debugging issues during development. He also talks JAMStack and how it continues to evolve and democratize the ability for more people to put their thoughts online for all the world to see. Definitely a must listen for anyone interested in improving their dev skills. Panel
In this episode of React Round Up, we talked with Shawn Wang, a prolific React author, speaker and teacher, about the future of React. We discussed what’s new in React Core, the React routing world, React DevTools (webpack, rollup, parcel, etc), CSS, and a whole lot more. Panel
In this episode of React Round Up, Tanner Linsley, co-founder of startup Nozzle.io, and most known lately for his OSS project React Query, joins the panel today to discuss how he was inspired to create React Query to simplify data-fetching and state management in React applications. Just a few months after releasing React Query to the dev community, it’s already making waves and garnering the attention of notable React thought leaders and large companies alike, and part of the secret to Tanner’s success is that the majority of his popular OSS projects come from him needing to solve a need for his company, Nozzle.io. Learn about if React Query (or other projects) might be something to incorporate into your own React applications, as well as tips for getting involved in (and making the case for) working on OSS projects. Panel
In this episode of React Round Up we chatted with James Smith from Bugsnag. We talked about the importance of error monitoring and reporting, and how to actually implement those workflows in your production apps. James shared a number of tips for React developers, like what are the most common errors and how you can help prevent them (hint: linters help a lot). We also got into mobile, and what developers can do to protect against third-party SDK errors. Panel
In this episode of React Round Up, we talk with Alex Thomas, an open source enthusiast with hundreds of npm packages to his name. We talk about moving from React Native to React, and Alex’s prolific work in the open source world. We also chat about Ethereum, and Alex’s background in the decentralized finance world.. Panel
In this episode of React Round Up, Dana Yudelevich shares her experiences of building internal component libraries. Dana explains in detail how she has built components in her previous jobs and the challenges she has faced in maintaining them. She also talks about how you can stand out at your current job by setting goals for yourself and becoming a “do-veloper” Panel
Ionic’s own Ely Lucas joins the React Round Up panel to discuss building the Ionic framework to work with React under the hood. Ely talks through how the team’s been hard at work making Ionic easy to pick up for any JavaScript developer with experience in React, as well as some of the benefits it can provide over straight React or React Native. Some of the biggest benefits are having just one shared codebase to power iOS, Android, Electron and PWAs, access to React Hooks and over 100 ready-to-use, easy to customize UI components on install. If you’ve heard about Ionic but want to learn more about it, and it’s newest offering Ionic React, this is the episode for you. Panel
In this episode of React Round Up, Alex Kempton joins us to talk about Hedron, a tool he built for enhancing live audio shows with cool visuals. We chat about MIDI, WebGL and web audio, and how Alex wrapped those all up into an app he uses for live performances. Panel
In this special episode of React Round Up, guest Nikolas Burk delves into the Prisma database and why it’s worth checking out. Panel
When meetup.com announced last year that it wanted to charge users $2 for using the platform, a number of users expressed their strong opposition to the proposal. Developer Chris Achard was one of them and he built meetingplace.io in response to users who were looking for alternatives. In today’s episode, Chris, who is also an egghead.io instructor, explains how he built an MVP in a week using Ruby, React and other technologies. He also shares his tips on how to find consulting jobs and teach others online. Panel
In this episode of React Round Up, Glen Maddern joins us to talk about a new tool he’s been working on called Frontend Application Bundles, or FABs. We chat about how FABs allow you to write server-side logic in a vendor-agnostic way, as well as some of the other interesting problems FABs solve. Panel
In this episode of React Round Up, Carson Farmer joins us to talk about the decentralized web. We discuss what the decentralized web actually is, and some interesting new way the web could work. Panel
Functional programming can be tricky to start with, especially in TypeScript aps. In today’s show, Robin Pokorny shares tips on how to start with functional programming, and how you can integrate functional programming into the apps you’re building today. He also shares tips on libraries to help make functional programming with TypeScript easier, including fp-ts. Panel
Dr. Meghna Srivastava joins React Round Up to share how she transitioned from a dentist in her native country of India to a software developer today in Berlin, Germany. Although she practiced for a few years after graduating dental school, Meghna wasn't completely satisfied with her career choice, and things at work began to feel stale to her. At the same time, she saw the flexibility her partner enjoyed as a backend developer, and began dabbling in Python to see if coding might be something she was interested in pursuing as well. Fast forward a year, and Meghna found herself in Germany due to her partner's job, and unemployed, giving her the time she needed to really focus on learning to code, and she discovered she enjoyed JavaScript's browser-focused interactions more than backend languages. Then she progressed on to the React framework as she began to build up her portfolio. Panel
Front end developer Maksim Ivanov talks about working for Mojang, the company behind the ridiculously popular game Minecraft. As it turns out, Maksim uses React to build different pieces of the game, and runs the code through a custom renderer to make it work in the game world. In addition to his day job, he also found time to write a book about TypeScript after realizing how much easier getting familiar with new code bases could be if TypeScript was used instead of JavaScript. The panel has used TypeScript to varying degrees themselves, but nobody's gone all in, and they talk about the pros and cons of it, including the initial learning curve and how it can help prevent bugs in the code. Maksim's book covers many aspects of TypeScript in great detail, and it sounds like a good read for anyone just picking up the language. Panel
If you’ve tried using SVGs in your application, chances are you’ve found it tricky or difficult. In today’s show, Elizabet Oliviera shares some tips on how you can begin using SVGs to create scalable illustrations and animations. She also shares her experiences of building a library of SVG animations Panel
Charles Max Wood monologues about how to get what you want and making a plan. The main focus of his discussion is about sticking it out through the boring or lonely parts and continuing to work for the career and life you’re looking for. Panel
Sponsors ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Picks Follow React Round Up on Twitter > @reactroundupTJ VanToll hops on the Round Up to discuss when and where it makes sense to use open source UI components versus paying for them. The tradeoffs wind up being more subtle than you think. We dive into team make-up, pros and cons, and the approaches to making the right decision on which library to pick up. Panel:
Travis Ralph works with With You With Me to help veterans transition from military service to IT jobs. He discusses the process of making the move from military service to software development, why they use React as part of their curriculum, and how to learn new skills. Panel:
Chuck and Thomas get together to discuss their favorite parts of the React Round Up. They talk about origins, favorite episodes, and the history of React. Panel
Tejas, Thomas, and Chuck talk about what Design Systems are, how they're used, and what goes into building them. The compare them to some UI libraries that don't quite meet the mark and talk about how they fit into the development ecosystem and people's career paths. Panelist
Brittany is a software engineer for Formidable Labs. She’s a team lead for some client work and likes to poke around in their open-source stuff in her free time. Last year she gave a talk at ReactConf called ‘Accessibility is a Marathon, Not a Sprint’. She talks about her background and how she came to specialize in accessibility. Brittany believes there are a lot of small things you can do to make your website more accessible, and that following best practices in accessibility makes the website easier to navigate for the able-bodied as well. She emphasizes that having accessibility in mind from the get-go will make your website more organized overall and that making things more accessible is as easy as starting with semantic HTML. Brittany and Charles discuss the moral responsibility for businesses to make their website accessible and whose responsibility it is to enforce accessibility. Brittany feels that accessibility really isn’t that hard, but people just don’t know what it looks like or where to get started. Brittany shares some methods to improve accessibility that take very little extra effort. One of the best things you can do is use semantic HTML. To learn things like what is a header, footer, article tag, etc. is, she advises listeners to consult the documents. She talks about the importance of a good pull request and even enlisting coworkers to help you to remember to use these accessibility-friendly methods. Charles and Brittany talk about using heading outline extensions to help you see what content is getting scraped off your site. Once semantic HTML is in place, they suggest testing to see if your site works with accessibility tools like screen readers, or if you can navigate with just a keyboard. They talk about different extensions that mimic visual impairments to ensure your pages are readable. The show concludes with Brittany talking about how this all ties into React. Panelist
Guest Becca Bailey gave a talk at ReactConf in 2019 called The State of React State in 2019 and will be giving another talk at an upcoming conference. She gives a summary of her ReactConf talk, which was inspired by her experiences she has had as a developer. In her talk, she talks about different tools and testing for state management. She and the panelists discuss how to recommend changing tools to a team instead of individuals. She shares some experiences from her job. They discuss ways to keep a work culture from turning toxic and how to start the conversation about state management. The React experts talk about strategies when you chose something for a project that ends up being the wrong decision, and prevent poor decisions like that in the future. It’s important to strike a balance between preparing for the future and anticipating it. Becca and the panel discuss alternatives to using Redux for state management, and some of the advantages of using it. They discuss how to decide what is put into local versus global state and how to know when you can depreciate shared state. Becca has helped teams decide what conventions they will use moving forward for managing local and global state, which gives you a standard for code reviews that reduces decision fatigue. They discuss common use cases for refactoring. Put simply, refactoring becomes necessary when it becomes hard to make simple changes. Becca also talks about being intentional about managing team culture and ways to prevent problems from arising in the future. Panelists
In this episode of React Native Radio Charles Max Wood continues interviewing speakers at RxJS Live. First, he interviews Mike Ryan and Sam Julien. They gave a talk about Groupby, a little known operator. They overview the common problems other mapping operators have and how Groupby addresses these problems. The discuss with Charles where these types of operators are most commonly used and use an analogy to explain the different mapping operators. Next, Charles talks to Tracy Lee. Her talk defines and explains the top twenty operators people should use. In her talk, she shows real-world use cases and warns against gotchas. Tracy and Charles explain that you don’t need to know all 60 operators, most people only need about 5-10 to function. She advises people to know the difference between the different types of operators. Tracy ends her interview by explaining her desire to inspire women and people of minority groups. She and Charles share their passion for diversity and giving everyone the chance to do what they love. Dean Radcliffe speaks with Charles next and discusses his talk about making React Forms reactive. They discuss binding observables in React and how Dean used this in his business. He shares how he got inspired for this talk and how he uses RxJS in his everyday work. The final interview is with Joe Eames, CEO of Thinkster. Joe spoke about error handling. He explains how he struggled with this as did many others so he did a deep dive to find answers to share. In his talk, he covers what error handling is and what it is used for. Joe outlines where most people get lost when it comes to error handling. He also shares the three strategies used in error handling, Retry, Catch and Rethrow and, Catch and Replace. Charles shares his admiration for the Thinkster teaching approach. Joe explains what Thinkster is about and what makes them special. He also talks about The DevEd podcast. Panelists
In this episode of React Round Up Charles Max Wood hosts a solo podcast sharing his perspective on designing your perfect life. In this episode he addresses finding your dream job, building your dream life, and staying current. Start by deciding where you want to end up. Do you see yourself retiring? Working forever? Charles shares his vision for his future and discusses the retirements of others in his life. Working back from the end of your life, Charles has you ask yourself what kind of life and career you want. Charles shares his vision for both his personal life and his career. After you pick your goal, build the skills, and knowledge to reach that goal. He uses the example of becoming a speaker at conferences. He also recommends you find a mentor or someone who has sone what you want to and get there help. Charles explains how important it is to get out of your own way mentally. Many people find reasons real or imagined as to why they can’t reach their goal. He agrees that the world is unfair and barriers can be real. The best way to show others they can overcome barriers is by doing it yourself and working towards your goals. You can if you believe you can and you work for it. Panelists
In this episode of React Round Up Charles Max Wood interviews speakers at GitLab Commit 2019. Eddie Zaneski from Digital Ocean talks about "Creating a CI/CD Pipeline with GitLab and Kubernetes in 20 minutes", Shamiq Islam from Coinbase talks about "Closing the SDLC Loop- Automating Security" and Jasmine James, from Delta Airlines, discusses " How Delta Became Cloud Native-Avoiding the Vendor Lock". Eddie, Shamiq, and Jasmine give the 5 min "elevator pitch" for the talks they gave at the conference. In his talk, Eddie deploys a fake startup going through the whole pipeline: building the application, containerizing an application and shipping it off to Kubernetes. Shamiq, talks about how the conventional approach to security is to consider it at the very end after all developer has wrapped up their work and why that should change. Jasmine explains more in-depth what it means for a big corporation like Delta to be in a Vendor Lock. Sponsors
In this episode of React Round Up Charles Max Wood interviews speakers at JAMstack Conf SF. Mandy Michael gives a talk about responsive typography and variable fonts. Mandy explains what variable fonts are and how they can be used to shrink, stretch and do some very fun and creative thing with them. They discuss how to use them and Mandy explains some of the demos from her talk. Charles asks Mandy what some of the things were that she had to cut from her talk. She had to cut a few longer demos, details and performance improvements that can be made with responsive typography. Mandy shares what she is working on now with responsive typography and explains how much fun she has had expressing herself through variable fonts. To see more of Mandy’s demos and to learn more about responsive typography and variable fonts see the links below. Next, Charles interviews Shawn Erquhart work runs the Netlify CMS project. Charles shares his experience using Netlify and Shawn addresses some of the issues Charles has come across. Charles does say the using Netlify is simple, clean and nice. Shawn shares the origin story of Netlify. They discuss what it means to be a git-based content management system. They discuss how to contribute to the Netlify CMS open source project. Charles mentions his book and they discuss how contributions to open source projects like these are a great way to get a job. Shawn explains how to get started implementing Netlify CMS and how they target different static site generators. Finally, Charles talks with Tammy Everts. Tammy gives a listeners a sneak peek into her talk about website performance, more specifically JavaScript performance. Charles discusses the performance of Devchat.tv and Google Lighthouse scores. Tammy explains that while Google Lighthouse is good it isn’t completely reliable and can miss chunks of time when your JavaScript is failing and you have unhappy users. Tammy shares ways to drill down and see how your JavaScript is behaving in the wild. She talks about blocking Javascript which every developer is familiar with and non-blocking JavaScript that has high blocking CPU time which makes for janky sites. Tammy and Charles discuss what CPU is and what it measures. Tammy names resources and tools to help avoid this problem. Rules of thumb for avoiding these issues are explained by Tammy. First, Reduce, make sure all the JavaScript needs to be there. Next, Monitor, track your metrics. She also suggests working with vendors and maintaining a performance budget for metrics that matter. The interview ends with a little about Speedcurve and what they do. Tammy is the CXO of Speedcurve. Panelists
Today the panel and Sean Grove are talking about the future of programming with GraphQL. GraphQL is a new way of building APIs that is more product and frontend focused. All of the panelists agree that it is easy to get exactly what they need with ease when using GraphQL. There are also benefits for backend developers too, since GraphQL lets you see exactly what fields your clients are using. You can also reach out to specific clients who have accessed specific fields before. This is possible because every GraphQL server is introspectable by a computer, and Sean explains how it works. This introspectivity is the basis for an idea he has that allows users to generate realistic fake data before signing up so they know exactly how their application will work before committing, and gives some examples of how it can be used. They all agree that GraphQL is very well formatted and that it provides solutions to real world problems, The conversation turns to the article How OneGraph Onboards Users Who are New to GraphQL. In particular, they discuss how the GraphiQL Explorer works versus OneGraph. GraphiQL Explorer is an extension that will look at your operations and generate a full React or Bash app from them. Sean talks about the different kinds of operations and how naming them can help you track their performance more easily. There is even a code generator that will flag unnamed queries to help you learn best practices, but won’t stop you from running your code. They talk about the benefits of using OneGraph, a single graphQL endpoint through which you can get all your data from other apps. By wrapping all the APIs in GraphQL, you get access to all the nice GraphQL tooling. They talk about how it works and some of the benefits it can have, such as helping you stay under rate limits. They talk about other interesting tools available for GraphQL and what the explosion of tools means for the GraphQL community. They talk more about how GraphQL fits into the React environment and what they think the future holds. Panelists
In this week’s episode of React Round Up the panel works their way through a blog post outlining best practices for React. The first is “keeping components small and function-specific”. The panel discusses the pros of using this best practice and how it relates to the single responsibility principle. This best practice also helps with the next, “reusability is important”. The panel considers this second best practice and points out some of its flaws. It recommends avoiding the creation of new components. The panel explains that by avoiding creating new components it saves time but can also cause problems as you adapt components to fit more projects. The next best practice is “consolidate duplicate code”, the panel shares their philosophies on dry code and when to consolidate. The fourth best practice is comment only when necessary, Charles explains how he uses comments to help him keep track of things inside his code and the panel warns against using too many comments as it may clog up your code making it hard to read. The fifth best practice is, “name the component after the function”. The panel explains how it is an art finding a name that is not too generic but is not overly specific; mastering the art of naming is something that will benefit everyone. Naming relates to the sixth best practice as well. “Use capitals when naming components”. The panel explains the need for convention and advises developers not to go off-book as this will slow down others. The last six best practices are all self-explanatory says the panel. “Separate stateful aspects from rendering” is nothing new. “Code should execute as expected and be testable”, the panel explains how this allows for trust between developers. “All files relating to a single component should be in the same folder”, this makes everything easy to find when necessary. “Use tools like Bit”, while the panel doesn’t use Bit, they share tool recommendations. They also comment on the progress being made it tooling and the future of automated tools. “Use snippet libraries”, the panel discusses favorite libraries and building their own libraries. The final best practice is “Follow linting rules”. Panelists
Today the panel is discussing how to introduce new tech at work. They agree that it’s important to get input from all teams on the decision, although it will primarily affect the development team. One should also consider the different ways people make decisions, such as through discussion or quiet thinking, and give everyone time to come to a decision. The panel talks about positive and negative examples of how to introduce new tech at work. Thomas believes that it is important to acknowledge your own biases in decision making and to try to avoid them. The React experts discuss the significance of the team dynamic and the necessity of different roles in decision making or if it is better to have an organic discovery phase. This relates to Thomas’ point about personal biases, and he believes that it is important to put people in roles that are opposite of their personality. When making decisions about new technology, it is also important to note that not all decisions require the same amount of input, and they discuss how to measure how much input is required for a decision. The discussion turns to methods for introducing testing, and the panelists talk about their experiences. The rule of thumb for introducing testing is to start simple, have an expected behavior, and test the output to see if it matches. Some other aspects of this discussion to consider are that introducing React Hooks could be considered introducing tech, testing is just a new process, introducing new tools, and budget concerns. Charles shares experience convincing his boss to introduce Agile practices which shows the importance of getting management to see the benefits of the new tech or strategy for themselves. The show concludes with the panel acknowledging that other than introducing tech, introducing philosophies on how to organize your code follows the same patterns as introducing technology. Panelists
In this episode of React Round Up Charles Max Wood interviews Ire Aderinokun at JAMstack conf 2019. Ire works for Buycoins, a cryptocurrency exchange for Africa. She gave a lightning talk, “Headless Chrome & Cloudinary for progressively enhanced dynamic content on the web”. After giving a brief overview of her talk to Charles, Ire defines progressive enhancement for the listeners. Walking through how progressive enhancement works, she explains how Headless Chrome and Cloudinary helped her with the project she shared in the talk. Ire and Charles consider the blindspot that developers experience because they work on high-end devices and how using progressive enhancement helps those who use lower-end devices. Ire shares her experience with JAMstack and explains how progressive enhancement works with JAMstack. Charles shares his experience using JAMstack. The episode ends with Ire giving advice and resources to help get started with progressive enhancement. Panelists
"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is available on Amazon. Get your copy here today only for $2.99!
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
Paul Cowan was a painter and decorator for 30 years until he switched to front end development. He got into React because for him, much of programming didn’t make a whole lot of sense until he read about the flux model, and React Redux was one of the few frameworks that followed the flux model. Spending most of his life outside of the programming world has granted him a unique perspective frameworks like React. He talks about some of his frustrations with React hooks. Hooks can be frustrating because it’s a new paradigm to learn JS, the dependencies array can get bungled, React relies on the order in which hooks are called, and closures can be difficult. Overall, hooks come off at deceptively simple. Paul believes that we shouldn’t need external tooling to keep the dependency array on the right track. To avoid these frustrations, Paul reminds listeners that hooks have to be called in the same order each time at the beginning of your functional components. You also cannot have a hook in an if statement or event handler. It’s also important to remember the declarative nature of React. In production code, updating states is the best way to go. The panel agrees that it’s good that react has clarified their position on what hooks are supposed to be used for, and how we are beginning to see the limitations of React hooks. They discuss unit testing with hooks and how to determine when the React framework becomes too big. They talk about some of the new features that are coming out and how they benefit new developers. When mistakes do happen, Paul talks about how he determines what went wrong. If you want to get advice from other humans, they suggest consulting StackOverflow, ReactiveFlux, and IRC chat. When you do consult these sources, it’s important that your problem is reproducible so that it’s easier for people to help you out. It’s also important that you learn how to ask questions. The show finishes with them discussing how they handle changes in the industry. They have found that reusing components is difficult across Angular and React. They talk about the positive ways that React went version to version. They discuss complexity management in apps. The panel talks about some ways to do things in React without hooks, but also caution that avoiding the popular thing can also get you into trouble. Panelists
Vitali Zaidman works for the WellDone Software consultancy. He has worked with a lot of different technologies, but currently works with React. In a recent React meetup, he talked about React performance. When someone says that React is not performant, Vitali disagrees and says that it is very performant unless you do certain things. If your React application is slow, it’s down to the tools you use. The panelists all agree that premature optimization is the root of all evil. The difference between premature optimization and good architecture comes down to experience. It is important to be data driven and consider performance a business environment. Vitali believes that performance is a feature and should be treated like any other. The panel discusses accessibility versus internationalization. Launching to one language is different than launching to one set of abilities. While you don’t need to internationalize on day one, don’t make it impossible to internationalize. They talk about how creating a timeline of changes in your project can help you pinpoint where your performance issues came from. It is also important to remember that developers have strong computers, while users generally do not. As you build, check your product on slower devices to make sure that it works for your users. Vitali talks about his tool why-did-you-render, which will notify you of avoidable re-renders. He also talks about considering why you are choosing to use React and whether or not is the correct choice for your project. The panel discusses their feelings on pure components. They talk about the importance of code review and manual QA since not everything can be automated, again suggesting having a slow computer or phone in the office to test as you go. They also agree that it is important to understand how your library works. They talk about the huge amount of work that is required to maintain an open source project, and how development is a team effort if you want to create sustainable software. The show concludes with Vitali talking about a performance issue he encountered and how he recognized it, diagnosed the problem, and fixed it. Panelists
In this episode of React Round Up the panel interviews Chris Biscardi. Chris is now working with Gatsby. He shares a bit about his background and how he got into programming. Chris explains his move from Kubernetes and Docker over to Gatsby. His overall drive is to increase leverage for other people and what drew him to these projects. Chirs explains what Gatsby is and what it has to offer to React developers. Gatsby is like a creat react app which is attached to a static site generator that has an API that allows you to pull in data from anywhere. Also, by using Gatsby developers do not have to operate alone, they get the whole Gatsby ecosystem to help them. The panel considers Gatsby and if it would be a good way for developers to learn React. Chris explains with Gatsby’s documentation it would be great for learning React. The panel believes it would be a good place to learn because of the hands-on goal-oriented work engaged in when using Gatsby. Chris shares what developers get when using Gatsby and why it appeals to programmers today. Chris explains what Gatsby themes are and how they are more powerful than CSS themes. The panel discusses how to use themes and how to write them. ThemeUI library is shared and Chris explains how it works. They consider what is next for both Gatsby and React. Panelists
Monica Lent has been interested in software from a very young age, and made her first domain name when she was 9 years old. She studied legacy languages Latin and Ancient Greek in university, but ended up keeping her college development job and going into software. She recently left her job and founded a startup, analytic tool designed for bloggers designed around affiliate marketing. She talks about some of the lessons she’s learned, including how to sift through data and how to make it useful for people. Monica gave a talk at React Finland and she first applies some of her principles from that talk to what she’s learned founding a startup. One of the main differences she’s found is a small startup has different needs and levels of stability than a business. In early stage business, you have to decide where you want to invest in quality and where you shouldn’t be investing. For example, her primary focus is on her algorithm that runs the tool, and UI is less of a priority. In a large company, this might be structured differently. The panel discusses how to distill the priorities from the project manager so you know where to spend your time, something that takes a lot of experience and failure. They agree that if something is business critical and will cause the business to lose money if it fails, those things should be a top priority. Second, the panel discusses the merits of different practices such as whether or not to deploy on Friday and having engineers on call. In Monica’s React Finland talk, she talks about the importance of constraints, which can help with these kinds of decisions. She explains that instead of thinking of architecture as something super abstract, think of it as enabling constraints, as picking ways to do less and end up with code that is safer to run, longer lasting, and has fewer bugs. Thomas shares how he used to oppose constraints and architecture, and how he changed his mind. They discuss the importance of automation over documentation for building sustainable code. Third, Monica explains her opinion on how copying and pasting code instead of adding dependencies is a positive constraint. She prefers this method most of the time but not in all cases because it keeps your code flexible and avoids unnecessary specialization. However she is not advocating for copy/paste over dependencies in every situation : rather the point comes down to using copy/paste instead of inappropriate coupling. Sometimes, when you create an abstraction and combine two pieces of code, this new combination makes code more brittle than it would be otherwise Components put in the shared folder almost never leave. This causes the component to become very specialized and not work in all scenarios. The panel discusses where this method may not work. Thomas talks about some of his favorite tools for simplifying complexity, React Hooks and Relay. Monica and the panelists discuss the merits of using TypeScript and proper methods for coupling code. Fourth, the panel discusses how so much of programming is dealing with other people and the importance of keeping your ego out of it when designing constraints, especially since developers hate other developer’s abstractions. They debate whether pride is a characteristic of junior or senior developers. They note that it is easier to get prideful and opinionated when you’re not working on a team. Thomas believes that if you aren’t working on a big team, you should force yourself to talk to people with opposing positions. The show concludes with the panelists agreeing that it all comes down to the balance between priorities and making things work. Sometimes we can get so focused on making something work that we lose sight of what actually matters. They agree that collaboration generally yields better results than leaving it to one person. Monica talks about the importance of senior developers nurturing their team by leading from behind to help people come up with their own solutions. The panelists talk about different methods they’ve seen for doing this. Panelists
In today’s show, Chuck talks about the recent Twitter thread about 10x engineers. He goes through each of the points in the tweet and talks about each of them in turn. There are only two points he sort of agrees with, and believes the rest to be absolute garbage. One of the issues with this tweet is that it doesn’t define what a 10x engineer is. Defining a 10x engineer is difficult because it is also impossible to measure a truly average engineer because there are many factors that play into measuring productivity. Chuck turns the discussion to what a 10x engineer is to him and how to find one. A 10x engineer is dependent on the organization that they are a part of, because they are not simply found, they are made. When a 10x engineer is added to a team, the productivity of the entire team increases. Employers have to consider firstly what you need in your team and how a person would fit in. You want to avoid changing the entire culture of your organization. Consider also that a 10x engineer may be hired as a 2x engineer, but it is the employer that turns them into a 10x engineer. Overall, Chuck believes these tweets are asinine because it’s impossible to measure what makes a 10x engineer in the first place, and hiring a person that fits the attributes in the list would be toxic to your company. Panelists
Dean Radcliffe has been web developing since the table tag was the new hotness. His interests include his wife and two kids, music, sports, and he likes to say he helps people make whatever they can dream of. Since starting to move towards the frontend, React has been his weapon of choice, which he got started with in 2014. Dean works at G2.com, a software review site. They are developing a review form, which requires the code to react to events. For example, a person’s position in the company would affect what questions they see, so the form needs to react to which box is checked. Dean talks about the use cases for building a reactive form and what kind of things are going to happen when you fill in an input. For his form, the input will be remembered, and they want to increase the user’s involvement with the form through incentives. To accomplish this, Dean uses component driven development with Storybook. Storybook is a tool available for React and other frameworks, which lets you jump directly to each state you want to view instead of having to go through them all one by one. Basically, it gives you shortcuts directly to the visual states of your components. These states facilitate development and the feedback cycle going back to the designers, allowing them to see more than just the finished application and enabling them to circumvent mistakes. Storybook relates to reactive programming because component driven development lets you discover the API and what sets of props are necessary to put this component into each possible state that can be displayed. Dean does not use it as a test environment on his team, but it does help them write unit tests. It has an addon that lets you write unit tests in Storybook, but he hasn’t used it. Dean compares where reactivity and Storybook come together by comparing it to a thermometer.A thermometer will get readings over time of discrete values, and that timing is how people experience your components. You can create an observable of those states, and Storybook Animate ties them together. Your components, however, are still your responsibility. Dean talks about how he creates the observables. The observables are hardcoded, but the great thing is you don’t need to know where it came from. Dean describes how the observables are connected to the components. Dean feels that having this dynamic feed cycle makes it kind of fun to write tests. There is also a function called After which creates a set time out, which creates an observable of that value over time. Dean talks about his other tool, RX Helper. RX Helper provides an ‘after’ abstraction, and an event oriented layer in React. RX helper allows you to listen for custom events raised from the individual components of a form, and you respond to those events with observables, and the observables produce values over time.The goal of RX Helper provides some transparency and makes it easier to try out concurrency designs. The show concludes with Dean talking about some of the changes he’s made to his tools and how he came up with the idea. Panelists
Dinesh Pandiyan is a developer from India. He started as a backend engineer and then moved to frontend. Currently he is working for ThinkMill in Sidney, Australia. Today Dinesh and the panel are talking about devtools and progressive SSR. Dinesh got started with React Redux. The panelists talk about their experiences using primarily Redux for projects. Dinesh talks about his transition from backend to frontend and how it’s a totally different world. On the backend he was working in Java and it ran on a server, but on the frontend, code runs in a browser and the browser is very different for each user. Frontend development is tricky because you don’t know where your code is going to run. One of the trickiest parts of frontend development is debugging something in production. Unless you have good logging tools, you won’t know what’s going on. Debugging this stuff when it’s running on client browsers is hard, but when you’re in development mode your own browser you’ve got handy tools. They talk about some of the tools in React, and agree that console.log is the greatest debugging tool of all time. Dinesh talks about some of the most surprising features about React dev tools. You can benchmark your preferences and identify weaklings in your project, which are things that slow down your application or things that might slow it down. On an application level, you have to build a mental model of how the data flows from the top, where things change, etc, and dev tools can help you build that pretty easily. They talk about how things had to be done before great React tools. In fact, Dinesh chose React just for the devtools. They talk about how the dev tools for React compare to Java. The most important thing is that you have a good debugger that can stop where you want it to. They transition to talking about the differences between SSR and progressive SSR For SSR (Server Side Rendering), rendering happens on the server and you send it to the client. CSSR (Client Server Side Rendering) is when all the rendering happens on the client’s side. PSSR (Progressive Server Side Rendering) is where you render small chunks on the server and then send it to the client bit by bit. They talk about how this has been occurring from the beginning of the internet. This concept is similar to microfrontends. Dinesh gives advice on how to implement PSSR. He says that when you surver render, it loads on differently. Your framework has to do one complete pass of the histiema, so this means you cannot send things to the client until the whole histema is designated. To beat this they’ve been doing a mix of SSR and CSR, with the header, body, and non critical content rendering on the client side. PSSR bridges the gap between SSR and CSSR. How do we make it real and how do we use it? The panel discusses ways to make PSSR a reality. Dinesh has been experimenting with it with extra services, and he gives his method for doing it, emphasizing the importance of where you divide your code is very important, it has to be in sequence. CSS Grid solves this problem, so you could render things out of order and the browser puts it in the right spot. They talk about other ways to get around it. Lucas shares some of the difficulties he’s encountered with streaming and rendering. They talk about the new feature for the Phoenix framework for Elixir, Live View Now. For this feature, you don’t need client side frameworks to generate dynamic content and it enables two way streaming. However, it does not scale well for extremely large apps. They talk about some of the tradeoffs for using this feature. They conclude by discussing the gap between website optimization and device performance. Panelists
Jeffrey Cross and Victor Savkin are the cofounders of NRWL. They used to work together at Google on the Angular team and started NRWL so that people could use Angular 2 well. Victor talks about NRWL’s tool NX, which came from the desire to help people develop like the tech giants. Companies like Google and Facebook develop in the same repository so that people can collaborate. NX is an open source tool for this collaborative development, known as a monorepo. Monorepo style development is a way to develop applications such that you develop multiple projects in the same repository and you use tooling to orchestrate development. The tooling connects everything, makes the experience coherent, and ultimately makes the monorepo style work. The benefits of monorepo development are that the tool chain enables you to interact with different projects in the same fashion, collaboration is more effective, and multiple apps can be refactored at once. The panel discusses what situations are appropriate for a monorepo and which are not. Victor believes that any company with more than one large product would benefit from a monorepo, but it would not benefit a company that wants to keep their teams distinct from one another. The hosts express some concerns about implementation, such as scaling and creating the infrastructure. Victor assures them that a monorepo is inherently scalable, and most tools will work for years and years. As for the infrastructure, companies like NRWL specialize in helping companies set up monorepos, and NX provides many of the necessary tools for a monorepo. A monorepo can be tailor-made to fit any size of company, and can even be created for already established projects. If you wanted to start your own monorepo, you can start by taking a project or handful of projects and moving them to the same place. As you develop, pull pieces of your applications out and put them into packages. Victor cautions that monorepos tend towards a single version policy, so you’ll want to get on the same version as your third party dependencies before you move your next application in. You can move things in and temporarily have different versions, but plan to make them the same version eventually. Victor talks about how the CI in a monorepo setup looks different, because you run tests against everything that might be broken by that change, not just the project its in. So, when you change something in your code, you need to consider what other pieces of code need to be taken into account. A monorepo does make dependencies more explicit, and when you have good tooling it’s easier to see the effect the changes you make have. This is where NX excels. One of the big advantages of NX is that it allows you to partition your application into packages with a well defined API, and prevents the project from becoming one giant node. You can then interact with those packages, and see what happens when you change something. You have a lot more clarity of how your app is partitioned and what the restraints are. NX allows you to share stuff between the front and backend. The show concludes with the conversation turning to Jeffrey and Victor’s consulting work. They talk about some of the interesting features that are happening outside of React that we are missing out on. Victor is very impressed with tooling in the Angular community. He talks about a tool called Console for NX. They end by talking about the schematic powered migrations in Angular. Panelists
Zain Sajjad is a frontend developer at his company Peekaboo Guru, an app built in React. The show begins with Zain explaining why he chose to build Peekaboo Guru in React. Ultimately, he chose React for its composability and reusability. He talks about how much data is shared between his React and React Native applications. Zain explains what he means by a container since he is not talking about Docker, and how he has the app organized. He talks about the differences between routing and navigation between React and React Native. When approaching these differences, he breaks things down into components, containers, and platform, paying careful attention to how they work together. This differentiation can actually help a lot with testing as well. The panel asks Zain about choosing between React navigation and React Native navigation, but Peekaboo Guru uses both React navigation and React Native navigation, but on different platforms. They use each on different platforms because React Native doesn’t let you configure it with existing native apps. He talks about the pros and cons of each, but prefers React Native navigation. They decided to use both because Peekaboo Guru is based in a region where there aren’t many users with high end devices, so this decision was made to accommodate them. They then discuss how to approach making important software decisions with a team and how to make an objective decision away from your bias against old or new technology. Zain believes that you have to step out of your comfort zone and think of the team rather than yourself. They talk about the thought process of making these decisions, especially concerning who is going to do the maintenance. They talk about ways to give good feedback even when the maintenance is not going to be your responsibility and the importance of staying humble. Making decisions like this can be tricky because it is where hard skills and soft skills intersect. The panel moves on to talking about machine learning, and Zain talks about his experience using it to screen comments on Peekaboo Guru. Machine learning is getting more and more common, with giants like Snapchat and Facebook doing it as well. There is also a lot of machine learning on our phones that we don’t think about. Zain gives advice for those who want to start learning about machine learning. He advises people to think of it in two parts, preparing a model and using a model. Thomas feels that machine learning is more approachable than it first appears to be, though it is always related to how good the abstraction is. They compare machine learning to AI and a database to assist with understanding. If you want to play around with AI, Zain counsels that programming has the addiction of success. Keep your tasks small to keep getting those tastes of success. He advises that it is best to start by using the inference part and then make a model. He talks about different tools to help with the math. The show concludes with the panel agreeing to his counsel and reminding listeners that failure is trying to go from 0 to perfect in one step. Panelists
Episode Summary Today’s guest is Farzad Yousef Zadeh, a developer from Iran with a unique path into computer programming. He started by studying astrophysics and aerospace engineering in college, then dropped out in his last semester because it wasn’t the right path. He then taught himself to code, working mostly in web programming and frontend development. Despite his change in course, Farzad remains passionate about observing the night sky. Farzad is here today to talk about the ideas in his talk Explicitness and Consistency in UI, where he talks about the difficulties of developing a user interface and how the experience can be improved by using state machines and state charts. He talks about his inspiration for the talk and how he has implemented state machines and state charts into his work. The panel backtracks and talks about the definition of state machines and state charts. A state machine, from an academic background, is a model for computing something. It's for managing and controlling, taking over branching and managing a finite amount of state declaratively. State machines are not so much about sharing or reusing, but about how your communicate a certain behavior. Despite the fact that event driven programming permeates the programming consciousness, thinking about state charts and state machines is actually more natural than it first appears. The panel explains how it’s the same principle as whiteboarding to solve a problem. Lucas asks how state charts are different from pure React. Farzad talks about how it’s important not to just treat your static states as first class, but also the transitions between them. Otherwise, you would end up with something that looks like a map with cities and towns, but no roads. Using statecharts and state machines makes testing an application much easier, and in some ways you let the machine test itself. The machine will know what to do with your states because you define the path, and the machine will take the path for you. They again talk about the difference between state machines and state charts. A state machine defines a finite set of states and defining the events that the machine can take and respond to when transitioning from state A to B. If you use only this, you will encounter a snag called ‘state explosion’ because not non-concrete things cannot be modeled. So, state charts were invented to compensate for this. A state chart brings the idea of an extended state, or the context and data you need to hold and reason from. Farzad talks about other types of machines and supports that exist for branching, entry actions, and exit actions. This is similar to the use effect hook in React. He gives examples of where you would use this logic and how it would be worked into frameworks. Farzad talks about how your machine is just a definition, a declarative model of how something is supposed to behave, and how having that separation between the definition of the logic and behavior vs the implementation of API has given us so much more freedom and portability The panel talks about how using state machines and charts is an investment in the long term maintainability of your code. They agree that using state machines and charts makes it easier to communicate with other developers, new team members, and even non developers. They talk about Cerebral.js and its contributions and model. As with everything in programming, state machines are not a silver bullet and don’t work in every situation. Farzad talks about situations where state machines can be unhelpful. It is still valuable to consider state machines and charts because it forces you to dedicate time thinking and organizing your thoughts so that you can build something maintainable that won’t just be thrown away. The panel discusses how thinking things out before starting to code can be beneficial. They finish by talking about how React Hooks has started them on the path to implement state machines and charts into their code. Panelists
Episode Summary Today’s guest is Håkon Krogh, and the panel is discussing his talk on lightning fast SSR React apps given at React Amsterdam. He gives a brief overview and defines his use of the Uncanny Valley (called the Valley of Lies in his talk). In this instance, the Uncanny Valley in programming occurs when everything in a website or application looks great, but none of the buttons work or users simply can’t connect. This is especially common when users try to connect to a site or app with their cell phone rather than a computer. The panel discusses what can be done. It’s important to begin by measuring the lag in your applications. Designing the progressive loading experience first is suggested as a solution, as well as organizing what loads first and using React and HTML for different parts of the app. It’s important to realize that some tools don’t work in every situation. The panel talks about the merits of Next.js. Next they talk about what kinds of applications require SSR that make the loading slow. They discuss the importance of SEO ratings and how it can affect your rank in a Google search. Services like Lighthouse can give you an SEO rating so that you can improve. Håkon and the panel talk about other ways to improve on the Uncanny Valley. It’s important to make sure that users have a way to use your site even if they’re stuck in the Uncanny Valley. One way to do this is to provide fallbacks so that if your React isn’t working, the site is still usable. They discuss the merits of micro frontends, using SSR for only part of the app, and reducing bundle size. Unfortunately there is no silver bullet, so solutions will vary by what you’re building. In spite of these setbacks, one of the great features of React is you don’t have to do everything in React. They discuss the emerging idea of shipping different JavaScript for different things and talk about some of the React-like alternatives available. Bridging the Uncanny Valley is vital because it is the reason many people are afraid of their computers, and a good user experience can make people gravitate towards your product. The show concludes with Håkon talking about things in the React community that are piquing his interest. Panelists
Episode Summary Andrey Okonetchnikov is a specialist in frontend architecture and design systems. He runs his own consultancy and made the package lint-staged. Andrey has been in programming for 20 years and talks about his background, how he got into React, and why he started component-driven.io. Andrey has always been interested in design tools and design systems, it just wasn’t the right time because the right tools weren’t available. Since Andrey has been working in frameworks for 20 years and has watched them come and go, Lucas asks Andrey how he has seen the communication between developers and business owners evolve over that time. Andrey reflects on his first conference talk and believes that not much has changed, even if the tools have. His perfect interaction between developers and business owners would be codeless, and would instead draw his design on a napkin. This idea ties into Andrey’s ideas of creating things in primitives instead of wireframes. He relates his idea to the pattern philosophy of the building architect Christopher Alexander, the idea that specific design problems require specific solutions. He talks about since everything in React is a component, we can encapsulate a design decision into a component. Since the power of components is redistributing knowledge, the panel discusses how components promotes reusability, accessibility, and sustainability in code. However, Frankenstein components are the dark side of reusability. Andrey talks about the dynamic view of a design system that does reuse and how to make sure that it evolves cleanly. They discuss how much of can be planned in advance the first time you’re creating a component versus how much should you not try to think too far ahead and fix it when it comes up. They all agree that early abstraction can be almost as destructive as early optimization Panelists
Sponsors
Sponsors
Sponsors
PanelSponsors
PanelSponsors
Sponsors
PanelSponsors
Sponsors
Sponsors
Sponsors
Sponsors
Sponsors
Sponsor
Sponsors
Sponsors
Sponsors
Sponsors
Sponsors
Sponsors
Sponsors
Sponsors
Sponsors
PanelSponsors
Sponsors
Sponsors
Sponsors
Sponsors
Sponsors:
Sponsors:
PanelSponsors
Sponsors:
Sponsors
Sponsors
Sponsors
Panel:
Panel:
Panel:
- Lucas Reis
- Charles Max Wood
- Justin Bennett
Special Guest: https://twitter.com/drenther In this episode, the panelists talk with https://github.com/drenther (India) who is a full-stack developer and cybersecurity enthusiast. The panel and the guest talk about design patterns and designing simpler code for clarity and less confusion. Check out today’s episode! Show Topics: 0:00 – https://www.telerik.com/kendo-ui?utm_campaign=kendo-ui-awareness-jsjabber&utm_medium=social-paid&utm_source=devchattv 0:31 – Chuck: Our panelists are and our guest is Soumyajit! Introduce yourself please! Are you doing React on the side? 1:02 – https://twitter.com/drenther I am a master’s student and I am doing freelancing. 1:42 – Panel. 1:49 – Guest. 2:10 – Chuck: I am feeling very up-to-date. Woo! Universities are teaching this and that and they are focused on theory. The flipside is that they are going to write real code for real systems. 3:10 – Panel: I like your well-written blog posts. You talk about design patterns. 3:50 – Guest: The design patterns at the university had to do with real JavaScript applications. 4:09 – Chuck: I am curious you are talking about the design patterns – how can people from React find/use it? 4:45 – Panel: It depends on your definition of design patterns. 5:35 – Lucas: Maybe you are using one or two here and reading through the design patterns is like going through your toolbox. You only need a screwdriver but you bought the whole toolbox. Get familiar with it and from time to time solve problems and thing: what tool can help me here? It’s clear to me with this toolbox analogy. I understand now – that tool I saw 2 months ago could help me. 7:00 – Guest: I have an interesting story with this about design patterns. Let me share! 7:36 – Justin: It was a similar thing but I wasn’t in JavaScript at the time. I’ve used a lot of C++ code. Design patterns became very useful. I saw it the same way Lucas! 9:23 – Justin continues: How and why to use a certain tool. That’s important. 10:28 – Chuck: Okay this is the default pattern and that’s where we can go for the fallback. Here is the fallback if this doesn’t work here or there. 10:49 – Lucas: This is important to remember. It’s not how to use the tool but it’s why am I using this tool here or there? 11:57 – Justin: It’s so much information in general. People get information overload and they have to just start! One of the challenges we do is that we over-engineer things. Do what you need to know. Look it up but play with it. 12:40 – Lucas: It’s interesting by another blog post that you wrote Soumyajit – and you are using a render prop. You showed a problem and showed the solution. 13:30 – Guest: Yeah I’ve written a lot of blog posts about this topic. 13:48 – Panel: Often times – it’s hard for people just to dive-in. People need to see you solving a problem and it really helps with the learning process. 15:03 – Chuck: What patterns do you find most useful? 15:11 – Panel: Functional components have changed my world! 16:23 – Guest: Around these functional components... 17:17 – Panel: I will go with the patterns that are not useful. Don’t make your code pattern-oriented. This is my favorite pattern now and going back to basics. 18:53 – Panelists go back-and-forth. 19:01 – Lucas. 19:41 – Chuck: You talk about over-engineering things and that’s what I found myself doing sometimes with my new project. When I figure out how to make it simpler I get excited and it’s easy to follow. 20:15 – Panel: We celebrate the person who deleted the most lines of code. 20:28 – Panel: I am going to steal that idea. 21:04 – Guest: I have an interesting story of over-engineering something – let me share! 21:53 – https://www.freshbooks.com/?adgroupid=51893696397&campaignid=717543354&crid=285105591548&dv=c&gclid=EAIaIQobChMI4ey45u-T3wIVhCJpCh0fZgOJEAAYASAAEgLXS_D_BwE&gclsrc=aw.ds&ntwk=g&ref=ppc-fb&source=GOOGLE&targetid=kwd-298507762065 22:59 – Panel: Building too much is b/c I don’t have a clear understanding of what I am doing. I get excited about problems. What’s the more simple way / most naïve way possible! 24:36 – Lucas: If you are going to change something you will be changing it in several different places. 25:50 – Chuck: When I heard the concept, all the codes that change together should be together. 26:08 – Lucas comments. 26:53 – Panel: Keeping things contained in one place. We have our presentational component and higher-level component, so you can see it all. 28:28 – Lucas: Different people working on different technologies. 29:15 – Panel: Can I break this down to smaller parts, which makes sense to me? 29:48 – Guest: Looking for keywords will cause a distraction. Finding a balance is good. 30:04 – Chuck: If you have a large rile there could be a smaller component that is there own concern. That feels like the real answer to me. It has a lot less than the length of the file versus... Chuck: If I cannot follow it then I need to keep the concept simple. 30:51 – Lucas: The quantity of lines and the line count – I think it’s better how many indentations you have. 32:43 – Guest. 32:48 – Lucas: Yes, so in the horizontal scrolling you have to keep things in your mind. 33:41 – Panel: There are so many different metrics that you can use and the different line count or different characters. There are more scientific terms that we could plugin here. If you have a lot of these abstract relations that can...write it 34:23 – Chuck: So true. 34:52 – Chuck: I want to move onto a different problem so it’s an attention thing for me too. 35:06 – Panel: We have to get okay with not always writing the best code in that it just needs to do what it needs to do. 35:30 – Chuck. 35:57 – Panel: We write it once – then it falls apart and then we write it again and learn from the process. Learning is the key here – you see where it works and where it doesn’t work well. 36:31 – Panel. 36:47 – Chuck mentions service-side rendering. Chuck: Should we schedule another episode? 37:11 – Panel: I think it’s own episode b/c it’s a complex problem overall. 39:33 – Lucas: Try to find memory leaks in the file components and server-side rendering. Where we have lost a lot of sleep and a higher level of complication. Sometimes it’s necessary. 41:42 – Chuck: Yeah let’s do another episode on this topic. Sounds like there is a lot to dive into this topic. Soumyajit, how do people find you? 42:10 – Guest: Twitter and https://github.com/drenther 42:28 – Picks! 42:30 – https://www.digitalocean.com/ End – https://www.cachefly.com Links:
- https://rubyonrails.org
- https://angular.io/guide/quickstart
- https://www.javascript.com
- https://elm-lang.org/community
- https://phoenixframework.org
- https://github.com
- https://devchat.tv/get-a-coder-job/
- https://reactpatterns.com
- https://calibreapp.com
- https://mitpress.mit.edu/books/engineering-safer-world
- https://muz.li
- https://www.amazon.com/Monster-Hunter-International-Second-Hunters-ebook/dp/B00XLQ9PF6/ref=as_li_ss_tl?ie=UTF8&keywords=monster+hunters+international+series&language=en_US&linkCode=sl1&linkId=8677e2fa9b6c3b5fe9de5c749f826715&qid=1540397018&sr=8-6&tag=devchattv-20
- https://github.com/drenther
- https://twitter.com/drenther
Sponsors:
- https://devchat.tv/get-a-coder-job/
- https://www.cachefly.com
- https://www.freshbooks.com/?adgroupid=53169078638&ag=%257Efreshbooks&camp=US%2528SEM%2529Branded%257CEXM&campaignid=717543354&crid=289653575014&dclid=CPaQ6KX0id4CFUTcwAodvfQEcA&dv=c&gclid=EAIaIQobChMIwr_9ofSJ3gIVyrfACh1DkQVNEAAYASAAEgJIUvD_BwE&gclsrc=aw.ds&kw=fresh%2520books&kwid=kwd-299596828929&ntwk=g&ref=ppc-na-fb&source=GOOGLE
- https://www.telerik.com/kendo-ui?utm_campaign=kendo-ui-awareness-jsjabber&utm_medium=social-paid&utm_source=devchattv
Picks: Justin
-
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
Panel:
Panel:
Panel: Charles Max Wood Special Guests: Ed Thomson In this episode, the React Round Up Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news! Show Topics: 0:59 – Live at Microsoft Ignite 1:03 – Ed: Hi! I am a Program Manager at Azure. 1:28 – Rewind 2 episodes to hear more about Azure DevOps! 1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great. 2:38 – Chuck talks about features he does and doesn’t use. 2:54 – Ed. 3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub. 3:18 – Ed: Technically we have not officially acquired GitHub. 3:34 – Chuck: It’s not done. It’s the end of September now. 3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone... Ed continues to talk about this topic. He is talking about One Drive and these repositories. 6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me. 6:54 – Chuck. 6:59 – Ed: It has come a long way. 7:07 – Chuck: Beyond the FSF are we talking about other features or? 7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate. 8:17 – Chuck. 8:37 – Ed: You just can’t set it up with Apache. You have to figure it out. 8:51 – Chuck: The method of pushing and pulling. 9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that. 9:38 – Ed and Chuck continue to talk. 9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there. 10:55 – Chuck: How can someone start with this? 11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know. 12:05 – Chuck: What if I am using both a backend and a frontend? 12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the... There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there. 13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated. 13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this... It’s not just running a script. 15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows? 15:26 – Chuck: How much work do you have to do to set-up a Pipeline like that? 15:37 – Ed answers the question in detail. 16:03 – Chuck asks a question. 16:12 – Ed: Now this is where it gets contentious. If one fails... Our default task out of the box... 16:56 – Chuck: If you want 2 steps you can (like me who is crazy). 17:05 – Ed: Yes, I want to see if it failed. 17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment. 17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!). Ed continues this conversation. 18:43 – Chuck: And it just pulls it? 18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility 19:04 – Chuck: VPN credentials? 19:10 – Ed: Just run the... 19:25 – Chuck comments. 19:36 – Ed: ...Take that Zip... 20:02 – Ed: Once the planets are finely aligned then...it will just pull from it. 20:25 – Chuck: I host my stuff on Digital Ocean. 20:46 – Ed: It’s been awhile since I played with... 20:55 – Chuck. 20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations. 21:10 – Ed: What is Phoenix? 21:20 – Chuck explains it. 21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support. 22:41 – Advertisement. 23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and... 23:49 – Ed: I think it’s going to happen. 23:55 – Ed: Exactly. 24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud? 24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk. 25:07 – Chuck: With continuous deployment... 25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master... Ed continues this hypothetical situation with full details. Check it out! 27:03 – Chuck: You probably can do just about anything – deploy by Tweet! 27:15 – Ed: You can stop the deployment if people on Twitter start complaining. 27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source? That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time. 30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments. 31:03 – Chuck: Then you can use time for coding style and other things. I can take mental shortcuts. 31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then... 32:30 – Chuck adds his comments. Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those? 33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and... 34:05 – Chuck: It works with a lot of languages. 34:14 – Ed. 34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry... 35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it. Mac OS dies a fine job. That’s why we have all of those. 35:29 – Chuck: But I want to run my tests, too! 35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run. 36:29 – Chuck: The deployment is different, though, right? 36:40 – Ed: I have a friend who clicks a button in... Azure DevOps. 37:00 – Chuck: I like to remind people that this isn’t a new product. 37:15 – Ed: Yes, Azure DevOps. 37:24 – Chuck: Any new features that are coming out? 37:27 – Ed: We took a little break, but... 37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website. 39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure t
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
Panel:
Panel: Charles Max Wood Special Guest: Brady Gaster In this episode, Chuck talks with https://twitter.com/bradygaster about https://www.asp.net/signalr that is offered through Microsoft. Brady Gaster is a computer software engineer at Microsoft and past employers include Logical Advantage, and Market America, Inc. Check out today’s episode where the two dive deep into SignalR topics. Show Topics: 0:00 – Advertisement: https://angularbootcamp.com 0:56 – Chuck: Hello! We are going to talk about https://www.asp.net/signalr which is an offering through Microsoft. 1:09 – Guest: It started in 2011 that’s when I got involved, but I wasn’t with Microsoft, yet, at that point. I was working on the technology, though. Effectively you can do real time HTMP but what they did (Damon and David) let’s create a series of abstractions but not we have for Java. They basically cam up this idea let’s do web sockets and then go back to pole / pole / pole. It’s to see what the server and the client can support. Guest talks about https://socket.io, too. 6:45 – Chuck: What we are talking about real time coordination between apps. 6:56 – Guest: Web sockets, 1 million...and 2.6 million messages a second! 7:05 – Chuck: I can set that up like I usually set up web sockets? 7:17 – Guest: There is a client library for each. Effectively you have a concept called a connection. 9:48 – Chuck: How do you handle authentication on the frontend? 9:56 – Guest: We have server side things that we can attribute things. 10:09 – Chuck. 10:12 – Guest: If you authenticate to the site then the site passes the token and it basically sits on top of the same plumbing. 10:38 – Chuck. 10:42 – Guest. 10:54 – Chuck. 10:58 – Guest: We recently just had the https://www.dotnetconf.net. We had an all night, 24-hour thing. 11:48 – Chuck: Here you are, here you go. You hook it all up, JavaScript into your bundle. 12:05 – (The guest talks about how to install.) 13:12 – Chuck: I could come up with my own scheme. 13:25 – Guest: The traditional example is SEND A MESSAGE and then pass you string. Well tomorrow I do that and I just change the code – it’s great b/c I send up a ping and everybody knows what to do what that ping. It’s just a proxy. 14:17 – Chuck: I am trying to envision what you would use this for? If you are worried about it being stale then you refresh. But if you want the collaborative stuff at what point do you ask: Do I need SignalR? 15:00 – Guest: When I do my presentations on SignalR and being transparent I want to send you 1,000 messages but 1 or 2 messages will be dropped. You don’t want to transmit your order data or credit card information. Do you have a hammer and you need a screw? If you need stock tickers and other applications SignalR would work. Keeping your UI fresh it is a great thing. 19:02 – Chuck: You do that at the Hub? You set up the Hub and it passes everything back and forth. What can you do at the Hub for filtering and/or certain types of events? 19:26 – Guest: I am looking at a slide. What’s the cool thing about SignalR and the API is it’s deceptively simple on purpose. If you want to call out to clients, you can get a message to all of your clients if you select that/those feature(s). Some other features you have are OTHERS, and Clients.Group. 20:57 – Chuck: Can you set up your own? 20:58 – Guest: I don’t know. 21:12 – Chuck: Clients who belong to more than one group. 21:23 – Guest: Dynamics still give some people heartburn. (The guest talks about https://docs.microsoft.com/en-us/dotnet/csharp/ Dev, Hub, and more!) 23:46 – https://devchat.tv/get-a-coder-job/ 24:23 – Chuck: How do people get started with this? Do they need Azure? 24:30 – Guest: You don’t need Azure you can go to https://docs.microsoft.com/en-us/aspnet/signalr/overview/getting-started/introduction-to-signalr and it’s apart of the .NET team, too. 26:39 – Guest talks about how to installhttps://twitter.com/SignalR?lang=en – see links below! 27:03 – Chuck: You don’t have to KNOW .NET. 27:11 – Guest: It was created by that team (*fair enough*) but you don’t have to know .NET. 27:57 – Guest: You can I could do JavaScript all the way. 29:04 – Chuck: Yes, we keep moving forward. It will look different what people are using. 29:21 – Guest: That was an early thing and I was reading through the old bugs from 2011/2012 and that’s one thing that kept coming up. I didn’t want to use https://jquery.com to use SignalR – now you don’t. It’s a happy thing. 30:45 – Guest: Someone suggested using https://developer.android.com/reference/android/os/Parcel I have a question do you have any recommendations to have https://www.npmjs.com/package/node-sass workflow to have it less stressful? 31:30 – Chuck: It’s out of Ruby that’s my experience with Node-Sass. 31:40 – Guest: I haven’t used Ruby, yet. 31:46 – Guest: I haven’t heard of Phoenix what is that? 31:50 – Chuck answers. Chuck: It’s functional and very fast. Once you’ve figured out those features they almost become power features for you. Elixir has a lot of great things going for it. 32:50 – Guest: I tried picking up GO recently. 33:08 – Chuck: Lots of things going on in the programming world. 33:18 – Guest: I have always had a mental block around Java. I was PMing the Java guys and I asked: will this stuff work on... Once I got it then I thought that I needed to explore this stuff more! I want to learn Ruby, though. 34:16 – Chuck: Anything else in respect to http://signalr.net 34:15 – Guest: I really think I have dumped everything I know about Signal R just now. I would draw people to the DOCS pages. A guide for anything that could happen on the JavaScript side – check them out! We have tons of new ideas, too! 37:33 – Picks! 37:42 – https://www.freshbooks.com/?adgroupid=51893696557&ag=r%252F+%257Efreshbooks&camp=US%2528SEM%2529Branded%257CEXM&campaignid=717543354&crid=284685866051&dclid=CO7qmoiOh94CFUnHwAodiCQBUA&dv=c&gclid=EAIaIQobChMI--6zho6H3gIVjsVkCh2wsQx6EAAYASAAEgL9B_D_BwE&gclsrc=aw.ds&kw=freshbooks&kwid=kwd-298507762065&ntwk=g&ref=ppc-na-fb&source=GOOGLE 47:54 – https://www.cachefly.com Links:
- https://vuejs.org
- https://jquery.com
- https://angular.io
- https://docs.microsoft.com/en-us/dotnet/csharp/
- https://twitter.com/cmaxw?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor
- https://www.asp.net/signalr
- https://twitter.com/SignalR?lang=en
- https://github.com/SignalR/SignalR
- https://socket.io
- https://www.npmjs.com/package/node-sass
- https://docs.microsoft.com/en-us/aspnet/signalr/overview/guide-to-the-api/hubs-api-guide-javascript-client
- http://signalr.net
- https://realtalkjavascript.simplecast.fm
- https://developer.android.com/reference/android/os/Parcel
- https://twitter.com/bradygaster
- https://github.com/bradygaster
- https://www.linkedin.com/in/bradygaster
Sponsors:
- https://angularbootcamp.com/
- https://www.digitalocean.com/
- https://devchat.tv/get-a-coder-job/
- https://www.cachefly.com
Picks: Brady
- Team on General Session
- https://www.korg.com/us/
-
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
Panel:
- https://github.com/lucasmreis
- https://github.com/zephraph
Special Guests: Alexey Ivanov and Andy Barnov In this episode, the panelists talk with https://twitter.com/savetherbtz?lang=en and https://github.com/progapandist They all discuss Alexey’s https://evilmartians.com/chronicles/optimizing-react-virtual-dom-explained titled: “Optimizing React Virtual DOM.” Listen to today’s episode to hear all the details about this article, the guests’ backgrounds and much, much more! Show Topics: 0:32 – Panel: Thanks for joining us and talking about this https://evilmartians.com/chronicles/optimizing-react-virtual-dom-explained 0:52 – Guest: Thanks for having us on your podcast! The guest talks about his community of developers and the offices are in San Francisco, Russia and other places. He talks about how the company helps their customers and how they can scale. Some of their companies are https://www.groupon.com/?gclid=EAIaIQobChMI9Puun7Kq3gIVDo1pCh2oDgiyEAAYASAAEgJZ7_D_BwE&utm_campaign=us_dt_sea_ggl_txt_naq_sr_cbp_ch1_ybr_k%2Agroupon_m%2Ae_d%2Agroupon-brand_g%2Agroupon-exact_c%2A137872562158_ap%2A1t1&utm_medium=cpc&utm_source=google and https://www.ebay.com 2:39 – Alexey. 3:09 – Panel: The article is https://evilmartians.com/chronicles/optimizing-react-virtual-dom-explained What is JSX how does it boil down to? It’s all supposed to help people and help them understand. 3:45 – Alexey: It’s about how to structure your state, etc. 4:15 – Panel: This keeps things small. He said when I have one idea I write a song and when I have 2 ideas I write 2 songs. If you try to put too many ideas into one post it maybe won’t go too far. 4:48 – Alexey. 5:50 – Panel. 5:56 – Panel: That’s a topic for another episode. The article is interesting in that the large percentage don’t think about rendering performance, so it’s a needed piece of content. Let’s talk about – what is the https://www.codecademy.com/articles/react-virtual-dom 6:32 – Alexey goes into detail with his answer to the panelist’s question. 8:50 – Panel: What I like about this article is that you go through a good progression: here is the JSX that you would write and here is the trans piled function is. And you show the virtual DOM pre-presentation is. I think that is a helpful thing. Let’s talk about that. How does React change to those things when it’s rendering? 9:50 – Alexey. 12:58 – Panel: Okay to recap...when you are rendering an element you write some JSX and the first thing (component) that will map over to the type property is for the Virtual DOM object? And then all of that is compared – when does that happen, the comparison? 13:28 – Alexey: You have React and you create... 15:20 – Panel: So it’s both React and set state these are the only 2 things that triggered state or is there anything else out there? 15:31 – Alexey. 15:47 – Panel: Interesting. You talked about the imperative way we did it before – and it’s much simpler to say what you want, but a question is that is there any world case where it does not work well? What are the trade-offs? Have you ever encountered one? 16:34 – Alexey: If you have changes in the browse, implementations...it’s simplest and easiest way. You just need to have some little changes... 17:53 – Panel: If it’s basic then you don’t have to do manual updates. 18:03 – Alexey. Alexey: To make it work you need competence in your bundle. 18:36 – Panel: I’ve heard – haven’t worked with – when we have these projects that are really web time based, hundreds of elements in real time on a screen, on a Virtual DOM it’s too slow. You have to be precise. They had performance issues, I’m sure 98.99% of the applications probably perform better with the Virtual DOM. 19:46 – Alexey. 21:38 – Panel: That is to reduce the amount of state changes so you are reducing the amount of time it renders – right? 21:50 – Alexey. 22:03 – https://www.freshbooks.com/?ref=10400&sscid=a1k2_rph9e&utm_campaign=87321&utm_medium=affiliate&utm_source=sas 23:11 – Panel: We talked about how type is the first thing that is checked. It does equal comparison to compare these types. What was really interesting is that class components are the same thing but not so. Is it always going to re-render for those components? 24:24 – Alexey: We have to talk about 2 things about this first. In my https://evilmartians.com/chronicles/optimizing-react-virtual-dom-explained 27:49 – Panel: That is a beneficial tool too to control your rendering. You talked about tools to show updates and we will include the link to the article in the links, also I would read it and check out that particular function. It’s cool to see HOW it’s actually rendering. 28:29 – Panel: Apparently sometimes things help us in principle cause we need performance. We need to open the tools and understand what is happening? Is it really a bottleneck like I think it is? One of those Twitter things I saw a few months ago... 30:52 – Alexey: Yes, do what makes sense to you at the time. 32:08 – Panel: We talked about render performance and the pure component and not creating functions...you have a big quote in your article... I have a big question for me: You have a component, and there is a child / parent component. I am curious about that pattern – will it re-render every time? Tell us your thoughts, please. 33:16 – Alexey. 34:11 – Panel: My only issue with the render props is not a performance issue it’s more of an architectural issue. Sometimes we want things to be interjected. I want to have access to this or that. Sometimes we want to access those on a life cycle. The higher the component makes it easier to add a... That’s my only complaint about render comps. 35:35 – Alexey. 36:00 – Panel: Like composing consumers? 36:06 – Alexey: What we are talking about is... 37:00 – Panel: I agree. There are some interesting cases with that pattern when you have a lot of those chained together – function, function, etc. – there are some components that will help you compose... 37:34 – Panel: It’s like callback hell all over again. Everything is a tradeoff somewhere. After the tree it looks clean with render props. I like it even with the drawbacks. 38:25 – Panel: You spent some time talking about lists of children and how you (if one of the children are removed) then it ends up re rendering all the children cause it’s comparing their positions. You mentioned key is one way to deal with that. Let’s talk about keys. When people use keys they are using an array of an index. It seems like it defeats the purpose of it – is that right? 39:20 – Alexey: Yes, you are right. 40:19 – Panel: I think that continually and it’s a smaller known thing but people want this key error to go away and they just shove something in there. To some extent it’s good to know if your tool requires something it’s good to know WHY it requires that. 40:52 – Panel: Last question. Is that the person to program and be a web developer and they are learning React. This is the tool and they are learning how to use React for an app then when we are throwing articles at them. If they are learning React and these articles are at them I think it’s a cognitive overload. What are your thoughts / advice? 42:07 – Guest: How beginner should you be before you learn React? Ideally you should be aware of JavaScript, right? Sometimes people do this to catch up to something shiny. This is just my 2 cents. 43:03 – Alexey. 44:49 – Panel: When you are going to hire someone to do something or choose a framework always try to do a little bit of work without it. Try to build an application w/o React, and then React is introduced to you, you will only see the benefits that they are brining. One thing that happens inside the React world is that people don’t write an application... Start with the basic building blocks – that makes sense to me. 46:05 – Panel: Let’s go to picks! 46:13 – https://www.digitalocean.com/ Links:
- https://rubyonrails.org
- https://angular.io/guide/quickstart
- https://www.javascript.com
- https://elm-lang.org/community
- https://phoenixframework.org
- https://github.com
- https://www.codecademy.com/articles/react-virtual-dom
- https://www.udemy.com/the-complete-elixir-and-phoenix-bootcamp-and-tutorial/
- https://twitter.com/SaveTheRbtz?lang=en
-
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
Panel:
- https://twitter.com/cmaxw?lang=en
Special Guests: https://github.com/adtm In this episode, the Chuck talks with https://www.aaron-gustafson.com who is a web standards and accessibility advocate working at Microsoft. Aaron and Chuck talk about PWAs and the ins and outs of these progressive web apps. Check out today’s episode to hear more! Show Topics: 0:36 – Chuck: Our guest is Aaron, say HI! 0:41 – Aaron: Hi! I have been working on the web for 20 plus years. I am working on the Edge team for accessibility among other things. I have done every job that you can do on the web. 1:08 – Chuck: That is one of OUR publications? 1:14 – Aaron: No the communities. I joined the staff as editor in chief for 1.5 year now. It’s a nice side project to do. 1:36 – Chuck: I thought it was a commercial thing. 1:40 – Aaron: No it’s volunteer. 1:52 – Chuck: Talk about your web background? 2:02 – Aaron: I remember the first book I got (title mentioned). My first job on the web (cash) I was the content manager in Florida and this was in 1999. Gel Macs just came out. I relocated from FL to CT and worked for other companies. I got into CSS among other things. It’s been a wild ride and done it all. 3:52 – Chuck: Let’s talk about web standards? 4:05 – Aaron: It depends on the organization and what the spec is and where it originates. It’s interesting to see how HTML developed back in the day. When standardization started working then everything started to converge. Everything is a little different now. Some specs come out from companies that... (Apple, https://responsiveimages.org, and Grid are mentioned among other things.) 7:37 – Chuck: We set up to talk about PWAs. Where did PWAs come from? 7:57 – Aaron: Modern web design, best web applications. Being secure. One of the underpinnings came out from Google and they have been supporters of that. Firefox is working on installation as well. The Chrome implementation is weird right now, but it becomes an orphaned app. It’s like the old chrome apps where in Windows you can install from the Microsoft store. But the case of Chrome you don’t have to go through the store. 10:14 – Chuck asks a question. 10:24 – Aaron answers. 11:53 – Chuck: What makes it a progressive web app rather than a regular website? 12:05 – Aaron: The definition is running on HTPS and... Aaron defines the terms that Chuck asks at 11:53. 12:43 – Aaron: Of course you can push forward if it makes sense from the baseline. 12:56 – Chuck: We have an Angular podcast, and we talked about PWAs and nobody had a good definition for it. 13:18 – Aaron. 13:22 – Chuck: What are the pros of having a PWA? Let’s start with the basics first. 13:33 – Aaron: The ability to control how you react to the network. We development is challenging maybe in other areas because of the lack of control and how your code gets to your users. Any special needs that YOU might have. Aaron goes into detail on this topic. 17:14 – Chuck: Is the service worker the star for PWAs? 17:20 – Aaron: In a way, kind of. Aaron goes into detail on this topic. Share 2 is mentioned, too. 19:42 – Chuck: If the service worker intermediates between the browser and the page / Internet would it make sense to have your worker have it load and then load everything else? Cause you have those Web Pack now. 20:14 – Aaron: Some people would consider it but I wouldn’t necessarily. I am not a fan for that. If anything goes wrong then nothing loads. I remember back when... 22:23 – Aaron: That is a lot of overhead. 22:34 – Chuck: I am wondering what is the best practice? How do you decide to pull in a service worker and then move into more complicated issues? 22:53 – https://www.youtube.com/channel/UCDWpGhFB8j6Kia4B_MKUG3w: Progressive Web App where they talk about their evolution about this. 25:17 – https://www.freshbooks.com/?adgroupid=51893696397&ag=%255Bfreshbooks%255D&camp=US%2528SEM%2529Branded%257CEXM&campaignid=717543354&crid=289640536553&dclid=CNGHh6XkmN4CFQO5TwodEqEA2w&dv=c&gclid=EAIaIQobChMIzpSso-SY3gIVDoxpCh0-HwkaEAAYASAAEgI6JfD_BwE&gclsrc=aw.ds&kw=freshbooks&kwid=kwd-298507762065&ntwk=g&ref=ppc-na-fb&source=GOOGLE Code: DEVCHAT. 26:25 – Chuck: In order to be a PWA you don’t need to have a push notification. 26:38 – Aaron: I don’t think anyone would want a push notification from me. 27:12 – Chuck: What features do PWAs have? 27:18 – Aaron: Features? None of them really, other than push notifications, it’s just standard it’s going to make an App feel more App “y”. If that’s something you want to do. It’s up to you to determine that. There is going to be like push notifications – sending person new updates about the order. If you were a new site you want to make sure you are not doing a push notifications on everything cause that would be too much. Exercising care with the capabilities with what the users are doing on your computer. This is a person that you are dealing with. We need to seem less needy. Give users control of how they want to use it. For example, Twitter will give you that control per user. 30:56 – Chuck: Could you also do it for different parts of the page? 31:01 – Aaron: It’s different scopes. Your servicer worker has different scopes and it needs to be in the root folder or the JavaScript folder. You can have different workers but they will come from different scopes. 31:32 – Chuck gives a hypothetical example. 31:50 – You can do a bunch of different service workers. 32:11 – Chuck: This is why we create different hierarchies in our code. 32:26 – Chuck: Is there a good point where people can be more informed with PWAs? 32:40 – Aaron: https://www.pwastats.com and https://twitter.com/pwastats with Cloud 4. 33:22 – Chuck asks a question. 33:26 – Aaron: Yes. If you are a photographer you don’t want to cash all of your photos on someone’s hard drive. We have to be good stewards of what is operating on people’s hard drives. Even something as simple as a blog can benefit from being a PWA. 35:01 – Chuck: Are there new things that are being added to a PWA? 35:12 – Aaron: A new feature is the background sync. Aaron: What is native and what is web? 36:33 – Chuck: Yeah it can detect a feature in your machine. Dark mode is... 36:48 – Aaron: It would be nice to see things standardized across the board. 37:00 – Chuck: How does this play into https://electronjs.org or Android or...? Do those need to be PWAs? 37:16 – Aaron: It depends on what you are building. So I talked with people through Slack and they want total control. If you r desire is to shift the same experience then https://electronjs.org can make a lot of sense. They will have to pay a premium, though, your users. If you are aware of that then go the https://electronjs.org route. But for most cases then https://electronjs.org might be overkill for you. You don’t need that extra overhead. 39:55 – Aaron continues. Aaron: I think the major benefit of PWA is... 41:15 – Chuck: The other angle to that is that in an Electron app does it make sense to use a PWA things? 41:23 – Aaron: Yes that makes sense. 41:34 – Unless for some reason you need to unlock into an older version, which I hope is not the case b/c of security reasons. 41:55 – Aaron continues. 42:34 – Chuck: Where can we find you? 42:35 – Aaron mentions Twitter and other sites. See Links! 43:02 – https://www.digitalocean.com/ Links:
- https://rubyonrails.org
- https://angular.io/guide/quickstart
- https://www.pwastats.com
- https://twitter.com/pwastats
- https://electronjs.org
- https://www.aaron-gustafson.com
- https://www.linkedin.com/in/aarongustafson
- https://twitter.com/AaronGustafson
- https://github.com/aarongustafson
- https://www.youtube.com/channel/UCDWpGhFB8j6Kia4B_MKUG3w
- https://medium.com/@AaronGustafson
- https://devchat.tv/get-a-coder-job/
- https://twitter.com/cmaxw?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor
Sponsors:
-
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
Panel:
- https://twitter.com/cmaxw?lang=en
- https://twitter.com/dabit3?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor
- https://github.com/zephraph
- https://github.com/lucasmreis
In this episode, the panel talks amongst themselves about: What is THE dream job? How do you define YOUR dream job? And how do you GET your dream job? Check out today’s episode to find out more! Show Topics: 1:02 – What does a dream job even mean? 1:08 – Nader: It means that you wake-up and you are excited to go to work instead of dreading it. 1:34 – Lucas: Dream jobs I think change depending on your life’s moments. It changes from person-to-person and from time-to-time. After some months there you are feeling like you are always growing as a person and as a professional. 2:24 – Chuck. 2:38 – Justin: My idea is that it has some impact on the people in your world. What is my impact on the world – what is my footprint – what am I doing? My last job was advertisement, and my job was to drive eyeballs to ads. That wasn’t what I wanted to do anymore. 3:49 – Charles: What do I want to do with DevChat? It’s not always fun, and why am I doing this. For me it’s personal freedom and an impact within the world. What are your big three that will make a big difference to you? There are all sorts of reasons, but once you know that then it’s easier. When my resume comes across their desk it comes with an endorsement. If you don’t have anything else to sell them, especially if you are a new developer. The last few jobs you’ve gotten how did you find them? 6:25 – Nader. 6:52 – Panelists: Recruiters. I used that to build myself up. Then I got into: Where DO I want to work? I will check Twitter, GitHub, Hacker News, and I keep my eyes open. At Artsy we try to build on those relationships. We are hiring! 8:31 – Chuck: I think most companies are like that – they will hire the people that they know. Doing the research, figuring out what company you want 9:10 – Panelists: Don’t be afraid to meet-up with people and ask them questions. You aren’t just trying to leech off of them and figure out what YOU can contribute back. 9:47 – Chuck: Even if you are trying to network with people to get a job – make sure you don’t look like you are trying to leech off of them. 10:20 – Lucas: When I moved to the U.S. about a year ago... A question I asked myself: Where will I contribute well? There are some markets that I am not interested in and there are some that I am interested in – that’s where I want to go. I like helping people with their health. Their website (company I am working for) is very eCommerce like. I know I can contribute, and it’s a mission that I am all about. Where do MY skillsets help? For junior levels time is on your side – contribute your time. You can help them with When you are young you have time. Everyone can follow their skillset. Try to find the places where you want and where do you want to contribute. 13:06 – Chuck. 13:20 – Even senior engineers we undervalue ourselves – it’s easy to do. When friends are trying to break into the industry I tell them to track their projects. 14:26 – Chuck: It shows the eagerness to learn and be willing to learn and contribute. On GitHub – be consistent with your contributions; it shows initiative. 15:33 – Nader, how did you get your job? 15:40 – Nader: Developer Advocate is the job I have now. Nader talks about how he got his current job. The main thing that I would recommend is to learn in public. Even if it’s not that impressive – overtime you will standout. It’s all about standing out, because you don’t want to sell yourself. 17:52 – https://www.freshbooks.com/?adgroupid=53169078638&ag=%257Efreshbooks&camp=US%2528SEM%2529Branded%257CEXM&campaignid=717543354&crid=289653575014&dclid=CPaQ6KX0id4CFUTcwAodvfQEcA&dv=c&gclid=EAIaIQobChMIwr_9ofSJ3gIVyrfACh1DkQVNEAAYASAAEgJIUvD_BwE&gclsrc=aw.ds&kw=fresh%2520books&kwid=kwd-299596828929&ntwk=g&ref=ppc-na-fb&source=GOOGLE 30-day trial. 18:58 – Chuck. 19:20 – Lucas: I am doing a lot of interviews now – a lot of times we want to hire people but we can’t for a certain skillset. One interesting thing is that even though you have an initial “no,” we could use that person later. 20:04 – Chuck: If it comes down to a good relationship then you can make that work to your advantage. People should be following-up to see if HR is reposting the job. Give them a lot of reasons to hire you! 22:30 – Panelist: If you aren’t excited to work there then it’s really telling. Searching for any opportunity just to grow is okay but it will be telling to your possible future employers. 23:40 – Chuck: Nader talked about standing out, and here you are talking about the same thing. Nobody goes to this level of effort to get a job at a company. 24:13 – Lucas: Do you think this applies to the big companies like Facebook or Google? 24:28 – Nader: I think these same principles do apply. When you start thinking about these big companies as actual people – then you have a better shot of getting hired. Go through Meetups and finding people who work there. Building relationships is what it’s about. 25:40 – Chuck: Companies are made-up of people – that’s it. Sometimes the company will go to bat for you and try to convince HR that you could be the right person. Give them reasons to hire you – sometimes it works and sometimes it doesn’t. 27:03 – Lucas: Sometimes you THINK you want to work for a company, but how do I gather that this is the correct decision. In the middle of the interview – I realized that this wasn’t the right place for me. How do I got about that? 27:50 – Chuck: I lay out the TOP Three in my eBook. The best place to find out this information is finding out through past or current employees through X company. A lot of information, too, you can get through GlassDoor. You can do a people search through LinkedIn. Have that conversation with them over lunch and ask them those questions and find out. 31:48 – Justin: As you are reaching out to these people, keep them in mind as a possible mentor. Someone who you can learn from and that they can possibly mentor you. I think that can be undervalued. Really focus on “is this someone I could build a relationship with to help me with my career.” The relationship is a give and take – you don’t want that to show through. You should be interested in the person and helping them in some way, too. 33:11 – Chuck: I agree. Chuck talks about mentor / advisor relationship some more. 34:00 – Lucas asks Chuck some questions. Lucas: Some people have a difficult time reaching out – what are some great tips for this? 34:31 – Chuck: Everyone is different. For me, I have to put out a certain number. You have to be willing to go out and do it. If you can’t work with people, then sorry tough luck. Nowadays you will be working with a team of other programmers. Relationships are all about give-and-take; like my wife and me. 36:17 – If you aren’t comfortable in social situations there are things to slowly get you comfortable. Maybe send a tweet through Twitter. Being visible and contribute to slowly put yourself out there. Do whatever you feel comfortable with and challenge yourself just to TRY. Most people aren’t trying. 37:45 – Chuck: Sometimes that direct approach is or isn’t there. You can strike up a conversation about code and then it can go from there. It can happen in stages. 38:37 – If our experiences don’t align then that’s okay. Really try. Make sure you put in more effort than the people that are applying just via their website. Do more than just the 39:17 – Chuck: The more personal you can make it the better chance you have of getting hired. 40:00 – Picks! 40:04 – https://www.digitalocean.com/ Links:
- https://www.telerik.com/kendo-ui?utm_campaign=kendo-ui-awareness-jsjabber&utm_medium=social-paid&utm_source=devchattv
- https://rubyonrails.org
- https://angular.io/guide/quickstart
- https://redux.js.org
- https://www.meetup.com
- https://devchat.tv/get-a-coder-job/
- https://twitter.com/cmaxw?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor
- https://twitter.com/dabit3
- https://github.com/jxnblk/mdx-deck
- https://jasperapp.io
- https://www.docz.site
Sponsors:
- https://devchat.tv/get-a-coder-job/
- https://www.cachefly.com
-
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
Panel:
Special Guests: Tomas Eglinskas In this episode, the panel talks with guest speaker, Tomas Eglinskas, and the panel talks to him about an article he wrote via Free Code Camp Medium. Currently, Tomas is a software developer at Zenitech. The panel and the guest dive-into lessons that not only apply to being a developer, but great life lessons that everyone can learn from. Check-out today’s episode! Show Topics: 1:18 – Chuck: Our special guest is Tomas Eglinskas. We want to talk to you about your article you wrote on the Free Code Camp Medium. How do you get something posted/published there? 1:29 – Tomas – It’s not that hard to get something published there. You can send your articles via email and they will publish it. You can get feedback and resend it, and perhaps they will publish it. 2:06 – Chuck: Quincy and you are besties, right? 2:11 – Chuck: We should get Quincy on this show. 2:21 – Chuck: How did you get into React? 2:25 – Tomas: How I got into React is a bit interesting. It started at the university; at first it was really, really hard for me. Time pressed on and I got hooked. It’s really, really fun. That’s how it initially started. 3:06 – Chuck: Article is titled: “The Most Important Lessons I’ve Learned After a Year of Working with React.” 3:18 – Tomas: What started behind it: I was doing my bucket list. I wanted to publish something at some point. I wanted to try to write and share something from my side of things. I wanted to prove to myself that I can/could. 4:05 – Nader: What do you do now with React? 4:13 – Tomas: We do everything: frontend and backend. In my company we usually use everything with React with production and with my own projects. I have tried Angular but I like React best. 4:45 – Chuck: I am curious...How do you get past that? Where my way is the right way. 5:10 – Thomas: That sentence came from when I was learning it. People would say: this is the way, or someone else would say: no, this is the way. People are afraid of doing their own projects and using the technology. Finding information and figure out what is right and what is wrong, but you eventually figure out your own opinion. There are so many opinions and tutorials and it’s frustrating, because there are too many things to learn. 6:26 – Chuck: Nader, what is the right way to do it? 6:33 – Nader: Yeah, I agree. It’s hard to decipher. What is right or what is wrong? How did you come to your conclusions? My best practices might not be the best practices for someone else. 7:18 – Tomas: Everyone is learning all the time. Their experiences are different. You have to decide what is best for the long-term. At least for me, it was practice and learning and reading from other people; from podcasts, articles, etc. I am open to say that I am not right, but want to know why it’s not “right.” Always trying, always making mistakes. I guess something like that. 8:42 – Nader: Don’t stick to the basics and become advanced. In any career right now you don’t know how to do everything, but to do one thing (topic) really well. The generalists aren’t the people they are hiring; they are hiring the specialists. 9:24 – Tomas comments. 9:37 – Chuck: There is something to be said – I think it’s good to know general things, but you are right. They are hiring the specialists. They are going to look at you differently than other people. You like your thinking challenged a bit. Where do you go to do that to upgrade your skills? 10:18 – Tomas: The silliest one is going to interiors. That’s the fastest way of feedback: what is right or wrong about my code. Going to conferences and Meetups, and doing projects with someone else. I was doing a project with a friend – everybody used Java – but we all used it differently. We all worked together and challenged each other. 11:43 – Chuck: Talking to people – asking them: how do you do this, or why do you do it this way? 12:01 – Tomas: Don’t be shy and have a presence. I guess in America there are a lot of Meetups, in my country we don’t. In the States you have the people who do the tutorials, and such. You can be challenged everyday. 12:40 – Chuck: It depends on where you are. Utah we have a strong community. It’s interesting to say. There was a talk given my Miles Forest at a conference. He would drive to Seattle to be apart of a users group to be apart of it – he would drive 2-3 hours to do this. Eventually, he made his own user group. 13:55 – Nader: I am here in Europe now. I have seen a lot of events going on. Just all of the countries I have heard of different events. I haven’t heard about Lithuania, where you are at Tomas. 14:28 – Chuck: Get A Coder Job. Find Meetups – I will tell people to do this. They will say: There aren’t any in my area. I tell them to type in different search words. To me, it’s telling because it’s “just TRY it!” You never know what will be out there. Go look and see if there is something out there for you. 15:28 – Nader: I agree. I learned a lot through those. 15:59 – Tomas: It is a dream to be an organizer of event but people are afraid that nobody will show. Nobody expected for people to show-up, but they did! Don’t be afraid – you’ll have a great time! 16:44 – Chuck: React is revolving so you need to be up-to-date – good point in your article. People want to reach some level of proficiency. You have to keep learning. How do you stay up-to-date with all of the new features? How do you know what to look at? 17:58 – Tomas: Don’t forget fundamentals. Now understand React from under the hood. You must know the reason behind it. I think that is the basic thing and the most important one, at least in my opinion. We get so wrapped up with the new things, but forgot the basics. 18:41 – Advertisement – Digital Ocean 19:27 – Nader: I am always checking Twitter. This is a good place to start, because I will see something being discussed and then maybe a year later how it all comes together. Twitter is real time. I follow the few top dozen important people through Twitter; Facebook people and other important people. They will talk about what is happening NOW and proposed things. Also, following people through Medium as well as GitHub. 21:01 – Tomas: I agree about Twitter. It’s fun to see what people are talking about. Things that you normally don’t hear through normal avenues. 21:27 – Nader: What interests you for the future? What do you want to specialize in? 21:41 – Tomas: As I progress, and I know more things (than I did before) I find that I want to KNOW more, in general! I am focused on React and try new things. I think about DevOps, but it’s important to know at some level different things as a whole: the backend and the frontend, too. Why is DevOps is important in the first place. I like to understand the system as a whole. And little by little I want to specialize in the frontend, too. It’s good to know the whole infrastructure, too. 23:23 – Nader comments. 22:45 – Tomas comments. 23:55 – Nader and Tomas go back-and-forth. 25:15 – Tomas: How big is your workshop? 25:24 – Nader: We just did one in Croatia. It depends really 2 days, etc. Different lengths. 25:47 – Chuck: Nader, how do people find these different workshops? 25:54 – Nader: Just follow me through Twitter! 26:11 – Tomas: I would like to attend. 26:19 – Chuck: What was one of these lessons that were the hardest for you to learn? 26:33 – Tomas: Not sticking to the basics. When you can show things that are more advanced. When you push yourself to know advanced topics then you are pushing those around you, too. You are encouraging others to learn, too! So that way both, you and the other people, aren’t stagnant. 27:51 – Chuck comments. 28:00 – Tomas: It’s not even “fancy” it’s knowing the basics. Tomas was talking about tutorials and other topics. 30:02 – Nader and Tomas go back-and-forth. 30:24 – Chuck: I think it’s telling and what you are pointing out in your article. Some people get to a level of proficiency, get the job, and then they go home, and that’s it. They aren’t pushing themselves. I’m not knocking these people. But there are people out there saying: Here is what I learned, this is what I want to share. 31:29 – Tomas: Yes, share your knowledge! 31:43 – Chuck: Other thing I want to talk about is another point in your article. 32:07 – Tomas: You will look at your code a few days/weeks later and you will say: Wow, I can do this better. Don’t bash yourPanel:
Special Guests: Peter Mbanugo In this episode, the panel talks with guest speaker, Peter Mbanugo. Peter is a computer software specialist who works with Field Intelligence and writes technical articles for Progress Software and a few others. He studied at SMC University and currently resides in Nigeria. They talk about his creation, Hamoni Sync, and article, Real-time editable data grid in React. Also, other topics such as Offline-First, Speed Curve, Kendo UI are talked about, too. Check out today’s episode Show Topics: 1:30 – Chuck: Let’s talk about what you built and how it works. Topic: Real-time editable data grid in React. 1:40 – Peter: Real time editing. It allows you to edit and have the data go across the different devices. Synchronizing your applications. For the 2:47 – I saw that you built also the... 2:58 – Peter: Yes, I built that with Real-time. Most of the time I have to figure out how to build something to go across the channel, such as the message. Then I built the chats. Next month 4:33 – Justin: It says that it can go offline. That is challenging. How are you going about that? 4:51 – Peter answers the question. Peter: When you loose connections and when the network comes back on then it will try to publish anything to the server while offline. If you are trying to initialize the... 5:42 – Awesome. 5:45 – Peter continues his thoughts. 5:56 – Lucas: This is really interesting. Form something really simple to tackle this problem. I have gotten into so many problems. Congratulations on at least having the courage to try such a system. 6:35 – Justin: When you have someone interacting with one of these applications, lose connectivity, is the service handling this behind the scenes? 6:56 – Peter: Yes. Peter goes into detail. 7:19 – Justin: Neat. That would be interesting to dig more into that. 7:35 – Lucas: I had a friend who sent me links and I was like WHOAH. It’s not an easy task. 7:57 – Peter: Yes, offline – I am learning each and everyday. There are different ways to go about it. Then I go write something about conflict free of different types. I thought that was the way to go. I didn’t want it to be something of the declines. 8:50 – Lucas: How did React work for you? 9:24 – Peter answers the question. 9:58 – Panelist: I was trying to synchronize the system. There are 2 types: Operational Transformations and CRDTs. It’s a really hard problem. 10:35 – Lucas: Now we have multiple devices and they can be far away from each other. Updates to send to the same server. I think that this is really complicated world. Even consider new techniques that we use in RI. You have a long in process. You need to react to them. Maybe dates that you cannot get. Hard problem we are solving now. 11:56 –Justin: Even interacting with applications that ... it has made our products that aren’t approachable if someone doesn’t have a good Internet connection. Synchronizing connections while offline. So you can have offline support. These are problems that we can resolve hopefully. 13:01 – Lucas: It affects everyone. Back in Brazil we had problems with connections, because it’s connections. Now I live in NY but the subway my connection is hurt. 13:40 – Peter: Yes, I agree. Peter talks about his connections being an issue while living in Africa. 14:52 – Justin: How does that affect your development workflow? 15:08 – Peter answers the question. 17:23 – Justin: Shout-out to the Chrome team. Tool called LIGHTHOUSE. It can test for accessibility, SEOs and etc. Good same defaults and trying to test Mobile First. When I was learning about performance I wasn’t thinking about the types of devices that people would use. The edits tab really helps think about those things. 18:41 – Digital Ocean’s Advertisement 19:18 – Justin: Any tools to help test your download speeds or anything authentication tools? 19:36 – Peter answers this question. 20:15 – Panelist asks the same question to Lucas. 20:22 – Lucas: interesting question. Even though the website was doing pretty well we were in the dark. We did a huge migration and it wasn’t clear about the performance. So my first mission here was start using a tool called SPEED CURVE. It only gets better. For a company who needs to acquire a tool SPEED CURVE is great. They have the LIGHTHOUSE measurements in their dashboards. So it can follow through time your scores and all of your analysis. These are the tools we use today. They have both synthetic and real user monitoring. So when we are measuring things on our Chrome it is a picture of your machine (biased picture) they make it both synthetic and film your page and compare through time. Analyze your assets. Some code on your application and collects statistics for each user. Relic I have used before, too. I do believe those tools are of great help. I am sure there are opensource initiatives, but I haven’t played 22:56 – Peter: Have you tried...? 23:07 – Lucas continues. LIGHTHOUSE. 23:56 – Justin: It gives great visualizations for people to see. SPEED CURVE. Where we are at – so they can see that – it’s powerful. 24:40 – Lucas: Interesting story we used SPEED CURVE. Real users and synthetic measurements; our website was getting slower and slower. We couldn’t figure it out. What is happening to our application? It turned out that the app more people were using it on the mobile. The real user speed was going up because they were using mobile. The share of mobile users and performance was getting better. You look at the overall average it was getting slower. Interesting lesson on how to look at data, interpret data and insights. It was really interesting. 26:21 – Peter. 26:25 – Lucas continues the previous conversation from 24:40. 27:00 – Justin: Taking the conversation back. It’s always a challenging problem because the implications are hard to use. What was your experience with React Table? What are the pros and cons? 27:40 – Peter: React Table is quite light. It is pretty good on data. I haven’t had much of a problem. It is okay to use. The other ones I haven’t tried them, yet. 28:08 – Justin: Same question to Charles and to Lucas. 28:21 – Lucas: I have never worked with big tables to render the massive data or tables that need to be edits and stuff like that. I don’t have experience with those components. Play here and there. It is interesting, because it is one of those components that are fighting the platform and it’s a good source of interesting solutions. 29:05 – Chuck: Kendo UI has one. I need something that his more barebones. AG Grid. 30:03 – Justin: React Windows. It optimizes long lists. It just renders what is in the current window. 30:22 – Ryan Vaughn. 30:28 – Justin: Cool library. 30:36 – Lucas: Use it as a learning tool. How do you all decide when to actually start using a library? As early as you can? Libraries to solve our problems? 31:19 – Peter: It depends on what I am doing. 31:53 – Fascinating question. Not one size fits all. It’s a balance between product deliverable needs and... There can be risks involved. Fine balance. I find myself doing a lot is I will default using a library first. Library that isn’t too large but what I need for that project. If there is a hairy feature I will use the library until my needs are met. 33:49 – Lucas adds his comments. Lucas: You want to differentiate yourself. I love GitHub. 35:36 – Question to Charles: I know you have tons of stuff going on. What’s your thought process? 35:53 – Chuck: If I can find stuff on the shelf I will pay for it. My time adds up much more quickly then what the dollars do. I will pay for something off the shelf. I only mess around for a while but if I can’t find something to help me then I will go and build something of my own. I got close with Zapier, but I got to the point that I wanted to put something together that I built my own thing through Ruby on Rails. Generally I will pay for it. 37:07 – Panelist: Yes, I don’t think we all don’t value our time and how expensive time is. 37:25 – Chuck: I own the business. My time is of value – it’s more important to me. It’s a trap that people fall into not to value their time. 38:11 – Lucas: We are not all working on what we SHOULD be working on. This isn’t going to bring business Productive time that we are using with stuff that is not our business or our main focus. Focus on the core proPanel:
Special Guests: Gant Laborde In this episode, the panel talks with Gant who has been programming for twenty years. In the past, he has been an adjunct professor and loves to teach. Finally, he talks at conferences and enjoys sharing his ideas. The panel talks about the React State Museum, among many other topics, such as: React Native, Flux, Redux, Agile, and XState. Show Topics: 1:24 – Chuck: What do you do? 2:02 – Chuck and Gant: We met at React Rally at 2016. 2:17 – Gant: I have my own sticker branding with a friend in Japan who is genius. She draws all these characters. They are my business card now. 2:41 – Chuck: React State Museum- talk about its brief history and what it is? 2:54 – Gant: React is this beautiful thing of passing these functional capsules around and managing them. Once you start creating another component, the question is how do you actually manage all of these components? We are all so happy to be on the cutting edge, but state management systems come up and die so fast. For like Facebook, there are 2 people who understand Flux. What happens is Redux is the one thing that shows up and... 6:34 – Chuck: I want to say...I think we need to change the topic. You said that JavaScript USED to be bad at classes, but it’s still bad at classes! 6:52 – Gant: Yep. 7:21 – Chuck: Typescript gets us close-ish. 7:31 – Chuck: Do you get feedback on the library? 8:12 – Gant: The requests that I’ve got - it’s from people who are better at (that0 than me. I wanted to test the lines of code. But that’s unfair because there are a lot of things to do. It really was a plan but what happens is – components that are used in this example is that in this node module... 9:41 – Panel: This is an interesting topic. When you assess any technology...if you are not a technology expert than you really can’t say. That’s interesting that you are doing this an open-source way. 10:25 – Gant: I am a huge fan of this vs. that. I am okay with say “this” one wins and “that” one looses. I don’t declare a winner cause it’s more like a Rosetta Stone. I had to find pitfalls and I respect that for the different perspectives. At the end of the day I do have opinions. But there is no winner. They are all the same and they are all extremely different. Are you trying to teach someone in one day? I learned Redux in 2 different days. 12:00 – Panel: Is there a library that helps with X, Y, Z, etc. 12:16 – Gant: I love for teaching and giving people a great start. I just set state and live life. I had to show what X is like. 13:59 – Chuck: Like this conversation about frameworks and which framework to use. Everyone was using Redux, because it was more or less what we wanted it to do. But at the time it cleaned up a bunch of code. Now we have all these other options. We are figuring out... How to write JavaScript if web assembly really took off? Do I write React with X or with Y. And how does this affect all of this? We had all of these conversations but we haven’t settled on the absolute best way to do this. 15:50 – Panel: This is great, and I think this is from the community as a whole. 17:20 – Chuck: I need to ask a question. Is this because the requirements on the frontend has changed? Or... I think we are talking about these state management systems, and this is what Lucas is talking about. 17:45 – Gant: I think it’s both. 18:43 – Panel: Websites have gotten bigger. We have always been pushing CSS. Panelist mentions Facebook Blue, among other things. What does your state look like? What does your validation look like? We are on so many different devices, and so on. 20:00 – Gant: I agree to echo everything that you all have said. I think the expectations are tighter now; that we have less drift. People are being more cognoscente and asking what is our brand. And it’s about brand consistency. And we are expecting more out of our technology, too. We keep pushing the envelope. What about these features? We want to be feature rich, and pushing these envelopes – how can we build more faster with less complexity while building it. You have to put that complexity somewhere. It’s interesting to watch. 22:00 – Chuck: How do we use this React State Museum...where are we going next? 22:19 – Gant: It’s a loaded question. Being able to ID new and interesting concepts. If you had a terrible version and Redux comes along, Redux is great for some companies but not all. You won’t see bugs that are crazy, there is a middle-wear, and maybe for your team going into Redux will make things more manageable. 25:25 – Advertisement – Digital Ocean 26:05 – Panel: Understanding your problem is the first thing to do. Talking about evolutionary architecture – to build your software to evolve. What does tha fit really well? So if you have to pick something new you are in a good position. What are my needs? Don’t look too much forward or 27:38 – Chuck: Advice on looking at your problem-sets? 27:52 – Panel: We have gone from planning too much to not planning at all. I don’t need to plan for too much or else it will “hurt” me. 28:42 – Chuck comments and mentions Agile. 29:29 – Panel and Guest chime in. 29:39 – Panel: I worked on a project (3 months) we needed to do a big change. I asked them why didn’t we take that into consideration. And their answer was... 30:30 – Gant: You might get away with... 30:55 – Chuck: What are some of the knobs on this? If I turn this know Redux is looking good, but if I do this... 31:12 – Gant: There are a lot of attractive knobs. Using app sync, not using app sync. 32:33 – Gant: Is your app really effective? That’s your first important question. How much state do I need on the frontend. And vice versa. 34:02 – Gant: How easy will this be to test? Can I teach someone how to do this? If I cannot teach it then it won’t do my team any good. 34:35 – Panel adds in comments. 35:08 – Gant: Looking at tests. 37:25 – Panel: If you have a great backend team then you can move the work across the team. You have a strong team to move that work along that line – normally you can’t cross that sort of thing. 38:03 – Chuck: There are so many options, too. I see Apollo getting reach here. I don’t see it as a statement tool instead I see it as... 38:31 – Panel: Apollo State – seems like they are pushing the envelope. It’s interesting to watch. 38:54 – Chuck. 39:12 – Gant: I am going to go ahead and use this tool – I am not going to worry about it. But now you are being held accountable. 39:29 – Panel: Question for folks: React not having a blessed ecosystem can hold people back in some ways? You have the freedom to use what you want. Here are the tools that you can use. Do you tink it be better if the Facebook team could do... 40:20 – Gant: I find that I don’t like (being told) this is what you will be using. I am a person with idea. We’d all be using Flux and all be very upset. 41:00 –Then there would be 3 people who don’t understand it. 41:17 – Gant: I loved Google Wave. Fool on my once and shame on me twice... Google Video! Google comes out and says here is BLESSED and you don’t have any choice. But it’s any author for themselves. It’s a little bit silly 0 I would like a beacon from Facebook saying: Here is a guide. It seems that they can’t focus. They are running a large company; I would like to keep it open – friendly energy. 42:24 – Chuck: I am mixed feelings about this. It only plays as far as people play into it. IN a React community there are so many voices. They all have opinions on what you should/shouldn’t use. The one thing that I like about a blessed / recommended stack – brand new person – it’s a good place to art. After that if they realize that Flux is hard then they can go and try other options. There are other things out there; there is a good balance there. 43:36 – Panel: That is the Angular way right? 43:38 – Chuck: Yes but Angular is more opinionated. It’s a different feel. 44:38 - Panel + Guest continue this conversation. 45:00 – The book DRIVE is mentioned. 45:21 – Gant: ... we need more recommendations. 45:43 – Chuck: Let’s talk about Repot and how to use this? If you go and get Repot – Google React State Museum it’s really easy. How should people come to this and pick it up? 46:18 – Gant: The table that comes in there – it links to the main Repot. A lot of people showed up and contributed. First of all show up. GaPanel:
- https://twitter.com/cmaxw?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor
- Lucas Reis (NY)
- Nader Dabit
Special Guests: http://cwbuecheler.com In this episode, the panel talks with http://cwbuecheler.com who is a web developer and moved into JavaScript in 2000. Christopher runs his own business, and records and edits videos among many other responsibilities. He also has a lot of hobbies, and guitars are one of them. Check out today’s episode where the panel and Christopher talk about how to form a tutorial course from start to finish. Show Topics: 2:38 – Chuck: I always am fascinated by how there are a lot of programmers who are musicians. 3:00 – Panelist: Yes, I agree. Coding takes creativity. People who are programmers are surprisingly into different arts where it asks for the person’s creativity. 3:17 – Panelist: Video games, music, cocktails, etc. 4:05 – Guest: Yes, for a while I liked to make beer. My current kitchen doesn’t allow for it now, though. 4:25 – Chuck: So your 84/86 tutorial course... 4:46 – Guest: I liked to be one or two weeks ahead. Now building the entire app, instead of doing it week-to-week. 5:35 – Chuck: What is the process like – building these videos? 5:51 – Guest: I try to focus on MVP products that are super easy, and that aren’t too complicated. For example, Music List. Add albums and artists, and see other people’s lists. It ended up being a long tutorial. The process: I build the app, rebuild the app from scratch, I start with a script, read the pretty version and have the marked-down one for my use. The script goes up as the text tutorial. Do my video editing in https://www.adobe.com/products/premiere.html?ef_id=W6K5tAAAAKzsP-f1%3A20180919210348%3As&gclid=EAIaIQobChMI_Onk6_vH3QIVBgppCh1aAwEVEAAYASAAEgIu8vD_BwE&mv=search&s_kwcid=AL%213085%213%21247425965201%21e%21%21g%21%21adobe%2520premier&sdid=KKQOM. 7:55 – Question from panel. 8:52 – Panelist: I have found that extremely hard to do. 9:29 – Chuck talks about his process of recording his tutorials. Chuck: I don’t have a script; I just walk through it as I am going along. You can get it transcribed, which I have done in the past. I have a license for https://www.adobe.com/products/premiere.html?ef_id=W6K5tAAAAKzsP-f1%3A20180919210348%3As&gclid=EAIaIQobChMI_Onk6_vH3QIVBgppCh1aAwEVEAAYASAAEgIu8vD_BwE&mv=search&s_kwcid=AL%213085%213%21247425965201%21e%21%21g%21%21adobe%2520premier&sdid=KKQOM. 11:04 – Panelist: I never recorded a tutorial before but I have written a lot of blog posts. I reviewed it, and reviewing it is a very interesting take. I learn a lot in the process. The things cement in my mind while reviewing. Videos you have the real-time thing going on. 12:00 – Guest adds additional comments. 13:39 – Chuck chimes in. Chuck: We really appreciate you leaving the mistakes in. 14:11 – Guest: Yes, they watch you debug. 14:20 – Panelist: Most of your tutorials are beginner focused, right? 14:23 – Guest: Yes. Christopher goes into detail here. 17:13 – Chuck chimes in. Chuck: My thought is to learn x, y, z in 1 hour. 17:35 – Guest: People are attracted to shorter tutorials. 5-minute React. Don’t build an 84 tutorial course. They are built up to digestible chunks. It’s not wall-to-wall coding, because that would seem overwhelming to me. Let’s learn something in a bite-size chunk. 18:41 – Panelist: https://egghead.io Because of their guidelines they do good work. 1-5 minutes long tutorials. You can get a good run-down and a good introduction. 19:24 – Panelist: You can find it really easy. You don’t need a 1-hour video. 19:40 – Chuck: Yeah, to break it up in small sections. People will see this in my e-book course. 20:02 – Panelist: Do people give you a lot of feedback? What parts of this React course do people have most difficulty with? 20:21 – Guest: It’s not React based, it’s actually other issues. 210:6 – Guest: https://redux.js.org. 21:53 – Guest: What’s the best way to use props? Where should I put my Logic versus... 22:15 – Panelist: This is very similar when I teach... 22:46 – Guest: I have seen people say that if you truly see how this works in JavaScript then you really understand how JavaScript works. React can be confusing if you are using class-based components. You have to use binder or error functions, etc. It becomes confusing at times. Another area you mentioned was state: component state or your application state. Two different things, but they interact with each other. Understanding the difference between the two. Should I store it in this store or...? 24:09 – https://www.digitalocean.com 24:47 – Panelist: Were you doing this as a side thing? How do you keep up in the industry if you aren’t making “real” projects? 25:25 – Guest gives his answer plus his background with companies, clients, and programs. Guest: I really wanted to build my own company, when I was thinking of ideas I came across some great brainstorming ideas. I have a lot of traffic coming to these tutorials. I really liked giving something back to the web development community. I liked interacting with people and getting them to their “Ah Ha!” moment. It’s able to support me and helps me moving forward. I follow a ton of people on Twitter – the React team. I pay a ton of attention to what people are looking to learn. I play around those things for my own edification. I pick up some contract work and it helps me to stay current. It’s always a culmination for things. Part of the job is not to fall behind. If you are creating tutorials you have to reteach yourself things as things changes. 28:46 – Panelist asks another question. How do you get new leads and new customers? 20:02 – Guest answers questions. Guest: I was on a mentality if “I build it they will come.” This isn’t the best mentality. That was not a good approach. I started working with a consultant: how do we get this out to people? No ads, no subscription service. My e-mail list. I have gone from 1,600 to 4,600 people on my email list. Find the people who are interested. 32:52 – Guest: Find your voice, and how you choose to deliver your information. Text? Video? Or both? What do you want to teach? Don’t teach what you think will sell the most. It’s more important to be excited an interested what you are teaching. 34:05 – Panelist: When I am teaching something I try to remember of the feeling when I was learning it. For example, Harrison Ford. What was I thinking? How did I learn this concept? 35:01 – Guest: When I learned React it was because a client asked me to learn it. 4-6 weeks of exhausting terror and me trying to learn this to make useful code for this client. In about that time (4-6 weeks) “Oh I understand what I am doing now!” We are still on good terms today with this said client. When I am trying to learn something, the next level is here is a blog, and comments. There aren’t a lot of intermediary steps. They explain every kind of step. I took a similar approach with my other course. That’s informed by my own experience when learning these different technologies. 37:08 – Guest: Yes – check out my newsletter, and my new resource every week. Follow me at Twitter or my personal Twitter where I talk about the NBA too much. Email me if you have any questions. 38:11 – Chuck: Anything else? Okay, picks! 38:24 – https://devchat.tv/get-a-coder-job/ 39:01 – Picks! Links:
- https://www.telerik.com/kendo-ui?utm_campaign=kendo-ui-awareness-jsjabber&utm_medium=social-paid&utm_source=devchattv
- https://rubyonrails.org
- https://angular.io/guide/quickstart
- https://devchat.tv/get-a-coder-job/
- https://redux.js.org
- https://www.adobe.com/products/premiere.html?ef_id=W6K5tAAAAKzsP-f1%3A20180919210348%3As&gclid=EAIaIQobChMI_Onk6_vH3QIVBgppCh1aAwEVEAAYASAAEgIu8vD_BwE&mv=search&s_kwcid=AL%213085%213%21247425965201%21e%21%21g%21%21adobe%2520premier&sdid=KKQOM
- https://closebrace.com
- https://closebrace.com/categories/five-minute-react
- https://egghead.io
- https://stateofjs.com
- https://statecharts.github.io
- http://jamesknelson.com
- http://cwbuecheler.com
- https://www.amazon.com/Christopher-Buecheler/e/B004KA4MLE
Become a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.
Panel:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel: Charles Max Wood Special Guests: Vesa Juvonen In this episode, the React Round Up panel talks to Vesa Juvonen about building SharePoint extensions with JavaScript. Vesa is on the SharePoint development team and is responsible for the SharePoint Framework, which is the modern way of implementing SharePoint customizations with JavaScript. They talk about what SharePoint is, why they chose to use JavaScript with it, and how he maintains isolation. They also touch on the best way to get started with SharePoint, give some great resources to help you use it, and more! In particular, we dive pretty deep on:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel: Charles Max Wood Special Guests: Matt Hernandez and Amanda Silver In this episode, the JavaScript Jabber panelists discuss Visual Studio Code and the VS Code Azure Extension with Matt Hernandez and Amanda Silver at Microsoft Build. Amanda is the director of program management at Microsoft working on Visual Studio and VS Code. Matt works on a mix between the Azure and the VS Code team, where he leads the effort to build the Azure extensions in VS code, trying to bring JavaScript developers to Azure through great experiences in VS Code. They talk about what’s new in VS Code, how the Azure extension works, what log points are, and much more! In particular, we dive pretty deep on:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel:
Panel: Charles Max Wood Tara Manicsic Nader Dabit Kent C. Dodds Cory House Special Guests: None In this episode of React Round Up, the panel discusses how they each got into React and they provide some great resources for people who want to learn more about React and what it’s all about. They emphasize the fact that React is a very straightforward language and can be used relatively painlessly with a little bit of learning before jumping in. In particular, we dive pretty deep on: