RRU 081: NX and Monorepos with Jeffrey Cross and Victor Savkin
React Round Up1 Loka 2019

RRU 081: NX and Monorepos with Jeffrey Cross and Victor Savkin

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
  • Leslie Cohn-Wein
  • Dave Ceddia
  • Lucas Reis
With special guest: Jeffrey Cross and Victor Savkin Sponsors Links Follow DevChatTV on Facebook and Twitter Picks Lucas Reis: Dave Ceddia: Victor Savkin: Jeffrey Cross: Leslie Cohn-Wein Special Guests: Jeff Cross and Victor Savkin.

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.

Jaksot(310)

RRU 061: Should Companies Have a Dedicated Frontend Team?

RRU 061: Should Companies Have a Dedicated Frontend Team?

Sponsors NetlifySentry use the code “devchat” for 2 months free on Sentry’s small plan Triplebyte offers a $1000 signing bonus CacheFly Panel Nader Dabit Lucas Reis Thomas Aylott Episode Summary Today the panel is discussing the necessity of companies having a dedicated frontend team. They begin by discussing the technologies that might be used by a dedicated frontend team. According to the panel, the necessity of a frontend team is determined by the size of the company. When you try to have a frontend team too soon, it ends up being a huge debacle, but once you get bigger and have multiple teams, it gets more useful. A company is ready for a dedicated frontend team when it is able to build with a common set of components. The panel discusses the concept of ownership in a company. Nader believes that things should be run where there is a team that’s in charge of building a component, and once the component has shipped, they are no longer in charge. The other panelists disagree with that method because they believe there is a danger of the project getting bloated. Thomas shares his experience with working for Facebook and Lucas talks about how he has previously set up his teams. They talk about the necessity of having a design system before having a React design system, and they all agree that it is useful Nader shares his experience with his brother working for Cartoon network and the design rules they had for the websites for each show like Dexter’s Lab and PowerPuff Girls. Since the panel agrees on the importance of consistency in visual communication and designs, they delve into deciding what is owned by the design system and what is shared between other teams, who maintains these things, and how to differentiate between the different kinds of components. They talk about the idea of Atomic Design in programming, separating component into categories called names like atoms, molecules, organisms, etc. Nader talks about his experience with this method. He found it difficult because components didn’t always fit cleanly into one category. The panel believes that it all comes back to ownership and it is important that companies are handling ownership well Links StorybookFrontendClouderaNext.jsGatsbyReact Native WebDoczMaterial Follow DevChat on Facebook and Twitter Picks Nader Dabit: React Native in Action by Nader Dabit Lucas Reis: Kickstarting a Library of Internal React Components for Multiple Teams by Javier Lefevre Thomas Aylott: The E-Myth RevisitedThe Design of Everyday ThingsAtomic Design by Brad Frost Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.

14 Touko 201945min

RRU 060: Linked lists in the Wild: React Hooks with Conlin Durbin

RRU 060: Linked lists in the Wild: React Hooks with Conlin Durbin

Sponsors NetlifySentry use the code “devchat” for 2 months free on Sentry’s small planTriplebyte offers a $1000 signing bonusCacheFly Panel Nader DabitJustin BennettLucas ReisDave CeddiaCharles Max Wood Joined by Special Guests: Thomas Aylott, Conlin Durbin Episode Summary Conlin Durbin is a front end software engineer for a company called Lessonly and occasionally writes about React. Thomas Aylott is a web guy from the 90’s who was briefly on the React team, and he makes thingsthatdostuff.com and groovytiesquad.com. The panel discusses  Conlin’s article Link Lists in the Wild: React Hooks. They begin by talking about the relationship between linked lists and React hooks. Linked lists are used under the hood to render hooks every time that they’re created and maintain integrity of the hook chain. They discuss the importance of knowing what goes on under the hood share their methods of learning. They give tips for learning on the job. The panel agrees that one of the best ways to learn is to teach. Conlin shares his experience working for Lessonly, a company that builds lesson-building software. The panel discusses WET (Write Everything Twice) vs DRY (Don’t Repeat Yourself) programming. They talk about when it is beneficial to have abstractions in code and when it is not. It’s also important to think about the humans that are going to be using it, and to write the code so that it’s humane. They praise good error messages that tell you exactly where you went wrong and how to fix it. They talk about the dangers of putting invariants everywhere, and finish by talking about ways to improve. Links Linked listReact FiberHooksBackboneJavaScriptReduxGatsbyFlowJake Archibald: In The Loop-JS Conf Asia 2018 (video)What the heck is the event loop anyway? (video)Practical 00 Design in  Ruby, Sandi MetzStop trying to be so DRY, instead Write Everything Twice (WET)Sebastian Markbage: Minimal API Surface Area – Learning patterns instead of frameworksSomeone Is Changing Your CodeConlin Durbin username for most places is ‘wuz’, except Twitter for twitter it’s @CallMeWuz Follow DevChat on Facebook and Twitter Picks Justin Bennett: The 3 most effective ways to build trust as a leader articlePheonix Live View Lucas Reis: Pamela ZaveSmall Functions Considered Harmful article Dave Ceddia: New Redux courseKinesis Advantage 2 Keyboard Charles Max Wood: MicroConfBuzzSprout Thomas Aylott: Noflojs.orgThe Laws of Human Nature by Robert Greene Conlin Durbin: https://dev.to/Soft Skills EngineeringConlin’s Discord serverSpecial Guests: Conlin Durbin and Thomas Aylott. Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.

7 Touko 20191h 10min

RRU 059: React Native's New Architecture with Parashuram

RRU 059: React Native's New Architecture with Parashuram

Sponsors NetlifySentry use the code “devchat” for 2 months free on Sentry’s small planTriplebyte offers a $1000 signing bonusCacheFly Panel Justin BennettLucas Reis Joined by Special Guest: Parashuram Summary Parashuram (aka Ram) and the panel compares various frameworks including the differences between React Native and NativeScript. Ram discusses what it’s like introducing react native to mobile teams which leads to a panel discussion of web app developer experience compared to mobile app developers. Ram shares the changes that are being made to React Native and what this means for its developers. Some of the things to look forward to are a leaner and more browser-like React Native.  The episode ends with Ram sharing a little of his story. Links http://artsy.github.io/blog/2017/07/06/React-Native-for-iOS-devs/http://artsy.github.io/artsy-x-react-native.htmlhttps://github.com/necolas/react-native-webhttps://github.com/vincentriemer/react-native-domhttps://microsoft.github.io/reactxp/https://facebook.github.io/react-native/blog/2018/11/01/oss-roadmaphttp://nparashuram.com/https://twitter.com/nparashuramhttps://www.facebook.com/React-Round-Uphttps://twitter.com/reactroundup Picks Justin Bennett: http://artsy.github.io/blog/2017/07/06/React-Native-for-iOS-devs/http://artsy.github.io/artsy-x-react-native.htmlhttps://github.com/vadimdemedes/ink Parashuram: https://github.com/react-native-community/discussions-and-proposalshttps://github.com/facebook/react-360 Lucas Reis: Family TimeSpecial Guest: Parashuram. Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.

30 Huhti 201950min

RRU 058: React.js and WebAssembly to Rewrite Native Apps with Florian Rival

RRU 058: React.js and WebAssembly to Rewrite Native Apps with Florian Rival

Sponsors NetlifySentry use code “devchat” for 2 months free Triplebyte Panel Lucas Reis Charles Max Wood Special Guest: Florian Rival Episode Summary Florian is a software engineer working for Facebook. He has previously worked with React Native making apps. He has also created an open source game creation software called GDevelop. Florian talks about his inspiration for GDevelop. He delves into the nature of GDevelop as a desktop app built on the web. Florian talks about his decision to not go full JavaScript in his app and to redo the interface. He ultimately decided to combine C++ and JavaScript, and top it with a React interface. Florian discusses how C++ is used in this web application and how it connects to react. The panel discusses the use cases for WebAssembly and the performance quality. They discuss the bundle sizes in WebAssembly compared to other languages and compatibility with different browsers. Florian talks about how WebAssembly and React work together in his app. He talks about some of the issues and solutions you had in desiging the UI and how he created the editable lists and trees. Florian concludes by saying that any LLVM language can be compiled into web assembly Links React NativeReactWebGLJavaScriptHTMLStorybookFeedback LoopC++The DOMAngularClankQT5EnscriptenC MakeEV computationC#WebAssemblyDomain Driven DesignSlackReact Sortable TreeCanvasGodotPixyLLVM Picks Lucas Reis: American food Charles Max Wood: Podfest Alita: Battle Angel Florian Rival: Material UIGatsbySpecial Guest: Florian Rival. Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.

23 Huhti 201957min

RRU 057: Playing with Polyhedra with Nat Alison

RRU 057: Playing with Polyhedra with Nat Alison

Sponsors NetlifySentry use the code “devchat” for 2 months free on Sentry’s small plan TriplebyteCacheFly Panel Justin Bennett Lucas Reis Joined by Special Guest: Nat Alison Summary Nat Alison shares with the panel her work in translating Reactjs. Lucas Reis thanks her for her work in this very important project. Nat updates the panel on how the translation is going and discusses some of the specifics of updating, changing language direction and how it all got started. The panel moves on to discussing Nat’s work with her Polyhedra application. Nat discloses what she learned while creating this app, how she tested the app and why she used the react framework for this project. The panel discusses suspense features and what they could do for this app. Nat ends the episode by sharing her inspiration for this app. Links https://github.com/reactjs/reactjs.org-translationhttps://reactjs.org/languageshttps://isreacttranslatedyet.com/https://polyhedra.tessera.li/https://github.com/tesseralishttps://twitter.com/tesseralishttps://www.linkedin.com/in/nat-alison-2768a449https://www.facebook.com/React-Round-Uphttps://twitter.com/reactroundup Picks Lucas Reis http://shadow-cljs.org/ Justin Bennett https://zeit.co/nowhttps://github.com/artsy/dupe-report Nat Alison https://www.npmjs.com/package/cronSpecial Guest: Nat Alison. Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.

16 Huhti 201950min

RRU 056: React Conf 2018 with Adam Laycock

RRU 056: React Conf 2018 with Adam Laycock

Sponsors NetlifySentry use the code “devchat” for $100 creditTriplebyte offers a $1000 signing bonusCacheFly Panel Charles Max WoodNader DabitJustin Bennett Joined by Special Guest: Adam Laycock Summary Adam Laycock describes his experience at React conf 2018, the atmosphere, the people and the talks. The panel shares how the approach conferences, taking notes, getting to know people, accessing information and getting out of their comfort zone. Adam shares some of the major topics covered at including, hooks, suspense, and concurrent rendering. The panel considers these topics and React conferences they look forward to attending. The episode ends with the panel comparing Angular and React, conferences, upgrades, and routers for React. Links https://www.microsoft.com/en-us/buildhttps://medium.com/curated-by-versett/talks-worth-watching-react-conf-2018-bfbdd40922aahttps://reactjs.org/community/conferences.htmlhttps://twitter.com/atlaycockhttps://github.com/alaycockhttps://adamlaycock.ca/https://medium.com/@adam.laycockhttps://twitter.com/reactrounduphttps://www.facebook.com/React-Round-Up Picks Charles Max Wood https://www.notion.so/The Effective Executive by Peter F. Druckerhttp://entreprogrammers.com/Michael FeathersKent Beck Nader Dabit https://dev.to/dabit3 Justin Bennett https://github.com/Bogdan-Lyashenko/codecrumbshttps://medium.com/palantir/tslint-in-2019-1a144c2317a9https://www.npmjs.com/package/rate-limiter-flexible Adam Laycock https://kentcdodds.com/blog/please-stop-building-inaccessible-forms-and-how-to-fix-themhttps://medium.com/curated-by-versett/dont-eject-your-create-react-app-b123c5247741Clean Architecture: A Craftsman's Guide to Software Structure and Design by Robert C. MartinSpecial Guest: Adam Laycock. Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.

9 Huhti 201956min

RRU 055: Building Static Sites with Gatsby with Ajay NS

RRU 055: Building Static Sites with Gatsby with Ajay NS

Sponsors NetlifySentry use the code “devchat” for 2 months free on Sentry’s small planCacheFly Panel Lucas ReisJustin BennettCharles Max Wood Special Guest: Ajay NS Episode Summary In this episode of React Round Up, the panel talks with Ajay NS, a Computer Engineering student at National Institute of Technology Surat who is passionate about frontend development and design. Ajay talks about his article Why you should use GatsbyJS to build static sites on Medium and why he felt the need to write it. After attending the Plone Conference in Tokyo where he gave a talk about GatsbyJS, he realized that compared to React or Angular, Gatsby helped new developers learn about frontend development without facing too many complications. Ajay explains that he decided to write the article and share his experiences with Gatsby to help ease the learning process for new developers who are curious about frontend development. They discuss best cases to use Gatsby for and also cases where it may not be a good idea to use it. They then discuss the best tools for people who are new to web development and are trying to find jobs as remote developers. One of the best methods recommended is pair programming which can also be done remotely. Links Why you should use GatsbyJS to build static sitesAjay NS — Plone Conference 2018 – TokyoAjay's Talk in the Plone ConferenceAjay’s LinkedInAjay’s TwitterAjay’s GitHubNetlifyEleventyhttps://www.facebook.com/React-Round-Uphttps://twitter.com/reactroundup Picks Justin Bennett: gatsby-starter-typescript-rebass-netlifycmshttps://github.com/artsy/palettehttps://github.com/FormidableLabs/inspectpack Lucas Reis: react-spring Charles Max Wood: Green ScreenLED lighting for video  Ajay NS: https://github.com/storybooks/storybookBodymovin PluginSpecial Guest: Ajay NS. Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.

2 Huhti 201959min

RRU 054: GraphQL and React – Even Better together with Chris Toomey

RRU 054: GraphQL and React – Even Better together with Chris Toomey

Sponsors Sentry use the code “devchat” for $100 creditTriplebyteCacheFly Panel Lucas ReisJustin BennettCharles Max Wood Joined by special guests: Chris Toomey Episode Summary In this episode of React Round Up, Chris Toomey introduces himself, talks about his work and his podcast and moves on to explaining the differences between a React vs GraphQL centric application. Justin explains in detail how the Relay framework works, and Chris describes the scenarios where GraphQL stands out in the process of building an application and also throws some light on the benefits of choosing it over other APIs such as REST. The panel then discusses how GraphQL is advantageous in the documentation context since it has a good schema, and also in data modeling. Chris shares some past examples of creating React applications where GraphQL and Apollo made things much simpler, and also elaborates on the trade-offs and challenges associated with it. Links The Bike ShedChris Toomey: React & GraphQL – Bringing Simplicity to Client-Side Development / React Boston 2018Chris’s TwitterThe Past, Present, and Future of GraphQL Native - Nick Schrock @ GraphQL Europe Picks Justin Bennett: Where art thou, my error?Auto by Intuit on GitHub Lucas Reis: MDX Deck libraryCode Surfer library Charles Max Wood: HubSpotZapierGoogle Docs Chris Toomey: Tell me when it closesQuicklinkUpcaseSpecial Guest: Chris Toomey. Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/react-round-up--6102072/support.

26 Maalis 20191h 11min

Suosittua kategoriassa Liike-elämä ja talous

sijotuskasti
psykopodiaa-podcast
mimmit-sijoittaa
rss-rahapodi
ostan-asuntoja-podcast
rss-lahtijat
pomojen-suusta
taloudellinen-mielenrauha
rahapuhetta
io-techin-tekniikkapodcast
oppimisen-psykologia
rss-seuraava-potilas
inderespodi
kasvun-kipuja
sijoituspodi
hyva-paha-johtaminen
rss-markkinointiradio
leadcast
kultaiset-hoitajat
rss-rikasta-elamaa