Speaker 1: Welcome to React Round Up, and I'm Jack Harrington, your
Speaker 1: host for today and with me our page. Hey everybody,
Speaker 1: and TJ Hey everyone, And our guest today.
Speaker 2: Is Chris Laughlin. Hey everybody, all right, Well.
Speaker 1: Chris, why do you start us out by telling us
Speaker 1: a little bit about why you're here and what you
Speaker 1: want to talk about?
Speaker 2: Yeah?
Speaker 3: So I was My name is Chris Laughlin. I recently
Speaker 3: published an article for side Points. I'm using the webcit
Speaker 3: speech recognition ape guy built in the browser and then
Speaker 3: building that into erect application. So many to utilize your
Speaker 3: voice to potentially control an application, do different commands, interact
Speaker 3: with it in a novel in different way.
Speaker 2: And that's awesome. So how did you apply that in
Speaker 2: this particular case?
Speaker 3: So in this case I kind of went through an
Speaker 3: iteration of building a basic speech recognition function alown a
Speaker 3: user bibility to turn on the marketphone, speak to the browser,
Speaker 3: and then kind of follo about how I get like
Speaker 3: build this and do the React way of thinking. So
Speaker 3: using you know, hooks is the modern way of building
Speaker 3: React applications to decide write, okay, let's build this in
Speaker 3: first just a normal functional component, then start ups tracking
Speaker 3: us out in the hook trying to find the bits
Speaker 3: and pieces that were unique and reusable, and then created
Speaker 3: a used voice hook that you could then start recording voice,
Speaker 3: stop recording voice, and in return that translated text. So
Speaker 3: then a React application could you take advantage of this.
Speaker 3: The example that I used in the in the article
Speaker 3: was to search for all books based on the author's name.
Speaker 3: So using the Open Library Web API, you could say
Speaker 3: like your favorite authors, or like Roule Dal or think
Speaker 3: of other authors. I can't think of any of the
Speaker 3: top of the head. Yeah, yeah, all token. So then
Speaker 3: using that that then call it and bring back a
Speaker 3: list of books. I think the beauty is that you
Speaker 3: never touched the keyboard de voice to do that. Interactions
Speaker 3: all through vocal commands.
Speaker 4: So was there some business application that you were trying
Speaker 4: to solve with this or was this more of just hey,
Speaker 4: this is a cool web API. I want to see
Speaker 4: what I can do with it.
Speaker 3: I yet to find a business API. I had a
Speaker 3: business reason for applying this, Yeah, I think for my case, like,
Speaker 3: I do a lot of kind of like you know,
Speaker 3: side projects where I try and take an API and
Speaker 3: or library and build something fun and interesting. So the
Speaker 3: first version of this application was a Giffee search, So
Speaker 3: using the giffees API to like search for gifts using
Speaker 3: your voice because usually like I can never think of
Speaker 3: what the type out, but I could probably just say
Speaker 3: a phrase and get back like a funny gift. So
Speaker 3: I wanted to like apply this to see different levels.
Speaker 3: But from kind of buildness side it can. It made
Speaker 3: me think about different applications. So if you had a website,
Speaker 3: you could potentially have like a don' want to say
Speaker 3: the key word case people are listening to this outliine,
Speaker 3: but hey, no gorgle, you know interock with my site,
Speaker 3: so like no contact support. Potentially you know, tell them
Speaker 3: your problem in type the problem.
Speaker 5: Yeah, I think I've seen this. This is to me,
Speaker 5: this falls in the bucket of the sort of APIs
Speaker 5: that are pretty common and native mobile apps that I
Speaker 5: think people just don't expect to be on the web
Speaker 5: because I know I personally don't use it, but I'm
Speaker 5: aware of several native apps that have this, like searches.
Speaker 5: I think the super common one that anytime you're searching
Speaker 5: for someone something, giving people an option to just say
Speaker 5: it versus typing it out can be kind of handy
Speaker 5: and actually that makes me wonder because I'm wondering, like
Speaker 5: what the engine is under this, Like is the API good? Like,
Speaker 5: because that's that's like my biggest concern with these things
Speaker 5: that like I talk to these and I search for J. R. R.
Speaker 5: Tolkien and then it's looking for like JBB Tollinger or
Speaker 5: something like that. Right, So when you're playing with this,
Speaker 5: like did it do a pretty good job working with that?
Speaker 3: I was pleasantly surprised how well it worked. Like I
Speaker 3: have an Irish accent, and usually like when I talk
Speaker 3: to my own like smart speaker at home, I would
Speaker 3: say seven percent time it doesn't understand me for the
Speaker 3: browser able to pick us up, and I've you know,
Speaker 3: I mumbled towards it and I talk really fast and
Speaker 3: talk really slow and pitch my voice. It was still
Speaker 3: Attleit pickout everything you can feed it like a grammar list,
Speaker 3: so you can say, like these are no key words
Speaker 3: that you're going to be looking at for and particular
Speaker 3: words that may or may not be understood. As far
Speaker 3: as understanding it's it's working off like the Chrome level API.
Speaker 3: So I think Google's may be back in this with
Speaker 3: their can I speak condition.
Speaker 5: Yeah, it's sort of interesting because considering it's a browser API,
Speaker 5: presumably each browser would have to provide their own implementation,
Speaker 5: right Like, I can't. I doubt it's like the W
Speaker 5: three C doesn't like they wouldn't provide an implementation. So
Speaker 5: I imagine it would be up to like Google and Apple
Speaker 5: and Mozilla, et cetera to sort of come up with
Speaker 5: the actual engine that drives this, right.
Speaker 6: Yeah.
Speaker 3: Unfortunately, like the Bruiser support and I think for that
Speaker 3: reason is very minimal. I think at the moment it's
Speaker 3: agile Chrome fully supported, Firefox with low support, so you're
Speaker 3: kind of stuck with the browser that you're working with,
Speaker 3: and that that's kind of the other challenge when it
Speaker 3: came to emviolentness was doing Browiser detection inside of the hook,
Speaker 3: and then you know with doing conditional statements inside hooks,
Speaker 3: like you know, we use a fact and stuff don't
Speaker 3: play nice if you put them inside the conditional so
Speaker 3: kind of having the hacker round that.
Speaker 2: So you tell me us or go to Chrome where
Speaker 2: this isn't going to work, I say seventy percent. I'm sorry,
Speaker 2: go ahead.
Speaker 1: I got to say seventy percent is pretty good. My
Speaker 1: my home speaker seems to hate me. You can get
Speaker 1: like thirty percent, but I'm really impressed here. I think
Speaker 1: this article to me is like a twofer. You get
Speaker 1: not only this insight into this really cool speed recognition API,
Speaker 1: but also how to write a custom hook around it,
Speaker 1: which I think a lot of people tend to avoid
Speaker 1: in React. So it's good to see a demonstration of that.
Speaker 1: Is that something you do a lot, it's customer hooks?
Speaker 3: Yeah, Like I'm a full time React developer with the
Speaker 3: kind of like these little side projects that build. Usually
Speaker 3: you always end up in like one or two files
Speaker 3: at max, so kind of build little hooks in and
Speaker 3: you know, trying to abstract layers out. And as part
Speaker 3: of the learning process of doing this was like how
Speaker 3: can I build this? How I can make it reusable?
Speaker 3: I probably won't use it again because you know, the
Speaker 3: middle of the side project is completed, it's dead, and
Speaker 3: the next sledge project takes over. But building it into
Speaker 3: like a reusable kind of pattern at least teaching me
Speaker 3: how to build scalable, reusable code. Maybe eventually I'll release
Speaker 3: it as an MPM package, but there's probably already one
Speaker 3: rut there that does this.
Speaker 5: We use voice as a fantastic name, so you've got
Speaker 5: the naming down as well.
Speaker 2: The domain.
Speaker 5: I am curious how you chose to deal with because
Speaker 5: this strikes me as a really unique situation, like a
Speaker 5: hook that sort of like conditionally works. So I'm curious,
Speaker 5: like what approach did you take, Like what what would
Speaker 5: look using the hook look like if you're in a
Speaker 5: browser that doesn't support these APIs at all?
Speaker 3: So if yours doesn't support it, it'll it'll do the
Speaker 3: pricer detection annoyingly in the hook, like the state to
Speaker 3: handle what text was returned from the API and the
Speaker 3: weather it's recording or not recording, because you can turn
Speaker 3: it off and on. Annoyingly, you can't have them after
Speaker 3: a conditional statement because of the way hooks work, so
Speaker 3: you can't have to declare the state. They'll exist. But
Speaker 3: then an if statement will check to see if your
Speaker 3: browser supports it and then returns a value to say
Speaker 3: like this is an own supportive browser, which then you
Speaker 3: can control like a visual message to say, you know,
Speaker 3: please try a different browser. I wish that I could
Speaker 3: have had that before and not even created any of
Speaker 3: the state variables that were needed for this to work,
Speaker 3: But the nature of React kind of just made it
Speaker 3: go that way.
Speaker 1: Is a really great library out there, React use that
Speaker 1: has a whole bunch of really great hooks on it,
Speaker 1: and it does have a speech one, but it's actually
Speaker 1: the opposite. It's given me a piece of text and
Speaker 1: I'll speak it for you. So this could be a
Speaker 1: nice other side of that. So you can always pr
Speaker 1: that into that repo and get it out there.
Speaker 3: Yeah, I think contribute to one people where they were
Speaker 3: taking different hooks for different uses, and one was that
Speaker 3: used economic code. So you can declare the use economic
Speaker 3: code and the user could type in the a being
Speaker 3: updown that right, start and then trigger and action based
Speaker 3: on that.
Speaker 4: I've seen some other repos or some other pieces of
Speaker 4: code that have done that, And one of the developers
Speaker 4: that I learned from actually told me that he had
Speaker 4: done that at a previous place of employment, that if
Speaker 4: you typed in the economic code, a fireball and come
Speaker 4: across the browser window, which is pretty cool. So you
Speaker 4: said they you work with React full time in your
Speaker 4: day job. What is your day job?
Speaker 3: So I'm like titles principal software engineer, but I manage
Speaker 3: the team of UI developers working on a secret book.
Speaker 3: So I work for a company called rap at seven.
Speaker 3: We do like cybersecurity, so we have like a large
Speaker 3: scale React project, our own style and library. We build
Speaker 3: our own React component library as well, so we work
Speaker 3: across those teams kind of building maintaining improving our scalability
Speaker 3: when it comes to building a component that can work
Speaker 3: across from multiple products as well. Building this into the
Speaker 3: more like usable, user friendly, and also adding like layers
Speaker 3: of security in there to keep things protected and safe.
Speaker 4: That sounds challenging to say the least.
Speaker 3: It's very challenging, especially like with the code basically work on.
Speaker 3: We'd started whenever React with Virgin fourteen and everything was
Speaker 3: written completely different then, and when you have a code
Speaker 3: base of over the thousand files, it's hard to rewrite
Speaker 3: everything the modern way doing that. So we have like
Speaker 3: three different state management libraries mixed across the code base. Classes,
Speaker 3: functional components, hooks, all that kind of stuff.
Speaker 1: Yeah, that can be really challenging to make sure that
Speaker 1: you get that consistency across the code base.
Speaker 2: It's interesting.
Speaker 1: I'm a Princevial engineer as well, and it's cool to
Speaker 1: see you going and investing your time into building these
Speaker 1: little projects like this and communicating that that information about
Speaker 1: how those work, because that's actually I think one of
Speaker 1: the primary roles of a princevial engineer is that kind
Speaker 1: of education. So is this something you do a lot of,
Speaker 1: is like talk to your teams, show small examples of
Speaker 1: how to do stuff.
Speaker 3: Yeah, I find like I'm very much of a do
Speaker 3: something to learn kind of person, So I'll have to
Speaker 3: build a little small Projects'll have to take some of them.
Speaker 3: Like if I find someone tweaking about some new utility library,
Speaker 3: I'll go off and try and build an example so
Speaker 3: I can understand that to bring it back to the
Speaker 3: team and they kind of recycle and share that knowledge
Speaker 3: because there's no there's no like well there's lots of
Speaker 3: courses money, but sort of there's no formal education. JavaScript
Speaker 3: that wasn't like a certificateation you could do, so kind
Speaker 3: of have to learn and it was always learning in
Speaker 3: the evenings and then bring it back into the team.
Speaker 3: So now we try and change that pattern. We're doing
Speaker 3: a lunch and learn with the team, you know, maybe
Speaker 3: using the course or using someone, you know, random tweak
Speaker 3: that we've seen building the pots. We have one really
Speaker 3: interestingly recently where we were looking at a different way
Speaker 3: of doing a switch statement. So using conditional cases, we
Speaker 3: pass in through and then the logic is the needs
Speaker 3: of the cases and whether like this is a viable
Speaker 3: thing to use, when is the use case for how
Speaker 3: you can build it, and then building out different examples
Speaker 3: the team could understand what it meant.
Speaker 4: That's what I was going to ask, is you know,
Speaker 4: it's it's very cool to learn about this stuff, but
Speaker 4: sometimes I'm just at a loss for what do I
Speaker 4: want to learn because there's so many interesting things happening,
Speaker 4: and Twitter is, you know, changing at rapid speed. So
Speaker 4: how do you how do you kind of, I guess,
Speaker 4: filter out the grip it and say, hey, this is
Speaker 4: something that actually could be interesting to learn about and
Speaker 4: then be possibly be useful in the day to day
Speaker 4: of what our team is doing.
Speaker 3: I think I'm very guilty of using Twitter too much
Speaker 3: as like a pipeline for information. But I think after
Speaker 3: a while you see the pattern of someone will tweet
Speaker 3: this is amazing, this is the best thing ever, and
Speaker 3: then two weeks later a little tweet and like, this
Speaker 3: is the best thing ever. In a contradict that the
Speaker 3: first week I was actually talking to them. Remember the
Speaker 3: team recent but kind of you know, kind of grew
Speaker 3: your knowledge how to focus. And he was asking me
Speaker 3: like different books to recommend, and I kind of let
Speaker 3: more towards like recommend the podcasts, Like this podcast is
Speaker 3: a great resource. But there's a number of other react
Speaker 3: ones and dropscript ones are you and I find they're
Speaker 3: really good because like this, these people are you know, focus,
Speaker 3: they're trying to like share and teach. That'll filter out
Speaker 3: all the noise you get from Twitter or Another great
Speaker 3: resource is like newsletters, so you know Josh Grip Weekly Actiatus.
Speaker 3: Those kind of news letters can give you a good
Speaker 3: list of like these are the articles of people have
Speaker 3: felt of some importance and they're worth looking into. There's
Speaker 3: a lot of noise and a lot of information, but
Speaker 3: it's kind of over time you learn how to felt
Speaker 3: the right like yeah I don't need to read this,
Speaker 3: or oh yeah I should read that.
Speaker 5: I feel like one of the more valuable skills is
Speaker 5: you almost develop like your own algorithm for processing all
Speaker 5: this information, right, Like if I see something come up
Speaker 5: this many times, or if this is relevant to me
Speaker 5: in some way, then it reaches that level of like
Speaker 5: maybe I should check this out otherwise, like because when
Speaker 5: you first get started, you just get it's easy to
Speaker 5: get overwhelmed because you think like everything's important. Then you
Speaker 5: realize like only a small subset is probably important to you,
Speaker 5: and learning to recognize that it's almost the skill in
Speaker 5: and of itself.
Speaker 6: Yeah.
Speaker 3: I think filtering is really good because at the beginning
Speaker 3: I would read every article and try and understand everything,
Speaker 3: and then I got the point where like, well, what
Speaker 3: am I doing day to day that I need to improve?
Speaker 3: So like, if I see a typescript, I don't write
Speaker 3: use typescript, I do want to eventually use it. About
Speaker 3: me keeping up with the latest of bounce with the
Speaker 3: typescript when I'm not actively doing it, isn't that I
Speaker 3: help where I could be reading something else? So like,
Speaker 3: is there a new table library out there that's so fast?
Speaker 3: Is there a better you know, API for talking to
Speaker 3: graph gl or managing the state and opusing all that
Speaker 3: instead of learning something I know I'm never going to use.
Speaker 3: I go through the pattern of open a newsletter out
Speaker 3: of ring the pocket and then never read it over again.
Speaker 3: But I start tiging things like I will eventually read
Speaker 3: this article usually a date.
Speaker 1: Yeah, you end up with a massive reading list. I know,
Speaker 1: I have several incognito windows that it's like, oh, yeah,
Speaker 1: I'll get there, eventually, I'll read that article.
Speaker 2: I know it.
Speaker 1: And yeah, unfortunately I end up falling into that trap
Speaker 1: of clicking on those clickbait articles just too easily.
Speaker 4: Yeah, the group tabs that Chrome introduced not that long ago,
Speaker 4: it's been a good thing and a huge detriment to
Speaker 4: me because I'm never going to close that group, even
Speaker 4: though I'm actually never going to read those articles that
Speaker 4: I grouped together.
Speaker 3: I've seen the recently released search for your Times and
Speaker 3: I was like, that's a submission to broken, like a
Speaker 3: broken and just making it worse.
Speaker 2: So true, Hi Carl, welcome to the party.
Speaker 3: Hey hey, s.
Speaker 6: Had him over a bit.
Speaker 1: Yeah, absolutely, meet Chris. And Chris did an article on
Speaker 1: speech recognition API. Yes, hey, good good, I'm by the
Speaker 1: I'm in England. So just because the border and nine.
Speaker 6: That name is.
Speaker 3: Enjoined the Goodwiller, We're finally.
Speaker 7: Oh gosh today it was okay in the morning, but
Speaker 7: now I've been reading a bit so yeah, passic English weather.
Speaker 2: Say good weather in England. That's that's not as.
Speaker 4: Advertised, unheard of, so Chris, I'm curious because I'm looking
Speaker 4: you've written a number of articles for site Point. How
Speaker 4: did you get started kind of taking these projects that
Speaker 4: you were building and then besides sharing them with your
Speaker 4: team and with the people that you work with regularly,
Speaker 4: how did you get into like actually writing these these
Speaker 4: tutorials and stuff.
Speaker 3: I think it's some of like a couple of years ago,
Speaker 3: like most developers always have my own blog, and you
Speaker 3: spent more time rewriting the blog architecture and writing blog posts.
Speaker 3: And I got the one where like when I did
Speaker 3: write a blog post, I was like, yeah, this is cool,
Speaker 3: maybe I'll share it all read it, but no one's
Speaker 3: really going to read it, and there's no motivation to
Speaker 3: keep me learning, and were just and trying to find
Speaker 3: me things it was fly enough to develop our work with.
Speaker 3: He had written a Java article for site Points and
Speaker 3: he was like, yeah, like you can submit an article
Speaker 3: and you know they'll publish it. I'm like, this is
Speaker 3: this is awesome. So this has given me like a
Speaker 3: kick in the backside to say, right, you know I've
Speaker 3: submitted this, I need to actually build and write and
Speaker 3: you know, create an application for this post. So that
Speaker 3: kind of like snowball from there. And every time I
Speaker 3: would post something, that's like, right, well, now I need
Speaker 3: to find a new idea to post the next one.
Speaker 3: And it kept me like really engaged with like what
Speaker 3: can I learn new? What's brand new out there. One
Speaker 3: of the articles I posted recently was on the React
Speaker 3: framework Remotion, and it was like brand new at the
Speaker 3: time building videos using React, and I was like, this
Speaker 3: is amazing. I need to write about this share so
Speaker 3: other people can see it and can continue to getting
Speaker 3: that feedback. And it's kind of it's rewardedt to see
Speaker 3: that you're sharing your knowledge, are getting it out there
Speaker 3: so others can build and grow and do the same.
Speaker 5: Say, Remotion is really really fun. Maybe you could if
Speaker 5: you wrote about it, could explain to the audience like
Speaker 5: roughly what it is, because I think it's a pretty
Speaker 5: exciting project.
Speaker 3: Also, yeah, it's really cool. I kind of liken it too.
Speaker 3: It's almost like Windows movie Maker, but for the browser,
Speaker 3: so you can like you run Remotion that's like the
Speaker 3: applications itself, and then it'll bring up a prevy window
Speaker 3: you can scrub through a video. But the brilliant part
Speaker 3: is like how you actually create a video. So if
Speaker 3: I want to go and create a vidy and I
Speaker 3: and like I needed graphics and move around the screen,
Speaker 3: I would have to get you some software written by
Speaker 3: Adobe or someone like that and pay licensing and everything.
Speaker 3: Whereas remotions free open source. I can just run that
Speaker 3: from MPM. It works in the visor. So the core
Speaker 3: Remotion is like a library that allows you to use
Speaker 3: React components to build out frames of a video, and
Speaker 3: then re Emotion allows you to expert out so you
Speaker 3: can use reacts, HTML, CSS, whatever you normally build a
Speaker 3: web application of, but it generates a video at the
Speaker 3: end of it.
Speaker 5: Yeah, and it's cool because I've always thought it's an
Speaker 5: interesting project because there are people out there that use
Speaker 5: like these, like Adobe tools or there's other tools like
Speaker 5: it to create these things. But and there's people that
Speaker 5: are very good at that. But if you're building with
Speaker 5: web tech, if you're building with React, like it opens
Speaker 5: so many doors that you could never do with a
Speaker 5: tool like that. Like if you wanted to programmatically do
Speaker 5: some things as part of your videos, Like let's say
Speaker 5: you want to generate a unique video for like each
Speaker 5: of your users, right and bring in some like customized stats,
Speaker 5: Well you can use a fetch call to bring in
Speaker 5: some stats and like incorporate that into your video production
Speaker 5: or like algorithmically change parts of the video based off
Speaker 5: of whatever. Right, It's it's a React app, So the
Speaker 5: sky's the limit, and it sort of just blows my
Speaker 5: mind a little bit at the possibilities just because it's
Speaker 5: it's just such a unique idea because I would have
Speaker 5: never thought to build videos with React, right, like in
Speaker 5: my brain, like I have a segmented part for like,
Speaker 5: oh yeah, that's for like really complicated Adobe tools or
Speaker 5: screen Flow or Cantasia or whatever, like that's not something
Speaker 5: I do with web tech.
Speaker 2: That's that's nuts.
Speaker 3: It's interesting you mentioned like the kind of customization because
Speaker 3: as it was like working with it, I kept thinking
Speaker 3: like we're wheking this, go hyping this get better because
Speaker 3: of just it wrong three MPM how you normally wring
Speaker 3: a code, Like what if you set up with get
Speaker 3: up action every time you re release like open source library,
Speaker 3: it generates a release notes video that can then automatically
Speaker 3: publish the Twitter. And I was talking to someone recently
Speaker 3: who was like big in the no code movement where
Speaker 3: you could then utilize that so users could be building
Speaker 3: videos in a drag and drop environment, but it's all
Speaker 3: just React code under the hood.
Speaker 5: Yeah, because I mean all you had to do, like
Speaker 5: you could picture a form where you just put in
Speaker 5: what's my project, what's my version number, and then a
Speaker 5: remotion project grabs that information programmatically from GitHub, tosses it
Speaker 5: into the video, spits out a like MP four whatever
Speaker 5: video file, and like you said, like you could tie
Speaker 5: that into like integrations posted somewhere.
Speaker 2: It's it's kind of cool and kind of nuts.
Speaker 6: Yeah.
Speaker 7: I think React it's actually coming kind of like a platform,
Speaker 7: right because you've got so many libraries for like an
Speaker 7: one for like three D stuff, one for gaming, one
Speaker 7: for this, one for remotion, So you can see probably
Speaker 7: in the future that becomes this kind of platform you
Speaker 7: can kind of build all kinds of things on it,
Speaker 7: as opposed to be when it started off, was an
Speaker 7: ib for you at a moment, But now it's kind
Speaker 7: of morphing into this thing where you can basically do
Speaker 7: a lot more of it than at the beginning.
Speaker 4: Yeah, it sounds a little bit familiar, a little bit
Speaker 4: similar to recut if you've seen anything about that on
Speaker 4: Twitter that Dave, I think Dave Sidia created it, and
Speaker 4: what it does is if you're filming and I don't
Speaker 4: know if it's built with React under the hood, actually,
Speaker 4: but if you're filming and you stop speaking or you
Speaker 4: flow a line or something like that, it makes it
Speaker 4: very easy to take out the I guess the line
Speaker 4: that you've potentially messed up while you're speaking, as well
Speaker 4: as any silences. It just automatically cuts those out, which
Speaker 4: people have been saying is really amazing for all the
Speaker 4: content creators out there.
Speaker 1: Yeah, there actually is like an off the shoe shelf
Speaker 1: product for that called the Script, which is really good.
Speaker 1: It actually gives you a running translation or I guess
Speaker 1: transcript as you go, and then you can literally just
Speaker 1: like edit your your text be like oh those arms,
Speaker 1: just get rid of them, done, and it does the transition.
Speaker 2: It's very smooth.
Speaker 4: Oh, very cool.
Speaker 5: Yeah, I'm just like recatting. It still amazes me that
Speaker 5: this is built with React and not like, I don't
Speaker 5: know C plus plus.
Speaker 7: I had a question for Chris regarding your unblogging a
Speaker 7: U A workflow that you you kind of have kind
Speaker 7: of figured out over the years in terms of your drafts,
Speaker 7: and then you put your research, your ideas and your
Speaker 7: editing publishing, like what's your what's your thing? That your
Speaker 7: posts for your brooking.
Speaker 3: Lige wholeheartedly and that it's not perfect, and it follows constantly. Yeah,
Speaker 3: because at the beginning I would just start writing and
Speaker 3: then get really confused and you know, get bored halfway
Speaker 3: through the article and just want to write the conclusion.
Speaker 3: But it can I start of like usually each each
Speaker 3: post is is based on you know, using something in
Speaker 3: job script to do something or exposing like a new
Speaker 3: framework libry. So I'll think of an idea of like
Speaker 3: why can I take this make it fun so relatable
Speaker 3: that you know, isn't as a do app or isn't
Speaker 3: you know, some sort of business logic that you would
Speaker 3: do as a practice in a workplace. To build out
Speaker 3: that application as a building, I'll take notes to think
Speaker 3: we are the important parts, where did I struggle, Where
Speaker 3: did I get excited, and like all this is really
Speaker 3: cool that that worked and it's kind of thing. So
Speaker 3: build the list of that. That usually then kind of
Speaker 3: forms into the contents of it, like you know, getting
Speaker 3: start with this, running on the issues how to debook that,
Speaker 3: then build out a little bit further kind of like
Speaker 3: go through you know, iterations how you could potentially change
Speaker 3: that out, and then you flash that into the final
Speaker 3: article where it'll like flow like a tutorial, but not
Speaker 3: very much like a kind of do this and then
Speaker 3: do this and copy that command do that command. I
Speaker 3: kind of let the user figure it out what themselves,
Speaker 3: but also kind of literally guiding them along the kind
Speaker 3: of journey that I had whenever I was doing this.
Speaker 4: Yeah.
Speaker 1: I think that's a great way to get your side
Speaker 1: projects out there. I know there is a ton of
Speaker 1: hilarious tweets about like, oh, you know, this is yet
Speaker 1: another side project that I've gotten myself into and having
Speaker 1: that output at the end of it, Like hey, I'll
Speaker 1: just you know, make a dev two article on this,
Speaker 1: and that gives me some conclusion point and something I
Speaker 1: can go back to later and take a look at
Speaker 1: it if I choose to get back into it. Hey,
Speaker 1: I got my own thing written by me. It explains
Speaker 1: it to me, but it's also helpful and it gets
Speaker 1: it out there and it gets it on your resume.
Speaker 1: It's like, oh, this is something else I can do.
Speaker 1: I can teach people about how to do the cool
Speaker 1: stuff like speech recognition.
Speaker 3: Yeah, like for me, it kind of really progress. At
Speaker 3: the start of like the lockdown, I was at home
Speaker 3: at all the time. I need to be learned. I
Speaker 3: need to do something to keep myself busy. So I
Speaker 3: decided I'm going to start a Twitch channel. I'm going
Speaker 3: to start a series called Hello Drunk World, where I
Speaker 3: have a glass or two of wine and get myself
Speaker 3: an hour and a half to go from like an
Speaker 3: empty folder to a full application published live that users
Speaker 3: can access and each time try and use something I've
Speaker 3: never used before, so may it be like a random
Speaker 3: library or an API, and then kind of build and
Speaker 3: grow upon that. And it gave me that kind of
Speaker 3: structure of like I need. And they start off with
Speaker 3: every two weeks. Now it's every fortnight, and then it's
Speaker 3: probably turning every month. But I had this kind of
Speaker 3: fear every Sunday night. I need to think of a
Speaker 3: brand new idea and an application I can build using
Speaker 3: this random bit attack to kind of learn and grow.
Speaker 2: I want to watch that. I'm so.
Speaker 3: It's good fun. It's good to kind of do that.
Speaker 3: And then I like the fact because I was explaining
Speaker 3: to some coworkers that I'm I'm a couple of drinks
Speaker 3: like coding, and everyone has that fear like if someone's
Speaker 3: over your shoulder watching your code, You're going to make mistakes,
Speaker 3: You're going to do typos, You're going to run the problems.
Speaker 3: And I like it's constantly just shouting to the people
Speaker 3: on Twitch and like, right, where am I going wrong?
Speaker 3: I can't see the problem here? Is it a semi
Speaker 3: colon or something else? Like someone how's to help me?
Speaker 3: Especially like I'm really bad at CSS, So anytime you
Speaker 3: came to style and I was like, what am I
Speaker 3: trying to do here? And like asking people in the
Speaker 3: chat like give me what I need.
Speaker 4: Yeah, that's awesome that it's kind of that live experience
Speaker 4: of people talking to you in real time. Although it
Speaker 4: seems like it would be difficult because I've not really
Speaker 4: done much live stream to keep up with both what
Speaker 4: you're trying to do on your own screen and what
Speaker 4: people in the chat are talking to you about at
Speaker 4: the same time, it's.
Speaker 3: Not too bad. The kind of minds I always said
Speaker 3: at the start, like it's fine if I ignore people
Speaker 3: in the chat. I kind of try and think like
Speaker 3: I'm doing this alone, and I'll look off to the
Speaker 3: side when I'm stuck.
Speaker 2: Now, I think it might be easier if you're a
Speaker 2: little tipsy.
Speaker 1: I gotta say kind of, you know, Lucy, I'm sure
Speaker 1: there's like a curve where too many drinks and it's
Speaker 1: just it's not coding anymore.
Speaker 2: But somewhere in the middle there is a.
Speaker 1: Nice sweet spot of a productivity where you're okay with
Speaker 1: people looking over your shoulder.
Speaker 3: Yeah. The start, I'm very quiet and reserve, and then
Speaker 3: by the end of it, when not deploy button, it's
Speaker 3: like no one can stop me.
Speaker 1: Oh yeah, And I think that the deploy button might
Speaker 1: have to have to have a trigger on it. You know,
Speaker 1: X number of drinks, you know, I can't hit the
Speaker 1: deploy button anymore.
Speaker 4: It's a math before this will deploy.
Speaker 1: The production exactly like that Google thing. Are you sure
Speaker 1: you want to send this email right now?
Speaker 2: So?
Speaker 1: What are some other side projects you've done that our
Speaker 1: listeners might be interested in?
Speaker 3: Don't think? Well, so, I think the first one I
Speaker 3: did was trying to build build an application was felt
Speaker 3: because I never used it. So I was trying to
Speaker 3: come from the React pantagy and the learns felt and
Speaker 3: I was like I was building tender for dogs, but
Speaker 3: trying to use felt the whole way through it, And
Speaker 3: I thought that was a kind of good one because
Speaker 3: I like started with that kind of built upon it,
Speaker 3: built upon it, and then kind of trying to learn
Speaker 3: how to use stayed in this library, how to make
Speaker 3: shareable components, and trying to flash it out. I think
Speaker 3: that kind of snow the next time that I was
Speaker 3: working with Redwood, because I do want to deployments with Netify,
Speaker 3: so I kind of try and stick with the jam
Speaker 3: stack kind of style. So I was like, right, I
Speaker 3: want to use Redwood. I want to deploy a full
Speaker 3: jam architecture. It went hardly wrong and I never made
Speaker 3: the light a day, but kind of like learning using
Speaker 3: the API is building upon it. I kind of trying
Speaker 3: and always make them, make them a little bit fun
Speaker 3: and kind of quirky. So there's one of the reasons
Speaker 3: where I was interested on everyone wants to make bumble
Speaker 3: sizes smaller and optimize you know what libraries are print
Speaker 3: in their product, and there's always people talking about like
Speaker 3: all you know this library ships and it's no not
Speaker 3: point not I'm not no one megabytes. I was like,
Speaker 3: how does that relate when you think about it? Physically.
Speaker 3: So I built a site where you could give it
Speaker 3: the r L and go off and fetch your site,
Speaker 3: pull all the job script files, and then tell you
Speaker 3: how many floppy disks it would take to hold that website.
Speaker 3: And then the top light you could upload your web
Speaker 3: pack stats jays on file and we do the same.
Speaker 3: So we said, you know, it would take five floppy
Speaker 3: disks the carrier site.
Speaker 2: The folks that actually know what a flabby is.
Speaker 3: Yeah, I think a lot of like, well, I imagine
Speaker 3: a lot of my viewers are of my time and era,
Speaker 3: and I will remember those days.
Speaker 1: So did you find it helpful learning spell? Did it
Speaker 1: help inform the stuff that you do in react?
Speaker 3: I haven't had enough time like after the kind of
Speaker 3: stream and all, but it was interesting to see just
Speaker 3: how they approach things, how they thought about exstruction. I
Speaker 3: think it was I was more looking from like a
Speaker 3: kind of structural projects. I think the national syntax, because
Speaker 3: they they'll never really kind of murder up. But it
Speaker 3: kind of gave me insid like this is how they're thinking,
Speaker 3: This is how they're building out their products. You know
Speaker 3: what way are they thinking? Definitely from a normal reactive
Speaker 3: It is something I want to explore more and learn
Speaker 3: about because it's it is gaining popularity. It seems to
Speaker 3: have you know, a lot of advantages, so I'm curiousity
Speaker 3: where it's going to go, how it's going to end up.
Speaker 2: Absolutely, so you're saying we instantly rebrand the problem podcast.
Speaker 2: This is now spelt around. Is that a go? Or
Speaker 2: is that a no go?
Speaker 3: Maybe some more episodes and reactions for me to learn this.
Speaker 6: I think like a react with a spelt kind of
Speaker 6: showdown in.
Speaker 2: Order that sounds fun.
Speaker 4: You can throw a view in there as well.
Speaker 1: Yeah, absolutely, that sounds actually really really fun.
Speaker 7: I've been meaning to actually find some time to actually
Speaker 7: look at spelts and actually try and build kind of
Speaker 7: a terplication. And then I saw yesterday as well there
Speaker 7: was a new one that came out called footage Yes
Speaker 7: and it was built by one of the person's works
Speaker 7: for eBay on their Marco uy So it was published
Speaker 7: I think this week and it seems to be getting
Speaker 7: quite the buzz.
Speaker 6: So maybe it's the new hotness. Who knows?
Speaker 5: Yes, See, this gets into what we were talking about
Speaker 5: earlier of like trying to process when something is relevant
Speaker 5: or not, and like I'm still hitting the PUZ button.
Speaker 5: Then spelt even like it's getting to the point where
Speaker 5: it's like it's approaching close enough that I want to
Speaker 5: take a look at it. But like I tend to
Speaker 5: be super conservative on these things, I wait until it's
Speaker 5: like hit mainstream essentially before I dive in.
Speaker 7: Now I'm with you, actually, I think for me, I
Speaker 7: like to look at a job John craimons and actually
Speaker 7: see how many are not asking for a particular framework,
Speaker 7: because that's a flavor of whether or not that tool
Speaker 7: has become kind of mainstream and has got I can
Speaker 7: mass behind it as opposed to you it's too for
Speaker 7: the cool kids.
Speaker 4: Yeah, yeah, I definitely took notice when I first started
Speaker 4: to see Gatsby mentioned among like static site generators for
Speaker 4: some companies. I was like, Oh, that's that's really it's
Speaker 4: becoming a thing that and Next like Next has just
Speaker 4: taken off. It seems like for good reason too. I
Speaker 4: get it.
Speaker 2: So I've got a question for y'all, So getthub co pilot.
Speaker 1: Is that actually going to stall new platform development? Because
Speaker 1: what essentially means is you have to have a certain
Speaker 1: amount of open source code out there for folks to
Speaker 1: be able to use copilot on your platform. So unless
Speaker 1: you have that initial momentum, right, how how is that
Speaker 1: going to work?
Speaker 2: Is it gonna so? Yeah, question for y'all.
Speaker 5: Okay, So I'll start by just saying, maybe for the
Speaker 5: listeners and for me personally, maybe you could just explain
Speaker 5: what GitHub copilot like is and what it does. I've
Speaker 5: heard the name, but I don't totally understand what it is.
Speaker 2: Right.
Speaker 1: It's an AI extension for I think it's just vs
Speaker 1: code at this point, I don't know. But essentially, just
Speaker 1: type in a comment and then run this copilot on it,
Speaker 1: and the code and the comment can be something along
Speaker 1: the lines of give me a function that multiplies two numbers,
Speaker 1: and it will literally give you a function in whatever
Speaker 1: environment you're in that potentially matches.
Speaker 2: What you asked for.
Speaker 1: You know, you could say, give me all a list
Speaker 1: of all the pokemon, and it might use a fetch
Speaker 1: api to go and get all of the pokemon, and
Speaker 1: it's essentially using GitHub and all of the repos in
Speaker 1: there as a training set for this AI. And then
Speaker 1: it's you know, there's this essentially I guess a variant
Speaker 1: on the GPT three AI engine. This customized more towards
Speaker 1: code that then essentially pulls out a fragment and gives
Speaker 1: you the code that would do that.
Speaker 3: So it's pretty interesting. It doesn't you mentioned like will
Speaker 3: it open source? Coupe becomes stale because potentially this AI
Speaker 3: is right in everring. But we'll get to the point
Speaker 3: then where so much was written using an AI that
Speaker 3: the AI then starts suggesting it's a AI generated code.
Speaker 3: So like, at the minute, it's harvesting all this manual
Speaker 3: code that was written by people, and eventually it's going
Speaker 3: to be all this code written by an AI. So
Speaker 3: it's just given its own results.
Speaker 2: Back that's inevitable and will have it extremely quickly.
Speaker 5: Personally, I'm always skeptical of these sorts of things, so
Speaker 5: I have not tried it. I would be kind of
Speaker 5: fascinated to play with this, so I'm going to have
Speaker 5: to poke around with this IS afterwards. But and any
Speaker 5: of these sort of like algorithmically decided things, especially for code,
Speaker 5: I'm I don't know, I'm just skeptical. I have trouble
Speaker 5: believing that the GitHub API is smart enough to be
Speaker 5: able to generate code that's going to actually solve problems
Speaker 5: for me enough that i'd actually want to use it,
Speaker 5: but I've also been wrong about this sort of thing before.
Speaker 5: But my initial reaction to skepticism that this will be useful.
Speaker 4: I've seen a little bit about it, and I haven't
Speaker 4: played with it yet either. But one thing that I
Speaker 4: have seen that people are at least a little bit
Speaker 4: upset about is how, I guess, maybe how GitHub is
Speaker 4: classifying open source code, because different repos have different levels
Speaker 4: of you can use this without any attribution, or you
Speaker 4: must use some sort of attribution that you're borrowing from this,
Speaker 4: And I don't think that the AI is doing much
Speaker 4: in the way of filtering, are doing attribution for sources
Speaker 4: that it's getting this code from. I could potentially see
Speaker 4: it being useful, but I also, like YOUTJ, I'm a
Speaker 4: little skeptical that the good old manual way of figuring
Speaker 4: stuff out the groute force method and then refining it
Speaker 4: and refactoring it into something that makes more sense to
Speaker 4: everybody besides you who wrote the code.
Speaker 5: Yeah, Like, well, at the top of my head, and
Speaker 5: like your example, like if I need a function that
Speaker 5: multiplies two numbers, I'm sure this tool is great, but
Speaker 5: like the day to day problems, I'm solving is I've
Speaker 5: got like my widgets and a function, and the widgets
Speaker 5: have like these three properties that are unique to my company,
Speaker 5: and I need to do some conditional logic based off
Speaker 5: of it, right, and AI is not going to really
Speaker 5: help with that. So it might help me google something
Speaker 5: like preventing from Google things like that stupid thing like
Speaker 5: how do I capitalize the first letter of like like
Speaker 5: a string, like some of those stupid things that we've
Speaker 5: probably searched twenty thousand times and like seen the same
Speaker 5: stack overflow posts. It seems like it would help with that,
Speaker 5: like save me a step. But for like the real logic,
Speaker 5: I need to write, like the nitty gritty stuff. That's
Speaker 5: the part I guess I'm skeptical about.
Speaker 7: Yeah, I think in practice you sometimes don't do things
Speaker 7: that code look right away because for that particular solution
Speaker 7: it works. But I'm getting the AI might be like, no,
Speaker 7: this is the right way, but I think, no, for
Speaker 7: this solution, it's okay if you break the moves, because
Speaker 7: I need to make this work. So yeah, definitely, I
Speaker 7: think it won't be practical for those kind of day
Speaker 7: to day tasks, but maybe like a fun thing to
Speaker 7: put on with and.
Speaker 3: If you want to be Yeah, like the examples of
Speaker 3: it's been very accurate and it's built really good. Cool.
Speaker 3: But as you said, like it's it's always small stuff
Speaker 3: like I need to fletchers the users and that kind
Speaker 3: of thing. So it's it's it's saving your copy and
Speaker 3: pits from stack which I don't think we should be
Speaker 3: removing less write a passage of going to Stackle tool
Speaker 3: to use jQuery even though, and learning with that experience.
Speaker 3: I see we said there's been reports that it's potentially
Speaker 3: throwing like API keys and secrets. Yeah, well, accidentally committed
Speaker 3: the code and I'm like, oh, this is where it
Speaker 3: gets full and interesting.
Speaker 4: Well, and that's that's a good point. Actually, not necessarily
Speaker 4: that we're copy pasting from stack overflow, but learning to
Speaker 4: ask the right questions to find the answer that you
Speaker 4: need is such a crucial part of becoming a decent developer.
Speaker 4: It's like that is that is a huge part of
Speaker 4: every developer's job is how do I phrase this so
Speaker 4: that I can actually find an answer that makes sense
Speaker 4: for my use case. And the other thing that I
Speaker 4: was just thinking about is so much of what we
Speaker 4: do is writing not very good code the first time around,
Speaker 4: and then figuring out through experience and through pull request
Speaker 4: comments and through just building more stuff, how to write
Speaker 4: better code the next time around. And if we have
Speaker 4: an AI kind of suggesting this is either the best
Speaker 4: way to do it or this is the right way
Speaker 4: to do it from the get go, there's a lot
Speaker 4: less of that learning experience, I think, and then being
Speaker 4: able to go back six months later and say, wow,
Speaker 4: this was really not very good. Now I think I
Speaker 4: can write it a lot better and a lot cleaner.
Speaker 5: Well, you could make the argument, though you still have
Speaker 5: to find a right way to ask the robot your
Speaker 5: question too, because I'm sure like the robot could potentially
Speaker 5: interpret different things depending on how you like phrase your comment,
Speaker 5: because somewhere deep down in the source code, something is
Speaker 5: parsing those search strings and feeding it to its algorithm
Speaker 5: or whatever it's doing under the hood. It's like the
Speaker 5: same process but like different.
Speaker 3: Yeah, you mentioned like pular requests, Like if if someone
Speaker 3: raises the polar requests and some of the coops written
Speaker 3: by the AI, are you going to comment on it
Speaker 3: or you're going to say, well.
Speaker 4: Fix this?
Speaker 6: Right?
Speaker 7: Also that question that is all about the ganty, right,
Speaker 7: I remember the case I think it was it was
Speaker 7: it Uber, but it last year or the year before
Speaker 7: where a lady was hit by a car that was
Speaker 7: surpriving itself, if you like, And then the case Okay,
Speaker 7: so that's the software.
Speaker 6: If it's in that moment AI, who's liable? Is it Uber?
Speaker 6: Is it a developer? Like?
Speaker 7: How do you like that the ganety becomes those kind
Speaker 7: of a grayer because obviously the person behind it isn't
Speaker 7: is AI. So AI can't be held accountable because it's
Speaker 7: a person. But yeah, it's an interesting question because I
Speaker 7: guess going forward, as well as more and more kind
Speaker 7: of AI gets gets into your day to day lives,
Speaker 7: that's going.
Speaker 6: To become a topic that needs to be kind of
Speaker 6: addressed and so it sut out otherwise.
Speaker 1: Yeah, I think it's one of the issues around AI
Speaker 1: is the fact that a lot of this is just
Speaker 1: training sets and models and we don't really understand why
Speaker 1: it works. We've trained it, we understand how the weights
Speaker 1: work and it creates this model, but we don't really
Speaker 1: understand this is why. You know, we've got out the
Speaker 1: slide rule and we did the calculations and YadA YadA, YadA.
Speaker 1: I mean nowadays, you know, when we land to something,
Speaker 1: it's more by training it on tons of failure as
Speaker 1: opposed to actually doing all the math and figuring out, Oh,
Speaker 1: here's how you hover slam a rocket.
Speaker 2: You know, maybe you do.
Speaker 3: I don't know.
Speaker 1: I'm not a rocket scientist. But yeah, it's certainly interesting,
Speaker 1: certainly interesting. The legal challenge around this. Wait, wow, we
Speaker 1: have come really far from speech recognition APIs but not
Speaker 1: maybe maybe.
Speaker 5: Yeah, the Vicial studio code is web based they could implement.
Speaker 5: And it's it's chromium based too, they So the web
Speaker 5: speech API should be there, right, like it could. You
Speaker 5: could use the speech recognition API to feed into the robot.
Speaker 4: Right.
Speaker 2: You don't even have to write comments, just use your
Speaker 2: voice the robot.
Speaker 5: You could just dictate your code, right, and the robot
Speaker 5: is going to fill in the blanks for you.
Speaker 6: Amazing. Actually I'm lazy, just be talking to the right.
Speaker 7: Okay, So line to consle name X, open bracket.
Speaker 1: You've got your next article right here. Take that vs
Speaker 1: code extension strang on it. But yeah, there it is
Speaker 1: nicely done. Well, I think that's a great time for
Speaker 1: picks And let's start out this week with Carl.
Speaker 7: Yeah, So I've got one pick today, and it's not
Speaker 7: really a pick, but I subscribe to a number of
Speaker 7: different front end or JS emos. But what I've been
Speaker 7: doing lately is actually subscribing to emos about things that mightamain.
Speaker 7: For example, right now, I subscribe to an email and
Speaker 7: alixa one and how to be a tech Lead, and
Speaker 7: there's another one on a on a different topic.
Speaker 6: And I do so just to.
Speaker 7: Every week when I go through my emails and look
Speaker 7: at it is news. It basically helps me kind of
Speaker 7: see what's happening outside front end side. Yes, and sometimes
Speaker 7: you find the about this thing in exile or whatever,
Speaker 7: and I think it's good to get a kind of
Speaker 7: rounded view of what's happening outside you kind of domain.
Speaker 6: And I definitely recommend it.
Speaker 7: Just try and find something outside your language or framework
Speaker 7: and just be keeping update on that EPs in week.
Speaker 2: Couldn't agree more, how about you, Paige.
Speaker 4: My pick this week is going to be a keyboard.
Speaker 4: It is the Logitech mx keys wireless keyboard and I
Speaker 4: recently I bought one this past weekend. And this thing
Speaker 4: is awesome. It is low profile, it is quiet because
Speaker 4: I am not a lover of mechanical keyboards that make
Speaker 4: so much noise that you can't hear yourself, and it
Speaker 4: is so far, it's just been amazing. It paired up well.
Speaker 4: It has three different toggles, so you can have three
Speaker 4: different computers paired to it, and it works for both
Speaker 4: Mac and Windows and probably Linux, and it's just been
Speaker 4: it's fantastic. So I would highly highly recommend that if
Speaker 4: you are not a mechanical keyboard enthusiast and you want
Speaker 4: something that's quiet and feels just right on your in
Speaker 4: your hands. It's got a good weight to it, it's
Speaker 4: Bluetooth compatible, it's it's pretty sweet. I very much would
Speaker 4: recommend it to anybody who's looking for a new one.
Speaker 2: Nice. I love their mice, all right, Chris, What do
Speaker 2: you got to Mine?
Speaker 3: Is kind of like utility application script by John Linquist.
Speaker 3: Now recently you did a side project almost before and
Speaker 3: it's like in Michael, actually have like Spotlight. We can
Speaker 3: do commands space, I mean type for files, but this
Speaker 3: you can do all space and you get like a
Speaker 3: pop up where you can type in and no commands
Speaker 3: like open up a Google search or you can move Windows.
Speaker 3: But it's built on JavaScript, so you can write your
Speaker 3: own scripts, and it has an API you can use MPM,
Speaker 3: so you can do whatever. You can do a job
Speaker 3: script like call servers interact with the machine, and my
Speaker 3: own jobscript. I think it's really cool.
Speaker 1: Ah, that's awesome. I totally am gonna look at that.
Speaker 1: That's great.
Speaker 2: DJ.
Speaker 5: Yeah, I'm gonna pick something called the Manfroto Magic Arm.
Speaker 5: It's basically an arm for mounting something like lights or
Speaker 5: like a more heavy duty camera. I've been doing some
Speaker 5: work in the home office and I got a nicer camera,
Speaker 5: and I was spent a lot of time researching something
Speaker 5: that would actually hold it and found this thing. It's
Speaker 5: a little pricier. It's like a one hundred and fifty
Speaker 5: dollars arm, So like, you don't want this for like
Speaker 5: a really like light thing. It's designed to be a
Speaker 5: little more heavy duty. But if you have something that's
Speaker 5: heavier and that you need to mount somewhere, if it's
Speaker 5: a light, it's a camera or whatever, it's good. I
Speaker 5: am like the world's worst person at like putting things
Speaker 5: together and setting things up. I'm comically bad at it,
Speaker 5: and even I was able to figure it out, and
Speaker 5: it's incredibly configurable. It's got like three different joints, so
Speaker 5: you can kind of fit it in anywhere you need.
Speaker 5: So I'll put the links in the show notes so that
Speaker 5: I don't have to read out the numbers. But it's
Speaker 5: a man Proto magic arm and I've liked it.
Speaker 2: Yeah, Manfroto is great.
Speaker 1: I've got one of their tripods and they've got a
Speaker 1: nice little interchangeable system that you can use, so you
Speaker 1: can take the same connection that's on your tripod and
Speaker 1: put it onto any of their stuff.
Speaker 2: I think.
Speaker 1: So that's really handy. All right, So my pick for
Speaker 1: this week is solid JS. So I don't know if
Speaker 1: you've taken a look at this yet, but it's essentially
Speaker 1: if you're looking for the spelt speed but you don't
Speaker 1: want to leave React world, solid JS is a really
Speaker 1: good alternative. It's kind of as if somebody reimagined React
Speaker 1: starting at like twenty twenty. So it's all functional components.
Speaker 1: It's all reactive, so it's all using kind of hooks
Speaker 1: and similar kind of this data changes then update this
Speaker 1: kind of thing, and it.
Speaker 2: Is wicked fast.
Speaker 1: So it's certainly something to look into if you still
Speaker 1: want to have components. You still maybe wanted to do
Speaker 1: the micro affe thing. You don't want to lose from
Speaker 1: area area already with React, but you do want somebody
Speaker 1: that's just crazy fast. Solid gass is a cool thing
Speaker 1: to look into. Nice all right. Well, that I think
Speaker 1: wraps us up for this week, Tuning again next week
Speaker 1: for React round Up.
Speaker 5: See you then, see everybody.
Speaker 6: Yeah fres