Podcasts about thinkster

The full schedule for Latent Space LIVE! at NeurIPS has been announced, featuring Best of 2024 overview talks for the AI Startup Landscape, Computer Vision, Open Models, Transformers Killers, Synthetic Data, Agents, and Scaling, and speakers from Sarah Guo of Conviction, Roboflow, AI2/Meta, Recursal/Together, HuggingFace, OpenHands and SemiAnalysis. Join us for the IRL event/Livestream! Alessio will also be holding a meetup at AWS Re:Invent in Las Vegas this Wednesday. See our new Events page for dates of AI Engineer Summit, Singapore, and World's Fair in 2025. LAST CALL for questions for our big 2024 recap episode! Submit questions and messages on Speakpipe here for a chance to appear on the show!When we first observed that GPT Wrappers are Good, Actually, we did not even have Bolt on our radar. Since we recorded our Anthropic episode discussing building Agents with the new Claude 3.5 Sonnet, Bolt.new (by Stackblitz) has easily cleared the $8m ARR bar, repeating and accelerating its initial $4m feat.There are very many AI code generators and VS Code forks out there, but Bolt probably broke through initially because of its incredible zero shot low effort app generation:But as we explain in the pod, Bolt also emphasized deploy (Netlify)/ backend (Supabase)/ fullstack capabilities on top of Stackblitz's existing WebContainer full-WASM-powered-developer-environment-in-the-browser tech. Since then, the team has been shipping like mad (with weekly office hours), with bugfixing, full screen, multi-device, long context, diff based edits (using speculative decoding like we covered in Inference, Fast and Slow).All of this has captured the imagination of low/no code builders like Greg Isenberg and many others on YouTube/TikTok/Reddit/X/Linkedin etc:Just as with Fireworks, our relationship with Bolt/Stackblitz goes a bit deeper than normal - swyx advised the launch and got a front row seat to this epic journey, as well as demoed it with Realtime Voice at the recent OpenAI Dev Day. So we are very proud to be the first/closest to tell the full open story of Bolt/Stackblitz!Flow Engineering + Qodo/AlphaCodium UpdateIn year 2 of the pod we have been on a roll getting former guests to return as guest cohosts (Harrison Chase, Aman Sanger, Jon Frankle), and it was a pleasure to catch Itamar Friedman back on the pod, giving us an update on all things Qodo and Testing Agents from our last catchup a year and a half ago:Qodo (they renamed in September) went viral in early January this year with AlphaCodium (paper here, code here) beating DeepMind's AlphaCode with high efficiency:With a simple problem solving code agent:* The first step is to have the model reason about the problem. They describe it using bullet points and focus on the goal, inputs, outputs, rules, constraints, and any other relevant details.* Then, they make the model reason about the public tests and come up with an explanation of why the input leads to that particular output. * The model generates two to three potential solutions in text and ranks them in terms of correctness, simplicity, and robustness. * Then, it generates more diverse tests for the problem, covering cases not part of the original public tests. * Iteratively, pick a solution, generate the code, and run it on a few test cases. * If the tests fail, improve the code and repeat the process until the code passes every test.swyx has previously written similar thoughts on types vs tests for putting bounds on program behavior, but AlphaCodium extends this to AI generated tests and code.More recently, Itamar has also shown that AlphaCodium's techniques also extend well to the o1 models:Making Flow Engineering a useful technique to improve code model performance on every model. This is something we see AI Engineers uniquely well positioned to do compared to ML Engineers/Researchers.Full Video PodcastLike and subscribe!Show Notes* Itamar* Qodo* First episode* Eric* Bolt* StackBlitz* Thinkster* AlphaCodium* WebContainersChapters* 00:00:00 Introductions & Updates* 00:06:01 Generic vs. Specific AI Agents* 00:07:40 Maintaining vs Creating with AI* 00:17:46 Human vs Agent Computer Interfaces* 00:20:15 Why Docker doesn't work for Bolt* 00:24:23 Creating Testing and Code Review Loops* 00:28:07 Bolt's Task Breakdown Flow* 00:31:04 AI in Complex Enterprise Environments* 00:41:43 AlphaCodium* 00:44:39 Strategies for Breaking Down Complex Tasks* 00:45:22 Building in Open Source* 00:50:35 Choosing a product as a founder* 00:59:03 Reflections on Bolt Success* 01:06:07 Building a B2C GTM* 01:18:11 AI Capabilities and Pricing Tiers* 01:20:28 What makes Bolt unique* 01:23:07 Future Growth and Product Development* 01:29:06 Competitive Landscape in AI Engineering* 01:30:01 Advice to Founders and Embracing AI* 01:32:20 Having a baby and completing an Iron ManTranscriptAlessio [00:00:00]: Hey everyone, welcome to the Latent Space Podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co-host Swyx, founder of Smol.ai.Swyx [00:00:12]: Hey, and today we're still in our sort of makeshift in-between studio, but we're very delighted to have a former returning guest host, Itamar. Welcome back.Itamar [00:00:21]: Great to be here after a year or more. Yeah, a year and a half.Swyx [00:00:24]: You're one of our earliest guests on Agents. Now you're CEO co-founder of Kodo. Right. Which has just been renamed. You also raised a $40 million Series A, and we can get caught up on everything, but we're also delighted to have our new guest, Eric. Welcome.Eric [00:00:42]: Thank you. Excited to be here. Should I say Bolt or StackBlitz?Swyx [00:00:45]: Like, is it like its own company now or?Eric [00:00:47]: Yeah. Bolt's definitely bolt.new. That's the thing that we're probably the most known for, I imagine, at this point.Swyx [00:00:54]: Which is ridiculous to say because you were working at StackBlitz for so long.Eric [00:00:57]: Yeah. I mean, within a week, we were doing like double the amount of traffic. And StackBlitz had been online for seven years, and we were like, what? But anyways, yeah. So we're StackBlitz, the company behind bolt.new. If you've heard of bolt.new, that's our stuff. Yeah.Swyx [00:01:12]: Yeah.Itamar [00:01:13]: Excellent. I see, by the way, that the founder mode, you need to know to capture opportunities. So kudos on doing that, right? You're working on some technology, and then suddenly you can exploit that to a new world. Yeah.Eric [00:01:24]: Totally. And I think, well, not to jump, but 100%, I mean, a couple of months ago, we had the idea for Bolt earlier this year, but we haven't really shared this too much publicly. But we actually had tried to build it with some of those state-of-the-art models back in January, February, you can kind of imagine which, and they just weren't good enough to actually do the code generation where the code was accurate and it was fast and whatever have you without a ton of like rag, but then there was like issues with that. So we put it on the shelf and then we got kind of a sneak peek of some of the new models that have come out in the past couple of months now. And so once we saw that, once we actually saw the code gen from it, we were like, oh my God, like, okay, we can build a product around this. And so that was really the impetus of us building the thing. But with that, it was StackBlitz, the core StackBlitz product the past seven years has been an IDE for developers. So the entire user experience flow we've built up just didn't make sense. And so when we kind of went out to build Bolt, we just thought, you know, if we were inventing our product today, what would the interface look like given what is now possible with the AI code gen? And so there's definitely a lot of conversations we had internally, but you know, just kind of when we logically laid it out, we were like, yeah, I think it makes sense to just greenfield a new thing and let's see what happens. If it works great, then we'll figure it out. If it doesn't work great, then it'll get deleted at some point. So that's kind of how it actually came to be.Swyx [00:02:49]: I'll mention your background a little bit. You were also founder of Thinkster before you started StackBlitz. So both of you are second time founders. Both of you have sort of re-founded your company recently. Yours was more of a rename. I think a slightly different direction as well. And then we can talk about both. Maybe just chronologically, should we get caught up on where Kodo is first and then you know, just like what people should know since the last pod? Sure.Itamar [00:03:12]: The last pod was two months after we launched and we basically had the vision that we talked about. The idea that software development is about specification, test and code, etc. We are more on the testing part as in essence, we think that if you solve testing, you solve software development. The beautiful chart that we'll put up on screen. And testing is a really big field, like there are many dimensions, unit testing, the level of the component, how big it is, how large it is. And then there is like different type of testing, is it regression or smoke or whatever. So back then we only had like one ID extension with unit tests as in focus. One and a half year later, first ID extension supports more type of testing as context aware. We index local, local repos, but also 10,000s of repos for Fortune 500 companies. We have another agent, another tool that is called, the pure agent is the open source and the commercial one is CodoMerge. And then we have another open source called CoverAgent, which is not yet a commercial product coming very soon. It's very impressive. It could be that already people are approving automated pull requests that they don't even aware in really big open sources. So once we have enough of these, we will also launch another agent. So for the first one and a half year, what we did is grew in our offering and mostly on the side of, does this code actually works, testing, code review, et cetera. And we believe that's the critical milestone that needs to be achieved to actually have the AI engineer for enterprise software. And then like for the first year was everything bottom up, getting to 1 million installation. 2024, that was 2023, 2024 was starting to monetize, to feel like how it is to make the first buck. So we did the teams offering, it went well with a thousand of teams, et cetera. And then we started like just a few months ago to do enterprise with everything you need, which is a lot of things that discussed in the last post that was just released by Codelm. So that's how we call it at Codelm. Just opening the brackets, our company name was Codelm AI, and we renamed to Codo and we call our models Codelm. So back to my point, so we started Enterprise Motion and already have multiple Fortune 100 companies. And then with that, we raised a series of $40 million. And what's exciting about it is that enables us to develop more agents. That's our focus. I think it's very different. We're not coming very soon with an ID or something like that.Swyx [00:06:01]: You don't want to fork this code?Itamar [00:06:03]: Maybe we'll fork JetBrains or something just to be different.Swyx [00:06:08]: I noticed that, you know, I think the promise of general purpose agents has kind of died. Like everyone is doing kind of what you're doing. There's Codogen, Codomerge, and then there's a third one. What's the name of it?Itamar [00:06:17]: Yeah. Codocover. Cover. Which is like a commercial version of a cover agent. It's coming soon.Swyx [00:06:23]: Yeah. It's very similar with factory AI, also doing like droids. They all have special purpose doing things, but people don't really want general purpose agents. Right. The last time you were here, we talked about AutoGBT, the biggest thing of 2023. This year, not really relevant anymore. And I think it's mostly just because when you give me a general purpose agent, I don't know what to do with it.Eric [00:06:42]: Yeah.Itamar [00:06:43]: I totally agree with that. We're seeing it for a while and I think it will stay like that despite the computer use, et cetera, that supposedly can just replace us. You can just like prompt it to be, hey, now be a QA or be a QA person or a developer. I still think that there's a few reasons why you see like a dedicated agent. Again, I'm a bit more focused, like my head is more on complex software for big teams and enterprise, et cetera. And even think about permissions and what are the data sources and just the same way you manage permissions for users. Developers, you probably want to have dedicated guardrails and dedicated approvals for agents. I intentionally like touched a point on not many people think about. And of course, then what you can think of, like maybe there's different tools, tool use, et cetera. But just the first point by itself is a good reason why you want to have different agents.Alessio [00:07:40]: Just to compare that with Bot.new, you're almost focused on like the application is very complex and now you need better tools to kind of manage it and build on top of it. On Bot.new, it's almost like I was using it the other day. There's basically like, hey, look, I'm just trying to get started. You know, I'm not very opinionated on like how you're going to implement this. Like this is what I want to do. And you build a beautiful app with it. What people ask as the next step, you know, going back to like the general versus like specific, have you had people say, hey, you know, this is great to start, but then I want a specific Bot.new dot whatever else to do a more vertical integration and kind of like development or what's the, what do people say?Eric [00:08:18]: Yeah. I think, I think you kind of hit the, hit it head on, which is, you know, kind of the way that we've, we've kind of talked about internally is it's like people are using Bolt to go from like 0.0 to 1.0, like that's like kind of the biggest unlock that Bolt has versus most other things out there. I mean, I think that's kind of what's, what's very unique about Bolt. I think the, you know, the working on like existing enterprise applications is, I mean, it's crazy important because, you know, there's a, you look, when you look at the fortune 500, I mean, these code bases, some of these have been around for 20, 30 plus years. And so it's important to be going from, you know, 101.3 to 101.4, et cetera. I think for us, so what's been actually pretty interesting is we see there's kind of two different users for us that are coming in and it's very distinct. It's like people that are developers already. And then there's people that have never really written software and more if they have, it's been very, very minimal. And so in the first camp, what these developers are doing, like to go from zero to one, they're coming to Bolt and then they're ejecting the thing to get up or just downloading it and, you know, opening cursor, like whatever to, to, you know, keep iterating on the thing. And sometimes they'll bring it back to Bolt to like add in a huge piece of functionality or something. Right. But for the people that don't know how to code, they're actually just, they, they live in this thing. And that was one of the weird things when we launched is, you know, within a day of us being online, one of the most popular YouTube videos, and there's been a ton since, which was, you know, there's like, oh, Bolt is the cursor killer. And I originally saw the headlines and I was like, thanks for the views. I mean, I don't know. This doesn't make sense to me. That's not, that's not what we kind of thought.Swyx [00:09:44]: It's how YouTubers talk to each other. Well, everything kills everything else.Eric [00:09:47]: Totally. But what blew my mind was that there was any comparison because it's like cursor is a, is a local IDE product. But when, when we actually kind of dug into it and we, and we have people that are using our product saying this, I'm not using cursor. And I was like, what? And it turns out there are hundreds of thousands of people that we have seen that we're using cursor and we're trying to build apps with that where they're not traditional software does, but we're heavily leaning on the AI. And as you can imagine, it is very complicated, right? To do that with cursor. So when Bolt came out, they're like, wow, this thing's amazing because it kind of inverts the complexity where it's like, you know, it's not an IDE, it's, it's a, it's a chat-based sort of interface that we have. So that's kind of the split, which is rather interesting. We've had like the first startups now launch off of Bolt entirely where this, you know, tomorrow I'm doing a live stream with this guy named Paul, who he's built an entire CRM using this thing and you know, with backend, et cetera. And people have made their first money on the internet period, you know, launching this with Stripe or whatever have you. So that's, that's kind of the two main, the two main categories of folks that we see using Bolt though.Itamar [00:10:51]: I agree that I don't understand the comparison. It doesn't make sense to me. I think like we have like two type of families of tools. One is like we re-imagine the software development. I think Bolt is there and I think like a cursor is more like a evolution of what we already have. It's like taking the IDE and it's, it's amazing and it's okay, let's, let's adapt the IDE to an era where LLMs can do a lot for us. And Bolt is more like, okay, let's rethink everything totally. And I think we see a few tools there, like maybe Vercel, Veo and maybe Repl.it in that area. And then in the area of let's expedite, let's change, let's, let's progress with what we already have. You can see Cursor and Kodo, but we're different between ourselves, Cursor and Kodo, but definitely I think that comparison doesn't make sense.Alessio [00:11:42]: And just to set the context, this is not a Twitter demo. You've made 4 million of revenue in four weeks. So this is, this is actually working, you know, it's not a, what, what do you think that is? Like, there's been so many people demoing coding agents on Twitter and then it doesn't really work. And then you guys were just like, here you go, it's live, go use it, pay us for it. You know, is there anything in the development that was like interesting and maybe how that compares to building your own agents?Eric [00:12:08]: We had no idea, honestly, like we, we, we've been pretty blown away and, and things have just kind of continued to grow faster since then. We're like, oh, today is week six. So I, I kind of came back to the point you just made, right, where it's, you, you kind of outlined, it's like, there's kind of this new market of like kind of rethinking the software development and then there's heavily augmenting existing developers. I think that, you know, both of which are, you know, AI code gen being extremely good, it's allowed existing developers, it's allowing existing developers to camera out software far faster than they could have ever before, right? It's like the ultimate power tool for an existing developer. But this code gen stuff is now so good. And then, and we saw this over the past, you know, from the beginning of the year when we tried to first build, it's actually lowered the barrier to people that, that aren't traditionally software engineers. But the kind of the key thing is if you kind of think about it from, imagine you've never written software before, right? My co-founder and I, he and I grew up down the street from each other in Chicago. We learned how to code when we were 13 together and we've been building stuff ever since. And this is back in like the mid 2000s or whatever, you know, there was nothing for free to learn from online on the internet and how to code. For our 13th birthdays, we asked our parents for, you know, O'Reilly books cause you couldn't get this at the library, right? And so instead of like an Xbox, we got, you know, programming books. But the hardest part for everyone learning to code is getting an environment set up locally, you know? And so when we built StackBlitz, like kind of the key thesis, like seven years ago, the insight we had was that, Hey, it seems like the browser has a lot of new APIs like WebAssembly and service workers, et cetera, where you could actually write an operating system that ran inside the browser that could boot in milliseconds. And you, you know, basically there's this missing capability of the web. Like the web should be able to build apps for the web, right? You should be able to build the web on the web. Every other platform has that, Visual Studio for Windows, Xcode for Mac. The web has no built in primitive for this. And so just like our built in kind of like nerd instinct on this was like, that seems like a huge hole and it's, you know, it will be very valuable or like, you know, very valuable problem to solve. So if you want to set up that environments, you know, this is what we spent the past seven years doing. And the reality is existing developers have running locally. They already know how to set up that environment. So the problem isn't as acute for them. When we put Bolt online, we took that technology called WebContainer and married it with these, you know, state of the art frontier models. And the people that have the most pain with getting stuff set up locally is people that don't code. I think that's been, you know, really the big explosive reason is no one else has been trying to make dev environments work inside of a browser tab, you know, for the past if since ever, other than basically our company, largely because there wasn't an immediate demand or need. So I think we kind of find ourselves at the right place at the right time. And again, for this market of people that don't know how to write software, you would kind of expect that you should be able to do this without downloading something to your computer in the same way that, hey, I don't have to download Photoshop now to make designs because there's Figma. I don't have to download Word because there's, you know, Google Docs. They're kind of looking at this as that sort of thing, right? Which was kind of the, you know, our impetus and kind of vision from the get-go. But you know, the code gen, the AI code gen stuff that's come out has just been, you know, an order of magnitude multiplier on how magic that is, right? So that's kind of my best distillation of like, what is going on here, you know?Alessio [00:15:21]: And you can deploy too, right?Eric [00:15:22]: Yeah.Alessio [00:15:23]: Yeah.Eric [00:15:24]: And so that's, what's really cool is it's, you know, we have deployment built in with Netlify and this is actually, I think, Sean, you actually built this at Netlify when you were there. Yeah. It's one of the most brilliant integrations actually, because, you know, effectively the API that Sean built, maybe you can speak to it, but like as a provider, we can just effectively give files to Netlify without the user even logging in and they have a live website. And if they want to keep, hold onto it, they can click a link and claim it to their Netlify account. But it basically is just this really magic experience because when you come to Bolt, you say, I want a website. Like my mom, 70, 71 years old, made her first website, you know, on the internet two weeks ago, right? It was about her nursing days.Swyx [00:16:03]: Oh, that's fantastic though. It wouldn't have been made.Eric [00:16:06]: A hundred percent. Cause even in, you know, when we've had a lot of people building personal, like deeply personal stuff, like in the first week we launched this, the sales guy from the East Coast, you know, replied to a tweet of mine and he said, thank you so much for building this to your team. His daughter has a medical condition and so for her to travel, she has to like line up donors or something, you know, so ahead of time. And so he actually used Bolt to make a website to do that, to actually go and send it to folks in the region she was going to travel to ahead of time. I was really touched by it, but I also thought like, why, you know, why didn't he use like Wix or Squarespace? Right? I mean, this is, this is a solved problem, quote unquote, right? And then when I thought, I actually use Squarespace for my, for my, uh, the wedding website for my wife and I, like back in 2021, so I'm familiar, you know, it was, it was faster. I know how to code. I was like, this is faster. Right. And I thought back and I was like, there's a whole interface you have to learn how to use. And it's actually not that simple. There's like a million things you can configure in that thing. When you come to Bolt, there's a, there's a text box. You just say, I need a, I need a wedding website. Here's the date. Here's where it is. And here's a photo of me and my wife, put it somewhere relevant. It's actually the simplest way. And that's what my, when my mom came, she said, uh, I'm Pat Simons. I was a nurse in the seventies, you know, and like, here's the things I did and a website came out. So coming back to why is this such a, I think, why are we seeing this sort of growth? It's, this is the simplest interface I think maybe ever created to actually build it, a deploy a website. And then that website, my mom made, she's like, okay, this looks great. And there's, there's one button, you just click it, deploy, and it's live and you can buy a domain name, attach it to it. And you know, it's as simple as it gets, it's getting even simpler with some of the stuff we're working on. But anyways, so that's, it's, it's, uh, it's been really interesting to see some of the usage like that.Swyx [00:17:46]: I can offer my perspective. So I, you know, I probably should have disclosed a little bit that, uh, I'm a, uh, stack list investor.Alessio [00:17:53]: Canceled the episode. I know, I know. Don't play it now. Pause.Eric actually reached out to ShowMeBolt before the launch. And we, you know, we talked a lot about, like, the framing of, of what we're going to talk about how we marketed the thing, but also, like, what we're So that's what Bolt was going to need, like a whole sort of infrastructure.swyx: Netlify, I was a maintainer but I won't take claim for the anonymous upload. That's actually the origin story of Netlify. We can have Matt Billman talk about it, but that was [00:18:00] how Netlify started. You could drag and drop your zip file or folder from your desktop onto a website, it would have a live URL with no sign in.swyx: And so that was the origin story of Netlify. And it just persists to today. And it's just like it's really nice, interesting that both Bolt and CognitionDevIn and a bunch of other sort of agent type startups, they all use Netlify to deploy because of this one feature. They don't really care about the other features.swyx: But, but just because it's easy for computers to use and talk to it, like if you build an interface for computers specifically, that it's easy for them to Navigate, then they will be used in agents. And I think that's a learning that a lot of developer tools companies are having. That's my bolt launch story and now if I say all that stuff.swyx: And I just wanted to come back to, like, the Webcontainers things, right? Like, I think you put a lot of weight on the technical modes. I think you also are just like, very good at product. So you've, you've like, built a better agent than a lot of people, the rest of us, including myself, who have tried to build these things, and we didn't get as far as you did.swyx: Don't shortchange yourself on products. But I think specifically [00:19:00] on, on infra, on like the sandboxing, like this is a thing that people really want. Alessio has Bax E2B, which we'll have on at some point, talking about like the sort of the server full side. But yours is, you know, inside of the browser, serverless.swyx: It doesn't cost you anything to serve one person versus a million people. It doesn't, doesn't cost you anything. I think that's interesting. I think in theory, we should be able to like run tests because you can run the full backend. Like, you can run Git, you can run Node, you can run maybe Python someday.swyx: We talked about this. But ideally, you should be able to have a fully gentic loop, running code, seeing the errors, correcting code, and just kind of self healing, right? Like, I mean, isn't that the dream?Eric: Totally.swyx: Yeah,Eric: totally. At least in bold, we've got, we've got a good amount of that today. I mean, there's a lot more for us to do, but one of the nice things, because like in web container, you know, there's a lot of kind of stuff you go Google like, you know, turn docker container into wasm.Eric: You'll find a lot of stuff out there that will do that. The problem is it's very big, it's slow, and that ruins the experience. And so what we ended up doing is just writing an operating system from [00:20:00] scratch that was just purpose built to, you know, run in a browser tab. And the reason being is, you know, Docker 2 awesome things will give you an image that's like out 60 to 100 megabits, you know, maybe more, you know, and our, our OS, you know, kind of clocks in, I think, I think we're in like a, maybe, maybe a megabyte or less or something like that.Eric: I mean, it's, it's, you know, really, really, you know, stripped down.swyx: This is basically the task involved is I understand that it's. Mapping every single, single Linux call to some kind of web, web assembly implementation,Eric: but more or less, and, and then there's a lot of things actually, like when you're looking at a dev environment, there's a lot of things that you don't need that a traditional OS is gonna have, right?Eric: Like, you know audio drivers or you like, there's just like, there's just tons of things. Oh, yeah. Right. Yeah. That goes . Yeah. You can just kind, you can, you can kind of tos them. Or alternatively, what you can do is you can actually be the nice thing. And this is, this kind of comes back to the origins of browsers, which is, you know, they're, they're at the beginning of the web and, you know, the late nineties, there was two very different kind of visions for the web where Alan Kay vehemently [00:21:00] disagree with the idea that should be document based, which is, you know, Tim Berners Lee, you know, that, and that's kind of what ended up winning, winning was this document based kind of browsing documents on the web thing.Eric: Alan Kay, he's got this like very famous quote where he said, you know, you want web browsers to be mini operating systems. They should download little mini binaries and execute with like a little mini virtualized operating system in there. And what's kind of interesting about the history, not to geek out on this aspect, what's kind of interesting about the history is both of those folks ended up being right.Eric: Documents were actually the pragmatic way that the web worked. Was, you know, became the most ubiquitous platform in the world to the degree now that this is why WebAssembly has been invented is that we're doing, we need to do more low level things in a browser, same thing with WebGPU, et cetera. And so all these APIs, you know, to build an operating system came to the browser.Eric: And that was actually the realization we had in 2017 was, holy heck, like you can actually, you know, service workers, which were designed for allowing your app to work offline. That was the kind of the key one where it was like, wait a second, you can actually now run. Web servers within a [00:22:00] browser, like you can run a server that you open up.Eric: That's wild. Like full Node. js. Full Node. js. Like that capability. Like, I can have a URL that's programmatically controlled. By a web application itself, boom. Like the web can build the web. The primitive is there. Everyone at the time, like we talked to people that like worked on, you know Chrome and V8 and they were like, uhhhh.Eric: You know, like I don't know. But it's one of those things you just kind of have to go do it to find out. So we spent a couple of years, you know, working on it and yeah. And, and, and got to work in back in 2021 is when we kind of put the first like data of web container online. Butswyx: in partnership with Google, right?swyx: Like Google actually had to help you get over the finish line with stuff.Eric: A hundred percent, because well, you know, over the years of when we were doing the R and D on the thing. Kind of the biggest challenge, the two ways that you can kind of test how powerful and capable a platform are, the two types of applications are one, video games, right, because they're just very compute intensive, a lot of calculations that have to happen, right?Eric: The second one are IDEs, because you're talking about actually virtualizing the actual [00:23:00] runtime environment you are in to actually build apps on top of it, which requires sophisticated capabilities, a lot of access to data. You know, a good amount of compute power, right, to effectively, you know, building app in app sort of thing.Eric: So those, those are the stress tests. So if your platform is missing stuff, those are the things where you find out. Those are, those are the people building games and IDEs. They're the ones filing bugs on operating system level stuff. And for us, browser level stuff.Eric [00:23:47]: yeah, what ended up happening is we were just hammering, you know, the Chromium bug tracker, and they're like, who are these guys? Yeah. And, and they were amazing because I mean, just making Chrome DevTools be able to debug, I mean, it's, it's not, it wasn't originally built right for debugging an operating system, right? They've been phenomenal working with us and just kind of really pushing the limits, but that it's a rising tide that's kind of lifted all boats because now there's a lot of different types of applications that you can debug with Chrome Dev Tools that are running a browser that runs more reliably because just the stress testing that, that we and, you know, games that are coming to the web are kind of pushing as well, but.Itamar [00:24:23]: That's awesome. About the testing, I think like most, let's say coding assistant from different kinds will need this loop of testing. And even I would add code review to some, to some extent that you mentioned. How is testing different from code review? Code review could be, for example, PR review, like a code review that is done at the point of when you want to merge branches. But I would say that code review, for example, checks best practices, maintainability, and so on. It's not just like CI, but more than CI. And testing is like a more like checking functionality, et cetera. So it's different. We call, by the way, all of these together code integrity, but that's a different story. Just to go back to the, to the testing and specifically. Yeah. It's, it's, it's since the first slide. Yeah. We're consistent. So if we go back to the testing, I think like, it's not surprising that for us testing is important and for Bolt it's testing important, but I want to shed some light on a different perspective of it. Like let's think about autonomous driving. Those startups that are doing autonomous driving for highway and autonomous driving for the city. And I think like we saw the autonomous of the highway much faster and reaching to a level, I don't know, four or so much faster than those in the city. Now, in both cases, you need testing and quote unquote testing, you know, verifying validation that you're doing the right thing on the road and you're reading and et cetera. But it's probably like so different in the city that it could be like actually different technology. And I claim that we're seeing something similar here. So when you're building the next Wix, and if I was them, I was like looking at you and being a bit scared. That's what you're disrupting, what you just said. Then basically, I would say that, for example, the UX UI is freaking important. And because you're you're more aiming for the end user. In this case, maybe it's an end user that doesn't know how to develop for developers. It's also important. But let alone those that do not know to develop, they need a slick UI UX. And I think like that's one reason, for example, I think Cursor have like really good technology. I don't know the underlying what's under the hood, but at least what they're saying. But I think also their UX UI is great. It's a lot because they did their own ID. While if you're aiming for the city AI, suddenly like there's a lot of testing and code review technology that it's not necessarily like that important. For example, let's talk about integration tests. Probably like a lot of what you're building involved at the moment is isolated applications. Maybe the vision or the end game is maybe like having one solution for everything. It could be that eventually the highway companies will go into the city and the other way around. But at the beginning, there is a difference. And integration tests are a good example. I guess they're a bit less important. And when you think about enterprise software, they're really important. So to recap, like I think like the idea of looping and verifying your test and verifying your code in different ways, testing or code review, et cetera, seems to be important in the highway AI and the city AI, but in different ways and different like critical for the city, even more and more variety. Actually, I was looking to ask you like what kind of loops you guys are doing. For example, when I'm using Bolt and I'm enjoying it a lot, then I do see like sometimes you're trying to catch the errors and fix them. And also, I noticed that you're breaking down tasks into smaller ones and then et cetera, which is already a common notion for a year ago. But it seems like you're doing it really well. So if you're willing to share anything about it.Eric [00:28:07]: Yeah, yeah. I realized I never actually hit the punchline of what I was saying before. I mentioned the point about us kind of writing an operating system from scratch because what ended up being important about that is that to your point, it's actually a very, like compared to like a, you know, if you're like running cursor on anyone's machine, you kind of don't know what you're dealing with, with the OS you're running on. There could be an error happens. It could be like a million different things, right? There could be some config. There could be, it could be God knows what, right? The thing with WebConnect is because we wrote the entire thing from scratch. It's actually a unified image basically. And we can instrument it at any level that we think is going to be useful, which is exactly what we did when we started building Bolt is we instrumented stuff at like the process level, at the runtime level, you know, et cetera, et cetera, et cetera. Stuff that would just be not impossible to do on local, but to do that in a way that works across any operating system, whatever is, I mean, would just be insanely, you know, insanely difficult to do right and reliably. And that's what you saw when you've used Bolt is that when an error actually will occur, whether it's in the build process or the actual web application itself is failing or anything kind of in between, you can actually capture those errors. And today it's a very primitive way of how we've implemented it largely because the product just didn't exist 90 days ago. So we're like, we got some work ahead of us and we got to hire some more a little bit, but basically we present and we say, Hey, this is, here's kind of the things that went wrong. There's a fix it button and then a ignore button, and then you can just hit fix it. And then we take all that telemetry through our agent, you run it through our agent and say, kind of, here's the state of the application. Here's kind of the errors that we got from Node.js or the browser or whatever, and like dah, dah, dah, dah. And it can take a crack at actually solving it. And it's actually pretty darn good at being able to do that. That's kind of been a, you know, closing the loop and having it be a reliable kind of base has seemed to be a pretty big upgrade over doing stuff locally, just because I think that's a pretty key ingredient of it. And yeah, I think breaking things down into smaller tasks, like that's, that's kind of a key part of our agent. I think like Claude did a really good job with artifacts. I think, you know, us and kind of everyone else has, has kind of taken their approach of like actually breaking out certain tasks in a certain order into, you know, kind of a concrete way. And, and so actually the core of Bolt, I know we actually made open source. So you can actually go and check out like the system prompts and et cetera, and you can run it locally and whatever have you. So anyone that's interested in this stuff, I'd highly recommend taking a look at. There's not a lot of like stuff that's like open source in this realm. It's, that was one of the fun things that we've we thought would be cool to do. And people, people seem to like it. I mean, there's a lot of forks and people adding different models and stuff. So it's been cool to see.Swyx [00:30:41]: Yeah. I'm happy to add, I added real-time voice for my opening day demo and it was really fun to hack with. So thank you for doing that. Yeah. Thank you. I'm going to steal your code.Eric [00:30:52]: Because I want that.Swyx [00:30:52]: It's funny because I built on top of the fork of Bolt.new that already has the multi LLM thing. And so you just told me you're going to merge that in. So then you're going to merge two layers of forks down into this thing. So it'll be fun.Eric [00:31:03]: Heck yeah.Alessio [00:31:04]: Just to touch on like the environment, Itamar, you maybe go into the most complicated environments that even the people that work there don't know how to run. How much of an impact does that have on your performance? Like, you know, it's most of the work you're doing actually figuring out environment and like the libraries, because I'm sure they're using outdated version of languages, they're using outdated libraries, they're using forks that have not been on the public internet before. How much of the work that you're doing is like there versus like at the LLM level?Itamar [00:31:32]: One of the reasons I was asking about, you know, what are the steps to break things down, because it really matters. Like, what's the tech stack? How complicated the software is? It's hard to figure it out when you're dealing with the real world, any environment of enterprise as a city, when I'm like, while maybe sometimes like, I think you do enable like in Bolt, like to install stuff, but it's quite a like controlled environment. And that's a good thing to do, because then you narrow down and it's easier to make things work. So definitely, there are two dimensions, I think, actually spaces. One is the fact just like installing our software without yet like doing anything, making it work, just installing it because we work with enterprise and Fortune 500, etc. Many of them want on prem solution.Swyx [00:32:22]: So you have how many deployment options?Itamar [00:32:24]: Basically, we had, we did a metric metrics, say 96 options, because, you know, they're different dimensions. Like, for example, one dimension, we connect to your code management system to your Git. So are you having like GitHub, GitLab? Subversion? Is it like on cloud or deployed on prem? Just an example. Which model agree to use its APIs or ours? Like we have our Is it TestGPT? Yeah, when we started with TestGPT, it was a huge mistake name. It was cool back then, but I don't think it's a good idea to name a model after someone else's model. Anyway, that's my opinion. So we gotSwyx [00:33:02]: I'm interested in these learnings, like things that you change your mind on.Itamar [00:33:06]: Eventually, when you're building a company, you're building a brand and you want to create your own brand. By the way, when I thought about Bolt.new, I also thought about if it's not a problem, because when I think about Bolt, I do think about like a couple of companies that are already called this way.Swyx [00:33:19]: Curse companies. You could call it Codium just to...Itamar [00:33:24]: Okay, thank you. Touche. Touche.Eric [00:33:27]: Yeah, you got to imagine the board meeting before we launched Bolt, one of our investors, you can imagine they're like, are you sure? Because from the investment side, it's kind of a famous, very notorious Bolt. And they're like, are you sure you want to go with that name? Oh, yeah. Yeah, absolutely.Itamar [00:33:43]: At this point, we have actually four models. There is a model for autocomplete. There's a model for the chat. There is a model dedicated for more for code review. And there is a model that is for code embedding. Actually, you might notice that there isn't a good code embedding model out there. Can you name one? Like dedicated for code?Swyx [00:34:04]: There's code indexing, and then you can do sort of like the hide for code. And then you can embed the descriptions of the code.Itamar [00:34:12]: Yeah, but you do see a lot of type of models that are dedicated for embedding and for different spaces, different fields, etc. And I'm not aware. And I know that if you go to the bedrock, try to find like there's a few code embedding models, but none of them are specialized for code.Swyx [00:34:31]: Is there a benchmark that you would tell us to pay attention to?Itamar [00:34:34]: Yeah, so it's coming. Wait for that. Anyway, we have our models. And just to go back to the 96 option of deployment. So I'm closing the brackets for us. So one is like dimensional, like what Git deployment you have, like what models do you agree to use? Dotter could be like if it's air-gapped completely, or you want VPC, and then you have Azure, GCP, and AWS, which is different. Do you use Kubernetes or do not? Because we want to exploit that. There are companies that do not do that, etc. I guess you know what I mean. So that's one thing. And considering that we are dealing with one of all four enterprises, we needed to deal with that. So you asked me about how complicated it is to solve that complex code. I said, it's just a deployment part. And then now to the software, we see a lot of different challenges. For example, some companies, they did actually a good job to build a lot of microservices. Let's not get to if it's good or not, but let's first assume that it is a good thing. A lot of microservices, each one of them has their own repo. And now you have tens of thousands of repos. And you as a developer want to develop something. And I remember me coming to a corporate for the first time. I don't know where to look at, like where to find things. So just doing a good indexing for that is like a challenge. And moreover, the regular indexing, the one that you can find, we wrote a few blogs on that. By the way, we also have some open source, different than yours, but actually three and growing. Then it doesn't work. You need to let the tech leads and the companies influence your indexing. For example, Mark with different repos with different colors. This is a high quality repo. This is a lower quality repo. This is a repo that we want to deprecate. This is a repo we want to grow, etc. And let that be part of your indexing. And only then things actually work for enterprise and they don't get to a fatigue of, oh, this is awesome. Oh, but I'm starting, it's annoying me. I think Copilot is an amazing tool, but I'm quoting others, meaning GitHub Copilot, that they see not so good retention of GitHub Copilot and enterprise. Ooh, spicy. Yeah. I saw snapshots of people and we have customers that are Copilot users as well. And also I saw research, some of them is public by the way, between 38 to 50% retention for users using Copilot and enterprise. So it's not so good. By the way, I don't think it's that bad, but it's not so good. So I think that's a reason because, yeah, it helps you auto-complete, but then, and especially if you're working on your repo alone, but if it's need that context of remote repos that you're code-based, that's hard. So to make things work, there's a lot of work on that, like giving the controllability for the tech leads, for the developer platform or developer experience department in the organization to influence how things are working. A short example, because if you have like really old legacy code, probably some of it is not so good anymore. If you just fine tune on these code base, then there is a bias to repeat those mistakes or old practices, etc. So you need, for example, as I mentioned, to influence that. For example, in Coda, you can have a markdown of best practices by the tech leads and Coda will include that and relate to that and will not offer suggestions that are not according to the best practices, just as an example. So that's just a short list of things that you need to do in order to deal with, like you mentioned, the 100.1 to 100.2 version of software. I just want to say what you're doing is extremelyEric [00:38:32]: impressive because it's very difficult. I mean, the business of Stackplus, kind of before bulk came online, we sold a version of our IDE that went on-prem. So I understand what you're saying about the difficulty of getting stuff just working on-prem. Holy heck. I mean, that is extremely hard. I guess the question I have for you is, I mean, we were just doing that with kind of Kubernetes-based stuff, but the spread of Fortune 500 companies that you're working with, how are they doing the inference for this? Are you kind of plugging into Azure's OpenAI stuff and AWS's Bedrock, you know, Cloud stuff? Or are they just like running stuff on GPUs? Like, what is that? How are these folks approaching that? Because, man, what we saw on the enterprise side, I mean, I got to imagine that that's a huge challenge. Everything you said and more, like,Itamar [00:39:15]: for example, like someone could be, and I don't think any of these is bad. Like, they made their decision. Like, for example, some people, they're, I want only AWS and VPC on AWS, no matter what. And then they, some of them, like there is a subset, I will say, I'm willing to take models only for from Bedrock and not ours. And we have a problem because there is no good code embedding model on Bedrock. And that's part of what we're doing now with AWS to solve that. We solve it in a different way. But if you are willing to run on AWS VPC, but run your run models on GPUs or inferentia, like the new version of the more coming out, then our models can run on that. But everything you said is right. Like, we see like on-prem deployment where they have their own GPUs. We see Azure where you're using OpenAI Azure. We see cases where you're running on GCP and they want OpenAI. Like this cross, like a case, although there is Gemini or even Sonnet, I think is available on GCP, just an example. So all the options, that's part of the challenge. I admit that we thought about it, but it was even more complicated. And it took us a few months to actually, that metrics that I mentioned, to start clicking each one of the blocks there. A few months is impressive. I mean,Eric [00:40:35]: honestly, just that's okay. Every one of these enterprises is, their networking is different. Just everything's different. Every single one is different. I see you understand. Yeah. So that just cannot be understated. That it is, that's extremely impressive. Hats off.Itamar [00:40:50]: It could be, by the way, like, for example, oh, we're only AWS, but our GitHub enterprise is on-prem. Oh, we forgot. So we need like a private link or whatever, like every time like that. It's not, and you do need to think about it if you want to work with an enterprise. And it's important. Like I understand like their, I respect their point of view.Swyx [00:41:10]: And this primarily impacts your architecture, your tech choices. Like you have to, you can't choose some vendors because...Itamar [00:41:15]: Yeah, definitely. To be frank, it makes us hard for a startup because it means that we want, we want everyone to enjoy all the variety of models. By the way, it was hard for us with our technology. I want to open a bracket, like a window. I guess you're familiar with our Alpha Codium, which is an open source.Eric [00:41:33]: We got to go over that. Yeah. So I'll do that quickly.Itamar [00:41:36]: Yeah. A pin in that. Yeah. Actually, we didn't have it in the last episode. So, so, okay.Swyx [00:41:41]: Okay. We'll come back to that later, but let's talk about...Itamar [00:41:43]: Yeah. So, so just like shortly, and then we can double click on Alpha Codium. But Alpha Codium is a open source tool. You can go and try it and lets you compete on CodeForce. This is a website and a competition and actually reach a master level level, like 95% with a click of a button. You don't need to do anything. And part of what we did there is taking a problem and breaking it to different, like smaller blocks. And then the models are doing a much better job. Like we all know it by now that taking small tasks and solving them, by the way, even O1, which is supposed to be able to do system two thinking like Greg from OpenAI like hinted, is doing better on these kinds of problems. But still, it's very useful to break it down for O1, despite O1 being able to think by itself. And that's what we presented like just a month ago, OpenAI released that now they are doing 93 percentile with O1 IOI left and International Olympiad of Formation. Sorry, I forgot. Exactly. I told you I forgot. And we took their O1 preview with Alpha Codium and did better. Like it just shows like, and there is a big difference between the preview and the IOI. It shows like that these models are not still system two thinkers, and there is a big difference. So maybe they're not complete system two. Yeah, they need some guidance. I call them system 1.5. We can, we can have it. I thought about it. Like, you know, I care about this philosophy stuff. And I think like we didn't see it even close to a system two thinking. I can elaborate later. But closing the brackets, like we take Alpha Codium and as our principle of thinking, we take tasks and break them down to smaller tasks. And then we want to exploit the best model to solve them. So I want to enable anyone to enjoy O1 and SONET and Gemini 1.5, etc. But at the same time, I need to develop my own models as well, because some of the Fortune 500 want to have all air gapped or whatever. So that's a challenge. Now you need to support so many models. And to some extent, I would say that the flow engineering, the breaking down to two different blocks is a necessity for us. Why? Because when you take a big block, a big problem, you need a very different prompt for each one of the models to actually work. But when you take a big problem and break it into small tasks, we can talk how we do that, then the prompt matters less. What I want to say, like all this, like as a startup trying to do different deployment, getting all the juice that you can get from models, etc. is a big problem. And one need to think about it. And one of our mitigation is that process of taking tasks and breaking them down. That's why I'm really interested to know how you guys are doing it. And part of what we do is also open source. So you can see.Swyx [00:44:39]: There's a lot in there. But yeah, flow over prompt. I do believe that that does make sense. I feel like there's a lot that both of you can sort of exchange notes on breaking down problems. And I just want you guys to just go for it. This is fun to watch.Eric [00:44:55]: Yeah. I mean, what's super interesting is the context you're working in is, because for us too with Bolt, we've started thinking because our kind of existing business line was going behind the firewall, right? We were like, how do we do this? Adding the inference aspect on, we're like, okay, how does... Because I mean, there's not a lot of prior art, right? I mean, this is all new. This is all new. So I definitely am going to have a lot of questions for you.Itamar [00:45:17]: I'm here. We're very open, by the way. We have a paper on a blog or like whatever.Swyx [00:45:22]: The Alphacodeum, GitHub, and we'll put all this in the show notes.Itamar [00:45:25]: Yeah. And even the new results of O1, we published it.Eric [00:45:29]: I love that. And I also just, I think spiritually, I like your approach of being transparent. Because I think there's a lot of hype-ium around AI stuff. And a lot of it is, it's just like, you have these companies that are just kind of keep their stuff closed source and then just max hype it, but then it's kind of nothing. And I think it kind of gives a bad rep to the incredible stuff that's actually happening here. And so I think it's stuff like what you're doing where, I mean, true merit and you're cracking open actual code for others to learn from and use. That strikes me as the right approach. And it's great to hear that you're making such incredible progress.Itamar [00:46:02]: I have something to share about the open source. Most of our tools are, we have an open source version and then a premium pro version. But it's not an easy decision to do that. I actually wanted to ask you about your strategy, but I think in your case, there is, in my opinion, relatively a good strategy where a lot of parts of open source, but then you have the deployment and the environment, which is not right if I get it correctly. And then there's a clear, almost hugging face model. Yeah, you can do that, but why should you try to deploy it yourself, deploy it with us? But in our case, and I'm not sure you're not going to hit also some competitors, and I guess you are. I wanted to ask you, for example, on some of them. In our case, one day we looked on one of our competitors that is doing code review. We're a platform. We have the code review, the testing, et cetera, spread over the ID to get. And in each agent, we have a few startups or a big incumbents that are doing only that. So we noticed one of our competitors having not only a very similar UI of our open source, but actually even our typo. And you sit there and you're kind of like, yeah, we're not that good. We don't use enough Grammarly or whatever. And we had a couple of these and we saw it there. And then it's a challenge. And I want to ask you, Bald is doing so well, and then you open source it. So I think I know what my answer was. I gave it before, but still interestingEric [00:47:29]: to hear what you think. GeoHot said back, I don't know who he was up to at this exact moment, but I think on comma AI, all that stuff's open source. And someone had asked him, why is this open source? And he's like, if you're not actually confident that you can go and crush it and build the best thing, then yeah, you should probably keep your stuff closed source. He said something akin to that. I'm probably kind of butchering it, but I thought it was kind of a really good point. And that's not to say that you should just open source everything, because for obvious reasons, there's kind of strategic things you have to kind of take in mind. But I actually think a pretty liberal approach, as liberal as you kind of can be, it can really make a lot of sense. Because that is so validating that one of your competitors is taking your stuff and they're like, yeah, let's just kind of tweak the styles. I mean, clearly, right? I think it's kind of healthy because it keeps, I'm sure back at HQ that day when you saw that, you're like, oh, all right, well, we have to grind even harder to make sure we stay ahead. And so I think it's actually a very useful, motivating thing for the teams. Because you might feel this period of comfort. I think a lot of companies will have this period of comfort where they're not feeling the competition and one day they get disrupted. So kind of putting stuff out there and letting people push it forces you to face reality soon, right? And actually feel that incrementally so you can kind of adjust course. And that's for us, the open source version of Bolt has had a lot of features people have been begging us for, like persisting chat messages and checkpoints and stuff. Within the first week, that stuff was landed in the open source versions. And they're like, why can't you ship this? It's in the open, so people have forked it. And we're like, we're trying to keep our servers and GPUs online. But it's been great because the folks in the community did a great job, kept us on our toes. And we've got to know most of these folks too at this point that have been building these things. And so it actually was very instructive. Like, okay, well, if we're going to go kind of land this, there's some UX patterns we can kind of look at and the code is open source to this stuff. What's great about these, what's not. So anyways, NetNet, I think it's awesome. I think from a competitive point of view for us, I think in particular, what's interesting is the core technology of WebContainer going. And I think that right now, there's really nothing that's kind of on par with that. And we also, we have a business of, because WebContainer runs in your browser, but to make it work, you have to install stuff from NPM. You have to make cores bypass requests, like connected databases, which all require server-side proxying or acceleration. And so we actually sell WebContainer as a service. One of the core reasons we open-sourced kind of the core components of Bolt when we launched was that we think that there's going to be a lot more of these AI, in-your-browser AI co-gen experiences, kind of like what Anthropic did with Artifacts and Clod. By the way, Artifacts uses WebContainers. Not yet. No, yeah. Should I strike that? I think that they've got their own thing at the moment, but there's been a lot of interest in WebContainers from folks doing things in that sort of realm and in the AI labs and startups and everything in between. So I think there'll be, I imagine, over the coming months, there'll be lots of things being announced to folks kind of adopting it. But yeah, I think effectively...Swyx [00:50:35]: Okay, I'll say this. If you're a large model lab and you want to build sandbox environments inside of your chat app, you should call Eric.Itamar [00:50:43]: But wait, wait, wait, wait, wait, wait. I have a question about that. I think OpenAI, they felt that people are not using their model as they would want to. So they built ChatGPT. But I would say that ChatGPT now defines OpenAI. I know they're doing a lot of business from their APIs, but still, is this how you think? Isn't Bolt.new your business now? Why don't you focus on that instead of the...Swyx [00:51:16]: What's your advice as a founder?Eric [00:51:18]: You're right. And so going into it, we, candidly, we were like, Bolt.new, this thing is super cool. We think people are stoked. We think people will be stoked. But we were like, maybe that's allowed. Best case scenario, after month one, we'd be mind blown if we added a couple hundred K of error or something. And we were like, but we think there's probably going to be an immediate huge business. Because there was some early poll on folks wanting to put WebContainer into their product offerings, kind of similar to what Bolt is doing or whatever. We were actually prepared for the inverse outcome here. But I mean, well, I guess we've seen poll on both. But I mean, what's happened with Bolt, and you're right, it's actually the same strategy as like OpenAI or Anthropic, where we have our ChatGPT to OpenAI's APIs is Bolt to WebContainer. And so we've kind of taken that same approach. And we're seeing, I guess, some of the similar results, except right now, the revenue side is extremely lopsided to Bolt.Itamar [00:52:16]: I think if you ask me what's my advice, I think you have three options. One is to focus on Bolt. The other is to focus on the WebContainer. The third is to raise one billion dollars and do them both. I'm serious. I think otherwise, you need to choose. And if you raise enough money, and I think it's big bucks, because you're going to be chased by competitors. And I think it will be challenging to do both. And maybe you can. I don't know. We do see these numbers right now, raising above $100 million, even without havingEric [00:52:49]: a product. You can see these. It's excellent advice. And I think what's been amazing, but also kind of challenging is we're trying to forecast, okay, well, where are these things going? I mean, in the initial weeks, I think us and all the investors in the company that we're sharing this with, it was like, this is cool. Okay, we added 500k. Wow, that's crazy. Wow, we're at a million now. Most things, you have this kind of the tech crunch launch of initiation and then the thing of sorrow. And if there's going to be a downtrend, it's just not coming yet. Now that we're kind of looking ahead, we're six weeks in. So now we're getting enough confidence in our convictions to go, okay, this se

SHOW SUMMARY:For this episode of NgXP, Joe Eames from ng-conf and Thinkster.io joins us to discuss the pros and cons and the ins and outs of pair programming. What exactly is pair programming and why would you want to invest time in such a process? Who exactly is it for? What are the best practices for pair programming and when is it most effective? You'll get answers to all these questions and so much more!LINKS:https://twitter.com/josepheameshttps://enterprise.ng-conf.org/https://thinkster.io/CONNECT WITH US:Joe Eames @josepheamesBrooke Avery @JediBraveryErik Slack @erik_slack

I spoke with Joe Eames. Joe is an educator with over 20 courses published on Pluralsight. When you look at his courses, you will quickly realize that Joe focus a lot on Test Driven Development and Angular. He has also acquired Thinkster a few years back, which is a learning site with courses on front-end development. Joe loves putting together tech events and he is one of the original ng-conf organizers. ng-conf is the most well-known Angular Conference and at the time there was no conference like that in the Angular space. We have explored a bit the challenges of putting together an event like that. Joe also mentioned that nowadays he is a sales engineer as part of a new venture with a friend. They are helping clients with extended support for an older version of Angular called AngularJS. All-in-all, I just had a great time talking to the super nice Joe Eames. Listen to this conversation to understand why Joe says that the things that you don't get paid for are the ones most valuable to you. Enjoy the chat! Full show notes and links: https://SoloCoder.com/82

I spoke with Eric Simons. Eric is the CEO of StackBlitz, an online browser based IDE where you can start coding on any front-end framework is seconds. I personally use it when I'm teaching full-stack development using Angular or React. Eric is a super nice and talkative guy. We discussed about his previous company Thinkster, which was acquired a few years ago and how that company give origin to StackBlitz. Eric shared with me his long term vision for StackBlitz and the kinds of hard problems they are trying to solve within his current team of about 10 people. When asked which front-end framework he would pick from Angular, React and Vue, his answer and reasoning will surprise you! Stick around to hear from the outspoken Eric Simons, CEO of StackBlitz. Enjoy the chat! Full show notes and links: https://SoloCoder.com/76

Raj Valli: Founder & CEO of Thinkster talks with me about Thinkster Math, Thinkster apps, test prep, and tutoring. This is episode 326 of Teaching Learning Leading K12, an audio podcast. Raj Valli founded - Thinkster.  He is a data and statistics guy at heart. As a certified Six Sigma Black Belt, he helped multi-billion dollar companies save money by making sure that their products and services were of the highest quality. Six Sigma means having less than 3.4 defects per 1 million pieces of anything you produce - engines, coffee cups, your shirt...tutoring….anything! That’s outstanding almost defect-free quality! He has worked for major multi-billion dollar corporations leading functional areas in marketing, finance, operations, strategy, and M&A, across Aerospace, Automotive, Life Sciences, Chemicals, Materials, Pharmaceuticals, Industrial Controls, BioTech, Services, and Software. He spent 20+ years volunteering his time to help provide basic education for underprivileged children. Several years ago, his daughters were using a worksheet based math learning program (like Kumon, Mathnasium) to help accelerate their math learning. He was frustrated by the lack of progress they were having in truly understanding math concepts. They were getting really good in the process of solving math problems in a very formulaic way without really understanding why they were doing what they were doing. He looked everywhere for a math program that would let his daughter’s learn math for life and not just for a test or completing homework.  He wanted a guaranteed approach to learning math. Not hope. But GUARANTEED! Like, Six-Sigma defect-free!  He knew that if they had a real strong foundation in math, it would take them places. He found nothing other than a few books on the topic or needed to hire an excellent math tutor for $100/hour. He took matters into his own hands and looked for efficient and fool-proof ways of getting students to learn not only math, but to develop a strong foundation in problem solving skills and to help them improve their critical thinking and logical reasoning skills.  He wanted them to develop the capacity to unpack and solve ANY problems in life - not just math problems. His strategy worked so well, that it got his daughters to ace math in middle and high school and eventually it also helped them into a top Ivy League University. This strategy became Thinkster….   Lots to learn today. Thanks for listening. Don't forget to share & subscribe. Enjoy!   Connect and Learn More: https://hellothinkster.com/ https://www.youtube.com/channel/UCYJdwYjaKLSYovlcW8x_GHw https://www.linkedin.com/in/rajvalli/ https://twitter.com/hellothinkster https://www.facebook.com/ThinksterMath/?fref=ts   Length - 46:03

In this four-part series, the Angular Show breaks down testing in Angular. Do you test? Should you have automated tests? And if you do test, what types of tests should you implement? Should you unit test? Should you have end-to-end tests? What about integration tests? This series tackles all of these questions and more.In part one, panelists Aaron Frost and Jennifer Wadella invite Joe Eames, CEO of Thinkster.io and Pluralsight author, along with Shai Reznik, founder and author of testangular.com, to share their knowledge and love of unit testing in Angular.While you are most likely performing manual testing, you may not be leveraging automated testing. Automated testing enables us to prevent regressions, increasing the quality of our applications. While many of us may not be leveraging automated testing, it can be extremely valuable when moving fast, when we have multiple developers on a team or in the code base, and perhaps even multiple teams in an organization that is sharing the same code and repository. The end result is confidence. Having a high level of confidence in shipping quality software provides significant value. Of course, implementing an automated testing strategy comes at a cost. Weighing the benefits with the cost is critical and should not be missed in your organization or team.Don't forget to subscribe so you can be notified when Testing Series Part 2 on using Jest for unit testing in Angular is available for download!

As software engineers and programmers, we work and live in an environment that is ever-expanding. Staying current in technology is not only a necessity in our career but often a challenge as well. As a result, entire industries have sprung up to assist us in meeting these challenges, the education sector being at the forefront of those industries. But then the question arises: Of all the options, which modality of learning is best? The answer is often a combination of your personal preference, how much time you have, and the required effectiveness.In episode 23 of The Angular Show, panelists Aaron Frost, Brian Love, Shai Reznik, and Jennifer Wadella invite Joe Eames, author at Pluralsight & CEO of Thinkster.io, to share his knowledge and love for teaching and learning. Joe has taught many of us on topics ranging from the Fundamentals of Angular to unit and end-to-end testing. Listen in as Joe teaches us about the modalities of learning and the advantages and disadvantages of each, and how we can effectively choose tools that will put us on effective learning pathways for achieving optimum success.@josepheames

Drew Perkins talks with Raj Valli, CEO of Thinkster, about updating education to meet the demands of today's knowledge economy. Links & Resources Mentioned In This Episode: HelloThinkster.com Thinkster on Twitter and Facebook @rajvalli Visit wegrowteachers.com for more info on our workshops and services.

Quick show notes Our Guest: Jenn Creighton What she'd like for you to see: Her Twitter feed | React Day NYC | Thinkster React Component Course (coming soon) | useReactNYC Her JAMstack Jams: Gatsby | Netlify Her musical Jam: Halsey's You Should Be Sad Our sponsor this week: TakeShape Transcript Bryan Robinson 0:04 Welcome, welcome everyone to a new episode of that's my JAMstack the podcast where we explore the deepest parts of the developer psyche by asking, what's your jam in the JAMstack. On today's episode we're chatting with Jenn Creighton, Jenn is a conference speaker and the organizer of useReact NYC. She's also the front end architect for The Wing. Bryan Robinson 0:23 Also, this week, we have our amazing sponsor TakeShape. Find out more about their JAMstack content platforms stick around after the episode or head over to takeshape.io/thatsmyjamstack. Bryan Robinson 0:36 All right. Well, thanks for joining us on the podcast today, Jenn. Jenn Creighton 0:38 Thank you for having me. Bryan Robinson 0:40 Thanks. So tell us a little bit about yourself. What do you do for work? What do you do for fun, that sort of thing? Jenn Creighton 0:45 Sure. So I am a front end architect at a company called The Wing. We work on building out co working spaces that are really geared towards women. So we're thinking a lot about what women need in those spaces, and also there's a lot of networking events and things like that in our spaces. Jenn Creighton 1:03 So I'm the front end architect there, I lead all of front end. I help ensure our system stays healthy. I work on our technical decisions there. You can already tell I'm a lot of fun because I really love tech. And honestly, like what I do for fun, I'm usually at a conference. I'm usually speaking at a conference, I really, really enjoy giving technical talks. So you will find that I'm often at a conference, I travel a lot to do that. I did 14 conferences last year, which I won't be repeating but it was a lot of fun. I had a good time. And if I'm genuinely not doing any tech related things, I am probably with my cats or my puppy or I am sewing. I really enjoy sewing. Bryan Robinson 1:53 So I saw and I think this is on like your Noti.st profile, is your dog's name really Sailor Moon because that's amazing Jenn Creighton 2:00 Her name IS Sailor Moon. She is named after the you know, Sailor Guardian Sailor Moon and she's a little blonde dachsund and, and I grew up watching Sailor Moon. I loved that show. I would watch it so much. And when I was thinking of names for her, I really want something kind of fun. So I picked out that it's really great too, because when you tell people her name, you can tell if they watch the show or not. Because they're either That is amazing. Or they're Wow, that's a lot of a name. Bryan Robinson 2:35 I'll be honest, do you just call her Sailor Moon all the time. Jenn Creighton 2:39 We usually call her sailor or if she's being a bit sassy Miss moon. Bryan Robinson 2:43 That works that work. And any fun sewing projects that you're working on. Jenn Creighton 2:48 I actually haven't sold in a long time because of the mentioned 14 conferences. So actually did not so I think anything last year. No, that's not true. Wait, I took a sewing class in November as my like, you're gonna do it and I sewed a pair of pants for the first time I took a sewing class to like force myself into a non tech hobby, which is a good thing to do once in a while. Bryan Robinson 3:17 Yeah, especially 14 conferences in 12 months. How many how many months were filled with more than two conferences? Did you did you group together and how exhausting was that? Jenn Creighton 3:28 Some months were grouped together. Um, let's see, I think I know at least I did, in September, I did two. And I traveled really far for them. So I did JS Conf Korea, and Components Comf in Australia together. And I think I had some some weeks and breaks there but a couple of them were like, in the same month and so I would knock out like two or three in the same month and then have like a little bit of a break which usually Wasn't a break. Like between Components Conf and React Conf. I actually had to write my React Conf talk. Bryan Robinson 4:09 The glamour of being a conference speaker! Jenn Creighton 4:11 It's so not glamorous, it's so exhausting. And yet, we can like people who enjoy it can't stop doing it. I don't know if you remember this, but there was a survey that came out many many years ago that said that people are more afraid of public speaking than they are of death. And so conference speaking is actually like a near death experience. As you get like this ridiculous rush, you're terrified you feel great afterwards. You're like, I'll just do it again. Bryan Robinson 4:44 I just watched the the Imagineering story the the story of all like the Disney theme park building and all that. And it talks about all the all the rides and how the goal is to make people feel like they're about to die without getting them actually all the way to death. So it's the same basic principle just with public speaking. Jenn Creighton 5:01 I think that happens with code too, Like, I just spent two days solving this issue of my tests failing on circle ci when they weren't failing locally. And I wanted to die. I want to lay down and die. I was like, take me, Lord, now and then I figured it out. I felt great. Bryan Robinson 5:20 So this is a JAMstack podcast, let's talk about the JAMstack a little bit. What's been kind of your introduction into that world or into static sites or wherever you kind of came to it from? Jenn Creighton 5:30 I think with static sites, the first time I remember seeing like a static site generator was Jekyll. And this was back at a startup many, many years ago. I remember we used it for I believe our marketing site, which was like pretty typical. And I really didn't know that there would be static site generators. It was kind of surprising to me. But I also didn't really play with it because I was just trying to learn JavaScript. I was like, this is where I'm like, trying to figure things out. The actual JAMstack, you know, JavaScript API's and markup, my introduction to that has come a lot later than I think a lot of people I actually just started, I'd say late last year getting interested in the concept and starting to learn about it. We use it at work for our marketing website. And then personally, we've used it for a meetup that I run here in New York called useReactNYC. Bryan Robinson 6:28 What's sort of technology stack are you messing with right now? Jenn Creighton 6:32 So both of them are using Gatsby, but the marketing site is Gatsby plus Contentful. So that of course, our marketing people can make their own changes to the site, and we don't have to be, you know, nudged. "Hey Can you do a thing?" Bryan Robinson 6:48 "Please deploy, please, deploy!" Jenn Creighton 6:49 "Please make this change." So it gives them the freedom to do that without having to wait on us to make changes. It gives us the freedom not to think about the marketing site, very much. Then for useReactNYC, we wanted to create a website for the meetup so that people could learn more about us what we're about, and also join our community, both by attending the meetups, but also by joining our slack community, and also by helping us to build the site. And since we're a React meetup, it made a lot of sense that this would be a static site, and that we would make it with Gatsby. Bryan Robinson 7:27 Very nice. And any sort of ... Is there any sort of like API integration? Are you pulling in like meetup information from a third party? Or is it all just manual entry into into Gatsby? Jenn Creighton 7:37 Right now let's just manual entry. We definitely want to expand it at some point. We're just not sure that we have the time right now between the five organizers that there are, we actually took on another organizer this year to make five of us Yuraima joined us and we have just all been really stretched thin. So even with the fifth organizer, we're still like "huuu", but we're hopefully gonna start recording the meetup soon and hopefully we'll also host them there so that people can view the content. Bryan Robinson 8:08 Pretty cool. I definitely understand that. That meetup organizer life where you're like, hey, PRs are accepted, and then no one submits a PR. Jenn Creighton 8:16 Yeah, we did have a particular member of the community, Nick, who came in and helped us really do a lot of work on the site, when we were all stretched very thin. And my very good friend Melissa, helped us actually by creating the design of the site, and it's really beautiful. She did a wonderful job. She also designed our stickers. So really, like all community events, it is really like we wouldn't have done it without the community like helping us out. That's was important. Bryan Robinson 8:45 Cool. So uh, are you You said that the marketing site at The Wing is currently built on Gatsby. What other sorts of projects do you work on at The Wing other than obviously getting the word out about these kind of co-working spaces? Jenn Creighton 8:58 So what what I personally work on is that I work on our single page application. So Gatsby is for our marketing site. But we do have a single page application that is for our members. That's our members portal as well as an admin site for us to handle things like applications or members, information, adjusting settings for them, so on and so forth. But our members portal is where everything really happens for them, they're allowed to find other people in the community and chat with them. There are job postings on the site as well. And there are a lot of events at The Wing that are very specific to what our members want to hear and see. And so they can RSVP for those as well on the site, as well as just the general thing of like adjusting settings or registering guests. So I work on all of that and as we try to build out new features that are going to help our members connect more and forum like real in life connections are putting a lot of those in this single page application. Bryan Robinson 10:01 Very cool. And so just like -- I have a degree in philosophy, so I have to sometimes dive into philosophy on the podcast -- So where would you kind of consider kind of breakpoint, because you said, you know, I'm using the JAMstack for the marketing site. And for the meetup site, I've always kind of thought of any SPA as having JAMstack asked qualities. Where do you kind of draw that line? Like, what what's JAMstack versus non JAMstack for you. Jenn Creighton 10:28 So the reason that I qualified as a single page application instead of anything to do with the JAMstack, is because it's built using create react app. And so it actually has a server. So nothing's actually served by CDN, which I think is an important component of JAMstack sites, you know, they have to be served statically through CDN or some means of static. So they're not pre rendered. They're not static. It's it's an actual serving of just an index.html, and then we fill in the JavaScript for everything. Bryan Robinson 10:59 I gotcha. Cool. That's the the kind of fun thing about running this podcast is that I hear lots of opinions. And they literally run the full gamut of like, everything's the JAMstack to like, even smaller like subsets. And it's just yeah, it's awesome. Jenn Creighton 11:15 Yeah, I mean, and when you hear like that it's JavaScript API's and markup, you're like, well, how is this not every single page application? And that totally makes sense. Definitely. I think the JAMstack has some really specific qualities to it, though, that are very different from something built with like create react app that actually does have a server that you're not actually serving at statically. And you're relying on the JavaScript to do all the heavy lifting of creating all the page. It's not pre rendered. You know, we certainly don't have the ability for... One of the things I really like about the JAMstack is that it closes that gap for the user, right like they get the stuff immediately. And also how your deploys go. You know, you can roll them back and there get based. But you don't have that with the single page application. And sometimes I was wondering with that I was like, does this need to be anyway, I was like, but I'm not rewriting the whole thing. And that decision was made before I came into the company. And I was like, You know what, it's, it's fine. Bryan Robinson 12:22 And still React. So you still get to work on react. Jenn Creighton 12:25 Yeah, and I love I love react. So that like, is a joy for me. Bryan Robinson 12:29 And so is there anything that you've that you've been learning based on your work in Gatsby that you're bringing back into the the server side and the Create React App side of all that Jenn Creighton 12:41 Not specifically? I think Gatsby comes with a lot of wonderful things that are not even technically part of JAMstack, right. Like I would say I would say that there is a great amount of focus on accessibility and Gatsby I really, really appreciate that. And that is something we're really focused on at work. So like many startups, so our product team is really new at the way. And like many startups, the first version of our product was built externally by a third party. And so we're now as a product team, picking it up and sort of changing the architecture and making it more of a long term scalable application. And that includes taking a look at our accessibility and realizing that we're really far off the mark right now. And we need to do something about that. I really appreciate that Gatsby, in addition to using JAMstack is actually really like moving forward with accessibility and giving you a lot of information about that along the way. Bryan Robinson 13:46 Yeah. And the great thing for me is that there's so many people jumping on Gatsby right now, just in terms of like, it is like probably one of the hotness is in the JAMstack right now. And to have that their focus so that people who might not have learned about accessibility in the are getting those tips and tricks just by having that in their code base by default. I think that's amazing. Jenn Creighton 14:05 Yeah, exactly. And that's one of the things I really enjoy about that project. And that's one of the things like, as you're working on that, you get to learn that you can bring that to all your future projects. It's not specific to the JAMstack. It is all about the web. Bryan Robinson 14:19 Best platform there is... the web. Jenn Creighton 14:21 Yes. Bryan Robinson 14:22 Cool. So So would it be fair to say that in the JAMstack, the Gatsby is your jam? Are there any other technologies that you're really interested in right now? Jenn Creighton 14:30 I think Gatsby is the main one. Obviously, we're really enjoying also Netlify and being able to like push things out really easy. So we use Netlify also for our preview links at work which is really great. So just definitely enjoying that. But yeah, I think definitely Gatsby considering that I've used it at work and now in this useReactNYC project. Bryan Robinson 14:54 Nice and so work when when people are saving into contentful, are y'all deploying Preview deploys to send them links at same time. So like they can see it live on the site before they publish it. Jenn Creighton 15:06 I think so. Yeah. I forget because I haven't worked with it in a hot second and if anyone's changed behind my back, but yeah. Bryan Robinson 15:14 You never know. Jenn Creighton 15:15 Honestly, with a startup you never know. Bryan Robinson 15:18 It's so easy to deploy, right? Jenn Creighton 15:20 Things happen in a startup that I'm like, wait a minute, you're doing what now? Can we just Can we just grab five really quickly and make sure this is a good idea? All the time. Bryan Robinson 15:30 Okay, gotta move fast, right? Jenn Creighton 15:32 Yes. Move fast break. Things. Break. ... Both of us are like "arrrrgh no!" Bryan Robinson 15:39 Yeah. Don't Don't tell QA that you broke it. It's fine. Jenn Creighton 15:44 Yeah. Bryan Robinson 15:46 Cool. So let's, let's talk about actual musical jams. Then what are you listening to right now? It's in your headphones. What's going on there? Jenn Creighton 15:53 So my number one thing right now is Halsey. Which is strange. I didn't listen to her before, but I actually so I'm a big fan of Saturday Night Live. I love Saturday Night Live. And she hosted not that long ago. And she was the host and the musical guests. And I wasn't familiar really with her music, but she had this song on there, You Should Be Sad. And I just fell in love with it. So I've actually been playing that on repeat for like a while. I love her vocals on it. It like just makes me feel really good. Bryan Robinson 16:28 Yeah, so specifically that song but then kind of the whole, her whole artistry. Jenn Creighton 16:34 I let I let that song play and then I'll listen to like a lot of the other ones on the album and I'm finding that I really enjoy her songs, which is really great. Jenn Creighton 16:44 And just depends on what mood I'm in. Bryan Robinson 16:47 What other moods strike you for, for other musical tastes. Jenn Creighton 16:51 And sometimes we like to go old school like country. Little little like kind of plucky banjo sound You know, really enjoy that sometimes. So I went through an Iggy Azalea phase. That was an interesting period of my life. Bryan Robinson 17:10 I think we've all been through that sort of phase. We've all been there. Jenn Creighton 17:14 Sometimes my my discover weekly on Spotify, I think is consistently confused. It's like, remember when you were sad? Well, here's all the sad songs and I'm like, oh, but Spotify. I'm not sad anymore. It's like, Okay. Here's poppy feminist music. I'm like, no, we're not in that mood. We're angry, now. Where's the angry? It's like, I cannot help you, I'm sorry. Sorry, Spotify. Bryan Robinson 17:39 The algorithm can only do so much for you. Cool. So is there anything that you would like to promote something you're doing something you want get out to the JAMstack community? Jenn Creighton 17:47 Well, first of all, if they're interested, they can follow me on Twitter. My handle is gurlcode girl with a "u". I'm also going to be speaking here in New York at React Day New York. Later in September, I'm going to be speaking about some things I have learned going from React to React Native, which is a whole new world for me. And then I'm also developing a course on React component architecture. That's my, my favorite sort of subject. I'm developing it for Thinkster. So that should be coming out, I think in a few months, if I have enough time to do all the recordings Bryan Robinson 18:24 Very cool. And also, I haven't watched it yet, but I'm super excited now that I've seen it to go watch your the "What happens next", the choose your own adventure with iterators. Like, I have to go watch that I saw that topic. I said, Okay, carving out the time for that one. Jenn Creighton 18:39 I love iterators I love them so much. They're wild. They're in so many things that we use in JavaScript, and we have no clue. And that's what that talk is about. And also it's like ridiculous and silly. You're on like an alien planet solving a mystery. And I had this artists do this beautiful work for it. So it's ridiculous, but yeah, Bryan Robinson 19:00 Ridiculous is the best way to go. Jenn Creighton 19:03 Yeah, it's like funny and weird. I enjoy it. Bryan Robinson 19:06 Well, I appreciate you taking the time to talk with us. And we'll be sure to link all those, all those amazing things that you're doing up in the show notes. And yeah, thanks for taking the time. Jenn Creighton 19:14 Thank you for having me really enjoyed it. Bryan Robinson 19:16 And as always, thank you to the amazing JAMstack community, your continued support via shares, likes favorites, and all those mechanisms is so incredible that I literally just don't have the words to deal with it. Bryan Robinson 19:29 With that it's sponsored time, and we're talking about the amazing content platform take shape. This week, I want to mention their amazing GraphQL API. It's not an afterthought, but a fully realized part of their platform. It means that whether you use their CMS or another platform entirely, you have an incredibly easy access to all your data in one simple API call. Do you want to see what that's like? Head on over to takeshape.io/that'smyjamstack to sign up. And with that, I'll take my leave of your ears. So until next week, Keep doing amazing things on the web and keep things JammyTranscribed by https://otter.aiIntro/outtro music by bensound.comSupport That's my JAMstack by donating to their Tip Jar: https://tips.pinecast.com/jar/thats-my-jamstack

In this podcast episode, we talk about how automation and scaling your business does not necessarily mean becoming impersonal with your clients.  It can be a way of showing love and appreciation to them. Learn how systems and automation can help you create a foolproof customer experience where no customer will be left hanging. ----- Automated Transcript Below: Dean Soto  0:00   Hey! This is Dean Soto, founder of FreedomInFiveMinutes.com and ProSulum.com. P-R-O-S-U-LU-M.com. We're here again with another Freedom In Five Minutes podcast episode. Today's topic is this:   Dean Soto  0:21   I Systemize Because I Love You. That and more, coming up.   Dean Soto  0:29   Well, good morning! And hey, if you have not subscribed to the Freedom In Five Minutes podcast,   Dean Soto  0:35   go to Google and whether you like   Dean Soto  0:39   Apple podcasts, Spotify, Stitcher or whatever it might be... Just type Freedom In Five Minutes and Apple podcasts; or Freedom In Five Minutes and Spotify; or Freedom In Five Minutes and Stitcher Radio.   Dean Soto  0:59   And you will get the ability to subscribe using your favorite platform to this podcast. So we're at a couple of hundred episodes. We're in the hundreds of episodes so far and if you have not subscribed yet... What is going on? You've got to get subscribed. Sounded like sound like a... Have you ever seen Homestar Runner? That was one of my favorite cartoons when it was still big and popular. They had a tarantula– No, I forgot. It was the rock band the hair rock band. And that's what the lead singer sounded like.   Dean Soto  1:41   You gotta subscribe. Anyway, Luna is just running around. I'm out on my land. And let's get into this episode.   Dean Soto  1:58   I'm on the board of a particular ministry that does amazing, amazing work. They actually have grown so much in the last few years. To the point where their last conference that happened in January sold out. And they actually had to get more. They had to get more people in there. I think it was like 3000 people. And they had to figure out how they could get more people in there. It looks like it's going to be 6000 people this next year, which is great. The thing about this particular ministry is the person who heads it... One, he's a really good friend; and two, he has the mindset of really being a good steward of his money – of the money that's been entrusted to him. He is being a really, really good steward of that money.   Dean Soto  3:07   If you're going to be a good steward of anything, you want to make sure that you get the most bang for your buck. You want to make sure that you get the most out of whatever it is you are spending. It could be money, it could be time. It could be anything. It doesn't necessarily have to be money. For example, if you have a homestead and you want to get as many eggs as you can out of your chickens while making them as happy as possible. Or with your parenting, you want your kids to get the most out of life without spoiling them. Different things like that. Well, this particular person is really good at utilizing his resources to maximum As much as possible,   Dean Soto  4:03   I had a phone call with him. He uses VSAs from Pro Sulum and FreedomInFiveMinutes.com and he uses Virtual Systems Architects for his ministry. They do everything from reaching out to donors, to talking with new donors, to handling new people who come into the membership site that have content and everything like that. They do all the process documentation, all of that type of stuff. It's pretty amazing what they're able to do. And they have one guy. One guy. This one guy is handling so many different things. And it has been really helping the organization tremendously. And one of the things that I started sharing with my friend is that...   Dean Soto  4:57   It was funny because he was talking about wanting to build the organization and scale the organization. But at the same time, he still wants to have that personal touch. He said essentially that, "If it grows, it's not going to be as personal, I know that but you know, I still want to do that as much as possible." And I rebuked him. I rebuked him and I said, "No, you don't have to get impersonal."   Dean Soto  5:41   No. So I said, "You know what? It's quite the opposite. The cool thing is now we have access to so many different tools that literally would have cost thousands of dollars per month to be able to do. And we now have these tools at our disposal that allow us to be personal, but still have run a small-ish organization."   Dean Soto  6:17   So I started talking to him, I'm like, "Look, my organization does everything from sending text messages to the handwritten cards in the mail, to gifts in the mail, to phone calls, voicemails and a whole bunch of different things. There's a whole mess of stuff that we do which completely wow our customers. It's because we're scaling."   Dean Soto  6:55   It is what Jermaine Griggs calls – one of my mentors – we are scaling personal attention. It doesn't matter if we have one customer or if we have 1000 customers because of what we – the data that we gather – because of the information that we are able to use in cards and we're able to use to trigger different things. We're able to give a personal touch.   Dean Soto  7:28   Even when we're we're a one person organization, a five person organization, a 10 person organization. We're able to touch thousands of people and continue to be profitable. At the same time, wow our customers.   Dean Soto  7:57   And maximize the money and resources that we have. Okay, now is that because "Gosh, Dean, you're just so genius and that's why because you're the Freedom In Five Minutes guy. You're the Pro Sulum guy that has these Virtual Systems Architects where you can show them how to do something in five minutes. They document it and then you never have to do that thing ever again. You're that guy, right? That's why because you were born anointed. So that you may do this for other people."    Dean Soto  8:34   And I do this for other people. You know, sometimes it is. Sometimes, people just have a really, really hard time with that and they pay me several thousand dollars – tens of thousands of dollars to do it for them. But the vast majority of people can do it by themselves. They can do it themselves. A lot of the time, they are just doing one of two things: It's embracing constraints and seeing what you have and utilizing what you have. And then, seeing systems as a way of saying, "I love you," to your customers, and "I appreciate you."   Dean Soto  9:12   A lot of the time, we think, "Well, my customers – the way that they will feel special and taken care of is if I'm constantly the one doing it." And it's true, in a sense, every now and then if you give a call, or you say, hey, I want to give you a free strategy session, just because you've been so amazing. That's totally fine. That's something that's completely true as well. And you know, they would appreciate that. However, the reality is just getting something in the mail – think of all of the different businesses that you do business with and think of how many times you have gotten something in the mail from them that wasn't an advertisement? Even something like a birthday thing?   Dean Soto  10:14   You know, say you got a birthday card in the mail where it was like "Hey, happy birthday. You're gonna get 20% $20 off your next visit." It's always some dumb advertisement. It's something that's never just given to you. Imagine getting a box of cookies in the mail and a card that just said, "Hey, we thank you so much for being a customer. It really does mean a lot to us that you value us and that you are getting a ton of value from what we're doing. Just wanted to say thank you." And not asking for anything in return.   Dean Soto  11:02   To me, that is something that goes so far right? And never happens and it costs you 10 bucks or 15 bucks?Maybe 20 bucks to do and you've already netted and profited from your client like $200 so 10% of that goes back to them just saying thank you.   Dean Soto  11:30   Nobody does that   Dean Soto  11:34   Nobody does that.   Dean Soto  11:37   And so when I have my customers get something like that. They're like, Whoa, I've never had this happen before. This is amazing. Or A phone call like after they buy. Even if it's an automated one where it goes to their voicemail. They're like, "Whoa Dean called. That's amazing." You know, this is all possible you have Twilio. You have Thinkster you have all these different things. You have send-out cards. you have all these different things that you can use to trigger different things based on how much someone has bought and where they are at in the sales cycle. Where are they? As a client and customer, how many people have they referred to you? All of this type of stuff, right? And so, when you set up these systems, you automate the saying of I love you. You automate the saying of I value you as a client and a customer and it keeps it to where... because the personal is great. Don't get me wrong – in person, over the phone, that is great. But there are times when you or an assistant or whomever drops the ball. And now you have a customer who is just dangling there. We want to have people... We always want to make it a foolproof type thing. Okay. So all that being said, I really want to tell you the importance of this. The more systems that you can develop that thank your customers and tell them that I love you, the more you're going to get referrals. Man I my business is based off of referrals for the most part, and they are the best.   Dean Soto  13:58   They come because of all these gifts and Stuff like that to happen and it comes because we have a great product obviously. No one's gonna refer if it's not a great product. But these gifts give the little nudges. These little gifts say I love you, it gives a little nudge to go, "Yeah, you know what? I really like these guys. I really want to have other people experience this as well." So what do you do? What system do you have right now that can say I love you and give that beautiful, wonderful personal touch, even though it might not be actually in person?    Dean Soto  14:35   So all right, this is Dean Soto. Founder of FreedomInFiveMinutes.com and ProSulum.com. I don't know where Luna is. She's somewhere lost in this area. I do not see her. So I'm gonna go and find her. So, all that being said, Go check out FreedomInFiveMinutes.com. Go check out ProSulum.com P-R-O-S-U-L-U-M.com. We got lots of amazing stuff there. And if you're ever wanting a Virtual Systems Architect and want to get to the next level. If you want to scale your business, want to grow your business and do it all in as little as five minutes a day. Go check out FreedomInFiveMinutes.com or ProSulum.com P-R-O-S-U-L-U-M.com. There's the answer to Freedom In Five Minutes. I will catch you on the next Freedom In Five Minutes podcast episode.

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 Charles Max Wood Guests Mike Ryan  Sam Julien Tracy Lee Dean Radcliffe Joe Eames Sponsors NxPlaybook.com - Use code ‘NXDEVCHAT’ for 50% off the official https://nx.dev/React Advanced Workspaces course!  CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________   Links https://www.rxjs.live/ RxJS Live Youtube Channel https://twitter.com/mikeryandev https://twitter.com/samjulien https://twitter.com/ladyleet? https://www.npmjs.com/package/rx-helper https://twitter.com/deaniusol https://twitter.com/josepheames https://devchat.tv/dev-ed/ https://www.facebook.com/React-Round-Up https://twitter.com/reactroundup

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 Charles Max Wood Guests Mike Ryan  Sam Julien Tracy Lee Dean Radcliffe Joe Eames Sponsors NxPlaybook.com - Use code ‘NXDEVCHAT’ for 50% off the official https://nx.dev/React Advanced Workspaces course!  CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________   Links https://www.rxjs.live/ RxJS Live Youtube Channel https://twitter.com/mikeryandev https://twitter.com/samjulien https://twitter.com/ladyleet? https://www.npmjs.com/package/rx-helper https://twitter.com/deaniusol https://twitter.com/josepheames https://devchat.tv/dev-ed/ https://www.facebook.com/React-Round-Up https://twitter.com/reactroundup

Quick show notes Our Guest: Sam Julien What he'd like for you to see: Auth0 Community Forum | His Gatsby Course on Thinkster | Get a Job in Tech His JAMstack Jams: The methodology and not needing to stand up a server for every little thing His Musical Jam: "Not" by Big Thief Other Technology Mentioned Gatsby Jekyll NextJS AirTable Twilio Our sponsor this week: TakeShape Transcript Bryan Robinson 0:02 Hello, everyone, and welcome to the first real episode of 2020 you're listening to That's My JAMstack, the podcast where we dare to ask the question, what is your jam in the JAMstack. I'm your host, Bryan Robinson. And today on the show, we have a speaker, author, teacher, a developer relations engineer at Auth0, Sam Julien. Bryan Robinson 0:24 I'm also pleased to welcome back to the show are sponsored TakeShape, find out more about their content platform after the episode or head over to takeshape.io/thatsmyjamstack for more information. Bryan Robinson 0:39 All right, Sam, thanks for joining us on the podcast today. Sam Julien 0:41 Yeah, thanks. I'm really happy to be here. Bryan Robinson 0:43 Cool. So tell us a little bit about yourself. What do you do for work? What do you do for fun? That sort of thing? Sam Julien 0:47 Yeah. So I am a Developer Advocate engineer at Auth0, which is just sort of a fancy word for Developer Relations. And so basically, spend my time I'm doing a lot of interacting with developers who use Auth0 the product and then kind of taking that feedback back to the different teams. Sam Julien 1:11 And so I, I do a lot of speaking at events and things like that and working on basically combining x technology with Auth0 and trying to find the problems with it. Sam Julien 1:22 And then for fun, I actually live in a rural area of the Pacific Northwest. I live on 10 acres of land with my partner. And then we have some friends who also are in the own the land with us, and so they come up on weekends and stuff. And so we have, we have 20 chickens that we raise, and we're getting some eggs from and yeah, and so ever since moving on to this land that's sort of taken over as my hobby. I feel like I was a lot more interesting when I lived in Portland as far as like hobbies and activities but that's aside from taking care of the property.I see you have a Breath of the Wild artwork on your wall. And that's basically my current hobby is playing Breath of the Wild. Bryan Robinson 2:13 You could think almost a lifetime into that. So that'd be fine. Sam Julien 2:15 Yeah, it's pretty crazy. I don't know if I'm gonna go ... So we only got a Switch a few months ago. And I don't know if I'm going to go for completion on it. But Amy is definitely. She's already I think she's already got like, 105 shrines or something. And she's, she's going for 100%. Bryan Robinson 2:36 You could spend a long time going for 100%. So you eat a lot of the eggs that you get fresh from the chickens? Sam Julien 2:43 Well, we we just actually just started laying. Like a week ago, actually, we got them when they were chicks. And so I think we've almost got a dozen at this point. So we're probably going to start eating them pretty soon. There first ones are always kind of duds because they're like trying to figure it out and not fully formed. And so but I think we're just about there to start eating them. Bryan Robinson 3:10 All right. Well, this is this is neither a chicken podcast nor a gaming podcast. Let's let's talk about the JAMstack a little bit, right.Unknown Speaker 3:17 Yeah, I suppose we should talk about the JAMstack. Bryan Robinson 3:20 So what was kind of your entry point into this idea whether there was static sites back in the day, JAMstack nowadays? What's your what's your entry point? Sam Julien 3:28 Well, I mean, aside from, you know, the, the, the real static site being like, index.html and everything. Aside from that, I would say my introduction to the JAMstack was through Gatsby, and my introduction to Gatsby was just through, umm... So before I was in Developer Relations at Auth0, I was on the content team. So I was writing tutorials and stuff and we sort of went through this process. The blog at Auth0 is in Jekyll, and there's sort of this ongoing debate internally of whether to migrate to Gatsby or not. And I don't, I don't know if they're going to end up doing it or not. Because you know how it is with wanting to rewrite a platform. It's like, it's like, is this a good idea? Like, legacy code is still, it still works. So. But uh, so anyway, so that's so some colleagues on that team, were telling me about Gatsby. Sam Julien 4:24 And so I started looking into it. And I kind of just like instantly fell in love with it and started messing around with it and building stuff with it and looking at everybody else's blogs and portfolios that they were making with it. And it just really like scratch the itch for me of both being a developer and a writer, and I just really liked it. So then that kind of led down the path of the rest of the jam stack and all that. I guess Bryan Robinson 4:51 So, when you got into Gatsby, had you done a lot of react previously or was that new too? Sam Julien 4:56 It was actually kind of my way into React. Because I, I'm historically an Angular developer, like I came from C# and then like C# and Angular kind of go really well together. And so I've done I had done a bunch of Angular over the last few years. And then, but Auth0 basically uses React almost exclusively internally. And so I was, it was already sort of on my list of things to learn. But Gatsby was sort of a nice, like way into react because it handled all the tooling and everything, since it's just, it's basically just a supercharged create react app. And so it sort of gave me this nice platform to just dig into react, while not having to kind of worry about the all the tooling involved. Bryan Robinson 5:50 it's also got, I think, I think, a pretty strong set of opinions to which helps kind of guide on best practices. Sam Julien 5:56 Right, exactly. And an Angular like, angular has A ton of strong opinions. And so that's sort of what I was used to. I mean, it's sort of there's pros and cons to both approach both approaches. But I think when I was first starting to learn react when I joined Auth0, I was a little like dizzy by just how many different ways you can slice and dice react. And so Gatsby really did kind of help just kind of narrow the focus of like, here's like, a set of tools, like a ready made thing for you now just write some react and and figure it out, you know. Bryan Robinson 6:31 So, how are you using the JAMstack professionally? I mean, I know you said that they're debating coming to Gatsby and they are on Jekyll. But you're not on that content team anymore. Are you doing some JAMstack type things and your developer relations that Auth0? Sam Julien 6:46 Yeah, so I I, I'm sort of doing both stuff personally and professionally with it from the professional side at off zero. It's mostly I've been really kind of digging into What authentication looks like in the jam stack because it's kind of an interesting. It's an it's an interesting, new problem set, because it's sometimes it's more like a traditional web app. And sometimes it's more like just a single page application. And sometimes you have these serverless models that you have to authenticate and stuff like that. Sam Julien 7:23 So so I'm sort of in this research phase right now if like trying to build different prototypes with Gatsby or Next or you know, things like that and wrap my head around what the problem set looks like of like, when is it more like a traditional web app? When is it more like a spa? When is there sort of this in between weird case of serverless stuff and all that and so that's sort of what I'm doing now is is figuring out how Azzurro fits in with jam stack stuff and how we can make it easy for developers and that kind of thing. And then from the on the personal side of things, I'm using Gatsby to build, build, I'm rebuilding, I am rebuilding my own personal site with Gatsby, which is I still am not convinced it's a great idea, but I'm going to do it anyway. And, and, and then I built I loved Gatsby so much, but I, I couldn't find exactly like the way of teaching it that that I liked. And so I built a course for a platform called things through.io on Gatsby just sort of like getting started with Gatsby. And so that's minute sort of another side project endeavors this, this course and different content, I ended up doing a couple egghead lessons on some Gatsby stuff. And so that's sort of my Gatsby sort of fueling my side hustle as well as my day job right now. Bryan Robinson 8:57 Cool. So uh, so what is kind of the thing that brings you to the JAMstack in terms of what do you love about it? What's your what's your jam in the JAMstack? Sam Julien 9:07 I really think this whole concept of not needing to pair a server with a front end is really nice. I just think that nowadays there there are so many different like SaaS products and like serverless products and things like that, that like, it seems like for a lot of cases other than complex enterprise stuff. You don't really need to spend a lot of time messing with building your own server and all of that, you know, it's just like, if you're just doing if you're pulling in data from outside, you know, like Twilio or wherever, you know, or AirTable or things like that. Sam Julien 9:53 Or if you're just making like a recently, a lot of developer relations as you know as building a lot of sample apps. And so recently I've been thinking I would always build like a little Express server to serve up data and stuff like that. And now I'm sort of like there's not really any point, I could just put this in a serverless function and reuse the same thing over and over again, and I don't really need it. So I'm really liking that, that the JAMstack has sort of opened up, like it's making so much stuff easier for a large a large percentage of apps that people need to build, you know what I mean? Bryan Robinson 10:31 Yeah, and so so you come from like a C# background so you're obviously not afraid of server side languages. I myself, deathly afraid serverside languages, so kind of, do you have a point where you would go and spin up your own server now or are you going to just be going in this serverless way going forward? Sam Julien 10:49 Well, I mean, I can see so like my my previous jobs were at like in doing like line of business applications for like bigger companies. One was like a finance company one was like a renewable energy nonprofit. So there, those places have a lot of complex business logic that has to happen, you know, with a bunch of data in a database where you have to manipulate and run a bunch of business rules and stuff like that. And to me that, that seems like kind of the obvious use case for like a real server where you actually, like, have a lot of stuff that has to interact with the database and, you know, sort of the more traditional route of, of servers and databases and all that. And so, but I think for a lot of modern stuff that's not enterprise level, the serverless JAMstack stuff works pretty well, you know, and especially with having node I mean, you can sort of just use JavaScript all the time and it's just things are just so much easier. It's It's really nice. Bryan Robinson 11:54 Front End Dev and designer like me, like it just makes my life so much more pleasant Sam Julien 12:00 Yeah, for sure. Definitely. Bryan Robinson 12:02 So so the kind of the whole methodology of that is is where where you're going with your jam, right? Sam Julien 12:07 Yeah, yeah. Basically the whole philosophy. Bryan Robinson 12:10 Yeah. So. So in terms of serverless and all that, right, so you said you started exploring authentication in this world for all zero. How's that going? Because I'll be honest, I haven't done a whole lot of research into it yet. Sam Julien 12:24 It's interesting. And one thing we can link to is one of our architects named Sandrino wrote this really cool article on NextJS and Auth0, but I mean, it's with Auth0, but it also anytime we write about Auth0, we try to also have things that are basically broad, more broad for authentication in general. But we're sort of figuring out that there's these like I said, sort of three different models basically, of like, sometimes it's more like a traditional web app because you're basically, if you're if you're doing everything server side, then it's sort of more like a traditional web app, right? Because you're, you're not really running anything in the browser. I mean, you're running it in the browser, but you're not. There's nothing dynamic happening in the browser. And so you would kind of go with the standard, standard web app approach. Sam Julien 13:21 And then there's things like Gatsby are sort of like Gatsby is interesting, because it's, it got its start as like a static site generator, but it's never actually like, holy a static site, right? Because it's still react, running, you know, like as a spa. And so that sort of this weird case where it's like, it's kind of a static site, but really, you would authenticate it just like you would a spa, pretty much. But then there's this like Next has this whole thing with the serverless deployment model. And from there, you sort of have to determine like where I need The authenticated data like do I need it when the page first renders? Or do I need it later? and Sandrino, you know, has some nice diagrams in that article that will do a better job of explaining it than I can in audio. Bryan Robinson 14:14 Lovely Mouth Blogging as Dave Rupert would say Sam Julien 14:16 Yeah, yeah. Yeah. So that stuff's really interesting. And I'm still sort of wrapping my head around at all and building out sample apps and stuff like that. But but it's, it's interesting. And it's definitely as the JAMstack continues to be as popular as it is more and more people will need to understand how to protect all their data and everything. Bryan Robinson 14:39 And Auth is probably the one of the biggest challenges to like adoption in the JAMstack right now to like, how do I protect pages when it's just static? Sam Julien 14:47 Yeah, yeah. Yeah. Our architecture and content and developer relations at Auth0 have all been sort of mulling this over for a little while, because I think actually, for this article, Sandrino was talking to people outside and stuff because it's sort of like how do we want to do this? You know, like, what are the best practices here? Bryan Robinson 15:08 Let's create some standards for it and kind of go Sam Julien 15:12 Yeah, exactly. Bryan Robinson 15:15 So let's let's talk musical jam now what are you listening to? what's what's your favorite song or musician or genre? Sam Julien 15:23 I finally I have a great answer for this now and it's because So have you ever heard of the band Big Thief I have made so they on their last on their most recent album, their their single is called Not. And it's got it's like one of the my, like, favorite songs that I've heard in several years. Like there's something very emotional about it. That is just really awesome. And it's nice because I yeah, I just haven't I haven't felt that kind of like connection to a song. In a really long time so I've been I've been playing that a lot not by big thief. Sam Julien 16:06 Let's see what else what else have I been? I feel like as I get older I have less and less like emotional connection to things because I'm not young and nostagic anymore but let's see what am I've been listening to you other than that. I like Tool's new album a lot. I liked Angel Olsen's most recent album, I'm a really big Angel Olsen fan. She's sort of like the singer songwriter type, but her album couple years ago, called What was it called My Woman in 2016. That was a fantastic album, if you haven't listened to it. Bryan Robinson 16:46 That's actually my favorite thing on the podcast other than learning about new technology is learning about all these like drastically different musical tastes and going and listening to what what everyone says. Sam Julien 16:53 I love that. I think that's a really great when I saw that question in the invite. I was like, Oh, that's cool. That's Great I like that. I'd be curious, what's what's your current jam right now? What are you listening? Bryan Robinson 17:05 You turn the tables on me! Sam Julien 17:06 I'm turning the tables Bryan Robinson 17:07 First time! You know, I just I'm behind the times always like that perpetually. But I just this past summer went and saw Hamilton, the touring company came around, and I didn't think I was going to... Like, I thought I would like it; like musical theater well enough, but like, I am in love with it. And it gets me going in the mornings like it really pumps me up. And then I go and research all the founding fathers and realize how horrible they were. But it it gets me going at least. Sam Julien 17:36 Yeah, now, Hamilton; Amy was really into Hamilton. And so I kind of I'm like neutral towards musical theater. Like, I don't I don't dislike it. I don't you know, but Amy was really into it. And so when it came to Portland, I got us tickets and we went, and I'll admit, like, I loved it. I thought it was like it was not overrated at all like I kind of went into it expecting it to be a little overrated because it's so popular, but like, I thought it was fantastic. Bryan Robinson 18:07 There's a reason it won all those awards. Sam Julien 18:08 Yeah, I mean, some some things are hyped up because they're actually that great, you know, like, like Beyonce. Bryan Robinson 18:17 Yeah, exactly. I found that running to it actually works really well, too. So I'm trying to get into running and that has just the right beat for how bad I am at running. SoUnknown Speaker 18:26 Oh, yeah. Yeah, that's great. I am. I really I had seen In the Heights A long time ago. And so I already liked Lin-Manuel Miranda. But yeah, it's, it's a great yeah. If you ever have a chance, I don't know if In the Heights is still playing anywhere, but if you ever have a chance to see it, it's a really good one. Bryan Robinson 18:46 I didn't even know he had written anything before that. And I researched what he had done was like, Oh, you've done this before. Okay. Sam Julien 18:51 Yeah, yeah, he's Yeah, he's super talented. But that one is about like Washington Heights in New York and stuff like that. It's really great. Bryan Robinson 19:00 For someone indifferent towards towards musical theater you you've got at least that much now. Sam Julien 19:05 Yeah, that's true. I I kind of Yeah, I would say. Other than that though I'm I tend to be pretty neutral about about theater, I could take it or leave it. I respect it. And I respect that other people love it. It's just not it's just not my thing. Not my jam... Bryan Robinson 19:24 All right. And so let me let me ask, Is there anything that you would like to promote? Get out to the JAMstack community? Anything that you're doing that you won't get out there? Sam Julien 19:30 Yeah, I'll say on the on the professional side. Yeah, just keep an eye on Auth0 for JAMstack stuff because we're actively working on it. And, and if people have like input or things they want to talk about, we have a great community forum. So if you're running into authentication problems in JAMstack stuff, like definitely let us know because we're always kind of putting our ear to the ground and trying to figure out what problems people are having. So we can Try to solve them. Sam Julien 20:02 And then personally Yeah, the the Gatsby course on Thinkster. I'm really proud of it. I think it's a good course. And so that would be good. I'm also I just started, I'm starting this new project called Get a Job in Tech. I'm a self taught developer, I transitioned from finance. And I was lucky because I had some mentors that sort of shepherded me along the way, and not everybody has that. And so I'm starting this new, it's still really early, but basically, I plan on I'm already like, right, sending out emails and stuff and writing content for it, but it's basically to help people with the like, meta skills of getting your first job because I feel like a lot of people think, you know, they learned they learned some stuff on like, Free Code Camp or any any other great site on learning to code and then they sort of get stuck because they're like, okay, where's like, how do I actually get the Job, and you just sort of throw your resume up on a lot of places. And then you get these rejection letters that are like, you don't have any experience and you're like, no duh don't have any. Bryan Robinson 21:10 It's a Junior position, come on!Unknown Speaker 21:12 Yeah, like literally, like, that's what it is like. And so there's all these skills of like, like learning in public with GitHub and stuff like that, that like, not many people really teach you, you know, like, there's sort of an art to getting or getting a job and that kind of thing. So that I've been really thinking about that lately. And so I started that up as a sort of a labor of love. And where's that it's get a job in dot tech, basically, I'll, I'll paste in the link. Yeah. And then and then basically, everything I do is tracked at SamJulien.com so you can always go there and I have an occasional email list and stuff like that. So if you ever want to keep up with talks I'm doing or lessons I'm publishing on egghead or thinkest or anything like that. Bryan Robinson 22:00 Perfect. Yeah. Awesome. Well, thanks for taking the time to talk with us today and share your insights. And I hope that you keep doing awesome stuff at all zero and that your chickens eggs are delicious.Unknown Speaker 22:09 Thanks. Yeah. Thanks for having me. I really appreciate it. Bryan Robinson 22:12 Yeah, no problem. All right. Well take care. Bryan Robinson 22:18 All right, it is sponsored time, I want to take a second and thank this week's sponsor TakeShape. TakeShape calls, their offering a content platform. And that's, that's really the best description. They have a handy CMS, a static site generator, and a simple GraphQL API all ready to use on the JAMstack. Bryan Robinson 22:35 Beyond all that they also have new features coming in all the time, like their new Mesh product that allows you to mix and match data from multiple sources into one neat GraphQL interface. If all that sounds interesting, you be sure to go to takeshape.io/thatsmyjamstack to find out more. Bryan Robinson 22:53 And as always, I want to thank the JAMstack community for listening for responding on Twitter for talking about things in communities. Just for being an amazing place to work and to play and to spend my time. So if you like this podcast let me know by hitting the like, subscribe, all those good things and whatever podcast app you use, and until next week, keep doing amazing things and keep things jamming.Transcribed by https://otter.aiIntro/outtro music by bensound.comSupport That's my JAMstack by donating to their Tip Jar: https://tips.pinecast.com/jar/thats-my-jamstack

In this episode of Adventures in Angular 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 Charles Max Wood Guests Mike Ryan  Sam Julien Tracy Lee Dean Radcliffe Joe Eames Sponsors Sentry -use the code "devchat" for 2 months free on Sentry's small plan CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________   Links https://www.rxjs.live/ RxJS Live Youtube Channel https://twitter.com/mikeryandev https://twitter.com/samjulien https://twitter.com/ladyleet? https://www.npmjs.com/package/rx-helper https://twitter.com/deaniusol https://twitter.com/josepheames https://devchat.tv/dev-ed/ https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast

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 Charles Max Wood Guests Mike Ryan  Sam Julien Tracy Lee Dean Radcliffe Joe Eames Sponsors Infinite Red G2i CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________   Links https://www.rxjs.live/ RxJS Live Youtube Channel https://twitter.com/mikeryandev https://twitter.com/samjulien https://twitter.com/ladyleet? https://www.npmjs.com/package/rx-helper https://twitter.com/deaniusol https://twitter.com/josepheames https://devchat.tv/dev-ed/ https://www.facebook.com/ReactNativeRadio/ https://twitter.com/R_N_Radio  

In this episode of Adventures in Angular 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 Charles Max Wood Guests Mike Ryan  Sam Julien Tracy Lee Dean Radcliffe Joe Eames Sponsors Sentry -use the code "devchat" for 2 months free on Sentry's small plan CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________   Links https://www.rxjs.live/ RxJS Live Youtube Channel https://twitter.com/mikeryandev https://twitter.com/samjulien https://twitter.com/ladyleet? https://www.npmjs.com/package/rx-helper https://twitter.com/deaniusol https://twitter.com/josepheames https://devchat.tv/dev-ed/ https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast

In this episode of Adventures in Angular 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 Charles Max Wood Guests Mike Ryan  Sam Julien Tracy Lee Dean Radcliffe Joe Eames Sponsors Sentry -use the code "devchat" for 2 months free on Sentry's small plan CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________   Links https://www.rxjs.live/ RxJS Live Youtube Channel https://twitter.com/mikeryandev https://twitter.com/samjulien https://twitter.com/ladyleet? https://www.npmjs.com/package/rx-helper https://twitter.com/deaniusol https://twitter.com/josepheames https://devchat.tv/dev-ed/ https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast

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 Charles Max Wood Guests Mike Ryan  Sam Julien Tracy Lee Dean Radcliffe Joe Eames Sponsors Infinite Red G2i CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________   Links https://www.rxjs.live/ RxJS Live Youtube Channel https://twitter.com/mikeryandev https://twitter.com/samjulien https://twitter.com/ladyleet? https://www.npmjs.com/package/rx-helper https://twitter.com/deaniusol https://twitter.com/josepheames https://devchat.tv/dev-ed/ https://www.facebook.com/ReactNativeRadio/ https://twitter.com/R_N_Radio  

In this episode of JavaScript Jabber 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 Charles Max Wood Guests Mike Ryan  Sam Julien Tracy Lee Dean Radcliffe Joe Eames Sponsors ABOUT YOU |aboutyou.com/apply Sentry -use the code "devchat" for 2 months free on Sentry's small plan CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ___________________________________________________________ Links https://www.rxjs.live/ RxJS Live Youtube Channel https://twitter.com/mikeryandev https://twitter.com/samjulien https://twitter.com/ladyleet? https://www.npmjs.com/package/rx-helper https://twitter.com/deaniusol https://twitter.com/josepheames https://devchat.tv/dev-ed/ https://www.facebook.com/javascriptjabber https://twitter.com/JSJabber

In this episode of JavaScript Jabber 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 Charles Max Wood Guests Mike Ryan  Sam Julien Tracy Lee Dean Radcliffe Joe Eames Sponsors ABOUT YOU |aboutyou.com/apply Sentry -use the code "devchat" for 2 months free on Sentry's small plan CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ___________________________________________________________ Links https://www.rxjs.live/ RxJS Live Youtube Channel https://twitter.com/mikeryandev https://twitter.com/samjulien https://twitter.com/ladyleet? https://www.npmjs.com/package/rx-helper https://twitter.com/deaniusol https://twitter.com/josepheames https://devchat.tv/dev-ed/ https://www.facebook.com/javascriptjabber https://twitter.com/JSJabber

In this episode of JavaScript Jabber 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 Charles Max Wood Guests Mike Ryan  Sam Julien Tracy Lee Dean Radcliffe Joe Eames Sponsors ABOUT YOU |aboutyou.com/apply Sentry -use the code "devchat" for 2 months free on Sentry's small plan CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ___________________________________________________________ Links https://www.rxjs.live/ RxJS Live Youtube Channel https://twitter.com/mikeryandev https://twitter.com/samjulien https://twitter.com/ladyleet? https://www.npmjs.com/package/rx-helper https://twitter.com/deaniusol https://twitter.com/josepheames https://devchat.tv/dev-ed/ https://www.facebook.com/javascriptjabber https://twitter.com/JSJabber

This episode of the DevEd podcast is joined by special guest Thomas Desmond. Thomas is a software engineer currently working with .NET and Angular, has been a university instructor for three years and has a course coming up on Thinkster.io - Creating an API with ASP.NET Core. He defines ASP.NET, and describes its relation to ASP.NET Core. He explains the process of working with .NET on a Mac, differences between Visual Studio Code and Visual Studio Mac 2019, and the learning curve involved in C# and types languages such as TypeScript. The panelists share their learning transition from .NET to other languages and frameworks such as Angular, React and vice versa. They talk about the hurdles as well as effective strategies in learning ASP.NET, why is .NET considered to be Microsoft-specific, how does it compare to technologies such as Rails or Node, cloud development, and discuss reasons why bootcamps don't generally focus on learning ASP.NET. They end the show with picks. Panel Brooke Avery Luis Hernandez Mike Dane Jesse Sanders Lukas Ruebbelke Joined by special guest: Thomas Desmond Sponsors Thinkster.io Ruby Rogues CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links Thomas's Twitter Creating a C# ASP.Net Core API - Introduction Picks Thomas Desmond: The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth Luis Hernandez: Visual Studio Dev Essentials ASP.NET Mike Dane: Alta 21 Pack Jesse Sanders: Taxi Driver Bike Helmet Garmin watches Lukas Ruebbelke: Ed Motta Kurt Elling Brooke Avery: Noah Kahan - Busyhead Biteable The DevEd podcast is produced by Thinkster.io and published by DevChat.TV. Question #1: What is ASP.NET? Open source web application framework used to develop and build web apps using .NET. Question #2: How to use .NET on a Mac? Use Visual Studio for Mac, good support available. Question #3: What are some hurdles in learning ASP.NET? Understanding and reinforcing the idea that there is an API between the application and the server. Question #4: What are some effective tips while learning .NET? Do a lot of examples, repetitions, discuss questions with other students.

This episode of the DevEd podcast is joined by special guest Thomas Desmond. Thomas is a software engineer currently working with .NET and Angular, has been a university instructor for three years and has a course coming up on Thinkster.io - Creating an API with ASP.NET Core. He defines ASP.NET, and describes its relation to ASP.NET Core. He explains the process of working with .NET on a Mac, differences between Visual Studio Code and Visual Studio Mac 2019, and the learning curve involved in C# and types languages such as TypeScript. The panelists share their learning transition from .NET to other languages and frameworks such as Angular, React and vice versa. They talk about the hurdles as well as effective strategies in learning ASP.NET, why is .NET considered to be Microsoft-specific, how does it compare to technologies such as Rails or Node, cloud development, and discuss reasons why bootcamps don't generally focus on learning ASP.NET. They end the show with picks. Panel Brooke Avery Luis Hernandez Mike Dane Jesse Sanders Lukas Ruebbelke Joined by special guest: Thomas Desmond Sponsors Thinkster.io Ruby Rogues CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links Thomas's Twitter Creating a C# ASP.Net Core API - Introduction Picks Thomas Desmond: The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth Luis Hernandez: Visual Studio Dev Essentials ASP.NET Mike Dane: Alta 21 Pack Jesse Sanders: Taxi Driver Bike Helmet Garmin watches Lukas Ruebbelke: Ed Motta Kurt Elling Brooke Avery: Noah Kahan - Busyhead Biteable The DevEd podcast is produced by Thinkster.io and published by DevChat.TV. Question #1: What is ASP.NET? Open source web application framework used to develop and build web apps using .NET. Question #2: How to use .NET on a Mac? Use Visual Studio for Mac, good support available. Question #3: What are some hurdles in learning ASP.NET? Understanding and reinforcing the idea that there is an API between the application and the server. Question #4: What are some effective tips while learning .NET? Do a lot of examples, repetitions, discuss questions with other students.

In this episode of the DevEd podcast, the panel discusses Testing and Test Driven Development. They start the conversation by talking about automated testing with the help of unit tests using various tools available. Luis explains the terms regression testing, refactoring, mocking, continuous integration and continuous delivery (CI/CD). Everyone shares their experience with testing, mainly how and when they started learning automated testing and their journey with it so far. They then dive into the learning aspect of testing including some of the best ways to learn unit testing and give great tips and tools along the way. The next topic discussed is Test Driven Development - the definition, division of the development community into those support the methodology and those who do not, and more importantly, how effective it can be, it's benefits and drawbacks and the comparison between TDD and BDD (Behaviour Driven Development). They also talk about mocking, how testing can improve the quality of applications, and visual testing. In the end, they each mention their most favourite and least favorite testing tools. Panel Joe Eames Luis Hernandez Jesse Sanders Mike Dane Sam Julien Sponsors Thinkster.io Adventures in Angular ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links Uncle Bob - TDD The Magic Tricks of Testing by Sandi Metz Code Kata TDD Kata 1 - Roy Osherove cypress Jest SuperTest Testable Picks Mike Dane: YouTube Music Luis Hernandez: Microsoft Whiteboard Jesse Sanders: Tile for Keys Star Wars: The Rise of Skywalker - Final Trailer Easter Eggs Sam Julien: Strange Planet - Nathan W. Pyle Joe Eames: Stackbit The DevEd podcast is produced by Thinkster.io and published by DevChat.TV. Question #1: What is regression and refactoring? Regression is handling new changes that affect or break legacy code, refactoring is changing the way code is written without changing the functionality. Question #2: What are ways to learn unit-testing? Learning by example, practicing using open source codes, studying existing tests from a large codebase, trying to increase code-coverage, writing simple math based tests and Code Katas. Question #3: What is TDD? Writing tests before designing the implementation code, red-green-refactor approach - write a test and make it fail (red), write code to make it pass (green) and eventually refactor the code. Question #4: What is a mock? Artificially created responses that can be used and controlled by tests.

In this episode of the DevEd podcast, the panel discusses Testing and Test Driven Development. They start the conversation by talking about automated testing with the help of unit tests using various tools available. Luis explains the terms regression testing, refactoring, mocking, continuous integration and continuous delivery (CI/CD). Everyone shares their experience with testing, mainly how and when they started learning automated testing and their journey with it so far. They then dive into the learning aspect of testing including some of the best ways to learn unit testing and give great tips and tools along the way. The next topic discussed is Test Driven Development - the definition, division of the development community into those support the methodology and those who do not, and more importantly, how effective it can be, it's benefits and drawbacks and the comparison between TDD and BDD (Behaviour Driven Development). They also talk about mocking, how testing can improve the quality of applications, and visual testing. In the end, they each mention their most favourite and least favorite testing tools. Panel Joe Eames Luis Hernandez Jesse Sanders Mike Dane Sam Julien Sponsors Thinkster.io Adventures in Angular ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links Uncle Bob - TDD The Magic Tricks of Testing by Sandi Metz Code Kata TDD Kata 1 - Roy Osherove cypress Jest SuperTest Testable Picks Mike Dane: YouTube Music Luis Hernandez: Microsoft Whiteboard Jesse Sanders: Tile for Keys Star Wars: The Rise of Skywalker - Final Trailer Easter Eggs Sam Julien: Strange Planet - Nathan W. Pyle Joe Eames: Stackbit The DevEd podcast is produced by Thinkster.io and published by DevChat.TV. Question #1: What is regression and refactoring? Regression is handling new changes that affect or break legacy code, refactoring is changing the way code is written without changing the functionality. Question #2: What are ways to learn unit-testing? Learning by example, practicing using open source codes, studying existing tests from a large codebase, trying to increase code-coverage, writing simple math based tests and Code Katas. Question #3: What is TDD? Writing tests before designing the implementation code, red-green-refactor approach - write a test and make it fail (red), write code to make it pass (green) and eventually refactor the code. Question #4: What is a mock? Artificially created responses that can be used and controlled by tests.

In this episode of the DevEd podcast, David Graham - founder and CEO of Code Ninjas, introduces himself, gives a background of how he got into software development, briefly describes his vision that led to the creation of Code Ninjas and the interesting work that goes on there. The company essentially consists of coding centres for kids in multiple locations throughout the US, with cool learning programs catering to several age groups, its main purpose being teaching hands on software development combined with a lot of fun.  The panelists share their views about the current state of programming education in schools, if it is adequate, and what can be done to supplement it. They discuss that it is important to teach kids how to think and how to solve problems rather than relying on memory based learning. They mention ways to get students excited about programming, different learning tools and platforms, and similarities and differences in learning patterns between kids and adult learners.They talk on why should everyone care about coding education for kids, even those who do not have them, and how people can help out in getting youth involved in software development. They also discuss if there is anything they wish had existed to aid learning for young individuals also how it would help them in return. In the end, David explains how can people volunteer for Code Ninjas. Panel Brooke Avery Sam Julien Mike Dane Preston Lamb Joined by speacial guest: David Graham Sponsors Thinkster.io iPhreaks - Devchat.tv Views on Vue - Devchat.tv ________________________________________________________________________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood will be out on November 20th on Amazon.  Get your copy on that date only for $1. ________________________________________________________________________________________________________________________ Links Code Ninjas Code.org CodeCombat Picks Mike Dane: JBL Clip 3 David Graham: The Wheel of Time Preston Lamb: Disney+ Brooke Avery: Harry Potter Kano Coding Kit Sam Julien: Create Your Own Hacker Nebula with Angular Blockly by Jeff Whelpley & Madelyn Whelpley Blockly ng-club The DevEd podcast is produced by Thinkster.io and published by DevChat.TV.

In this episode of the DevEd podcast, David Graham - founder and CEO of Code Ninjas, introduces himself, gives a background of how he got into software development, briefly describes his vision that led to the creation of Code Ninjas and the interesting work that goes on there. The company essentially consists of coding centres for kids in multiple locations throughout the US, with cool learning programs catering to several age groups, its main purpose being teaching hands on software development combined with a lot of fun.  The panelists share their views about the current state of programming education in schools, if it is adequate, and what can be done to supplement it. They discuss that it is important to teach kids how to think and how to solve problems rather than relying on memory based learning. They mention ways to get students excited about programming, different learning tools and platforms, and similarities and differences in learning patterns between kids and adult learners.They talk on why should everyone care about coding education for kids, even those who do not have them, and how people can help out in getting youth involved in software development. They also discuss if there is anything they wish had existed to aid learning for young individuals also how it would help them in return. In the end, David explains how can people volunteer for Code Ninjas. Panel Brooke Avery Sam Julien Mike Dane Preston Lamb Joined by speacial guest: David Graham Sponsors Thinkster.io iPhreaks - Devchat.tv Views on Vue - Devchat.tv ________________________________________________________________________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood will be out on November 20th on Amazon.  Get your copy on that date only for $1. ________________________________________________________________________________________________________________________ Links Code Ninjas Code.org CodeCombat Picks Mike Dane: JBL Clip 3 David Graham: The Wheel of Time Preston Lamb: Disney+ Brooke Avery: Harry Potter Kano Coding Kit Sam Julien: Create Your Own Hacker Nebula with Angular Blockly by Jeff Whelpley & Madelyn Whelpley Blockly ng-club The DevEd podcast is produced by Thinkster.io and published by DevChat.TV.

In this episode of the DevEd podcast, Brooke interviews Sam on Gatsby, and Sam's new course on Thinkster.io. Sam works in Developer Relations at Auth0, is a Google Developer Expert for Angular and Web Technologies, and is very passionate about teaching. Sam starts by explaining in detail what Gatsby is and what it is used for. He talks on the performance benefits of Gatsby, its comparison to React in terms of tooling and usage as well as learning, and if there are any tools or technologies needed as prerequisites to use Gatsby. He elaborates on what made him learn Gatsby, how it helped him advance his programming career, and both his favorite and not so favorite aspects of Gatsby. He then talks at length about his course - Up and Running with Gatsby, reasons he chose this topic specifically, the course design, and compelling reasons why people should go for it. In the end, he shares his thoughts on how Gatsby is getting popular and can help speed up development in enterprise companies and large organizations. Panel Brooke Avery Sam Julien Sponsors Thinkster.io Links Up and Running with Gatsby: Introduction The DevEd podcast is produced by Thinkster.io and published by DevChat.TV.

In this episode of the DevEd podcast, Brooke interviews Sam on Gatsby, and Sam's new course on Thinkster.io. Sam works in Developer Relations at Auth0, is a Google Developer Expert for Angular and Web Technologies, and is very passionate about teaching. Sam starts by explaining in detail what Gatsby is and what it is used for. He talks on the performance benefits of Gatsby, its comparison to React in terms of tooling and usage as well as learning, and if there are any tools or technologies needed as prerequisites to use Gatsby. He elaborates on what made him learn Gatsby, how it helped him advance his programming career, and both his favorite and not so favorite aspects of Gatsby. He then talks at length about his course - Up and Running with Gatsby, reasons he chose this topic specifically, the course design, and compelling reasons why people should go for it. In the end, he shares his thoughts on how Gatsby is getting popular and can help speed up development in enterprise companies and large organizations. Panel Brooke Avery Sam Julien Sponsors Thinkster.io Links Up and Running with Gatsby: Introduction The DevEd podcast is produced by Thinkster.io and published by DevChat.TV.

In this week's episode of the DevEd podcast, the panelists talk on comments in programming. To give a context of the chosen topic, Joe mentions that he sends out regular newsletters to Thinkser.io subscribers related to a variety of concepts, and has recently been sending out some on code smells, in one of which he talks about commenting. He gives an idea of what code smells are, and shares his opinion on using comments. His point of view is that a comment can be looked at as a failure or an inability to express the code functionality or even the technology involved, or is needed to make the code completely readable to other programmers. Comments can become out of date or get replaced. The other panelists join in the discussion on whether comments are good or bad, and they state that for beginners they can be very useful while not so much for experienced programmers. Too many comments can cause a mess, so they ideally should be used for large complex functions. They are mostly used to specify if refactoring is needed at a later stage, they should explain the "why" instead of "how", and in general the code should ideally be self-sufficient. They talk about when do they actually like to use comments. If a certain piece of code is doing something unusual or non-obvious or might break the consistency with the rest of the code, then it is imperative to explain why it is written that way. It can also be a good idea to document things for new or junior developers in the team in order to explain what is going on or what should not be done, and also to pair program with them in case things are not clear. Commit messages could be a replacement for comments as well. Comments are also useful when static values and constants such as URLs or UIDs are used in the code, and for explaining specific error mechanisms. They share great practical advice for programmers who are in the earlier stages of their software development career and have generally been taught to use comments by their professors or mentors. The tips they give include taking time to look through the codebase, checking how and where comments are being used by other developers, refactoring the code to write more readable functions wherever things are unclear, using good naming conventions, trying to write self-documenting code, asking a lot of questions to whoever has written the code including asking the reasons why it is written a certain way, and not being afraid to add comments of your own. They then discuss some replies to the newsletter sent by Joe about code smells related to the importance of comments in the messy reality of engineering, pros and cons of their usefulness, tradeoff between maintaining self-documented vs heavily documented code. They end the show with picks. The DevEd podcast is produced by Thinkster.io and published by DevChat.TV. Panel Joe Eames Jesse Sanders Luis Hernandez Preston Lamb Mike Dane Sponsors Thinkster.io The Freelancers' Show React Round Up CacheFly Picks Luis Hernandez: Sourcetree Mike Dane: Google Fi Preston Lamb: Office Ladies podcast Jesse Sanders: Tesla cars Joe Eames: Gaslands Question #1: What are code smells? A pattern that indicates that there may be a problem in the code with a possibility of improvement. Question #2: When should comments be used? Comments could be useful for beginners, not so much for experienced folk. Too many comments can cause a mess, so they ideally should be used only for large complex functions. They can be used to specify if refactoring is needed at a later stage, and for explaining the "why" instead of "how". Question #3: What are some good reasons to use comments? 1. If a certain piece of code is doing something unusual/non-obvious/might break the consistency with the rest of the code. 2. For new or junior developers on the team in order to explain what is going on or what should not be done. 3. When using static values and constants. Question #4: Tips for new developers regarding comments? 1. Taking time to look through the codebase. 2. Checking how and where comments are being used by other developers. 3. Refactoring the code to write more readable functions wherever things are unclear, using good naming conventions. 4. Trying to write self-documenting code, asking a lot of questions to whoever has written the code including the reasons why it is written a certain way. 5. Not being afraid to add comments of your own.

In this week's episode of the DevEd podcast, the panelists talk on comments in programming. To give a context of the chosen topic, Joe mentions that he sends out regular newsletters to Thinkser.io subscribers related to a variety of concepts, and has recently been sending out some on code smells, in one of which he talks about commenting. He gives an idea of what code smells are, and shares his opinion on using comments. His point of view is that a comment can be looked at as a failure or an inability to express the code functionality or even the technology involved, or is needed to make the code completely readable to other programmers. Comments can become out of date or get replaced. The other panelists join in the discussion on whether comments are good or bad, and they state that for beginners they can be very useful while not so much for experienced programmers. Too many comments can cause a mess, so they ideally should be used for large complex functions. They are mostly used to specify if refactoring is needed at a later stage, they should explain the "why" instead of "how", and in general the code should ideally be self-sufficient. They talk about when do they actually like to use comments. If a certain piece of code is doing something unusual or non-obvious or might break the consistency with the rest of the code, then it is imperative to explain why it is written that way. It can also be a good idea to document things for new or junior developers in the team in order to explain what is going on or what should not be done, and also to pair program with them in case things are not clear. Commit messages could be a replacement for comments as well. Comments are also useful when static values and constants such as URLs or UIDs are used in the code, and for explaining specific error mechanisms. They share great practical advice for programmers who are in the earlier stages of their software development career and have generally been taught to use comments by their professors or mentors. The tips they give include taking time to look through the codebase, checking how and where comments are being used by other developers, refactoring the code to write more readable functions wherever things are unclear, using good naming conventions, trying to write self-documenting code, asking a lot of questions to whoever has written the code including asking the reasons why it is written a certain way, and not being afraid to add comments of your own. They then discuss some replies to the newsletter sent by Joe about code smells related to the importance of comments in the messy reality of engineering, pros and cons of their usefulness, tradeoff between maintaining self-documented vs heavily documented code. They end the show with picks. The DevEd podcast is produced by Thinkster.io and published by DevChat.TV. Panel Joe Eames Jesse Sanders Luis Hernandez Preston Lamb Mike Dane Sponsors Thinkster.io The Freelancers' Show React Round Up CacheFly Picks Luis Hernandez: Sourcetree Mike Dane: Google Fi Preston Lamb: Office Ladies podcast Jesse Sanders: Tesla cars Joe Eames: Gaslands Question #1: What are code smells? A pattern that indicates that there may be a problem in the code with a possibility of improvement. Question #2: When should comments be used? Comments could be useful for beginners, not so much for experienced folk. Too many comments can cause a mess, so they ideally should be used only for large complex functions. They can be used to specify if refactoring is needed at a later stage, and for explaining the "why" instead of "how". Question #3: What are some good reasons to use comments? 1. If a certain piece of code is doing something unusual/non-obvious/might break the consistency with the rest of the code. 2. For new or junior developers on the team in order to explain what is going on or what should not be done. 3. When using static values and constants. Question #4: Tips for new developers regarding comments? 1. Taking time to look through the codebase. 2. Checking how and where comments are being used by other developers. 3. Refactoring the code to write more readable functions wherever things are unclear, using good naming conventions. 4. Trying to write self-documenting code, asking a lot of questions to whoever has written the code including the reasons why it is written a certain way. 5. Not being afraid to add comments of your own.

In this episode of the DevEd podcast, Brooke and Preston mainly talk about Netlify, JAMStack (JavaScript, APIs, and Markup) and Preston's new course - Deploying Apps to Netlify. Preston starts with explaining what JAMStack is, why is it popular right now and it's numerous benefits. He talks about the difference between single-page applications and JAM, and how Netlify comes into the whole picture. He answers questions on how to do authentication with Netlify, what is CMS (content management system) in the context of JAMStack, CMS alternatives to Netlify, how Netlify handles dynamic data, serverless functions, Netlify pricing, possible substitutes for it and finally what makes it stand out from the others. He then talks about what made him choose Netlify as the topic for his course, the authoring process, what the course is all about, and why should developers resort to the courses on Thinkster.io in general. Panel Brooke Avery Preston Lamb Sponsors Thinkster.io Links Deploying Apps to Netlify The DevEd podcast is produced by Thinkster.io and published by DevChat.TV.

In this episode of the DevEd podcast, Brooke and Preston mainly talk about Netlify, JAMStack (JavaScript, APIs, and Markup) and Preston's new course - Deploying Apps to Netlify. Preston starts with explaining what JAMStack is, why is it popular right now and it's numerous benefits. He talks about the difference between single-page applications and JAM, and how Netlify comes into the whole picture. He answers questions on how to do authentication with Netlify, what is CMS (content management system) in the context of JAMStack, CMS alternatives to Netlify, how Netlify handles dynamic data, serverless functions, Netlify pricing, possible substitutes for it and finally what makes it stand out from the others. He then talks about what made him choose Netlify as the topic for his course, the authoring process, what the course is all about, and why should developers resort to the courses on Thinkster.io in general. Panel Brooke Avery Preston Lamb Sponsors Thinkster.io Links Deploying Apps to Netlify The DevEd podcast is produced by Thinkster.io and published by DevChat.TV.

This week's episode of the DevEd podcast is joined by Hudson Baker. Hudson has been a developer for five years now, specializing in Angular, and is currently working at BrieBug Software. The panel kickstarts the episode by answering the basic question - What is Gatsby? Sam explains that it is a static site generator which means that it takes in data and converts that into static files that can be hosted on any server. It has a lot of tooling and build process stuff built-in, and uses modern javascript concepts along with GraphQL to build fast-performance static sites. It is also a part of JAMStack. Speaking on what languages and technologies it is based on, Sam elaborates that Gatsby is built with React, the build process is webpack, the content can be written in markdown or any outside sources, and data querying is done using GraphQL. The next topic of discussion is static sites. They talk at length about what static sites are, if they can be written without a static site generator, the difference between Gatsby and other frameworks such as Angular and React, what makes the sites static, how to identify them, and how to make a clear distinction between static and dynamic sites. Next, they discuss that Gatsby can be a good starting point for people interested in learning React because it has a plethora of cool inbuilt tools, plugins and pre-packaged templates which can make the learning process easier, rather than starting to learn React from scratch. From a teaching perspective, React is a better choice if the goal is to teach web applications, whereas Gatsby is good for teaching how to build websites. They talk about the difference between Gatsby and server-side rendering frameworks such as Next.js. Luis explains that in server-side rendering, there is data on one side and template on the other, and each time a request is made to the server, the data and template are assembled on the fly and not at build time. On the contrary, in case of Gatsby, this is done at build time, so everything that is sent from the server is basically pre-calculated. Talking about performance considerations, he says that in server-side rendering there is a price to pay in terms of just-in-time calculations. Sam also chimes in with his views on the comparison and mentions that they are really close performance-wise and feature-wise. They then move on to discussing the learning aspect of Gatsby. Sam explains that if developers possess some knowledge about things like React, GraphQL, CSS in JS, etc., it can be easy to get fast results with Gatsby, however, it is still possible to secure some quick wins by using a simple starter project as a template and building on it. He then talks about the best use of Gatsby being in content-based sites, portfolios, product sales pages and so on. Joe asks how does Gatsby deal with adding other aspects on top of it, to which Sam answers that there may be some tweaking needed to get things done, but overall it works well given that there are a ton of plugins available to get things from external resources. Joe talks about learning GraphQL, and Sam explains how much of it is used in Gatsby. He talks about the positives of Gatsby documentation and the developer community. They end the show with picks. The DevEd podcast is produced by Thinkster.io and published by DevChat.TV. Panel Joe Eames Brooke Avery Sam Julien Jesse Sanders Mike Dane Luis Hernandez Joined by special guest: Hudson Baker Sponsors Thinkster.io Adventures in .NET - Devchat.tv Elixir Mix CacheFly Links Hudson's Twitter Comparison of Gatsby vs Next.js Picks Luis Hernandez: Focused and Diffuse: Two Modes of Thinking Mike Dane: Splitwise Jesse Sanders: Grumpy Cat :( DuckDuckGo Hudson Baker: Storybook Keep Talking and Nobody Explodes Brooke Avery: Star Wars Pinball Sam Julien: Overcooked! Joe Eames: Claudia.js   What is Gatsby? It is a static site generator that takes in data and converts it into static files that can be hosted on any server. It has a lot of tooling and build process stuff built-in, and uses modern javascript concepts along with GraphQL to build fast-performance static sites. What languages and technologies is Gatsby based on? Gatsby is built with React, the build process is webpack, the content can be written in markdown or any outside sources, and data querying is done with GraphQL. What is the difference between Gatsby and server-side rendering frameworks such as Next.js? In server-side rendering, there is data on one side and template on the other, and each time a request is made to the server, the data and template are assembled on the fly and not at build time. On the contrary, in case of Gatsby, this is done at build time, so everything that is sent from the server is pre-calculated. How does Gatsby deal with adding extra aspects on top of the basic functionality? There may be some tweaking required to get things done, but overall it works well given that there are a ton of plugins available to get things from external resources.

This week's episode of the DevEd podcast is joined by Hudson Baker. Hudson has been a developer for five years now, specializing in Angular, and is currently working at BrieBug Software. The panel kickstarts the episode by answering the basic question - What is Gatsby? Sam explains that it is a static site generator which means that it takes in data and converts that into static files that can be hosted on any server. It has a lot of tooling and build process stuff built-in, and uses modern javascript concepts along with GraphQL to build fast-performance static sites. It is also a part of JAMStack. Speaking on what languages and technologies it is based on, Sam elaborates that Gatsby is built with React, the build process is webpack, the content can be written in markdown or any outside sources, and data querying is done using GraphQL. The next topic of discussion is static sites. They talk at length about what static sites are, if they can be written without a static site generator, the difference between Gatsby and other frameworks such as Angular and React, what makes the sites static, how to identify them, and how to make a clear distinction between static and dynamic sites. Next, they discuss that Gatsby can be a good starting point for people interested in learning React because it has a plethora of cool inbuilt tools, plugins and pre-packaged templates which can make the learning process easier, rather than starting to learn React from scratch. From a teaching perspective, React is a better choice if the goal is to teach web applications, whereas Gatsby is good for teaching how to build websites. They talk about the difference between Gatsby and server-side rendering frameworks such as Next.js. Luis explains that in server-side rendering, there is data on one side and template on the other, and each time a request is made to the server, the data and template are assembled on the fly and not at build time. On the contrary, in case of Gatsby, this is done at build time, so everything that is sent from the server is basically pre-calculated. Talking about performance considerations, he says that in server-side rendering there is a price to pay in terms of just-in-time calculations. Sam also chimes in with his views on the comparison and mentions that they are really close performance-wise and feature-wise. They then move on to discussing the learning aspect of Gatsby. Sam explains that if developers possess some knowledge about things like React, GraphQL, CSS in JS, etc., it can be easy to get fast results with Gatsby, however, it is still possible to secure some quick wins by using a simple starter project as a template and building on it. He then talks about the best use of Gatsby being in content-based sites, portfolios, product sales pages and so on. Joe asks how does Gatsby deal with adding other aspects on top of it, to which Sam answers that there may be some tweaking needed to get things done, but overall it works well given that there are a ton of plugins available to get things from external resources. Joe talks about learning GraphQL, and Sam explains how much of it is used in Gatsby. He talks about the positives of Gatsby documentation and the developer community. They end the show with picks. The DevEd podcast is produced by Thinkster.io and published by DevChat.TV. Panel Joe Eames Brooke Avery Sam Julien Jesse Sanders Mike Dane Luis Hernandez Joined by special guest: Hudson Baker Sponsors Thinkster.io Adventures in .NET - Devchat.tv Elixir Mix CacheFly Links Hudson's Twitter Comparison of Gatsby vs Next.js Picks Luis Hernandez: Focused and Diffuse: Two Modes of Thinking Mike Dane: Splitwise Jesse Sanders: Grumpy Cat :( DuckDuckGo Hudson Baker: Storybook Keep Talking and Nobody Explodes Brooke Avery: Star Wars Pinball Sam Julien: Overcooked! Joe Eames: Claudia.js   What is Gatsby? It is a static site generator that takes in data and converts it into static files that can be hosted on any server. It has a lot of tooling and build process stuff built-in, and uses modern javascript concepts along with GraphQL to build fast-performance static sites. What languages and technologies is Gatsby based on? Gatsby is built with React, the build process is webpack, the content can be written in markdown or any outside sources, and data querying is done with GraphQL. What is the difference between Gatsby and server-side rendering frameworks such as Next.js? In server-side rendering, there is data on one side and template on the other, and each time a request is made to the server, the data and template are assembled on the fly and not at build time. On the contrary, in case of Gatsby, this is done at build time, so everything that is sent from the server is pre-calculated. How does Gatsby deal with adding extra aspects on top of the basic functionality? There may be some tweaking required to get things done, but overall it works well given that there are a ton of plugins available to get things from external resources.

In this week's episode of the DevEd podcast, the panelists talk to Tara Z. Manicsic. Tara is an Angular Developer Experience Engineer at Netlify, a blogger, and loves to work in her community educating and learning from other developers. The topic for this episode is work-life balance with an emphasis on balancing learning as a programmer. The first thing they discuss is if programmers are good at balancing work-life. The general consensus is that they aren't, but mostly because they love their job, and it is also always fun to learn newer technologies and concepts. They talk about hackations and coding in beautiful environments away from their regular desks. They talk about some strategies to maintain a good work-life balance especially in high-pressure scenarios where the work seems to never get over. They suggest time management, blocking off hours and segregating them into strictly work and non-work periods. Tara mentions working non-traditional hours while having an infant at home, while Brooke explains how to schedule things beforehand so that knowing the tasks ahead of time helps in managing them effectively. Others chip in with their suggestions as well. Tara also speaks on the importance of having a good manager with realistic expectations. They then touch on work-life balance from the perspective of managers too, where they advise them to make sure that their employees work reasonable hours, check in with them regularly and encourage them to take personal time off for their own mental health. They share their experiences related to death marches and the stress associated with it. They mention that while working as a junior developer in a high pressure environment that is hard to keep up with, it can be hard to change jobs. To deal with these kind of situations, they talk about how important it is to like the work being done, and if it is not something enjoyable, it is time to start looking for something completely different or take some time to unwind. Trying to do interesting things such as reading books, listening to music or podcasts at work during lunchtime, or while commuting, can also help in thriving in such environments. The next point discussed is how to deal with the need to learn along with working at a regular job and still manage to maintain a balance. Consuming relevant content in the background while going about our day-to-day chores, not underestimating the learning done on the job, carving out time for self development during work hours, writing regular blog posts of things learned which can eventually lead to an awesome portfolio, are some great recommendations. The last thing the panelists talk about is organizational tools for an awesome work-learn-life balance. They suggest Toggle, Asana, OmniFocus and Calendar. Luis mentions that given that we are constantly bombarded with information, it can be beneficial to sift through that, remove the unnecessary noise and concentrate on what is needed to free up significant amount of time. Joe recommends using a bullet journal, being physical and tactile while organising rather than digital, and Mike suggests switching the airplane mode on, among other things. Tara and Sam talk about meditation and mindfulness. They end the show with picks. The Dev Ed podcast is produced by Thinkster.io and published by DevChat.TV. Panel Joe Eames Brooke Avery Sam Julien Luis Hernandez Mike Dane Joined by special guest: Tara Z. Manicsic Sponsors Thinkster.io Adventures in DevOps - Devchat.tv The Freelancers Show CacheFly Links Tara's Twitter Picks Joe Eames: Beginner's Guide to Bullet Journaling | How to Start a Bullet Journal Boho Berry Bullet Journal introduction Tara Z. Manicsic: Check out the local children's museums JAMstack conf Mike Dane: LingQ Brooke Avery: Sporcle Star Wars Myths & Fables Luis Hernandez: Rework Getting Things Done Sam Julien: The Great British Bake Off How to maintain a great work-life balance, as an employee? Good time management, blocking off hours and segregating them into strictly work and non-work periods, scheduling tasks ahead of time. How to maintain a great work-life balance, as a manager? Making sure that employees work reasonable hours, checking in with them regularly and encouraging them to take personal time off for their own mental health. How to maintain a great work-learn-life balance? Consuming relevant content in the background while going about our day-to-day chores, not underestimating the learning done on the job, carving out time for self development during work hours, writing blog posts of things learned eventually leading to an awesome portfolio. What are some organizational tools to maintain work-life balance? Toggle, Asana, OmniFocus, Calendar, Bullet journals, Meditation

In this week's episode of the DevEd podcast, the panelists talk to Tara Z. Manicsic. Tara is an Angular Developer Experience Engineer at Netlify, a blogger, and loves to work in her community educating and learning from other developers. The topic for this episode is work-life balance with an emphasis on balancing learning as a programmer. The first thing they discuss is if programmers are good at balancing work-life. The general consensus is that they aren't, but mostly because they love their job, and it is also always fun to learn newer technologies and concepts. They talk about hackations and coding in beautiful environments away from their regular desks. They talk about some strategies to maintain a good work-life balance especially in high-pressure scenarios where the work seems to never get over. They suggest time management, blocking off hours and segregating them into strictly work and non-work periods. Tara mentions working non-traditional hours while having an infant at home, while Brooke explains how to schedule things beforehand so that knowing the tasks ahead of time helps in managing them effectively. Others chip in with their suggestions as well. Tara also speaks on the importance of having a good manager with realistic expectations. They then touch on work-life balance from the perspective of managers too, where they advise them to make sure that their employees work reasonable hours, check in with them regularly and encourage them to take personal time off for their own mental health. They share their experiences related to death marches and the stress associated with it. They mention that while working as a junior developer in a high pressure environment that is hard to keep up with, it can be hard to change jobs. To deal with these kind of situations, they talk about how important it is to like the work being done, and if it is not something enjoyable, it is time to start looking for something completely different or take some time to unwind. Trying to do interesting things such as reading books, listening to music or podcasts at work during lunchtime, or while commuting, can also help in thriving in such environments. The next point discussed is how to deal with the need to learn along with working at a regular job and still manage to maintain a balance. Consuming relevant content in the background while going about our day-to-day chores, not underestimating the learning done on the job, carving out time for self development during work hours, writing regular blog posts of things learned which can eventually lead to an awesome portfolio, are some great recommendations. The last thing the panelists talk about is organizational tools for an awesome work-learn-life balance. They suggest Toggle, Asana, OmniFocus and Calendar. Luis mentions that given that we are constantly bombarded with information, it can be beneficial to sift through that, remove the unnecessary noise and concentrate on what is needed to free up significant amount of time. Joe recommends using a bullet journal, being physical and tactile while organising rather than digital, and Mike suggests switching the airplane mode on, among other things. Tara and Sam talk about meditation and mindfulness. They end the show with picks. The Dev Ed podcast is produced by Thinkster.io and published by DevChat.TV. Panel Joe Eames Brooke Avery Sam Julien Luis Hernandez Mike Dane Joined by special guest: Tara Z. Manicsic Sponsors Thinkster.io Adventures in DevOps - Devchat.tv The Freelancers Show CacheFly Links Tara's Twitter Picks Joe Eames: Beginner's Guide to Bullet Journaling | How to Start a Bullet Journal Boho Berry Bullet Journal introduction Tara Z. Manicsic: Check out the local children's museums JAMstack conf Mike Dane: LingQ Brooke Avery: Sporcle Star Wars Myths & Fables Luis Hernandez: Rework Getting Things Done Sam Julien: The Great British Bake Off How to maintain a great work-life balance, as an employee? Good time management, blocking off hours and segregating them into strictly work and non-work periods, scheduling tasks ahead of time. How to maintain a great work-life balance, as a manager? Making sure that employees work reasonable hours, checking in with them regularly and encouraging them to take personal time off for their own mental health. How to maintain a great work-learn-life balance? Consuming relevant content in the background while going about our day-to-day chores, not underestimating the learning done on the job, carving out time for self development during work hours, writing blog posts of things learned eventually leading to an awesome portfolio. What are some organizational tools to maintain work-life balance? Toggle, Asana, OmniFocus, Calendar, Bullet journals, Meditation

Dillon Kearns is an Elm consultant who provides coaching and training to help people accelerate the way they write Elm to keep their codebases maintainable as they grow. He's the author of elm-graphql, and recently announced a new static site framework, elm-pages. Today the panel is discussing how building libraries and frameworks can aide with the learning process. Dillon talks about how building frameworks and working with languages has helped him. He uses them as a laboratory to learn new techniques. When working on a library or framework, he always tries to bring his best programming self to that project.He believes that libraries and frameworks are a low risk way to practice your skills because they’re unlikely to get adopted when you’re starting out. The panel defines what libraries and frameworks are and how they differ from one another. Libraries and frameworks are a type of project, with a library solving a specific class of problems. A framework is plugable and can be extended to solve problems that a framework author may not have imagined, though it does a set of core things. A library is something you put into your existing code base, a framework is the core you’re building on top of. They talk about an article, The Difference Between a Library and a Framework, that compares a library to a trip to Ikea when you already have a home, but you need to fill it with furniture, and a framework to building a home.  Next they talk about how libraries and frameworks are built and who builds them. Both are often built in open source, and some are funded by big companies while some are passion projects. They talk about the libraries that they’ve created and how it helped them to become a better developer. When Preston Lamb builds libraries, he learns how to do things he’s never done before. He doesn’t have a huge user base, but he finds it fun to sit down and have an idea, figure out how to do it, and make it reusable. Jesse Sanders talks about the company Rebug, and how somebody gave him the idea to write it as a schematic. Making libraries and frameworks is a continual way for developers to take a look at situations they don’t come across a lot and put them in a different mindset to make things truly reusable so that it can be adopted by others in the community. Dillon has found that making Elm GraphQL has given him the chance to be involved in very interesting conversations in the community. Creating a library or framework gives you the opportunity to be considered an expert in something and see they types of questions people are asking, problems they’re solving, and their interesting approaches. The panel talks about the difference between fluency and understanding, and agree that one of the best ways to learn is by teaching. By being involved in creating a library, you’re seen as an expert in that library, so people come to you with their questions and you have to figure out how to answer them. One of the most valuable things about building a library or framework is learning the core basic concepts of the language.  They agree that it is best to start this kind of project as soon as you find something that interests you, and assure listeners that even if you mess it up and it’s never used, the learning experience is the true value. Often times, you’ll surprise yourself and make something that’s actually useful. Building or contributing to frameworks takes away the mystery and magic of programming, makes problems seem more approachable, and helps you understand the fundamentals. To find a project to contribute to, they suggest checking Twitter, Slack channels, and Github. If you find a library you like on Github, they’ll often have a #goodfirstissue, and you can tackle that problem to get started. Listeners are encouraged to be curious and look up source code on Github if you ever have a question to see how different libraries tackle this problem.  Finally, they talk about how to decide what requires a small exercise and what requires a library or framework. If the goal is short term, it only requires a small focused exercise. If the goal is long term or you find yourself doing the same thing repeatedly, consider a library or framework to make that code reusable and publishing it for others to use. Their closing thoughts are don’t focus on making something popular, just make something useful to you and maybe someone else will find it useful, and a reminder that there’s something to learn from everybody. Always have an open mind and try to get clarity on what someone is saying, even if it sounds like a bad idea at first. Panelists Brooke Avery Jesse Sanders Preston Lamb Sam Julien Mike Dane Luis Hernandez With special guest: Dillon Kearns Sponsors Thinkster.io Sustain Our Software React Native Radio Links Elm The Difference Between a Framework and a Library Angular Elm GraphQL Follow DevChatTV on Facebook and Twitter Picks Dillon Kearns: Non-Violent Communication: A Language of Life by Marshall B. Rosenberg Incremental Elm Consulting Follow Dillon on Twitter, LinkedIn, and Medium Preston Lamb: One Second Every Day Jessie Sanders: Crashlands Mike Dane: FUNCL bluetooth headphones Luis Hernandez: Svelte framework Brooke Avery: Star Wars Drones (check Costco first)

Dillon Kearns is an Elm consultant who provides coaching and training to help people accelerate the way they write Elm to keep their codebases maintainable as they grow. He's the author of elm-graphql, and recently announced a new static site framework, elm-pages. Today the panel is discussing how building libraries and frameworks can aide with the learning process. Dillon talks about how building frameworks and working with languages has helped him. He uses them as a laboratory to learn new techniques. When working on a library or framework, he always tries to bring his best programming self to that project.He believes that libraries and frameworks are a low risk way to practice your skills because they’re unlikely to get adopted when you’re starting out. The panel defines what libraries and frameworks are and how they differ from one another. Libraries and frameworks are a type of project, with a library solving a specific class of problems. A framework is plugable and can be extended to solve problems that a framework author may not have imagined, though it does a set of core things. A library is something you put into your existing code base, a framework is the core you’re building on top of. They talk about an article, The Difference Between a Library and a Framework, that compares a library to a trip to Ikea when you already have a home, but you need to fill it with furniture, and a framework to building a home.  Next they talk about how libraries and frameworks are built and who builds them. Both are often built in open source, and some are funded by big companies while some are passion projects. They talk about the libraries that they’ve created and how it helped them to become a better developer. When Preston Lamb builds libraries, he learns how to do things he’s never done before. He doesn’t have a huge user base, but he finds it fun to sit down and have an idea, figure out how to do it, and make it reusable. Jesse Sanders talks about the company Rebug, and how somebody gave him the idea to write it as a schematic. Making libraries and frameworks is a continual way for developers to take a look at situations they don’t come across a lot and put them in a different mindset to make things truly reusable so that it can be adopted by others in the community. Dillon has found that making Elm GraphQL has given him the chance to be involved in very interesting conversations in the community. Creating a library or framework gives you the opportunity to be considered an expert in something and see they types of questions people are asking, problems they’re solving, and their interesting approaches. The panel talks about the difference between fluency and understanding, and agree that one of the best ways to learn is by teaching. By being involved in creating a library, you’re seen as an expert in that library, so people come to you with their questions and you have to figure out how to answer them. One of the most valuable things about building a library or framework is learning the core basic concepts of the language.  They agree that it is best to start this kind of project as soon as you find something that interests you, and assure listeners that even if you mess it up and it’s never used, the learning experience is the true value. Often times, you’ll surprise yourself and make something that’s actually useful. Building or contributing to frameworks takes away the mystery and magic of programming, makes problems seem more approachable, and helps you understand the fundamentals. To find a project to contribute to, they suggest checking Twitter, Slack channels, and Github. If you find a library you like on Github, they’ll often have a #goodfirstissue, and you can tackle that problem to get started. Listeners are encouraged to be curious and look up source code on Github if you ever have a question to see how different libraries tackle this problem.  Finally, they talk about how to decide what requires a small exercise and what requires a library or framework. If the goal is short term, it only requires a small focused exercise. If the goal is long term or you find yourself doing the same thing repeatedly, consider a library or framework to make that code reusable and publishing it for others to use. Their closing thoughts are don’t focus on making something popular, just make something useful to you and maybe someone else will find it useful, and a reminder that there’s something to learn from everybody. Always have an open mind and try to get clarity on what someone is saying, even if it sounds like a bad idea at first. Panelists Brooke Avery Jesse Sanders Preston Lamb Sam Julien Mike Dane Luis Hernandez With special guest: Dillon Kearns Sponsors Thinkster.io Sustain Our Software React Native Radio Links Elm The Difference Between a Framework and a Library Angular Elm GraphQL Follow DevChatTV on Facebook and Twitter Picks Dillon Kearns: Non-Violent Communication: A Language of Life by Marshall B. Rosenberg Incremental Elm Consulting Follow Dillon on Twitter, LinkedIn, and Medium Preston Lamb: One Second Every Day Jessie Sanders: Crashlands Mike Dane: FUNCL bluetooth headphones Luis Hernandez: Svelte framework Brooke Avery: Star Wars Drones (check Costco first)

Today’s episode of the Dev Ed podcast is joined by Tyler Legget, a structural engineering major working in the construction field primarily, and also on a number of side projects including property development, designing and building homes, co-founder of a company that made software for cycling race management. He also worked as a Product Manager on a platform that managed complex inventory of wood products. He then got involved in ng-conf, which spawned into an event management company called Zero Slope Events which he manages currently. Zero Slope Events provides event planning for conferences such as ng-conf, React conf and so on. After listening to Tyler’s diverse background where coding had been only a partial activity, Joe asks what made him not go into full-fledged software development. Tyler answers that while he enjoyed different aspects and the variety of it, he never felt like making a career out of it. To determine if software development may not be a good career, it needs to be tried first, one has to see if it fits their skillset and work ethic. The panelists also share that it is very important to enjoy the task at hand, be able to fully immerse into the work and not keep waiting for the day to get over. Even though the public notion is that developers get paid really well, salary should not be the only criteria for a career switch, it is basically like setting yourself up for a lifelong disappointment or even failure. The good news, however, is that you can always go back to what you were doing if you do not enjoy it. Job shadowing is a good idea to closely see the day-to-day workings of the job and make an informed decision. They then discuss if there are any situations where programming languages have proved to be extremely beneficial to the job. They give examples of Microsoft Excel, Microsoft Access where they were able to do awesome things and automate stuff, which piqued their interest in programming in general, and was also helpful to other team members as well, which can eventually foray into development. Teaching can also lead up to becoming a developer, through situations such as involving the search for good materials. Problem-solving is a great way to get into it as well, as are hobbies involving building or customizing things. The panelists discuss tools that help in programming, automate or organizing things while working. They recommend some great ones like the Office suite, Glitch, CMS systems, Webflow, If This Then That (IFTTT), Zapier, StackBlitz, Google docs, YouTube, Airtable and Stack Overflow. They then move onto talking about techniques to help out developers when they get stuck on something on the job and there is no one to turn to, during which they suggest a basic google search, YouTube videos, Stack Overflow, and Twitter channels. When trying to get better at programming, not just for fun but in a task-focused manner, some effective resources can be reading books including but not limited to the Dummies series, YouTube tutorials and Meetup groups. Speaking on finding platforms to work with custom applications, Shopify, WordPress, Google pages, can be of great help if working on your own. As the applications get more complex, it can be advantageous to hire a professional. Finally, in terms of hiring expenses, do not compromise on quality, make sure the requirements are clear and really know what the person can offer. Panel Joe Eames Brooke Avery Jesse Sanders Preston Lamb Luis Hernandez Joined by special guest: Tyler Leggett Sponsors Thinkster.io Adventures in .NET - Devchat.tv Adventures in Angular - Devchat.tv CacheFly Links Zero Slope Events Glitch Webflow IFTTT Zapier StackBlitz Airtable Stack Overflow Picks Jesse Sanders: Nebo Preston Lamb: Our Fake History podcast Luis Hernandez: unDraw Brooke Avery: Webflow Star Wars: Galaxy Edge - Disney Parks Tyler Leggett: Reply All

Today’s episode of the Dev Ed podcast is joined by Tyler Legget, a structural engineering major working in the construction field primarily, and also on a number of side projects including property development, designing and building homes, co-founder of a company that made software for cycling race management. He also worked as a Product Manager on a platform that managed complex inventory of wood products. He then got involved in ng-conf, which spawned into an event management company called Zero Slope Events which he manages currently. Zero Slope Events provides event planning for conferences such as ng-conf, React conf and so on. After listening to Tyler’s diverse background where coding had been only a partial activity, Joe asks what made him not go into full-fledged software development. Tyler answers that while he enjoyed different aspects and the variety of it, he never felt like making a career out of it. To determine if software development may not be a good career, it needs to be tried first, one has to see if it fits their skillset and work ethic. The panelists also share that it is very important to enjoy the task at hand, be able to fully immerse into the work and not keep waiting for the day to get over. Even though the public notion is that developers get paid really well, salary should not be the only criteria for a career switch, it is basically like setting yourself up for a lifelong disappointment or even failure. The good news, however, is that you can always go back to what you were doing if you do not enjoy it. Job shadowing is a good idea to closely see the day-to-day workings of the job and make an informed decision. They then discuss if there are any situations where programming languages have proved to be extremely beneficial to the job. They give examples of Microsoft Excel, Microsoft Access where they were able to do awesome things and automate stuff, which piqued their interest in programming in general, and was also helpful to other team members as well, which can eventually foray into development. Teaching can also lead up to becoming a developer, through situations such as involving the search for good materials. Problem-solving is a great way to get into it as well, as are hobbies involving building or customizing things. The panelists discuss tools that help in programming, automate or organizing things while working. They recommend some great ones like the Office suite, Glitch, CMS systems, Webflow, If This Then That (IFTTT), Zapier, StackBlitz, Google docs, YouTube, Airtable and Stack Overflow. They then move onto talking about techniques to help out developers when they get stuck on something on the job and there is no one to turn to, during which they suggest a basic google search, YouTube videos, Stack Overflow, and Twitter channels. When trying to get better at programming, not just for fun but in a task-focused manner, some effective resources can be reading books including but not limited to the Dummies series, YouTube tutorials and Meetup groups. Speaking on finding platforms to work with custom applications, Shopify, WordPress, Google pages, can be of great help if working on your own. As the applications get more complex, it can be advantageous to hire a professional. Finally, in terms of hiring expenses, do not compromise on quality, make sure the requirements are clear and really know what the person can offer. Panel Joe Eames Brooke Avery Jesse Sanders Preston Lamb Luis Hernandez Joined by special guest: Tyler Leggett Sponsors Thinkster.io Adventures in .NET - Devchat.tv Adventures in Angular - Devchat.tv CacheFly Links Zero Slope Events Glitch Webflow IFTTT Zapier StackBlitz Airtable Stack Overflow Picks Jesse Sanders: Nebo Preston Lamb: Our Fake History podcast Luis Hernandez: unDraw Brooke Avery: Webflow Star Wars: Galaxy Edge - Disney Parks Tyler Leggett: Reply All

In this episode of the Dev Ed podcast, the panelists talk to Joe Skeen. Joe is a Developer and a Mentor, who started tinkering with computers since childhood and later taught himself web languages. After getting into University, he started working with strongly typed languages as well. He gives a brief background of himself and his work and shares his Angular journey. The panel discusses the most effective steps involved in mentoring a brand new developer who is just starting out. The first thing that can be done is to hone any skills the developers already possess through their previous line of work or education so as to ensure a smooth transition into a new environment. Another idea is giving them relevant and meaningful things to practice which are needed for the job or the project rather than something vague or generic. They need to feel motivated and connected to the things they are learning. Another piece of advice is, as a mentor, make sure to be there for them, keep the commitment strong, don’t leave things unfinished and do not quit in the middle. As they are putting in a lot of effort into being a good developer, it is very important that the mentor puts in consistent effort as well. Give them constructive feedback. Practicing is the best way to learn something extremely well. Building apps and personal projects is a great way to put things into practice, leading to more and more learning in the process, so recommending beginner developers to create something based on the theoretical knowledge gained can be an effective suggestion. From the beginning, bringing them to meetings even though things are going above their head, keeping them actively involved thereby creating a feeling of belonging and being included, and making sure that they are aware that the team works interdependently, are crucial to boosting their motivation and self-confidence as well. They then discuss the differences between mentoring someone in a work environment versus mentoring a friend. In the professional sense, there tends to be more motivation since they are getting paid for learning or doing the job. But on a personal level, this gets harder as it is easy to give up and thus the responsibility of continuing falls on the mentors. Pair programming is a great technique to understand things through the process of working with someone. In the context of dealing with people who carry the attitude that they know more than the mentors, the panelists state that there is no need for mentoring as it simply cannot be done. It is important to have a conversation to make things clear and understand what is required from everyone involved. It helps to get to know the person better in this case, and respect and humility should be both ways. Making them comfortable, having open discussions on any mistakes and failures faced along the way, removing embarrassment around these topics and stressing on the fact that it is ok to not know something, giving them opportunities to share what they have learned before, are some of the remedial actions that can be taken while dealing with seemingly difficult individuals. Shedding light on the other side of things, they talk about dealing with developers who feel discouraged and helpless given that they are new to the workplace and everyone else seems to know more than them. They discuss giving them confidence so that they are capable of handling stuff on their own, accepting them as major contributors from the get-go, believing in them, repeating things if they don’t understand something, making sure to not overwhelm them, and giving positive feedback and achievable goals, making yourself vulnerable to them so that they can relate to it. The bottom line is no one is an expert and everyone is learning just like them. While talking about dealing with developers who write bad code, panelists mention pair programming, learning how to do things the right way from industry experts, teaching by example, having formal code reviews, and maintaining a balance between criticism and appreciation. They end the show on the note that the relationship between the mentor and mentee is the most important part of mentoring. Panel Joe Eames Brooke Avery Luis Hernandez Joined by special guest: Joe Skeen Sponsors Thinkster.io Adventures in DevOps - Devchat.tv My Angular Story - Devchat.tv CacheFly Links Joe’s Twitter Joe on Medium Picks Luis Hernandez: The Pragmatic Programmer, 20th Anniversary Edition Brooke Avery: Magic Jigsaw Puzzles Joe Eames: Netlify Deploying Apps to Netlify Joe Skeen: Dominion Companion Dominion Companion Randomizer

In this episode of the Dev Ed podcast, the panelists talk to Joe Skeen. Joe is a Developer and a Mentor, who started tinkering with computers since childhood and later taught himself web languages. After getting into University, he started working with strongly typed languages as well. He gives a brief background of himself and his work and shares his Angular journey. The panel discusses the most effective steps involved in mentoring a brand new developer who is just starting out. The first thing that can be done is to hone any skills the developers already possess through their previous line of work or education so as to ensure a smooth transition into a new environment. Another idea is giving them relevant and meaningful things to practice which are needed for the job or the project rather than something vague or generic. They need to feel motivated and connected to the things they are learning. Another piece of advice is, as a mentor, make sure to be there for them, keep the commitment strong, don’t leave things unfinished and do not quit in the middle. As they are putting in a lot of effort into being a good developer, it is very important that the mentor puts in consistent effort as well. Give them constructive feedback. Practicing is the best way to learn something extremely well. Building apps and personal projects is a great way to put things into practice, leading to more and more learning in the process, so recommending beginner developers to create something based on the theoretical knowledge gained can be an effective suggestion. From the beginning, bringing them to meetings even though things are going above their head, keeping them actively involved thereby creating a feeling of belonging and being included, and making sure that they are aware that the team works interdependently, are crucial to boosting their motivation and self-confidence as well. They then discuss the differences between mentoring someone in a work environment versus mentoring a friend. In the professional sense, there tends to be more motivation since they are getting paid for learning or doing the job. But on a personal level, this gets harder as it is easy to give up and thus the responsibility of continuing falls on the mentors. Pair programming is a great technique to understand things through the process of working with someone. In the context of dealing with people who carry the attitude that they know more than the mentors, the panelists state that there is no need for mentoring as it simply cannot be done. It is important to have a conversation to make things clear and understand what is required from everyone involved. It helps to get to know the person better in this case, and respect and humility should be both ways. Making them comfortable, having open discussions on any mistakes and failures faced along the way, removing embarrassment around these topics and stressing on the fact that it is ok to not know something, giving them opportunities to share what they have learned before, are some of the remedial actions that can be taken while dealing with seemingly difficult individuals. Shedding light on the other side of things, they talk about dealing with developers who feel discouraged and helpless given that they are new to the workplace and everyone else seems to know more than them. They discuss giving them confidence so that they are capable of handling stuff on their own, accepting them as major contributors from the get-go, believing in them, repeating things if they don’t understand something, making sure to not overwhelm them, and giving positive feedback and achievable goals, making yourself vulnerable to them so that they can relate to it. The bottom line is no one is an expert and everyone is learning just like them. While talking about dealing with developers who write bad code, panelists mention pair programming, learning how to do things the right way from industry experts, teaching by example, having formal code reviews, and maintaining a balance between criticism and appreciation. They end the show on the note that the relationship between the mentor and mentee is the most important part of mentoring. Panel Joe Eames Brooke Avery Luis Hernandez Joined by special guest: Joe Skeen Sponsors Thinkster.io Adventures in DevOps - Devchat.tv My Angular Story - Devchat.tv CacheFly Links Joe’s Twitter Joe on Medium Picks Luis Hernandez: The Pragmatic Programmer, 20th Anniversary Edition Brooke Avery: Magic Jigsaw Puzzles Joe Eames: Netlify Deploying Apps to Netlify Joe Skeen: Dominion Companion Dominion Companion Randomizer

Episode Summary In this episode of the Dev Ed podcast, the panelists talk to Nell Shamrell-Harrington, Principal Engineer at Chef Software. Nell introduces herself and gives a brief background about her software development journey so far and talks about how she started working with DevOps. She is also a co-host of the Adventures in DevOps podcast on Devchat.tv. The meaning of the term DevOps can be quite cloudy, so before discussing learning DevOps, they talk about what it actually means and how it differs from traditional development. Nell breaks down the term and describes in detail the approach of merging developers and operational professionals. Joe highlights the cultural aspect of DevOps and how it plays into the way of working. Nell explains the right way of organizing teams, the internal interactions among them, accountability, and some of the dos and don'ts involved. Other panelists chime in with their views on the DevOps culture as well. They discuss the best practices, challenges faced, eliminating silo and sharing responsibility. They tackle the question of how to encourage seamless communication among teams and avoid conflicts. Nell explains that what works well in these cases instead of getting everyone together leading to chaos and blame games, is selecting representatives from both development and operations and ironing out the miscommunication. The next topic of discussion is why should a beginner developer care about DevOps at all. As applications become more complex, the need arises to think about their underlying infrastructure in order to optimize them and it is beneficial to have an idea of where they might be deployed. As a developer progresses from the beginning stages to advanced ones, it is natural to know about the deployment environment, data centres, and DevOps concepts in general. Due to advancements in technology, these areas have become very accessible as well. They steer the discussion towards what parts of DevOps should one focus on while getting started, given that there are a plethora of tools and technologies involved. Nell advises listeners to pick any major cloud provider and learn the basics by working with it, which can later be applied to any other cloud provider. She also recommends learning programming languages to get a good software development foundation. Sam shares his own experience with Digital Ocean and highly recommends their learning materials. Mike and Jesse suggest understanding how Continuous Integration works and mention that it is a great starting point. Mike points out that knowing that there are multiple environments at play - staging, production, testing and so on, helps a great deal. Speaking about Docker, Nell says that while it is an amazing technology which made containers extremely usable on a large scale, it is not a good idea to run the entire infrastructure on just containers, given that containers can be very ephemeral and there is a risk of losing data. For learning purposes though, she recommends Docker as it runs well on local environments. She explains what Chef is and the difference between Docker and Chef. The panelists then describe what Netlify is, how it works, and how good it is from the learning perspective. They then talk about some great resources for beginners to start with, Nell recommends Kubernetes, and explains what it means to orchestrate containers. Sam talks about Bruno Krebs' Kubernetes tutorial and Thinkster's Docker courses as awesome learning materials. They end the show with picks. Panel Joe Eames Sam Julien Jesse Sanders Luis Hernandez Mike Dane Joined by special guest: Nell Shamrell-Harrington Sponsors Thinkster.io Sustain Our Software - Devchat.tv My Ruby Story - Devchat.tv CacheFly Links Nell's Twitter Adventures in DevOps The Phoenix Project Digital Ocean The Illustrated Children’s Guide to Kubernetes Kubernetes Tutorial Docker Courses - Thinkster.io Picks Luis Hernandez: Markdown Mike Dane: Day One Sam Julien: Ulysses app Nell Shamrell-Harrington: Round Health Jesse Sanders:

Episode Summary In this episode of the Dev Ed podcast, the panelists talk to Nell Shamrell-Harrington, Principal Engineer at Chef Software. Nell introduces herself and gives a brief background about her software development journey so far and talks about how she started working with DevOps. She is also a co-host of the Adventures in DevOps podcast on Devchat.tv. The meaning of the term DevOps can be quite cloudy, so before discussing learning DevOps, they talk about what it actually means and how it differs from traditional development. Nell breaks down the term and describes in detail the approach of merging developers and operational professionals. Joe highlights the cultural aspect of DevOps and how it plays into the way of working. Nell explains the right way of organizing teams, the internal interactions among them, accountability, and some of the dos and don'ts involved. Other panelists chime in with their views on the DevOps culture as well. They discuss the best practices, challenges faced, eliminating silo and sharing responsibility. They tackle the question of how to encourage seamless communication among teams and avoid conflicts. Nell explains that what works well in these cases instead of getting everyone together leading to chaos and blame games, is selecting representatives from both development and operations and ironing out the miscommunication. The next topic of discussion is why should a beginner developer care about DevOps at all. As applications become more complex, the need arises to think about their underlying infrastructure in order to optimize them and it is beneficial to have an idea of where they might be deployed. As a developer progresses from the beginning stages to advanced ones, it is natural to know about the deployment environment, data centres, and DevOps concepts in general. Due to advancements in technology, these areas have become very accessible as well. They steer the discussion towards what parts of DevOps should one focus on while getting started, given that there are a plethora of tools and technologies involved. Nell advises listeners to pick any major cloud provider and learn the basics by working with it, which can later be applied to any other cloud provider. She also recommends learning programming languages to get a good software development foundation. Sam shares his own experience with Digital Ocean and highly recommends their learning materials. Mike and Jesse suggest understanding how Continuous Integration works and mention that it is a great starting point. Mike points out that knowing that there are multiple environments at play - staging, production, testing and so on, helps a great deal. Speaking about Docker, Nell says that while it is an amazing technology which made containers extremely usable on a large scale, it is not a good idea to run the entire infrastructure on just containers, given that containers can be very ephemeral and there is a risk of losing data. For learning purposes though, she recommends Docker as it runs well on local environments. She explains what Chef is and the difference between Docker and Chef. The panelists then describe what Netlify is, how it works, and how good it is from the learning perspective. They then talk about some great resources for beginners to start with, Nell recommends Kubernetes, and explains what it means to orchestrate containers. Sam talks about Bruno Krebs' Kubernetes tutorial and Thinkster's Docker courses as awesome learning materials. They end the show with picks. Panel Joe Eames Sam Julien Jesse Sanders Luis Hernandez Mike Dane Joined by special guest: Nell Shamrell-Harrington Sponsors Thinkster.io Sustain Our Software - Devchat.tv My Ruby Story - Devchat.tv CacheFly Links Nell's Twitter Adventures in DevOps The Phoenix Project Digital Ocean The Illustrated Children’s Guide to Kubernetes Kubernetes Tutorial Docker Courses - Thinkster.io Picks Luis Hernandez: Markdown Mike Dane: Day One Sam Julien: Ulysses app Nell Shamrell-Harrington: Round Health Jesse Sanders:

Episode Summary In this episode of the Dev Ed podcast, the panelists talk to recurring guest Aspen Payton, who is currently working as a Lead Analyst Programmer at Mayo Clinic, has been in the software industry for about 20 years, and has over 32 granted patents to her name. Joe starts the discussion by giving a background on why he chose to talk about the essential developer skills. He divides the topic into different categories of skills and poses the first question to the panel - what fundamental technical skills should every developer have. Brooke shares her boot camp experience and stresses the importance of learning basic command-line operations. Sam mentions debugging with console.log in any language in any environment and explains how it can be a savior while troubleshooting all kinds of situations. Luis says that it is important to know how to efficiently use the editor, understand related tools and know how to type faster. Joe agrees and shares a funny anecdote from his initial days as a fast typist. Aspen mentions coding efficiently, reducing duplication and writing reusable code as some of the most essential skills. The panelists then discuss the pros and cons of AHA (Avoid Hasty Abstractions), the gist of which is to prefer abstraction over duplication and, to remove duplication when it is seen happening more than once. Brooke talks about learning how to solve problems and knowing what resources to use. Luis suggests that while working on different frameworks, it is important to learn the language associated with those frameworks and gives examples to further elaborate his point. The topic then shifts to languages and if there are any specific languages that developers need to learn. Aspen answers in the negative, saying that logic is the most crucial aspect of programming. Sam agrees, and talks about learning the basics and experimenting with various languages based on developers' requirements and comfort levels. Brooke advises listeners to go for the languages they are passionate about and mentions that they need to focus on learning the right way of thinking more than anything else. They discuss programming paradigms essential to be a good developer, which are mainly a mix of functional and object-oriented programming concepts. Talking about good software engineering practices, they list problem-solving, debugging, testing, reading documentation and understanding source code written by other developers, effective pair programming, code reviews, software patterns in the later stages of development, and version control systems such as git, as important strengths to have. The next category spoken about is educational skills. Some of the necessary ones being effective communication, ability to teach others well and convey ideas constructively, ability to pick up new languages and having a smooth transition from the old ones, not giving up and working on problems relentlessly (banging head on the wall!), tenacity, diligence and also, asking for help. They then list essential personal skills including the ability to work in a team while listening to others' ideas, giving them feedback and taking in criticism as well, time management, people skills, good writing, managing personal time and setting boundaries, humility, and empathy. They wrap up the episode by discussing organizational skills - organizing code, managing time across the team, being organized while learning something new, and task organization and move on to picks. Panel Joe Eames Brooke Avery Sam Julien Luis Hernandez Joined by special guest: Aspen Payton Sponsors Thinkster.io Sustain Our Software - Devchat.tv My Ruby Story - Devchat.tv CacheFly Links Aspen Payton - Twitter AHA Programming The Wrong Abstraction Picks Luis Hernandez: Chrome DevTools: Copy and extract all the CSS for an element on the page Brooke Avery: Robocode Sam Julien: Toggl Learn Identity - Auth0 Aspen Payton: The Nightingale - Audiobook Joe Eames: Roll for Adventure Sign up for Thinkster.io

Episode Summary In this episode of the Dev Ed podcast, the panelists talk to recurring guest Aspen Payton, who is currently working as a Lead Analyst Programmer at Mayo Clinic, has been in the software industry for about 20 years, and has over 32 granted patents to her name. Joe starts the discussion by giving a background on why he chose to talk about the essential developer skills. He divides the topic into different categories of skills and poses the first question to the panel - what fundamental technical skills should every developer have. Brooke shares her boot camp experience and stresses the importance of learning basic command-line operations. Sam mentions debugging with console.log in any language in any environment and explains how it can be a savior while troubleshooting all kinds of situations. Luis says that it is important to know how to efficiently use the editor, understand related tools and know how to type faster. Joe agrees and shares a funny anecdote from his initial days as a fast typist. Aspen mentions coding efficiently, reducing duplication and writing reusable code as some of the most essential skills. The panelists then discuss the pros and cons of AHA (Avoid Hasty Abstractions), the gist of which is to prefer abstraction over duplication and, to remove duplication when it is seen happening more than once. Brooke talks about learning how to solve problems and knowing what resources to use. Luis suggests that while working on different frameworks, it is important to learn the language associated with those frameworks and gives examples to further elaborate his point. The topic then shifts to languages and if there are any specific languages that developers need to learn. Aspen answers in the negative, saying that logic is the most crucial aspect of programming. Sam agrees, and talks about learning the basics and experimenting with various languages based on developers' requirements and comfort levels. Brooke advises listeners to go for the languages they are passionate about and mentions that they need to focus on learning the right way of thinking more than anything else. They discuss programming paradigms essential to be a good developer, which are mainly a mix of functional and object-oriented programming concepts. Talking about good software engineering practices, they list problem-solving, debugging, testing, reading documentation and understanding source code written by other developers, effective pair programming, code reviews, software patterns in the later stages of development, and version control systems such as git, as important strengths to have. The next category spoken about is educational skills. Some of the necessary ones being effective communication, ability to teach others well and convey ideas constructively, ability to pick up new languages and having a smooth transition from the old ones, not giving up and working on problems relentlessly (banging head on the wall!), tenacity, diligence and also, asking for help. They then list essential personal skills including the ability to work in a team while listening to others' ideas, giving them feedback and taking in criticism as well, time management, people skills, good writing, managing personal time and setting boundaries, humility, and empathy. They wrap up the episode by discussing organizational skills - organizing code, managing time across the team, being organized while learning something new, and task organization and move on to picks. Panel Joe Eames Brooke Avery Sam Julien Luis Hernandez Joined by special guest: Aspen Payton Sponsors Thinkster.io Sustain Our Software - Devchat.tv My Ruby Story - Devchat.tv CacheFly Links Aspen Payton - Twitter AHA Programming The Wrong Abstraction Picks Luis Hernandez: Chrome DevTools: Copy and extract all the CSS for an element on the page Brooke Avery: Robocode Sam Julien: Toggl Learn Identity - Auth0 Aspen Payton: The Nightingale - Audiobook Joe Eames: Roll for Adventure Sign up for Thinkster.io

Sponsors Thinkster.io Adventures in Blockchain - Devchat.tv My Ruby Story - Devchat.tv CacheFly Panel Joe Eames Brooke Avery Jesse Sanders Mike Dane Sam Julien Luis Hernandez Joined by special guest: Dylan Israel Episode Summary In this episode of the Dev Ed podcast, the panelists talk to Dylan Israel. Dylan is a self-taught software engineer working as a developer and a content creator. His YouTube channel has over 60k subscribers where he aims to help people trying to learn programming on their own. He teaches a course on Thinkster.io called "100 Algorithms Challenge", aimed at developers preparing for technical whiteboard interviews or those wanting regular challenges to improve their skills, and has a collection of the top most commonly asked interview questions on algorithms and data structures. Joe starts the discussion by throwing the fundamental question to the panel - What is the meaning of the terms "data structures" and "algorithms". Dylan explains that these are fairly common concepts in software development, and traditionally data structures represent the way data is organized and algorithms define how to parse through them while maintaining optimum performance using fewer iterations and reduced time. Others chime in as well and explain these terms using the analogy of building blocks and recipes. After the basics, they discuss why should one bother learning data structures and algorithms in the first place. The main reasons mentioned are cracking job interviews especially for high paying jobs at large companies, efficient computing, forcing one to think differently and out of the box, studying time and space complexity leading to a better understanding of the software. Joe mentions that what we learn in a computer science class is rarely used at an actual job, and asks the panel to challenge his statement that learning data structures and algorithms except for clearing job interviews, is inherently a waste of time. Brooke explains that learning about them helps in getting into the right mindset, whereas Dylan says that he has had a chance to use them in certain significant applications on his e-commerce platform, and Jesse adds that they help in honing developer skills to a large extent. Thinking on a level higher than what is expected in order to create efficient solutions, and understanding things well through problem-solving are some of the important takeaways from learning these concepts. The panelists then discuss some great ways to learn data structures and algorithms. They share their own interesting interview experiences offering insight into what worked for each of them, and suggest books, online resources including courses, and emphasize that practicing a ton of problem-solving on a whiteboard/paper is one of the best ways to go about it. They also mention that recognizing repetitive patterns in problems is a good approach, and using a different language to solve can be beneficial too. They also advise listeners to take into consideration the opportunity cost involved in spending a significant amount of time learning data structures and algorithms, so that they can take an informed decision. They talk about how much the knowledge of these concepts affects their hiring decisions and what exactly do they look for in candidates. They wrap up the show by each giving one piece of advice to someone preparing for a job - comparing solutions with others and learning from them, consistent attitude, test-driven development, interviewing a lot and researching about the interview as well as the interviewing panel. They end the episode with picks. Links Dylan Israel - YouTube 100 Algorithms Challenge Cracking the Coding Interview Picks Luis Hernandez: The Imposter's Handbook Combo Brooke Avery: 10 Day Algorithm Challenge The Art of Racing in the Rain Dylan Israel: Pramp Mike Dane: Google Fi Sam Julien: Base CS podcast You need a budget Jesse Sanders: CSS Tricks Hawaii Joe Eames: Stuff Matters: Exploring the Marvelous Materials That Shape Our Man-Made World

Sponsors Thinkster.io Adventures in Blockchain - Devchat.tv My Ruby Story - Devchat.tv CacheFly Panel Joe Eames Brooke Avery Jesse Sanders Mike Dane Sam Julien Luis Hernandez Joined by special guest: Dylan Israel Episode Summary In this episode of the Dev Ed podcast, the panelists talk to Dylan Israel. Dylan is a self-taught software engineer working as a developer and a content creator. His YouTube channel has over 60k subscribers where he aims to help people trying to learn programming on their own. He teaches a course on Thinkster.io called "100 Algorithms Challenge", aimed at developers preparing for technical whiteboard interviews or those wanting regular challenges to improve their skills, and has a collection of the top most commonly asked interview questions on algorithms and data structures. Joe starts the discussion by throwing the fundamental question to the panel - What is the meaning of the terms "data structures" and "algorithms". Dylan explains that these are fairly common concepts in software development, and traditionally data structures represent the way data is organized and algorithms define how to parse through them while maintaining optimum performance using fewer iterations and reduced time. Others chime in as well and explain these terms using the analogy of building blocks and recipes. After the basics, they discuss why should one bother learning data structures and algorithms in the first place. The main reasons mentioned are cracking job interviews especially for high paying jobs at large companies, efficient computing, forcing one to think differently and out of the box, studying time and space complexity leading to a better understanding of the software. Joe mentions that what we learn in a computer science class is rarely used at an actual job, and asks the panel to challenge his statement that learning data structures and algorithms except for clearing job interviews, is inherently a waste of time. Brooke explains that learning about them helps in getting into the right mindset, whereas Dylan says that he has had a chance to use them in certain significant applications on his e-commerce platform, and Jesse adds that they help in honing developer skills to a large extent. Thinking on a level higher than what is expected in order to create efficient solutions, and understanding things well through problem-solving are some of the important takeaways from learning these concepts. The panelists then discuss some great ways to learn data structures and algorithms. They share their own interesting interview experiences offering insight into what worked for each of them, and suggest books, online resources including courses, and emphasize that practicing a ton of problem-solving on a whiteboard/paper is one of the best ways to go about it. They also mention that recognizing repetitive patterns in problems is a good approach, and using a different language to solve can be beneficial too. They also advise listeners to take into consideration the opportunity cost involved in spending a significant amount of time learning data structures and algorithms, so that they can take an informed decision. They talk about how much the knowledge of these concepts affects their hiring decisions and what exactly do they look for in candidates. They wrap up the show by each giving one piece of advice to someone preparing for a job - comparing solutions with others and learning from them, consistent attitude, test-driven development, interviewing a lot and researching about the interview as well as the interviewing panel. They end the episode with picks. Links Dylan Israel - YouTube 100 Algorithms Challenge Cracking the Coding Interview Picks Luis Hernandez: The Imposter's Handbook Combo Brooke Avery: 10 Day Algorithm Challenge The Art of Racing in the Rain Dylan Israel: Pramp Mike Dane: Google Fi Sam Julien: Base CS podcast You need a budget Jesse Sanders: CSS Tricks Hawaii Joe Eames: Stuff Matters: Exploring the Marvelous Materials That Shape Our Man-Made World

Sponsors Thinkster.io React Native Radio - Devchat.tv Adventures in DevOps - Devchat.tv CacheFly Panel Joe Eames Brooke Avery Mike Dane Sam Julien Luis Hernandez Joined by special guest: Erik Hanchett Episode Summary In this episode of the Dev Ed podcast, the panelists talk to Erik Hanchett, a software developer focusing on Vue and Angular, author of Vue.js in Action and Ember.js Cookbook, educator and YouTuber. Erik starts the discussion by stating the benefits of working remotely and others join in with their inputs.They list several important advantages including work freedom, not having to commute, utilizing time well, privacy, less distractions, increased productivity and flexible schedules. They then discuss the downsides of it as well - less social interaction, no particular end time leading to long hours and difficulty in setting boundaries, feeling of being left out and managing different time zones. They also talk about techniques such as resorting to physical activity and proactive networking to combat these downsides. They then discuss the benefits and drawbacks of remote education. Learning from coworkers easily, productive interactions, collaboration and physical pair-programming could be some of the best parts of being on-site. On the other hand, being forced to solve problems independently and becoming self-reliant can prove to be beneficial when working remotely. They talk about how human contact is essential for learning and how classroom sessions are much more effective and increase retention of information. While speaking from the teachers' perspective, they point out that in case of classroom courses, teachers can customize the topics based on what students want, also, the decreased teacher-student ratio helps to build a good rapport between them leading to a better learning experience. They wrap up the episode by each sharing one tool/tip that has proven to be effective for remote work. Links Erik's Twitter Vue.js Fundamentals Program with Erik Picks Mike Dane: We Work Remotely Luis Hernandez: Visual Studio Live Share Sam Julien Zoom for Slack Erik Hanchett: Tuple Joe Eames: StackBlitz Brooke Avery: Loom

Sponsors Thinkster.io React Native Radio - Devchat.tv Adventures in DevOps - Devchat.tv CacheFly Panel Joe Eames Brooke Avery Mike Dane Sam Julien Luis Hernandez Joined by special guest: Erik Hanchett Episode Summary In this episode of the Dev Ed podcast, the panelists talk to Erik Hanchett, a software developer focusing on Vue and Angular, author of Vue.js in Action and Ember.js Cookbook, educator and YouTuber. Erik starts the discussion by stating the benefits of working remotely and others join in with their inputs.They list several important advantages including work freedom, not having to commute, utilizing time well, privacy, less distractions, increased productivity and flexible schedules. They then discuss the downsides of it as well - less social interaction, no particular end time leading to long hours and difficulty in setting boundaries, feeling of being left out and managing different time zones. They also talk about techniques such as resorting to physical activity and proactive networking to combat these downsides. They then discuss the benefits and drawbacks of remote education. Learning from coworkers easily, productive interactions, collaboration and physical pair-programming could be some of the best parts of being on-site. On the other hand, being forced to solve problems independently and becoming self-reliant can prove to be beneficial when working remotely. They talk about how human contact is essential for learning and how classroom sessions are much more effective and increase retention of information. While speaking from the teachers' perspective, they point out that in case of classroom courses, teachers can customize the topics based on what students want, also, the decreased teacher-student ratio helps to build a good rapport between them leading to a better learning experience. They wrap up the episode by each sharing one tool/tip that has proven to be effective for remote work. Links Erik's Twitter Vue.js Fundamentals Program with Erik Picks Mike Dane: We Work Remotely Luis Hernandez: Visual Studio Live Share Sam Julien Zoom for Slack Erik Hanchett: Tuple Joe Eames: StackBlitz Brooke Avery: Loom

Sponsors Thinkster.io Adventures in DevOps - Devchat.tv My Angular Story - Devchat.tv CacheFly Panel Joe Eames Brooke Avery Jesse Sanders Sam Julien Mike Dane Luis Hernandez Joined by special guest: Preston Lamb Episode Summary In this episode of the Dev Ed podcast, the panelists talk to recurring special guest Preston Lamb who is a software developer at MotivHealth. They start the discussion by each explaining how and when the imposter syndrome has affected them in their work. They talk about it being more frequent than generally thought of and how it impacts their confidence and leads to self-doubt. They share their experiences where switching career paths and learning something new tends to become intimidating and hard at times, causing anxiety and resulting in the feeling of not knowing things, especially on stage or while doing something like consulting where you are expected to be an expert. They discuss which activities are more likely to cause the imposter syndrome - teaching, being around other developers, conferences, getting new jobs and promotions, and also cases where they don't encounter it. They then describe useful strategies to combat it during each of the above mentioned activities and offer great tips for listeners along the way. They end the episode on a hopeful and encouraging note and mention one thing they would like to learn in the near future. Links Preston's Twitter Preston Lamb - Angular in Depth Things I Don't Know as of 2018 - Dan Abramov Picks Joe Eames: Jest Mike Dane: Webpack Sam Julien, Brooke Avery, Jesse Sanders: CSS Preston Lamb: Understanding how the web works Luis Hernandez: Regular expressions

Sponsors Thinkster.io Adventures in DevOps - Devchat.tv My Angular Story - Devchat.tv CacheFly Panel Joe Eames Brooke Avery Jesse Sanders Sam Julien Mike Dane Luis Hernandez Joined by special guest: Preston Lamb Episode Summary In this episode of the Dev Ed podcast, the panelists talk to recurring special guest Preston Lamb who is a software developer at MotivHealth. They start the discussion by each explaining how and when the imposter syndrome has affected them in their work. They talk about it being more frequent than generally thought of and how it impacts their confidence and leads to self-doubt. They share their experiences where switching career paths and learning something new tends to become intimidating and hard at times, causing anxiety and resulting in the feeling of not knowing things, especially on stage or while doing something like consulting where you are expected to be an expert. They discuss which activities are more likely to cause the imposter syndrome - teaching, being around other developers, conferences, getting new jobs and promotions, and also cases where they don't encounter it. They then describe useful strategies to combat it during each of the above mentioned activities and offer great tips for listeners along the way. They end the episode on a hopeful and encouraging note and mention one thing they would like to learn in the near future. Links Preston's Twitter Preston Lamb - Angular in Depth Things I Don't Know as of 2018 - Dan Abramov Picks Joe Eames: Jest Mike Dane: Webpack Sam Julien, Brooke Avery, Jesse Sanders: CSS Preston Lamb: Understanding how the web works Luis Hernandez: Regular expressions

Sponsors Triplebyte $1000 signing bonus Sentry use code “devchat” for 2 months free Linode Panel Charles Max Wood Aimee Knight Chris Ferdinandi AJ O’Neal Joe Eames Episode Summary Today the panel discusses what is necessary to get a website up and how complicated or simple it needs to be. They mention different tools they like for static sites and ways to manage their builds and websites. They talk about why some people choose to host their websites and at what point the heavier tools become a concern. They discuss whan it is necessary to use those heavy tools.  They caution listeners to beware of premature optimization, because sometimes businesses will take advantage of newer developers and make them think they need all these shiny bells and whistles, when there is a cheaper way to do it. It is important to keep the tools you work with simple and to learn them so that if you encounter a problem, you have some context and scope. The option of serverless website hosting is also discussed, as well as important things to know about servers. The panel discusses what drives up the price of a website and if it is worth it to switch to a cheaper alternative. They discuss the pros and cons of learning the platform yourself versus hiring a developer. The importance of recording the things that you do on your website is mentioned. Several of the panelists choose to do this by blogging so that if you search for a problem you can find ones you’ve solved in the past. Links Heroku Github Pages Netlify Eleventy DigitalOcean Lightsale Ubuntu Git clone Node static server Systemd script NGinx Cloud66 Thinkster Gatsby Docker Gentoo How to schedule posts with a static website How to set up automatic deployment with Git with a vps Automating the deployment of your static site with Github and Hugo Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Microsoft build Aimee Knight: Systems Thinking is as Important as Ever for New Coders Chris Ferdinandi: Adrian Holivadi framework video Server Pilot   AJ O’Neal: Jeff Atwood tweet More on Stackflow Architecture Minio Joe Eames: Miniature painting  

Sponsors Triplebyte $1000 signing bonus Sentry use code “devchat” for 2 months free Linode Panel Charles Max Wood Aimee Knight Chris Ferdinandi AJ O’Neal Joe Eames Episode Summary Today the panel discusses what is necessary to get a website up and how complicated or simple it needs to be. They mention different tools they like for static sites and ways to manage their builds and websites. They talk about why some people choose to host their websites and at what point the heavier tools become a concern. They discuss whan it is necessary to use those heavy tools.  They caution listeners to beware of premature optimization, because sometimes businesses will take advantage of newer developers and make them think they need all these shiny bells and whistles, when there is a cheaper way to do it. It is important to keep the tools you work with simple and to learn them so that if you encounter a problem, you have some context and scope. The option of serverless website hosting is also discussed, as well as important things to know about servers. The panel discusses what drives up the price of a website and if it is worth it to switch to a cheaper alternative. They discuss the pros and cons of learning the platform yourself versus hiring a developer. The importance of recording the things that you do on your website is mentioned. Several of the panelists choose to do this by blogging so that if you search for a problem you can find ones you’ve solved in the past. Links Heroku Github Pages Netlify Eleventy DigitalOcean Lightsale Ubuntu Git clone Node static server Systemd script NGinx Cloud66 Thinkster Gatsby Docker Gentoo How to schedule posts with a static website How to set up automatic deployment with Git with a vps Automating the deployment of your static site with Github and Hugo Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Microsoft build Aimee Knight: Systems Thinking is as Important as Ever for New Coders Chris Ferdinandi: Adrian Holivadi framework video Server Pilot   AJ O’Neal: Jeff Atwood tweet More on Stackflow Architecture Minio Joe Eames: Miniature painting  

Sponsors Triplebyte $1000 signing bonus Sentry use code “devchat” for 2 months free Linode Panel Charles Max Wood Aimee Knight Chris Ferdinandi AJ O’Neal Joe Eames Episode Summary Today the panel discusses what is necessary to get a website up and how complicated or simple it needs to be. They mention different tools they like for static sites and ways to manage their builds and websites. They talk about why some people choose to host their websites and at what point the heavier tools become a concern. They discuss whan it is necessary to use those heavy tools.  They caution listeners to beware of premature optimization, because sometimes businesses will take advantage of newer developers and make them think they need all these shiny bells and whistles, when there is a cheaper way to do it. It is important to keep the tools you work with simple and to learn them so that if you encounter a problem, you have some context and scope. The option of serverless website hosting is also discussed, as well as important things to know about servers. The panel discusses what drives up the price of a website and if it is worth it to switch to a cheaper alternative. They discuss the pros and cons of learning the platform yourself versus hiring a developer. The importance of recording the things that you do on your website is mentioned. Several of the panelists choose to do this by blogging so that if you search for a problem you can find ones you’ve solved in the past. Links Heroku Github Pages Netlify Eleventy DigitalOcean Lightsale Ubuntu Git clone Node static server Systemd script NGinx Cloud66 Thinkster Gatsby Docker Gentoo How to schedule posts with a static website How to set up automatic deployment with Git with a vps Automating the deployment of your static site with Github and Hugo Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Microsoft build Aimee Knight: Systems Thinking is as Important as Ever for New Coders Chris Ferdinandi: Adrian Holivadi framework video Server Pilot   AJ O’Neal: Jeff Atwood tweet More on Stackflow Architecture Minio Joe Eames: Miniature painting  

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Triplebyte offers a $1000 signing bonus CacheFly Host: Charles Max Wood Joined By Special Guests: Eric Simons, Albert Pai and Tomek Sulkowski Episode Summary Do you want to send your code to space? Find out how with Charles Max Wood, Eric Simons, Albert Pai and Tomek Sulkowski coming to you live from the podcast booth at ng-conf 2019. They talk about new happenings at StackBlitz (in astronaut suits!)  and how you can send your apps and websites to space! Eric and Albert talk about how they met and decided to co-found companies like Thinkster and StackBlitz together. Thinkster has been since acquired by Joe Eames whom they have met at a podcast at Devchat.tv. Listen to the show to hear more about their upcoming projects at StackBlitz as well as their favorite parts of ng-conf and how they spend their time when they aren't busy with StackBlitz. Links ng-conf 2019

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Triplebyte offers a $1000 signing bonus CacheFly Host: Charles Max Wood Joined By Special Guests: Eric Simons, Albert Pai and Tomek Sulkowski Episode Summary Do you want to send your code to space? Find out how with Charles Max Wood, Eric Simons, Albert Pai and Tomek Sulkowski coming to you live from the podcast booth at ng-conf 2019. They talk about new happenings at StackBlitz (in astronaut suits!)  and how you can send your apps and websites to space! Eric and Albert talk about how they met and decided to co-found companies like Thinkster and StackBlitz together. Thinkster has been since acquired by Joe Eames whom they have met at a podcast at Devchat.tv. Listen to the show to hear more about their upcoming projects at StackBlitz as well as their favorite parts of ng-conf and how they spend their time when they aren't busy with StackBlitz. Links ng-conf 2019

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Triplebyte offers a $1000 signing bonus CacheFly Host: Charles Max Wood Joined By Special Guests: Eric Simons, Albert Pai and Tomek Sulkowski Episode Summary Do you want to send your code to space? Find out how with Charles Max Wood, Eric Simons, Albert Pai and Tomek Sulkowski coming to you live from the podcast booth at ng-conf 2019. They talk about new happenings at StackBlitz (in astronaut suits!)  and how you can send your apps and websites to space! Eric and Albert talk about how they met and decided to co-found companies like Thinkster and StackBlitz together. Thinkster has been since acquired by Joe Eames whom they have met at a podcast at Devchat.tv. Listen to the show to hear more about their upcoming projects at StackBlitz as well as their favorite parts of ng-conf and how they spend their time when they aren't busy with StackBlitz. Links ng-conf 2019

Sponsors Sentry use code “devchat” for 2 months free Triplebyte $1000 signing bonus Linode Panel Charles Max Wood Aimee Knight Chris Ferdinandi AJ O’Neal Joe Eames Episode Summary Today the panel discusses the necessity of a front end framework. Overall, there is a consensus that frameworks are not necessary in all situations. They discuss the downsides of using frameworks, such as being restricted by the framework when doing edge development and the time required for learning a framework. They talk about the value of frameworks for learning patterns in programming. The panel delves into the pros and cons of different frameworks available. Joe shares a story about teaching someone first without a framework and then introducing them to frameworks, and the way it helped with their learning. One of the pros of frameworks is that they are better documented than manual coding. They all agree that it is not enough to just know a framework, you must continue to learn JavaScript as well. They talk about the necessity for new programmers to learn a framework to get a job, and the consensus is that a knowledge of vanilla JavaScript and a general knowledge of the framework for the job is important. New programmers are advised to not be crippled by the fear of not knowing enough and to have an attitude of continual learning. In the technology industry, it is easy to get overwhelmed by all the developments and feel that one cannot possibly learn it all. Charles gives advice on how to find your place in the development world. The show concludes with the panel agreeing that frameworks are overall a good thing and are valuable tools. Links JWT Angular Vue Backbone GoLang Express React Redux Hyper HTML 4each Pascal JQuery Npm.js Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Podwrench Aimee Knight: How to Love Your Job and Avoid Burnout So Good They Can’t Ignore You Chris Ferdinandi: Vanilla JS toolkit Thinkster Artifact Conference AJ O’Neal: Binary Cocoa Binary Cocoa Slamorama Kickstarter Binary Cocoa Straight 4 Root

Sponsors Sentry use code “devchat” for 2 months free Triplebyte $1000 signing bonus Linode Panel Charles Max Wood Aimee Knight Chris Ferdinandi AJ O’Neal Joe Eames Episode Summary Today the panel discusses the necessity of a front end framework. Overall, there is a consensus that frameworks are not necessary in all situations. They discuss the downsides of using frameworks, such as being restricted by the framework when doing edge development and the time required for learning a framework. They talk about the value of frameworks for learning patterns in programming. The panel delves into the pros and cons of different frameworks available. Joe shares a story about teaching someone first without a framework and then introducing them to frameworks, and the way it helped with their learning. One of the pros of frameworks is that they are better documented than manual coding. They all agree that it is not enough to just know a framework, you must continue to learn JavaScript as well. They talk about the necessity for new programmers to learn a framework to get a job, and the consensus is that a knowledge of vanilla JavaScript and a general knowledge of the framework for the job is important. New programmers are advised to not be crippled by the fear of not knowing enough and to have an attitude of continual learning. In the technology industry, it is easy to get overwhelmed by all the developments and feel that one cannot possibly learn it all. Charles gives advice on how to find your place in the development world. The show concludes with the panel agreeing that frameworks are overall a good thing and are valuable tools. Links JWT Angular Vue Backbone GoLang Express React Redux Hyper HTML 4each Pascal JQuery Npm.js Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Podwrench Aimee Knight: How to Love Your Job and Avoid Burnout So Good They Can’t Ignore You Chris Ferdinandi: Vanilla JS toolkit Thinkster Artifact Conference AJ O’Neal: Binary Cocoa Binary Cocoa Slamorama Kickstarter Binary Cocoa Straight 4 Root

Sponsors Sentry use code “devchat” for 2 months free Triplebyte $1000 signing bonus Linode Panel Charles Max Wood Aimee Knight Chris Ferdinandi AJ O’Neal Joe Eames Episode Summary Today the panel discusses the necessity of a front end framework. Overall, there is a consensus that frameworks are not necessary in all situations. They discuss the downsides of using frameworks, such as being restricted by the framework when doing edge development and the time required for learning a framework. They talk about the value of frameworks for learning patterns in programming. The panel delves into the pros and cons of different frameworks available. Joe shares a story about teaching someone first without a framework and then introducing them to frameworks, and the way it helped with their learning. One of the pros of frameworks is that they are better documented than manual coding. They all agree that it is not enough to just know a framework, you must continue to learn JavaScript as well. They talk about the necessity for new programmers to learn a framework to get a job, and the consensus is that a knowledge of vanilla JavaScript and a general knowledge of the framework for the job is important. New programmers are advised to not be crippled by the fear of not knowing enough and to have an attitude of continual learning. In the technology industry, it is easy to get overwhelmed by all the developments and feel that one cannot possibly learn it all. Charles gives advice on how to find your place in the development world. The show concludes with the panel agreeing that frameworks are overall a good thing and are valuable tools. Links JWT Angular Vue Backbone GoLang Express React Redux Hyper HTML 4each Pascal JQuery Npm.js Follow DevChat on Facebook and Twitter Picks Charles Max Wood: Podwrench Aimee Knight: How to Love Your Job and Avoid Burnout So Good They Can’t Ignore You Chris Ferdinandi: Vanilla JS toolkit Thinkster Artifact Conference AJ O’Neal: Binary Cocoa Binary Cocoa Slamorama Kickstarter Binary Cocoa Straight 4 Root

Sponsors Sentry use code “devchat” for 2 months free Triplebyte $1000 signing bonus Panel Charles Max Wood Aimee Knight Chris Ferdinandi AJ O’Neal Joe Eames Joined by Special Guest: Chris DeMars Episode Summary Special guest Chris DeMars is from Detroit, MI. Currently, he works for Tuft and Needle and is an international speaker, Google developer expert, Microsoft mvp, and web accessibility specialist. He comes from a varied work background, including truck driving and other non-tech jobs.   Today the panel discusses web accessibility for people with disabilities. According to a study done by WebAIM, 97.8% of homepages tested had detectable WCAG 2 failures. The panel discusses why web accessibility is doing so poorly. Chris talks about some of the biggest mistakes he sees and some very simple fixes to make sites more accessible. Chris talks about the importance of manual testing on screen readers and emphasizes that it is important to cover the screen to make sure that it really works with a screen reader. Chris talks about some of the resources available for those who wish to increase accessibility on their sites.   The team discusses tactics for prioritizing accessibility and if there is a moral obligation to make sites accessible to those with disabilities. Chris talks about his experience making accessibility a priority for one of the companies he worked for in the past. They discuss the futue of legal ramifications for sites that do not incorporate accessibility, and what responsibility falls on the shoulders of people who regularly use assistive devices to notify companies of issues. They finish the show with resources available to people who want to learn more. Links The DOM Semantic markup writings Alt attribute Axe by DeQue Bootstrap Aria lable WebAim study Follow DevChat on Facebook and Twitter Picks Charles Max Wood: LootCrate Aimee Knight: Implementing Git in Python tutorial Chris Ferdinandi: "Fighting Uphill" by Eric Bailey “The Web We Broke” by Ethan Marcotte AllBirds sneakers Newsletter AJ O’Neal: Golang Channel vs Mutex vs WaitGroup Nobuo Uematsu The Best Way to Tin Enameled Wire Joe Eames: Gizmos board game Thinkster.io accessibility course (not released yet) Chris DeMars: Dixxon Flannel Company Aquis.com accessibility simulator Refactr accessibility workshop in June Follow Chris

Sponsors Sentry use code “devchat” for 2 months free Triplebyte $1000 signing bonus Panel Charles Max Wood Aimee Knight Chris Ferdinandi AJ O’Neal Joe Eames Joined by Special Guest: Chris DeMars Episode Summary Special guest Chris DeMars is from Detroit, MI. Currently, he works for Tuft and Needle and is an international speaker, Google developer expert, Microsoft mvp, and web accessibility specialist. He comes from a varied work background, including truck driving and other non-tech jobs.   Today the panel discusses web accessibility for people with disabilities. According to a study done by WebAIM, 97.8% of homepages tested had detectable WCAG 2 failures. The panel discusses why web accessibility is doing so poorly. Chris talks about some of the biggest mistakes he sees and some very simple fixes to make sites more accessible. Chris talks about the importance of manual testing on screen readers and emphasizes that it is important to cover the screen to make sure that it really works with a screen reader. Chris talks about some of the resources available for those who wish to increase accessibility on their sites.   The team discusses tactics for prioritizing accessibility and if there is a moral obligation to make sites accessible to those with disabilities. Chris talks about his experience making accessibility a priority for one of the companies he worked for in the past. They discuss the futue of legal ramifications for sites that do not incorporate accessibility, and what responsibility falls on the shoulders of people who regularly use assistive devices to notify companies of issues. They finish the show with resources available to people who want to learn more. Links The DOM Semantic markup writings Alt attribute Axe by DeQue Bootstrap Aria lable WebAim study Follow DevChat on Facebook and Twitter Picks Charles Max Wood: LootCrate Aimee Knight: Implementing Git in Python tutorial Chris Ferdinandi: "Fighting Uphill" by Eric Bailey “The Web We Broke” by Ethan Marcotte AllBirds sneakers Newsletter AJ O’Neal: Golang Channel vs Mutex vs WaitGroup Nobuo Uematsu The Best Way to Tin Enameled Wire Joe Eames: Gizmos board game Thinkster.io accessibility course (not released yet) Chris DeMars: Dixxon Flannel Company Aquis.com accessibility simulator Refactr accessibility workshop in June Follow Chris

Sponsors Sentry use code “devchat” for 2 months free Triplebyte $1000 signing bonus Panel Charles Max Wood Aimee Knight Chris Ferdinandi AJ O’Neal Joe Eames Joined by Special Guest: Chris DeMars Episode Summary Special guest Chris DeMars is from Detroit, MI. Currently, he works for Tuft and Needle and is an international speaker, Google developer expert, Microsoft mvp, and web accessibility specialist. He comes from a varied work background, including truck driving and other non-tech jobs.   Today the panel discusses web accessibility for people with disabilities. According to a study done by WebAIM, 97.8% of homepages tested had detectable WCAG 2 failures. The panel discusses why web accessibility is doing so poorly. Chris talks about some of the biggest mistakes he sees and some very simple fixes to make sites more accessible. Chris talks about the importance of manual testing on screen readers and emphasizes that it is important to cover the screen to make sure that it really works with a screen reader. Chris talks about some of the resources available for those who wish to increase accessibility on their sites.   The team discusses tactics for prioritizing accessibility and if there is a moral obligation to make sites accessible to those with disabilities. Chris talks about his experience making accessibility a priority for one of the companies he worked for in the past. They discuss the futue of legal ramifications for sites that do not incorporate accessibility, and what responsibility falls on the shoulders of people who regularly use assistive devices to notify companies of issues. They finish the show with resources available to people who want to learn more. Links The DOM Semantic markup writings Alt attribute Axe by DeQue Bootstrap Aria lable WebAim study Follow DevChat on Facebook and Twitter Picks Charles Max Wood: LootCrate Aimee Knight: Implementing Git in Python tutorial Chris Ferdinandi: "Fighting Uphill" by Eric Bailey “The Web We Broke” by Ethan Marcotte AllBirds sneakers Newsletter AJ O’Neal: Golang Channel vs Mutex vs WaitGroup Nobuo Uematsu The Best Way to Tin Enameled Wire Joe Eames: Gizmos board game Thinkster.io accessibility course (not released yet) Chris DeMars: Dixxon Flannel Company Aquis.com accessibility simulator Refactr accessibility workshop in June Follow Chris

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Clubhouse CacheFly  Host: Charles Max Wood Guest: Joe Eames Episode Summary In this episode of My JavaScript Story, Charles Max Wood hosts Joe Eames, CEO of Thinkster.io and organizer of many different conferences, two of which are the AngularJS conference, ng-conf, and the WordPress developer conference, LoopConf. Joe is a front end web developer and an educator. He has authored over 10 Pluralsight.com courses. He is also a panelist on the JavaScript Jabber podcast and the Adventures in Angular podcast on DevChat.TV. Joe talks about his passion project, being on the organization team of Framework Summit, a two-day conference focused on all front end JavaScript frameworks, the first of which was held in Utah in October 2018. It was a great success and he and the rest of the organization team will be looking to repeat it in January of 2020. Another conference Joe was involved in organizing was React Conf 2018 which took place in October in Henderson, Nevada. He is in the process of organizing the React Conf 2019 with the rest of the organization team. Aside from organizing conferences Joe’s second passion is education. He has started up a podcast called Dev Ed Podcast. Joe has recently become the CEO of Thinkster.io. Thinkster.io is a unique platform where learners can really master web development with a lot of hands on training. Joe wants developers to be able to learn how to “generate” solutions to problems. He explains the concept of “interleaving” while learning a subject which helps students retain more and learn faster. Links https://webflow.com/ My Angular Story 049: Joe Eames My Angular Story 073: Joe Eames https://twitter.com/josepheames https://medium.com/@josepheames https://github.com/joeeames https://thinkster.io/ https://reactrally.com https://github.com/sveltejs/svelte https://github.com/stimulusjs/stimulus https://www.ng-conf.org/ https://twitter.com/loopconf http://www.pluralsight.com/author/joe-eames https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast https://www.frameworksummit.com/ https://conf.reactjs.org/ Dev Ed Podcast Picks Joe Eames: Gizmo Board Game Chronicles of Crime Board Game Deep Space D-6 Board Game https://boardgamegeek.com/ Charles Max Wood: Villainous Board Game Pandemic Legacy Season 2 Board Game Splendor Board Game Harry Potter: Hogwarts Battle Board Game

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Clubhouse CacheFly  Host: Charles Max Wood Guest: Joe Eames Episode Summary In this episode of My JavaScript Story, Charles Max Wood hosts Joe Eames, CEO of Thinkster.io and organizer of many different conferences, two of which are the AngularJS conference, ng-conf, and the WordPress developer conference, LoopConf. Joe is a front end web developer and an educator. He has authored over 10 Pluralsight.com courses. He is also a panelist on the JavaScript Jabber podcast and the Adventures in Angular podcast on DevChat.TV. Joe talks about his passion project, being on the organization team of Framework Summit, a two-day conference focused on all front end JavaScript frameworks, the first of which was held in Utah in October 2018. It was a great success and he and the rest of the organization team will be looking to repeat it in January of 2020. Another conference Joe was involved in organizing was React Conf 2018 which took place in October in Henderson, Nevada. He is in the process of organizing the React Conf 2019 with the rest of the organization team. Aside from organizing conferences Joe’s second passion is education. He has started up a podcast called Dev Ed Podcast. Joe has recently become the CEO of Thinkster.io. Thinkster.io is a unique platform where learners can really master web development with a lot of hands on training. Joe wants developers to be able to learn how to “generate” solutions to problems. He explains the concept of “interleaving” while learning a subject which helps students retain more and learn faster. Links https://webflow.com/ My Angular Story 049: Joe Eames My Angular Story 073: Joe Eames https://twitter.com/josepheames https://medium.com/@josepheames https://github.com/joeeames https://thinkster.io/ https://reactrally.com https://github.com/sveltejs/svelte https://github.com/stimulusjs/stimulus https://www.ng-conf.org/ https://twitter.com/loopconf http://www.pluralsight.com/author/joe-eames https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast https://www.frameworksummit.com/ https://conf.reactjs.org/ Dev Ed Podcast Picks Joe Eames: Gizmo Board Game Chronicles of Crime Board Game Deep Space D-6 Board Game https://boardgamegeek.com/ Charles Max Wood: Villainous Board Game Pandemic Legacy Season 2 Board Game Splendor Board Game Harry Potter: Hogwarts Battle Board Game

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Clubhouse CacheFly  Host: Charles Max Wood Guest: Joe Eames Episode Summary In this episode of My JavaScript Story, Charles Max Wood hosts Joe Eames, CEO of Thinkster.io and organizer of many different conferences, two of which are the AngularJS conference, ng-conf, and the WordPress developer conference, LoopConf. Joe is a front end web developer and an educator. He has authored over 10 Pluralsight.com courses. He is also a panelist on the JavaScript Jabber podcast and the Adventures in Angular podcast on DevChat.TV. Joe talks about his passion project, being on the organization team of Framework Summit, a two-day conference focused on all front end JavaScript frameworks, the first of which was held in Utah in October 2018. It was a great success and he and the rest of the organization team will be looking to repeat it in January of 2020. Another conference Joe was involved in organizing was React Conf 2018 which took place in October in Henderson, Nevada. He is in the process of organizing the React Conf 2019 with the rest of the organization team. Aside from organizing conferences Joe’s second passion is education. He has started up a podcast called Dev Ed Podcast. Joe has recently become the CEO of Thinkster.io. Thinkster.io is a unique platform where learners can really master web development with a lot of hands on training. Joe wants developers to be able to learn how to “generate” solutions to problems. He explains the concept of “interleaving” while learning a subject which helps students retain more and learn faster. Links https://webflow.com/ My Angular Story 049: Joe Eames My Angular Story 073: Joe Eames https://twitter.com/josepheames https://medium.com/@josepheames https://github.com/joeeames https://thinkster.io/ https://reactrally.com https://github.com/sveltejs/svelte https://github.com/stimulusjs/stimulus https://www.ng-conf.org/ https://twitter.com/loopconf http://www.pluralsight.com/author/joe-eames https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast https://www.frameworksummit.com/ https://conf.reactjs.org/ Dev Ed Podcast Picks Joe Eames: Gizmo Board Game Chronicles of Crime Board Game Deep Space D-6 Board Game https://boardgamegeek.com/ Charles Max Wood: Villainous Board Game Pandemic Legacy Season 2 Board Game Splendor Board Game Harry Potter: Hogwarts Battle Board Game

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Triplebyte offers a $1000 signing bonus CacheFly Host: Charles Max Wood Guest: Joe Eames Episode Summary In this episode of My Angular Story, Charles Max Wood hosts Joe Eames, CEO of Thinkster.io and organizer of many different conferences, two of which are the AngularJS conference, ng-conf, and the WordPress developer conference, LoopConf. Joe is a front end web developer and an educator. He has authored over 10 Pluralsight.com courses. He is also a panelist on the JavaScript Jabber podcast and the Adventures in Angular podcast on DevChat.TV. Joe talks about his passion project, being on the organization team of Framework Summit, a two-day conference focused on all front end JavaScript frameworks, the first of which was held in Utah in October 2018. It was a great success and he and the rest of the organization team will be looking to repeat it in January of 2020. Another conference Joe was involved in organizing was React Conf 2018 which took place in October in Henderson, Nevada. He is in the process of organizing the React Conf 2019 with the rest of the organization team. Aside from organizing conferences Joe’s second passion is education. He has started up a podcast called Dev Ed Podcast. Joe has recently become the CEO of Thinkster.io. Thinkster.io is a unique platform where learners can really master web development with a lot of hands on training. Joe wants developers to be able to learn how to "generate" solutions to problems. He explains the concept of “interleaving” while learning a subject which helps students retain more and learn faster. Links https://webflow.com/ https://devchat.tv/my-angular-story/mas-049-joe-eames/ https://twitter.com/josepheames https://medium.com/@josepheames https://github.com/joeeames https://thinkster.io/ https://reactrally.com https://github.com/sveltejs/svelte https://github.com/stimulusjs/stimulus https://www.ng-conf.org/ https://twitter.com/loopconf http://www.pluralsight.com/author/joe-eames https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast https://www.frameworksummit.com/ https://conf.reactjs.org/ Dev Ed Podcast Picks Joe Eames: Gizmo Board Game Chronicles of Crime Board Game Deep Space D-6 Board Game https://boardgamegeek.com/ Charles Max Wood: Villainous Board Game Pandemic Legacy Season 2 Board Game Splendor Board Game Harry Potter: Hogwarts Battle Board Game

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Triplebyte offers a $1000 signing bonus CacheFly Host: Charles Max Wood Guest: Joe Eames Episode Summary In this episode of My Angular Story, Charles Max Wood hosts Joe Eames, CEO of Thinkster.io and organizer of many different conferences, two of which are the AngularJS conference, ng-conf, and the WordPress developer conference, LoopConf. Joe is a front end web developer and an educator. He has authored over 10 Pluralsight.com courses. He is also a panelist on the JavaScript Jabber podcast and the Adventures in Angular podcast on DevChat.TV. Joe talks about his passion project, being on the organization team of Framework Summit, a two-day conference focused on all front end JavaScript frameworks, the first of which was held in Utah in October 2018. It was a great success and he and the rest of the organization team will be looking to repeat it in January of 2020. Another conference Joe was involved in organizing was React Conf 2018 which took place in October in Henderson, Nevada. He is in the process of organizing the React Conf 2019 with the rest of the organization team. Aside from organizing conferences Joe’s second passion is education. He has started up a podcast called Dev Ed Podcast. Joe has recently become the CEO of Thinkster.io. Thinkster.io is a unique platform where learners can really master web development with a lot of hands on training. Joe wants developers to be able to learn how to "generate" solutions to problems. He explains the concept of “interleaving” while learning a subject which helps students retain more and learn faster. Links https://webflow.com/ https://devchat.tv/my-angular-story/mas-049-joe-eames/ https://twitter.com/josepheames https://medium.com/@josepheames https://github.com/joeeames https://thinkster.io/ https://reactrally.com https://github.com/sveltejs/svelte https://github.com/stimulusjs/stimulus https://www.ng-conf.org/ https://twitter.com/loopconf http://www.pluralsight.com/author/joe-eames https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast https://www.frameworksummit.com/ https://conf.reactjs.org/ Dev Ed Podcast Picks Joe Eames: Gizmo Board Game Chronicles of Crime Board Game Deep Space D-6 Board Game https://boardgamegeek.com/ Charles Max Wood: Villainous Board Game Pandemic Legacy Season 2 Board Game Splendor Board Game Harry Potter: Hogwarts Battle Board Game

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Triplebyte offers a $1000 signing bonus CacheFly Host: Charles Max Wood Guest: Joe Eames Episode Summary In this episode of My Angular Story, Charles Max Wood hosts Joe Eames, CEO of Thinkster.io and organizer of many different conferences, two of which are the AngularJS conference, ng-conf, and the WordPress developer conference, LoopConf. Joe is a front end web developer and an educator. He has authored over 10 Pluralsight.com courses. He is also a panelist on the JavaScript Jabber podcast and the Adventures in Angular podcast on DevChat.TV. Joe talks about his passion project, being on the organization team of Framework Summit, a two-day conference focused on all front end JavaScript frameworks, the first of which was held in Utah in October 2018. It was a great success and he and the rest of the organization team will be looking to repeat it in January of 2020. Another conference Joe was involved in organizing was React Conf 2018 which took place in October in Henderson, Nevada. He is in the process of organizing the React Conf 2019 with the rest of the organization team. Aside from organizing conferences Joe’s second passion is education. He has started up a podcast called Dev Ed Podcast. Joe has recently become the CEO of Thinkster.io. Thinkster.io is a unique platform where learners can really master web development with a lot of hands on training. Joe wants developers to be able to learn how to "generate" solutions to problems. He explains the concept of “interleaving” while learning a subject which helps students retain more and learn faster. Links https://webflow.com/ https://devchat.tv/my-angular-story/mas-049-joe-eames/ https://twitter.com/josepheames https://medium.com/@josepheames https://github.com/joeeames https://thinkster.io/ https://reactrally.com https://github.com/sveltejs/svelte https://github.com/stimulusjs/stimulus https://www.ng-conf.org/ https://twitter.com/loopconf http://www.pluralsight.com/author/joe-eames https://www.facebook.com/adventuresinangular https://twitter.com/angularpodcast https://www.frameworksummit.com/ https://conf.reactjs.org/ Dev Ed Podcast Picks Joe Eames: Gizmo Board Game Chronicles of Crime Board Game Deep Space D-6 Board Game https://boardgamegeek.com/ Charles Max Wood: Villainous Board Game Pandemic Legacy Season 2 Board Game Splendor Board Game Harry Potter: Hogwarts Battle Board Game

Sponsors Kendo UI Sentry use the code “devchat” for $100 credit Clubhouse CacheFly Panel Joe Eames Aimee Knight Joined by special guest: Richard Feldman Episode Summary In this episode of JavaScript Jabber, Richard Feldman, primarily known for his work in Elm, the author of “Elm in Action” and Head of Technology at NoRedInk, talks about Elm 0.19 and the new features introduced in it. He explains how the development work is distributed between the Elm creator – Evan Czaplicki and the other members of the community and discusses the challenges on the way to Elm 1.0. Richard also shares some educational materials for listeners interested in learning Elm and gives details on Elm conferences around the world touching on the topic of having diversity among the speakers. He finally discusses some exciting things about Elm which would encourage developers to work with it. Links Elm in Action Frontend Masters – Introduction to Elm Frontend Masters – Advanced Elm Small Assets without the Headache Elm Guide ElmBridge San Francisco Renee Balmert Picks Aimee Knight: Most lives are lived by default Joe Eames: Thinkster Richard Feldman: Framework Summit 2018 – Keynote speech Nix Package Manager A Philosophy of Software Design

Sponsors Kendo UI Sentry use the code “devchat” for $100 credit Clubhouse CacheFly Panel Joe Eames Aimee Knight Joined by special guest: Richard Feldman Episode Summary In this episode of JavaScript Jabber, Richard Feldman, primarily known for his work in Elm, the author of “Elm in Action” and Head of Technology at NoRedInk, talks about Elm 0.19 and the new features introduced in it. He explains how the development work is distributed between the Elm creator – Evan Czaplicki and the other members of the community and discusses the challenges on the way to Elm 1.0. Richard also shares some educational materials for listeners interested in learning Elm and gives details on Elm conferences around the world touching on the topic of having diversity among the speakers. He finally discusses some exciting things about Elm which would encourage developers to work with it. Links Elm in Action Frontend Masters – Introduction to Elm Frontend Masters – Advanced Elm Small Assets without the Headache Elm Guide ElmBridge San Francisco Renee Balmert Picks Aimee Knight: Most lives are lived by default Joe Eames: Thinkster Richard Feldman: Framework Summit 2018 – Keynote speech Nix Package Manager A Philosophy of Software Design

Sponsors Sentry use the code “devchat” for $100 credit Netlify Triplebyte CacheFly Panel Lucas Reis Justin Bennett Nader Dabit Charles Max Wood Episode Summary In this 50th episode of React Round Up, the panelists start with talking briefly about themselves, their work, as well as their side projects. Lucas Reis is a Senior Frontend Engineer at Zocdoc, and is working on the Zocdoc website, specifically on performance and SEO. He is also involved in sharing frontend knowledge throughout the company. Justin Bennett is a Senior Engineer at Artsy and focuses on web performance along with several open source projects. He is also interested in release processes and continuous integration. Nader Dabit is with Amazon Web Services as a Developer Advocate, working on GraphQL, React to React Native, Vue and is involved in community work too. Charles Max Wood is mainly focused on making this podcast better that includes things like getting sponsors, dealing with business issues, releasing the episodes on time, etc. He talks about his mission to help people find fulfillment from coding and enabling them to achieve their ideal lifestyle. They discuss hard and soft skills in software development, their interdependence and importance, and also the fact that the skills required to become a good developer are needed for personal development in general as well. They then mention their favorite past episodes and the growth of different programming ecosystems and communities such as React, Vue, Angular, etc. With respect to upcoming projects in React, they talk a bit about Suspense, Concurrent React, server-side rendering, performance issues, Prepack, compiler optimizations and Reason React. Finally, they each mention what they do apart from regular development work to unwind and relax. Links Artsy The Dev Rev React 16 Roadmap Reason ReasonReact ClojureScript Thinkster Disney Heroes Battlemode Picks Justin Bennett: Inter Can’t Unsee design game Lucas Reis: The Law of Leaky Abstractions Nader Dabit: React Native Open GraphQL newsletter Charles Max Wood: Libsyn WordPress DigitalOcean Microphones – Electro-Voice RE20, Audio-Technica ATR2100

Sponsors Sentry use the code “devchat” for $100 credit Netlify Triplebyte CacheFly Panel Lucas Reis Justin Bennett Nader Dabit Charles Max Wood Episode Summary In this 50th episode of React Round Up, the panelists start with talking briefly about themselves, their work, as well as their side projects. Lucas Reis is a Senior Frontend Engineer at Zocdoc, and is working on the Zocdoc website, specifically on performance and SEO. He is also involved in sharing frontend knowledge throughout the company. Justin Bennett is a Senior Engineer at Artsy and focuses on web performance along with several open source projects. He is also interested in release processes and continuous integration. Nader Dabit is with Amazon Web Services as a Developer Advocate, working on GraphQL, React to React Native, Vue and is involved in community work too. Charles Max Wood is mainly focused on making this podcast better that includes things like getting sponsors, dealing with business issues, releasing the episodes on time, etc. He talks about his mission to help people find fulfillment from coding and enabling them to achieve their ideal lifestyle. They discuss hard and soft skills in software development, their interdependence and importance, and also the fact that the skills required to become a good developer are needed for personal development in general as well. They then mention their favorite past episodes and the growth of different programming ecosystems and communities such as React, Vue, Angular, etc. With respect to upcoming projects in React, they talk a bit about Suspense, Concurrent React, server-side rendering, performance issues, Prepack, compiler optimizations and Reason React. Finally, they each mention what they do apart from regular development work to unwind and relax. Links Artsy The Dev Rev React 16 Roadmap Reason ReasonReact ClojureScript Thinkster Disney Heroes Battlemode Picks Justin Bennett: Inter Can’t Unsee design game Lucas Reis: The Law of Leaky Abstractions Nader Dabit: React Native Open GraphQL newsletter Charles Max Wood: Libsyn WordPress DigitalOcean Microphones – Electro-Voice RE20, Audio-Technica ATR2100