Panel: - http://www.aimeemarieknight.com- https://twitter.com/cmaxw?lang=en (DevChat TV)- https://2013.boston.wordcamp.org/speakers/- https://twitter.com/josepheames Special Guests: https://twitter.com/justinbmeyer?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor In this episode, the panel talks with https://twitter.com/justinbmeyer?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor who is a co-author of DoneJS, CanJS, jQueryPP, StealJS, and DocumentJS. Justin currently works for https://www.bitovi.com/about and is their Director of R&D. He is also a fan of basketball and Michael Jackson. The panel and Justin talk about CanJS in-detail – check it out!Show Topics:0:58 – https://radiopublic.com/all-javascript-podcasts-by-devcha-WwEoX8/ep/s1!3b9d2 1:14 – Chuck: Can you tell everyone who you are?1:20 – Justin tells us his background.1:50 – Chuck.1:58 – Justin.2:06 – Chuck: Can you give us an introduction to what CanJS 4.0?2:11 – Justin: It is a JavaScript framework and is similar to Vue. It adds a very model layer, and uses Real Time very well.2:44 – Panelist.2:49 – Justin.2:55 – Panelist: What is the current...3:09 – Justin: Compatibility is very important to us. A lot of the same tools are still available. It has over 80 different repositories.Justin continues to talk about the differences/similarities between the different versions.4:55 – Panelist: Angular, React, and Vue are dominating, so I have 2 questions.1.) Where is the core strength of JS and its user base?2.) What is like to be the CanJS when everyone is talking about the other programs?5:31 – Justin: We have dealt with this for the past 10 years. Emotionally it’s not great, I wished it was more popular, but our priority is keeping our user-based happy. We’ve had big companies use it.Justin answers the second question.8:44 – Panelist: You mentioned two things.9:22 – Aimee: I think everything has trade-offs. I would use something because it was the right tool for the job. I wouldn’t want to make something that was “cool.” I would want to make it super accessible in a network.10:10 – Justin: That is a great marketing angle. We are trying to remove the worst parts of the program.10:26 – Now I am intrigued.10:32 – Justin: You have this mutable state and you aren’t sure. At least for https://twitter.com/canjs?lang=en I don’t see that occurring too often.10:54 – Aimee.10:58 – Justin: Deep inheritance is definitely a problem and it can create...11:13 – Aimee.11:19 – Justin: We have changed strategies a lot, and I think it’s helped https://twitter.com/canjs?lang=en grow; like 60% since January. We are doing a lot of user studies now. I run Meetups, etc. That being said inheritance schemes aren’t something that people will encounter. This is something that they won’t encounter months down the road.13:00 – Aimee.13:05 – Panelist: I would like to dig deeper into state-management. Everyone is doing Flux, talk about that with CanJS.13:20 – Justin: Yeah. It depends on what kind of user you are talking to. When I talk to new users off the street (people who just graduated, etc.)...If you look at React’s statistics – more than 50% doesn’t use any state management.16:15 – Panelist: I think it’s interesting that there are people that aren’t “oh my gosh...”16:43 – Justin: The last coolest thing I’ve done is...18:02 – Justin continues.18:16 – Panelist: I kind of have this belief that we as a community turn to frameworks and tools too much. From your perspective when does it make sense to turn to a tool like this or better off working with native...18:56 – It depends on how complex your app is and our ability to work through those problems. I think that’s a generic answer, but hopefully that helps. I don’t think you really can’t live without.19:49 – Panelist: I think that’s fair. One thing that I found is that there are many things layered into state-management. Because you mentioned performance, which is something I care about, too. At what point does the extra tooling become too heavy for the user’s experience? Where do you draw the line?21:11 – Justin: It depends. I don’t know what the parallel is – it’s like a richer developer problem. You have too many users where you can make those fine tuned adjustments. Do whatever is going to deliver the product first and then worry about performance later? I think our things are geared towards performance by default.22:41 – Panelist: Playing devil’s advocate, though. But isn’t there some danger in kind of suggesting that you focus on performance WHEN it’s a business issue? Maybe there is there a lack of empathy among developers. I worry that advice is hurting us.23:53 – Justin: No matter what you can build your homepage with Angular weird monstrosity, but then when you get to the point when people are using your product – you can just use native HTML, and native methods and build that one widget and as easy and fast as possible.24:50 – Panelist: Dealing with complexity. Now we need to do things like bundlers, and such to deal with this issue. I feel like a crotchety old man yelling because it takes forever.25:38 – Justin: I think it depends on where you are sitting. I think that comes down to the design. If your design has a lot of complex states, then...26:37 – Panelist: Because you care about performance...26:54 – https://sentry.io/welcome/ 27:53 – Justin: I don’t think that the run time of https://twitter.com/canjs?lang=en is going to be a critical performance path for anybody. Is there a responsibility? This is the oldest question. It’s like saying: where do you draw the line that you need to choose success/be elected to fight the battles if you really want to win.You need someone using your product or it doesn’t really matter. Start-ups use our product because they need to get something up and in. I am going to flip this back onto you guys.30:48 – Panelist: I think that’s fair.31:00 – Aimee: I have a question. You got into consultancy when do you recommend using CanJS or something else?31:15 – Justin: I always suggest people using CanJS.31:53 – Aimee: What do these people do when their contract is over? I have used an older version of Can, and...32:20 – Justin: Are you on https://github.com/gitterHQ?Aimee: No, I am not.32:25 – Justin: We do offer promote job posting to help them find somebody. We try our best to help people in any way we can.33:05 – Aimee: That’s helpful. Another question.33:28 – Justin: DoneJS is that. It uses the full kitchen sink. That’s what DoneJS is.33:50 – Panelist: Let’s talk about CanJS in the mark-up. Do you think it’s better now or worse than 2012? Less space or more space?34:13 – Justin: It’s probably worse. I think the methodology that we are using: focusing on our users. We get their feedback frequently. We are listening to our users, and I think we are being smarter.35:16 – Panelist: Is the space getting more welcoming or less?35:31 – It depends on what framework you are. It’s very hard to compete if you are the exact same thing as...The market is so dense and there are so many ideas, so it’s getting harder and harder. What helps people break-through? Is it the technology or the framework?36:36 – Panelist: I appreciate the richness of the field, as it exists right now. There aren’t a few things SMELT and ELM37:10 – Justin: Elm for sure. I don’t have a lot of experience with SMELT.37:23 – Panelist continues the talk.37:54 – Chuck.38:00 – Justin: I think it spreads by word-of-mouth. I used to think it was “technology” or... all that really matters is “can you deliver” and the person have a good experience.Usability is the most important to me. We will see how this turns out. I will be either right or wrong.39:18 – Panelist: Can we talk about the long-term future of Can JS?39:28 – Justin: We are connecting to our user-base and making them happy. If I had it my way (which I don’t anymore) I think https://reactjs.org/docs/jsx-in-depth.html is the best template language. We have been building integrations between JSX and...I am putting out proposals where most people don’t like them.Justin continues this conversation.44:24 – Picks!44:28 -https://devchat.tv/get-a-coder-job/ Links:- https://www.javascript.com- https://jquery.com- https://reactjs.org- https://elixir-lang.org- http://elm-lang.org- https://vuejs.org- https://polyfill.io/v2/docs/-Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Aimee KnightCharles Max WoodChristopher Ferdinandi (Boston) Special Guests: Dan Shappir (Tel Aviv)In this episode, the panel talks with Dan Shappir who is a computer software developer and performance specialist at Wix.com. As Dan states, his job is to make 100 million websites (hosted on the Wix platform) load and execute faster! Past employment includes working for companies, such as: Ericom, Ericom Software, and BackWeb. He studied at Technion Institute of Management and currently lives in Tel Aviv, Israel. The panel talks about web performance API among other things. Check it out!Show Topics:1:29 – Charles: Let us know who you are and why you’re famous!1:39 – “Hello!” from Dan Shappir.2:25 – Charles: You should say that you go to EACH site EVERY day out of the millions of sites out there.2:53 – Charles: My mom mentioned Wix to me at first. My mom teaches High School Math.3:16 – Dan: Yes that is our mission statement. That everyone can get a website without the knowledge of how to build a website.3:52 – Aimee makes her comments.3:59 – Dan: On our platform we try to offer people flexibility. There are bounds and limits, but people can do their very own thing, though. To make Wix faster because as we add more features and functionality that is our goal.4:40 – Chuck: Okay, I know how to make X perform a little bit better. You are looking at a platform that controls TONS of sites, how do you even go about that?4:58 – Dan: It is more difficult then that. We have millions of users leveraging the platform but there are a lot of developers in Wix who are developing the platform. I don’t think anyone at Wix has a total grasp of the complexity of the platform that we built. We have hundreds of frontend people working on our platform. All of them have pieces to the kingdom. We have processes in place with code reviews and whatnot, but there is so much going on. There is a change every 2 minutes, 24/7. We need to make sure progressing instead of regressing. 6:54 – Aimee: I think it was interesting in one of the links you sent over. Because you know when something is getting worse you consider that a bug.7:15 – Dan: It is more than a bug because if we see regression in performance then that is a problem. I can literally see any part of the organization and say, “stop” if it will7:57 – Chuck: We are talking about performance, but what does that mean? What measures are there?8:15: Dan: We are looking at performance can mean different things in different contents. User sites, for example, most important aspect is load time. How quickly the page loads and gets open to the viewer to that specific site. When they click something they want it instantly and no drag time. It does change in different contexts.9:58 – Chuck: People do talk about load time. People have different definitions of it.10:12: Dan: Excellent question. When you look at the different sites through Wix. Different people who build sites – load time can mean something else to everybody. It can mean when you see the MAIN text or the MAIN image. If it’s on an ECON site then how soon can they purchase or on a booking site, how long can the person book X product.I heard someone at a conference say that load time is when: HERO TEXT And HERO IMAGE are displayed.12:14 – Chuck: What is faster React or Vue?12:21 – NEW HOST: Not sure. It all depends.12:34 – Dan: We are big into React. We are one of the big React users outside of Facebook. I joined Wix four years ago, and even back then we were rebuilding our framework using React. One of our main modifications is because we wanted to do server-side rendered.13:27 – Christopher asks Dan a question.14:16 – Dan: We are in transition in this regard. Before we were totally client-site rendered, and that was the case until middle of last year. Then we deployed...Dan: We are 100% server-side rendered now. Some things we are still using JavaScript. We have another project going on now and it’s fully CSS, and little JavaScript as possible. What you might want to do with that site is...You might get in a few months every Wix site will be visible even if JavaScript is disabled.16:26 – Aimee adds in her comments and observations to this topic.16:55 – Dan: We don’t want things displayed incorrectly before it lays out. We hide the content while it’s downloading then make it visible. They lay-outing are done faster, because...17:44 – Christopher asks Dan a question.18:04 – Dan: I got into API...Either you are moving forward or are you moving back. AKA – You are either progressing or regressing.Different stages:1.) Development stage2.) Pre-Production (automated tools that check the performance with specific use cases)3.) Check it out!It’s beneficial to use these APIs.21:11 – Christopher: What is performance APIs?21:38 – Dan: There is a working group – Todd from Microsoft and others who are exposing the information (that is available in the browser) out into the browser. When the browser downloads a certain source (image, font, etc.) it can measure the various stages of downloading that feature.  You have these different sages of downloading this resource. The browser can measure each of these stages and then expose them to you. Basically it’s for the browser to expose this information to you and in a way that is coherent and uniform. It essentially maintains this buffer that puts performance entries sequentially.Dan continues explaining this topic in detail.25:55 – Dan: You have this internal buffer...28:45 – Advertisement – Sentry – They support opensource.29:39 – Christopher: everything you are saying seems that I can use this or that tab right now...Why would I prefer the API to something visual, hypothetically?30:03 – Dan: Three Different Stages. (See above.)This information is very, very helpful during the developmental stage. Say you got a link from someone...Dan mentions: Performance.mark 34:04 – Aimee: When you were talking about resource-ends. Many people don’t know what this is. Can you spend 2-3 minutes about how you guys are using these? Are there people can add for big bang for their buck?34:41 – Dan: This might want to be a topic for its own podcast show.Dan gives a definition of what a resource-end means.Go back to fonts as an example.Pre-connect for example, too.39:03 – Dan: Like I said, it’s a huge topic.You have to exercise some care. Bandwidth is limited. Make sure you aren’t blocking other resources that you do need right now.40:02 – Aimee: Sounds like a lot of great things to tap into. Another question I have is about bundling.40:27 – Dan: One of the things that we try to do (given that we are depending on the JavaScript we are downloading) we need to download JavaScript content to the client side. It has been shown often that JS is the most impactful resources that you need to download. You really want to be as smart as possible with that. What is even more challenging is the network protocols are changing.Dan continues to go in-depth about this topic. Dan: What we have found is that you want to strive to bundle resources together.44:10 – Aimee: Makes sense.44:15 – Dan continues talking about this topic.45:23 – Chuck asks two questions. (First question is now and second question is at 51:32.)2 Questions:1. You gather information from web performance AI - What system is that?45:42 – Dan: I am not the expert in that. I will try not to give misleading information. Actually let me phrase it different. There are 3rd party tools that you can use leverage in your website. IF you are building for commercial reasons I highly recommend that you use performance-monitoring solution. I am not going to advertise one because there are tons out there. We ended up rolling out our own infrastructure because our use case is different than most.At a conference I talked with a vendor and we talked about...51:32 – 2nd Question from Charles to Dan: Now you’ve gathered this information now what to you do? What patterns? What do you look for? And how do you decide to optimize things?54:23 – Chuck: Back to that question, Dan. How should they react to it and what are they looking for54:41 – Dan: Three main ways: 1.) Generate alerts 2.) See trends over long period of time 3.) Looking at real-time graphs.Frontend developer pro is that likely being woken up in the middle of the night is lower. We might be looking at the real time graph after we deployed...57:31 – Advertisement – Get a Coder Job!58:10 – Picks!Links:JavaScriptjQueryReactElixirElmVueWixBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Aimee KnightJoe EamesCharles Max Wood Special Guests: Ethan Brown In this episode, the panel talks with Ethan Brown who is a technological director at a small company. They write software to facilitate large public organizations and help make projects more effective, such as: rehabilitation of large construction projects, among others. There is a lot of government work through the endeavors they encounter. Today, the panel talks about his article he wrote, and other topics such as Flex, Redux, Ruby, Vue.js, Automerge, block chain, and Elm. Enjoy!Show Topics:2:38 – Chuck: We are here to talk about the software side of things.Let’s dive into what you are looking at mid-year what we need to know for 2018. You wrote this.3:25 – Ethan: I start off saying that doing this podcast now, how quickly things change. One thing I didn’t think people needed to know was symbols, and now that’s changed. I had a hard time with bundling and other things. I didn’t think the troubles were worth it. And now a couple of moths ago (an open source project) someone submitted a PR and said: maybe we should be using symbols? I told them I’ve had problems in the past. They said: are you crazy?!It’s funny to see how I things have changed.4:47 – Panel: Could you talk about symbols?4:58 – Aimee: Are they comparable to Ruby?5:05 – Ethan talks about what symbols are and what they do!5:52 – Chuck: That’s pretty close to how that’s used in Ruby, too.6:04 – Aimee: I haven’t used them in JavaScript, yet. When have you used them recently?6:15 – Ethan answers the question.7:17 – Panelist chimes in.7:27 – Ethan continues his answer. The topic of “symbols” continues. Ethan talks about Automerge. 11:18 – Chuck: I want to dive-into what you SHOULD know in 2018 – does this come from your experience? Or how did you drive this list?11:40 – Ethan: I realize that this is a local business, and I try to hear what people are and are not using. I read blogs. I think I am staying on top of these topics being discussed.12:25 – Chuck: Most of these things are what people are talking.12:47 – Aimee: Web Assembly. Why is this on the list?12:58 – Ethan: I put on the list, because I heard lots of people talk about this. What I was hearing the echoes of the JavaScript haters. They have gone through a renaissance. Along with Node, and React (among others) people did get on board. There are a lot of people that are poisoned by that. I think the excitement has died down. If I were to tell a story today – I would14:23 – Would you put block chain on there? And AI?14:34 – Panel: I think it’s something you should be aware of in regards to web assembly. I think it will be aware of. I don’t know if there is anything functional that I could use it with.15:18 – Chuck: I haven’t really played with it...15:27 – Panel: If you wrote this today would you put machine learning on there?15:37 – Ethan: Machine Learning...16:44 – Chuck: Back to Web Assembly. I don’t think you were wrong, I think you were early. Web Assembly isn’t design just to be a ... It’s designed to be highly optimized for...17:45 – Ethan: Well-said. Most of the work I do today we are hardly taxing the devices we are using on.18:18 – Chuck and panel chime in.18:39 – Chuck: I did think the next two you have on here makes sense.18:54 – Panel: Functional programming?19:02 – Ethan: I have a lot of thoughts on functional programming and they are mixed. I was exposed to this in the late 90’s. It was around by 20-30 years. These aren’t new. I do credit JavaScript to bring these to the masses. It’s the first language I see the masses clinging to. 10 years ago you didn’t see that. I think that’s great for the programming community in general. I would liken it to a way that Ruby on Rails really changed the way we do web developing with strong tooling. It was never really my favorite language but I can appreciate what it did for web programming. With that said...(Ethan continues the conversation.)Ethan: I love Elm. 21:49 – Panelists talks about Elm. *The topic diverts slightly.22:23 – Panel: Here’s a counter-argument. Want to stir the pot a little bit. I want to take the side of someone who does NOT like functional programming.24:08 – Ethan: I don’t disagree with you. There are some things I agree with and things I do disagree with. Let’s talk about Data Structures. I feel like I use this everyday. Maybe it’s the common ones. The computer science background definitely helps out.If there was one data structure, it would be TREES. I think STACKS and QUEUES are important, too. Don’t use 200-300 hours, but here are the most important ones. For algorithms that maybe you should know and bust out by heart.27:48 – Advertisement for Chuck’s E-book Course: Get A Coder Job28:30 – Chuck: Functional programming – people talk bout why they hate it, and people go all the way down and they say: You have to do it this way....What pay things will pay off for me, and which things won’t pay off for me? For a lot of the easy wins it has already been discussed. I can’t remember all the principles behind it. You are looking at real tradeoffs.  You have to approach it in another way. I like the IDEA that you should know in 2018, get to know X, Y, or Z, this year. You are helping the person guide them through the process.30:18 – Ethan: Having the right tools in your toolbox.30:45 – Panel: I agree with everything you said, I was on board, until you said: Get Merge Conflicts.I think as developers we are being dragged in...33:55 – Panelist: Is this the RIGHT tool to use in this situation?34:06 – Aimee: If you are ever feeling super imposed about something then make sure you give it a fair shot, first.34:28 – That’s the only reason why I keep watching DC movies.34:41 – Chuck: Functional programming and...I see people react because of the hype cycle. It doesn’t fit into my current paradigm. Is it super popular for a few months or...?35:10 – Aimee: I would love for someone to point out a way those pure functions that wouldn’t make their code more testable.35:42 – Ethan: Give things a fair shake. This is going back a few years when React was starting to gain popularity. I had young programmers all about React. I tried it and mixing it with JavaScript and...I thought it was gross. Everyone went on board and I had to make technically decisions. A Friend told me that you have to try it 3 times and give up 3 times for you to get it. That was exactly it – don’t know if that was prophecy or something. This was one of my bigger professional mistakes because team wanted to use it and I didn’t at first. At the time we went with Vue (old dog like me). I cost us 80,000 lines of code and how many man hours because I wasn’t keeping an open-mind?37:54 – Chuck: We can all say that with someone we’ve done.38:04 – Panel shares a personal story.38:32 – Panel: I sympathize because I had the same feeling as automated testing. That first time, that automated test saved me 3 hours. Oh My Gosh! What have I been missing!39:12 – Ethan: Why should you do automated testing? Here is why...You have to not be afraid of testing. Not afraid of breaking things and getting messy.39:51 – Panel: Immutability?40:00 – Ethan talks about this topic.42:58 – Chuck: You have summed up my experience with it.43:10 – Panel: Yep. I agree. This is stupid why would I make a copy of a huge structure, when...44:03 – Chuck: To Joe’s point – but it wasn’t just “this was a dumb way” – it was also trivial, too. I am doing all of these operations and look my memory doesn’t go through the roof. They you see it pay off. If you don’t see how it’s saving you effort, at first, then you really understand later.44:58 – Aimee: Going back to it being a functional concept and making things more testable and let it being clearly separate things makes working in code a better experience.As I am working in a system that is NOT a pleasure.45:31 – Chuck: It’s called legacy code...45:38 – What is the code year? What constitutes a legacy application?45:55 – Panel: 7 times – good rule.46:10 – Aimee: I am not trolling. Serious conversation I was having with them this year.46:27 – Just like cars.46:34 – Chuck chimes in with his rule of thumb.46:244 – Panel and Chuck go back-and-forth with this topic.47:14 – Dilbert cartoons – check it out. 47:55 – GREAT QUOTE about life lessons.48:09 – Chuck: I wish I knew then what I know now.Data binding. Flux and Redux. Lots of this came out of stuff around both data stores and shadow domes. How do you tease this out with the stuff that came out aroBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: AJ O’NealAimee KnightJoe EamesCharles Max Wood Special Guests: Chris Heilmann In this episode, the panel talks with programmer, Chris Heilmann. He has written books about JavaScript, in addition to writing a blog about it and is an educator about this program.  He currently resides in Berlin, Germany. Let’s welcome our special guest and listen to today’s episode!Show Topics:2:19 – Chuck talks.2:41 – Chris: He has talked about JavaScript in Berlin upon an invitation. You can get five different suggestions about how to use JavaScript. The best practices, I have found, are on the projects I am on now. JavaScript was built in ten days. My goal is to help people navigate through JavaScript and help them feel not disenfranchised. 5:47 – Aimee: The overall theme is...5:54 – Panelist: I really like what you said about helping people not feeling disenfranchised.6:47 – Chris: There is a lot of peer pressure at peer conferences7:30 – Aimee chimes in with some comments.7:50: Chris: I think we need to hunt the person down that put...8:03 – Panelist: A good point to that is, I try to avoid comments like, “Well, like we ALL know...”8:27 – Chris: There are things NOT to say on stage. It happens, but we don’t want to say certain things while we are teaching people. We are building products with different groups, so keep that in mind.9:40 – Aimee: My experience in doing this is that I have found it very rewarding to share embarrassing experiences that I’ve had. My advice would to tell people to let their guard down. It’s encouraging for me.10:26 – Chris: It helps to show that you are vulnerable and show that you are still learning, too. We are all learning together. 90% of our job is communicating with others.11:05 – Chuck: Now, I do want to ask this...11:35 – Chris answers.12:24 – What makes you say that? (Question to Chris)12:25 – Chris answers.13:55 – Chuck: The different systems out there are either widely distributed or...You will have to work with other people. There is no way that people can make that on their own. If you can’t work with other people, then you are a hindrance.14:31 – Aimee chimes in.14:53 – Chris: They have to be very self-assured. I want to do things that are at the next level. Each developer has his or her own story. I want to move up the chain, so I want to make sure these developers are self-assured.16:07 – Chris: Back to the article...18:26 – Chuck: Yes, I agree. Why go and fight creating a whole system when it exists.18:54 – Chris chimes in with some comments.19:38 – Panelist: I still use console logs.19:48 – Chris: We all do, but we have to...19:55 – Aimee: In the past year, I can’t tell you how much I rely on this. Do I use Angular? Do I learn Vue? All those things that you can focus on – tools.10:21 – Chris: We are talking about the ethics of interfaces. Good code is about accessibility, privacy and maintainability, among others. Everything else is sugar on top. We are building products for other people.22:10 – Chuck: That is the interesting message in your post, and that you are saying: having a deep, solid knowledge of React (that is sort of a status thing...). It is other things that really do matter. It’s the impact we are having. It’s those things that will make the difference. Those things people will want to work with and solves their problems.23:00 – Chris adds his comments. He talks about Flash.24:05 – Chris: The librarian motto: “I don’t know everything, but I can look “here” to find the answer.” We don’t know everything.24:31 – Aimee: Learn how to learn.24:50 – Chris: There is a big gap in the market. Scratch is a cool tool and it’s these puzzle pieces you put together. It was hard for me to use that system. No, I don’t want to do that. But if you teach the kids these tools then that’s good. 24:56 – Chuck: Here is the link, and all I had to do was write React components.26:12 – Chris: My first laptop was 5x more heavy then this one is. Having access to the Internet is a blessing.27:24 – Advertisement 28:21 – Chuck: Let’s bring this back around. If someone has gone through boot camp, you are recommending that they get use to know their editor, debugging, etc.Chris: 28:47 – Chris: Yes, get involved within your community. GitHub. This is a community effort. You can help. Writing code from scratch is not that necessary anymore. Why rebuild something if it works. Why fix it if it’s not broken?31:00 – Chuck talks about his experience.31:13 – Chris continues his thoughts.Chris: Start growing a community.32:01 – Chuck: What ways can people get involved within their community?32:13 – Chris: Meetup. There are a lot of opportunities out there. Just going online and seeing where the conferences34:08 – Chris: It’s interesting when I coach people on public speaking. Sharing your knowledge and learning experience is great!34:50 – Chuck: If they are learning how to code then...by interacting with people you can get closer to what you need/want.35:30 – Chris continues this conversation.35:49 – Chris: You can be the person that helps with x, y, z. Just by getting your name known then you can get a job offer.36:23 – Chuck: How do you find out what is really good content – what’s worth your time vs. what’s not worth your time?36:36 –Chris says, “That’s tricky!” Chris answers the question.37:19: Chris: The best things out there right now is...38:45 – Chuck: Anything else that people want to bring up?39:00 – Chris continues to talk.42:26 – Aimee adds in her thoughts.Aimee: I would encourage people to...43:00 – Chris continues the conversation.Chris: Each project is different, when I build a web app is different then when I build a...45:07 – Panelist: I agree. You talked about abstractions that don’t go away. You use abstractions in what you use. At some point, it’s safe to rly on this abstraction, but not this one. People may ask themselves: maybe CoffeeScript wasn’t the best thing for me.46:11 – Chris comments and refers to jQuery.48:58 – Chris continues the conversation.Chris: I used to work on eight different projects and they worked on different interfaces. I learned about these different environments. This is the project we are now using, and this will like it for the end of time. This is where abstractions are the weird thing. What was the use of the abstraction if it doesn’t have longevity? I think we are building things too soon and too fast.51:04 – Chris: When I work in browsers and come up with brand new stuff.52:21 – Panelist: Your points are great, but there are some additional things we need to talk about. Let’s take jQuery as an example. There is a strong argument that if you misuse the browser...53:45 – Chris: TheBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: - https://twitter.com/coolaj86?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor- http://www.aimeemarieknight.com- https://twitter.com/josepheames?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor- https://twitter.com/cmaxw?lang=en Special Guests: https://medium.com/@vzaidman In this episode, the panel talks with programmer, https://medium.com/@vzaidman, who is working with Software Solutions Company. He researches technologies and starts new projects all the time, and looks at these new technologies within the market. The panel talks about testing JavaScript in 2018 and https://jestjs.io.Show Topics:1:32 – Chuck: Let’s talk about testing JavaScript in 2018.1:53 – https://medium.com/@vzaidman talks about solving problems in JavaScript.2:46 – Chuck asks https://medium.com/@vzaidman a question.3:03 – Vitali’s answer.3:30 – Why https://jestjs.io? Why not Mocha or these other programs?3:49 – https://jestjs.io is the best interruption of what testing should look like and the best practice nowadays. There are different options, they can be better, but https://jestjs.io has this great support from their community. There are great new features.4:31 – Chuck to Joe: What are you using for testing nowadays?4:43 – Joe: I use Angular, primarily.6:01 – Like life, it’s sometimes easier to use things that make things very valuable.7:55 – Aimee: I have heard great things about http://www.cypress.com/documentation/software-and-drivers/free-and-open-source-software-download-page, but at work we are using another program.8:22 – Vitali: Check out my article.8:51 – Aimee: There are too many problems with the program that we use at work.9:39 – Panelist to Vitali: I read your article, and I am a fan. Why do you pick Test Café over Cypress, and how familiar are you with Cypress? What about Selenium and other programs?10:12 – Vitali: “Test Café and Cypress are competing head-to-head.”Listen to Vitali’s suggestions and comments per the panelists’ question at this timestamp.11:25 – Chuck: I see that you use sign-on...12:29 – Aimee: Can you talk abouthttps://github.com/GoogleChrome/puppeteer? It seems promising.12:45 – Vitali: Yes, Puppeteer is promising. It’s developed by Google and by Chrome. You don’t want to use all of your tests in Puppeteer, because it will be really hard to do in other browsers.13:26: Panelist: “...5, 6, 7, years ago it was important of any kind of https://www.javascript.com testing you had no idea if it worked in one browser and it not necessarily works in another browser. That was 10 years ago. Is multiple browsers testing as important then as it is now?14:51: Vitali answers the above question.15:30 – Aimee: If it is more https://www.javascript.com heavy then it could possibly cause more problems.15:56 – Panelist: I agree with this.16:02 – Vitali continues this conversation with additional comments.16:17 – Aimee: “I see that Safari is the new Internet Explorer.”16:23: Chuck: “Yes, you have to know your audience. Are they using older browsers? What is the compatibility?”17:01 – Vitali: There are issues with the security. Firefox has a feature of tracking protection; something like that.17:33 – Question to Vitali by Panelist.17:55 – Vitali answers the question.18:30 – Panelist makes additional comments.18:43 – If you use Safari, you reap what you sow.18:49 – Chuck: I use Chrome on my iPhone. (Aimee does, too.) Sometimes I wind up in Safari by accident.19:38 – Panelist makes comments.19:52 – Vitali tells a funny story that relates to this topic.20:45 – There are too many standards out there.21:05 – Aimee makes comments.21:08 – https://brutalist-web.design. Some guy has this site – https://brutalist-web.design – where he says use basic stuff and stop being so custom. Stop using the web as some crazy platform, and if your site is a website that can be scrolled through, that’s great. It needs to be just enough for people to see your content.22:16 – Aimee makes additional comments about this topic of https://brutalist-web.design.22:35 – Panelist: I like it when people go out and say things like that.22:45 – Here is the point, though. There is a difference between a website and a web application. Really the purpose is to read an article.23:37 – Vitali chimes in.24:01 – Back to the topic of content on websites.25:17 – Panelist: Medium is very minimal. Medium doesn’t feel like an application.26:10 – Is the website easy enough for the user to scroll through and get the content like they want to?26:19 – https://sentry.io/welcome/ 27:22 – See how far off the topic we got?27:31 – These are my favorite conversations to have.27:39 – Vitali: Let’s talk about how my article got so popular. It’s an interesting thing, I started researching “testing” for my company. We wanted to implement one of the testing tools. Instead of creating a presentation, I would write first about it in Medium to get feedback from the community as well. It was a great decision, because I got a lot of comments back. I enjoyed the experience, too. Just write about your problem in Medium to see what people say.28:48 – Panelist: You put a ton of time and energy in this article. There are tons of links. Did you really go through all of those articles?29:10 – Yes, what are the most permanent tools? I was just reading through a lot of comments and feedback from people. I tested the tools myself, too!29:37 – Panelist: You broke down the article, and it’s a 22-minute read.30:09 – Vitali: I wrote the article for my company, and they ad to read it.30:24 – Panelist: Spending so much time – you probably felt like it was apart of your job.30:39 – Vitali: I really like creating and writing. It was rally amazing for me and a great experience. I feel like I am talented in this area because I write well and fast. I wanted to express myself.31:17 – Did you edit and review?31:23 – Vitali: I wrote it by myself and some friends read it. There were serious mistakes, and that’s okay I am not afraid of mistakes. This way you get feedback.32:10 – Chuck: “Some people see testing in JavaScript, and people look at this and say there are so much here. Is there a place where people can start, so that way they don’t’ get too overwhelmed? Is there a way to ease into this and take a bite-size at a time?”32:52 – Vitali: “Find something that works for them. Read the article and start writing code.”He continues this conversation from here on out.34:03 – Chuck continues to ask questions and add other comments.34:16 – Vitali chimes-in. 34:38 – Chuck. 34:46 – Vitali piggybacks off of Chuck’s comments.36:14 – Panelist: Let’s go back to https://jestjs.io. There is a very common occurrence where we see lots of turn and we see ideas like this has become the dominant or the standard, a lot of people talk about stuff within this community. Then we get this idea that ‘this is the only thing that is happening.’ Transition to https://jquery.com to https://reactjs.org to... With that context do you feel like https://jestjs.io will be a dominant program? Are we going to see https://jestjs.io used just as common as Mocha and other popular programs?38:15 – Vitali comments on the panelist’s question.38:50 – Panelist: New features. Are the features in https://jestjs.io (over Jasmine, Mocha, etc.) so important that it will drive people to it by itself?40:30 – Vitali comments on this great question.40:58 – Panelist asks questions about features about https://jestjs.io.41:29 – Vitali talks about this topic.42:14 – Let’s go to picks!42:14 – https://www.digitalocean.com/ Links:- https://www.facebook.com/vzaidman- https://medium.com/@vzaidman- https://github.com/vzaidman- https://www.npmjs.com/~vzaidman-Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: - AJ O’Neal- Aimee Knight- Joe Eames Special Guests: http://naderdabit.me/#/ In this episode, the panel talks with programmer, Nader Dabit, who has been with Amazon’s AWS for the past six months. They discuss the new innovations that Amazon is currently working on, and the exciting new projects that Nader gets to be involved with. Check out this episode to hear all the latest!Show Topics:1:45 – There are two main things that Nader works with. Check out this timestamp to see what they are.3:29 – AJ to Nader: Tell me more about manage cloud. I am not sure about https://aws.amazon.com/cognito/?ef_id=W5RTKgAAAUa7GPf1%3A20180908225434%3As&s_kwcid=AL%214422%213%21293649588890%21p%21%21g%21%21cognito&sc_campaign=acquisition_USsc_publisher%3Dgoogle&sc_category=Security&sc_channel=PS&sc_content=cognito_p&sc_country=US&sc_detail=cognito&sc_matchtype=p&sc_medium=ACQ-P%257CPS-GO%257CNon-Brand%257CDesktop%257CSU%257CSecurity%257CCognito%257CUS%257CEN%257CText&sc_segment=293649588890.3:56 – https://aws.amazon.com/cognito/?ef_id=W5RTKgAAAUa7GPf1%3A20180908225434%3As&s_kwcid=AL%214422%213%21293649588890%21p%21%21g%21%21cognito&sc_campaign=acquisition_USsc_publisher%3Dgoogle&sc_category=Security&sc_channel=PS&sc_content=cognito_p&sc_country=US&sc_detail=cognito&sc_matchtype=p&sc_medium=ACQ-P%257CPS-GO%257CNon-Brand%257CDesktop%257CSU%257CSecurity%257CCognito%257CUS%257CEN%257CText&sc_segment=293649588890 5:06 – What are the other manage cloud services that companies want to offer through the tools you have?5:12 – Nader answers AJ’s question.7:30 – Can you give me more specifics on the storage solutions you are offering?8:03 – Nader answers AJ’s question. People store websites there for example. Frontend developers are using S3 buckets, and they are using the library, which is a storage solution.9:10 – AJ and Nader are having a dialogue between different situations, and Nader is giving the solutions to those hypothetical situations.10:17 – AJ: “I am interested in what you are talking about https://aws.amazon.com/appsync/. Can you tell me how that works?” AJ is picking Nader’s brain about how https://aws.amazon.com/appsync/ works.11:05 – Nader: “It is a single API layer for a point of entry. You can have multi-data sources.” Nader continues, in detail, answering AJ’s question.12:36 – AJ: As a frontend developer, it sounds like I will have to become familiar with the backend, too. How is it providing the most value? What is it that I do not have to touch, because I am using this?15:37 – How would these relations work? As a frontend developer, and I do not want to learn sequel, how would that might look like; currently or in the future? How do you extract that knowledge?16:18 – Yes, it is not an easy solution to solve. Nader goes into detail about how he would approach this situation.18:26 – AJ: Are these resolvers written in https://www.javascript.com?22:04 – Acronym fun!22:45 – https://nodejs.org/en/ 23:51 – Summarizing these pasts 20-some-minutes: Off-Storage, https://aws.amazon.com/appsync/,https://sites.google.com/site/landismodel/developers, and others are what people are using Amplify for. New Question/New Topic: Simplify.25:45 – https://aws.amazon.com/mobile/ – is not mobile specific.26:44 – If you are using https://angular.io, we have a plugin in https://angular.io to help you. We also have that for React and https://vuejsdevelopers.com as well.27:52 – https://sentry.io/welcome/ 28:56 – What should we be talking about?29:04 – Let’s talk about Amazon’s Lex, https://aws.amazon.com/lex/?ef_id=W5RTKgAAAUa7GPf1%3A20180908230815%3As&s_kwcid=AL%214422%213%21209039218013%21p%21%21g%21%21amazon%2520chatbot&sc_campaign=lex_2017&sc_category=lex&sc_channel=PS&sc_content=chatbot_p&sc_country=US&sc_detail=amazon%2520chatbot&sc_matchtype=p&sc_medium=awns_lex_b&sc_publisher=google&sc_segment=209039218013. Nader goes into full detail of this service.33:52 – https://www.apple.com/tv/ 34:00 – AJ: Sounds like this is more platform/ more agnostic than getting different things to come together, and the Microsoft one is more hybrid and the Amazon one is more open?35:13 – Joe, let’s go back to what you had to ask.35:28 – Nader, you talked about https://www.biznessapps.com/blog/what-is-a-push-notification/ earlier. What is https://cloud.google.com/pubsub/docs/overview?36:30 – Is this like traditional hooks? Or custom?37:25 – What is the “stuff” that gets you up in the morning and gets you excited to go to work at AWS?38:40 – Nader: I really had no desire to change career paths, but it happened.41:30 – AJ: I totally agree with the idea in that finding the common patterns, so that way someone on the lower-level can participate. AJ wants a platform that is open or purchase that can offer some of these benefits. It could be open-source or you used to buy the different tools.43:27 AJ: What about for the hobbyist?43:40 – Nader: I agree, that would be really nice. I can’t think of any free services that would be nice.44:03 AJ – Not free in “free,” but “free” towards the idea of “free speech.” They would all be available and you get to choose what works well for you.45:00 – SHOUTOUT to LISTENERS: Have an idea about this? Shoot the panel an e-mail!45:33 – Hopefully this opens the listeners’ eyes to what’s out there.45:48 – Cloud services.46:55 – Innovation follows niche markets. When something gets big and established, innovation comes to a plateau. The innovation will develop in a new economic area like hydraulics. AJ thinks a niche will develop.49:03 – Is there anything, Dabit, which you would like to talk about?49:15 – Can we talk about https://docs.aws.amazon.com/aws-technical-content/latest/aws-overview/artificial-intelligence-services.html?51:10 – Nader saw a demonstration recently.52:26 – Hearing these implications is so cool, but when it comes to ML a panelist dabbled a little bit. He watched some videos, unless you want to devote a year or two to learning it then it’s too complex to put together. Do you have to be genius-level to get through?53:29 – ML you are passing data. Nader is not quite sure.56:00 Nader just did a blog post  check-it-out!56:49 – Let’s do Picks!56:50 – https://www.digitalocean.com/ Links:- https://twitter.com/dabit3?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor- https://medium.com/@dabit3- https://www.linkedin.com/in/naderdabit/- https://github.com/dabit3- http://naderdabit.me/#/- https://www.youtube.com/channel/UC7mca3O0DmdSG2Cr80sOD7g- https://egghead.io/instructors/nader-dabit- https://www.javascript.com- https://aws.amazon.com/cognito/?ef_id=W5RTKgAAAUa7GPf1%3A20180908225434%3As&s_kwcid=AL%214422%213%21293649588890%21p%21%21g%21%21cognito&sc_campaign=acquisition_USsc_publisher%3Dgoogle&sc_category=Security&sc_channel=PS&sc_content=cognito_p&sc_country=US&sc_detail=cognito&sc_matchtype=p&sc_medium=ACQ-P%257CPS-GO%257CNon-Brand%257CDesktop%257CSU%257CSecurity%257CCognito%257CUS%257CEN%257CText&sc_segment=293649588890- https://aws.amazon.com/appsync/https://nodejs.org/en/- https://sites.google.com/site/landismodel/developers- https://aws.amazon.com/mobile/- https://vuejsdevelopers.com- https://angular.io-Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAJ O’NealAimee Knight Special Guests: Valeri Karpov In this episode, the panel talks with programmer, Valerie Karpov from Miami, Florida. He is quite knowledgeable with many different programs, but today’s episode they talk specifically about Async/Await and Promise Generators. Val is constantly busy through his different endeavors and recently finished his e-book, “Mastering Async/Await.” Check-out Val’s social media profiles through LinkedIn, GitHub, Twitter, and more.Show Topics:1:20 – Val has been on previous episodes back in 2013 & 2016.1:37 – Val’s background. He is very involved with multiple companies. Go checkout his new book! 2:39 – Promises generators. Understand Promises and how things sync with Promises. Val suggests that listeners have an integrated understanding of issues like error handling.3:57 – Chuck asks a question.6:25 – Aimee’s asks a question: “Can you speak to why someone would want to use Async/Await?”8:53 – AJ makes comments.10:09 – “What makes an Async/Await not functional?” – Val10:59 – “What’s wrong with Promises or Async/Await that people don’t like it?” - AJ11:25 – Val states that he doesn’t think there really is anything wrong with these programs it just depends on what you need it for. He thinks that having both gives the user great power.12:21 – AJ’s background is with Node and the Python among other programs.12:55 – Implementing Complex Business Logic.15:50 – Val discusses his new e-book.17:08 – Question from Aimee.17:16 – AJ answers question. Promises should have been primitive when it was designed or somewhat event handling.17:46 – The panel agrees that anything is better than Call Backs.18:18 – Aimee makes comments about Async/Await.20:08 – “What are the core principles of your new e-book?” – Chuck20:17 – There are 4 chapters and Val discusses, in detail, what’s in each chapter.22:40 – There could be some confusion from JavaScript for someone where this is their first language. Does Async/Await have any affect on the way you program or does anything make it less or more confusing in the background changes?24:30 – Val answers the before-mentioned question. Async/Await does not have anyway to help with this (data changes in the background).25:36 – “My procedural code, I know that things won’t change on me because it is procedural code. Is it hard to adjust to that?” – AJ26:01 – Val answers the question.26:32 – Building a webserver with Python. 27:31 – Aimee asks a question: “Do you think that there are cases in code base, where I would want to use Promises? Not from a user’s perspective, but what our preferences are, but actual performance. Is there a reason why I would want to use both or be consistent across the board?”28:17 – Val asks for some clarification to Aimee’s question.29:14 – Aimee: “My own personal preference is consistency. Would I want to use Promises in ‘x’ scenario and/or use Async/Await in another situation?”32:28 – Val and AJ are discussing and problem solving different situations that these programs33:05 – “When would you not want to use Async/Await?” – AJ33:25 – Val goes through the different situations when he would not use Async/Await. 33:44 – Chuck is curious about other features of Async/Await and asks Val.36:40 – Facebook’s Regenerator 37:11 – AJ: “Back in the day, people would be really concerned with JavaScript’s performance even with Chrome.” He continues his thoughts on this topic.38:11 – Val answers the AJ’s question.39:10 – Duck JS probably won’t include generators.41:18 – Val: “Have anyone used Engine Script before?” The rest of the panel had never heard of this before.42:09 – Windows Scripting Host 42:56 – Val used Rhino in the past.43:40 – Val: “Going back to the web performance question...”47:08 – “Where do you see using Async/Await the most?” – Chuck47:55 – Val uses Async/Await for everything on the backend because it has made everything so easy for him.48:23 – “So this is why you really haven’t used Web Pack?” – AJ49:20 – Let’s go to Aimee’s Picks!50:18 – AJ’s story, first, before we get to Promises.54:44 – Let’s transition to Promises Finally.54:53 – Val talks about Promises Finally.59:20 – PicksLinks:JavaScriptValeri Karpov’s GitHubValeri Karpov’s TwitterValeri Karpov’s LinkedInNew E-Book: Mastering Async/AwaitNodePythonWindows Scripting HostFacebook’s RegeneratorRhinoSponsors:Kendo UISentryDigital Ocean Picks:CharlesYouTube Video “IKEA” by CoultonConferenceAmazon Prime DayAimeeBlog Post ArticleAJIKEAhttps://ppl.familyValhttps://www.npmjs.com/package/servehttp://bit.ly/ultimate-skiinghttp://asyncawait.net/jsjabberNew E-Book: Mastering Async/AwaitSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Joe EamesAimee KnightAJ O'NealJoe Eames Special Guests: Christine LeggeIn this episode, the JavaScript Jabber panel talks to Christine Legge about functional programming with Ramda. Christine is a front-end software engineer and just recently got a new job in New York working at Google. Ramda is a utility library in JavaScript that focuses on making it easier to write JavaScript code in a functional way. They talk about functional programming and what it is, using Ramda in Redux, and referential transparency. They also touch on why she first got into Ramda, compare Ramda to Lodash and Underscore, and more!In particular, we dive pretty deep on:Chirstine intro Works as a front-end software engineerWhat is Ramda? JavaScriptUtility library like Lodash and UnderscoreLodash and Underscore VS RamdaFunctional programmingRamda and Functional programming as a mindsetRamda at ZenHubRamda with Redux and ReactWhat is referential transparency?Why would you use Ramda VS Lodash or Underscore?Why she first got into RamdaDidn’t always want to be a programmerBackground in MathLearning functional programming as a new programmerErlangDrRacket and JavaRamda makes it easy to compose functionsCreating clean and reusable codeHow do you start using Ramda?And much, much more! Links:RamdaLodashUnderscoreZenHubReduxReactErlangDrRacket@leggechrChirstine’s GitHubSponsorsKendo UISentryDigital OceanPicks:CharlesHome Depot Tool RentalPodcast MovementCESVRBOAimeeApple Cider VinegarJeremy Fairbank Talk – Practical Functional ProgrammingAJGoat’s MilkJoeTopgolfFramework SummitChristineDan ManganReply All PodcastSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel:Charles Max WoodJoe Eames Special Guests: AJ O'NealIn this episode, the JavaScript Jabber panel talks to AJ O'Neal about Greenlock and LetsEncrypt. LetsEncrypt is a brand name and is the first of its kind in automated SSL and Greenlock does what Certbot does in a more simplified form. They talk about what led him to create Greenlock, compare Greenlock to Certbot, and what it’s like to use Greenlock. They also touch on Greenlock-express, how they make Greenlock better, and more!In particular, we dive pretty deep on:Greenlock and LetsEncrypt overviewLetsEncrypt is free to get your certificateWhy Charles uses LetsEncryptWildcard domainsCertbotWhy he originally created GreenlockWorking towards home serversWanted to get HTTP on small devicesManages a certificate directoryGreenlock VS CertbotGreenlock can work stand aloneThe best use case for GreenlockExcited about how people are using his toolWhat is it like to use Greenlock?Working on a desktop clientGreenlock-expressAcme serversCAA recordMaking Greenlock better by knowing how people are using itUsing Greenlock-expressLet's Encrypt v2 Step by Step by AJAnd much, much more!Links:LetsEncryptGreenlockCertbotGreenlock-expressAcme serversLet's Encrypt v2 Step by Step by [email protected]’s GitGreenlock.js Screencast SeriesGreenlock.js PatreonSponsorsKendo UISentryDigital OceanPicks:CharlesTake some time offAJOverClocked RecordsSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Joe EamesAimee KnightAJ ONeal Special Guests: Tom DaleIn this episode, the JavaScript Jabber panel talks to Tom Dale about Ember 3.0 and the future of Ember. Tom is the co-creator of Ember and is a principle staff engineer at LinkedIn where he works on a team called Presentation Infrastructure. They talk about being in the customer service role, having a collaborative culture, and all the information on Ember 3.0. They also touch on the tendency towards disposable software, the Ember model, and more!In particular, we dive pretty deep on:How Joe met TomProgrammers as rule breakersThe pressure to conformTom introStaff engineer at LinkedInCustomer service roleHaving a way to role improvements out to a lot of different peopleJavaScript and Ember at LinkedInHaving a collaborative cultureAll about Ember 3.0Banner feature – there is nothing newCracked how you develop software in the open source world that has longevityMajor competition in Backbone previouslyThe Ember community has never been more vibrantTendency towards disposable softwareThe idea of steady iteration towards improvementThe Ember modelBeing different from different frameworksEmber adoption ratesPython 3Valuable from a business perspective to use EmberEmber community being friendly to newbiesHow much Ember VS how much JavaScript will a new developer have to learn?And much, much more!Links:[email protected]’s GitHubSponsorsKendo UISentryDigital OceanPicks:JoeFramework SummitJayneReact sent Evan You a cakeAimeeMaker's Schedule, Manager's Schedule by Paul GrahamAJJames VeitchTomJavaScript Tech TalkDrake’s TiesMelissa Watson Ellis at Hall MaddenSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Aimee KnightJoe EamesAJ ONeal Special Guests: Jeremy FairbankIn this episode, the JavaScript Jabber panel talks to Jeremy Fairbank about his talk Practical Functional Programming. Jeremy is a remote software developer and consultant for Test Double. They talk about what Test Double is and what they do there and the 6 things he touched on in his talk, such as hard to follow code, function composition, and mutable vs immutable data. They also touch on the theory of unit testing, if functional programming is the solution, and more!In particular, we dive pretty deep on:Jeremy introWorks for Test DoubleWhat he means by “remote”What is Test Double?They believe software is broken and they are there to fix itHis talk - Practical Functional ProgrammingThe 6 things he talked about in his talkPractical aspects that any software engineer is going to deal withPurity and the side effects of programming in generalHard to follow codeImperative VS declarative codeCode breaking unexpectedlyMutable data VS immutable dataThe idea of too much codeCombining multiple functions together to make more complex functionsFunction compositionElm, Elixir, and F#Pipe operatorScary to refactor codeStatic typesThe idea of nullThe theory of unit testingIs functional programming the solution?His approach from the talkAnd much, much more!Links:Test DoubleHis talk - Practical Functional ProgrammingElmElixirF#@elpapapollojeremyfairbank.comJeremy’s GitHubJeremy’s YouTubeSponsorsKendo UISentryDigital OceanPicks:AimeeAmerican DollarForce with leaseAJSuperfightJoeThe 2018 Web Developer Roadmap by Brandon MorelliSvelteJeremyProgramming ElmThe Secrets of Consulting by Gerald M. WeinbergConnect.TechSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodJoe EamesAimee Knight Special Guests: Kent BeckIn this episode, the JavaScript Jabber panel talks to Kent Beck. Kent left Facebook 4 months ago after working for them for 7 years and is now self-unemployed so that he can decompress from the stressful environment that he was a part of for so long. He now travels, writes, creates art, thinks up crazy programming ideas, and is taking a breather.  They talk about what he did at Facebook, what his coaching engagement sessions consisted of, and the importance of taking time for yourself sometimes. They also touch on what he has learned from his experience coaching, how to create a healthy environment within the workplace, and more!In particular, we dive pretty deep on:Kent intro/updateRuby Rogues Episode 23Worked at Facebook for 7 yearsWhat were you doing at Facebook?Unique culture at FacebookHis strengths as a developer didn’t match with the organization’sCoaching developersTDD and PatternsAdvantages as an old engineerWhat did coaching engagement consist of?Takes time to build trustDischarging shameNeed permission to take care of what you need toBeing at your best so you can do your best workVacation in placeWhat have you learned in your time working with people?The nice thing about coachingEveryone is differentHow do we create a healthy environment within the workplace?Mentor in Ward CunninghamWhat is it costing us?Why did you decide to leave?And much, much more!Links:Ruby Rogues Episode [email protected]’s GitHubSponsorsKendo UISentryDigital OceanPicks:CharlesThe Five Dysfunctions of a Team by Patrick LencioniCrucial Accountability by Kerry PattersonAimeen-backJoeTest Driven Development: By Example by Kent BeckKentThe Field Guide to Understanding 'Human Error' by Sidney DekkerConspiracy: Peter Thiel, Hulk Hogan, Gawker, and the Anatomy of Intrigue by Ryan HolidaySupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAJ ONeal Special Guests: Kurt MackeyIn this episode, the JavaScript Jabber panel talks to Kurt Mackey about Fly.io. At Fly.io, they are "building a JavaScript platform that gives you the power to build your own CDN." They talk about how Fly.io came to fruition, how CDN caching works, and what happens when you deploy a Fly app. They also touch on resizing images with Fly, how you actually build JavaScript platforms using Fly, and more!In particular, we dive pretty deep on:Fly.ioBuilding a programmable CDNHigh level overview of Fly.ioHow did this project come together?CDNs didn’t work with dynamic applicationsHas been working on this since 2008Extend application logic to the “edge”Putting burden of JavaScript “nastiest” onto the web serverFly is the proxy layerGetting things closer to visitors and usersCDN cachingCache APIsWriting logic to improve your lighthouse scoreHave you built in resizing images into Fly?Managing assets closer to the userCan you modify your own JavaScript files?What happens when you deploy a Fly appHaving more application logicDOM within the proxyGhostReact and GatsbyIntelligently loading client JavaScriptHow do you build the JavaScript platform?And much, much more!Links:Fly.ioJavaScriptGhostGatsbyReact@flydotio@mrkurtKurt at ARS TechnicaKurt’s GitHubSponsorsKendo UISentryDigital OceanPicks:CharlesGitLabAJGiteaBlack PantherKurtPacket.netThe Three-Body Problem by Cixin LiuSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max Wood Special Guests: Vesa JuvonenIn this episode, the JavaScript Jabber panel talks to Vesa Juvonen about building SharePoint extensions with JavaScript. Vesa is on the SharePoint development team and is responsible for the SharePoint Framework, which is the modern way of implementing SharePoint customizations with JavaScript. They talk about what SharePoint is, why they chose to use JavaScript with it, and how he maintains isolation. They also touch on the best way to get started with SharePoint, give some great resources to help you use it, and more!In particular, we dive pretty deep on:Vesa introWhat is SharePoint?Has existed since 2009People either know about it and use it or don’t know what it isBaggage from a customization perspectiveWhy JavaScript developers?Modernizing developmentSharePoint FrameworkMicrosoft Ignite ConferenceIs there a market for it?System integratorsAngular Element and ReactReact for SharePoint Framework back-endSupports VueReact Round Up PodcastHow do you maintain isolation?What’s the best way to get started with SharePoint extensions?Office 365 Developer ProgramSharePoint documentationSharePoint YouTubeWhat kinds of extensions are you seeing people build?And much, much more!Links:SharePointJavaScriptSharePoint FrameworkMicrosoft Ignite ConferenceAngular ElementReactVueReact Round Up PodcastOffice 365 Developer ProgramSharePoint documentationSharePoint YouTube @OfficeDev@vesajuvonenVesa’s blogVesa’s GitHub@SharePointSponsorsKendo UISentryDigital OceanPicks:CharlesZig ZiglarConversations with My Dog by Zig ZiglarPimsleur Lessons on AudibleVesaArmada by Ernest ClineSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAimee KnightAJ ONealJoe Eames Special Guests: Henry ZhuIn this episode, the JavaScript Jabber panel talks to Henry Zhu about Babel and open source software. Henry is one of the maintainers on Babel, which is a JavaScript compiler, and recently left this job to work on doing open source full time as well as working on Babel. They talk about where Babel is today, what it actually is, and his focus on his open source career. They also touch on how he got started in open source, his first PR, and more!In particular, we dive pretty deep on:Henry introBabel updateSebastian McKenzie was the original creator of BabelHas learned a lot about being a maintainerWhat is Babel?JavaScript compilerYou never know who your user isHas much changed with Babel since Sebastian left?Working on open sourceHow did you get started in pen source?The ability to learn a lot from open sourceAtrocities of globalizationMore decentralization from GitHubGitea and GitLabGitea installerOpen source is more closed nowHis first PRJSCSAuto-fixingPrettierLearning more about lintingYou don’t have to have formal training to be successfulCodefund.ioSustainability of open sourceAnd much, much more!Links:BabelJavaScriptGiteaGitLabGitea installerPrettierCodefund.io@left_padHenry’s GitHubhenryzoo.comHenry’s PatreonSponsorsKendo UISentryDigital OceanPicks:CharlesOrphan BlackCrucial Accountability by Kerry PattersonAimeeDesk with cubby holes for catsThe Key to Good Luck Is an Open Mind blog postAJGiteaGitea installerGreenlockJoeSoloJustifiedHenryCelesteZeit Day talksSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAlyssa NichollWard Bell Special Guests: David CramerIn this episode, the JavaScript Jabber panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more!In particular, we dive pretty deep on:David introFounder and CEO of SentryWhat is Sentry?Working with PHPDe-bugger for productionFocus on workflowGoal of SentryTriaging the problemWorkflow managementSentry started off as an open-source side projectInstrumentation for JavaScriptEmber, Angular, and npmGot their start in PythonLogsTotally open-sourceMost compatible with run-timeCan work with any languageDeep contextsDetermining the root causeAnd much, much more!Links:SentryJavaScriptEmberAngularnpmPythonSentry’s GitHub@getsentryDavid’s GitHubDavid’s Website@zeegSponsorsKendo UIFreshBooksLoot CratePicks:CharlesSocks as SwagDavidVS CodeKubernetesSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAJ ONealAimee KnightJoe Eames Special Guests: Jordan EldredgeIn this episode, the JavaScript Jabber panelists discuss Winamp2-js with Jordan Eldredge. Jordan is the creator of Winamp2-js and was inspired to create this media player from the old Winamp media player that he used back in the day. They talk about the importance of limitations, the value of having fun side projects, and pushing the boundaries. They also touch on skin parsing, making Webamp an electron app, and more!In particular, we dive pretty deep on:What is Winamp2-js?The history and future of WinampWACUPWinamp was the first big mp3 player that you could styleWebamp’s features and the technical challenges associated with themWhy JavaScript?Creative solutionsLimitations of browser and creating something that previously existedThe importance of limitationsHadn’t done very much JavaScript prior to this projectOriginally created with jQueryLed him into a career in JavaScriptPushing the boundariesSkin parsing“Bitrot” and making Winamp skins accessible againThe value of side projects, even stupid onesArchitecture docsWhat made you choose React and Redux?Spotiamp (Soptify’s canceled Winamp client)Making Webamp an Electron appWinamp visualizers being ported to the webThe domain name webamp.orgAnd much, much more!Links:Winamp2-jsWebampJavaScriptjQueryArchitecture docsReactReduxjordaneldredge.comJordan’s GitHub@captbaritoneSponsorsKendo UIFreshBooksLoot CratePicks:CharlesJAM XT SpeakerTrelloAJSamson GoMicGreenlock for Web ServersGreenlock for Node.jsAimeeKA Engineering PrinciplesJoe2ality.comWhat if JavaScript wins? Medium postJordanJavaScript GardenRust@winampskinsSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max Wood Special Guests: Ori Zohar and Gopinath ChigakkagariIn this episode, the JavaScript Jabber panelists discuss Cloud-Hosted DevOps with Ori Zohar and Gopinath Chigakkagari at Microsoft Build. Ori is on the product team at VSTS focusing on DevOps specifically on Azure. Gopinath is the group program manager in VSTS primarily working on continuous integration, continuous delivery, DevOps, Azure deployment, etc. They talk about the first steps people should take when getting into DevOps, define DevOps the way Microsoft views it, the advantages to automation, and more!In particular, we dive pretty deep on:Ori and Gopi introVSTS – Visual Studio Team ServicesVSTS gives developers the ability to be productiveDeveloper productivityWhat’s the first big step people should be taking if they’re getting into DevOps?The definition of DevOpsThe people and the processes as the most important pieceDevOps as the best practicesAutomating processesWhat people do when things go wrong is what really countsLetting the system take care of the problemsHave the developers work on what they are actually getting paid forTrend of embracing DevOpsShifting the production responsibility more onto the developer’sIncentivizing developersPeople don’t account for integrationContinuous integrationTrends on what customers are asking forSafetyDocker containersAnd much, much more!Links:AzureMicrosoft BuildVSTS@orizhrOri’s GitHubGopi’s GitHub@gopinachSponsorsKendo UILinodeFreshBooksPicks:Charles.NET Rocks!Shure SM58 MicrophoneZoom H6OriFitbitPacific Northwest HikingGopinathSeattle, WASupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAJ O’Neal Special Guests: Johannes SchicklingIn this episode, the JavaScript Jabber panelists discuss Prisma with Johannes Schickling. Johannes is the CEO and co-founder of GraphCool and works with Prisma. They talk about the upcoming changes within GraphCool, what Prisma is, and GraphQL back-end operations. They also touch on the biggest miscommunication about Prisma, how Prisma works, and much more!In particular, we dive pretty deep on:JSJ Episode 257 MJS Episode 055Raised a seed roundRebranding of GraphCoolWhat are you wanting to do with the seed money you raised?Focused on growing his team currentlyMaking GraphQL easier to doThe change in the way people build softwareWhat is Prisma?Two things you need to do as you want to adopt GraphQLApollo Client and RelayGraphQL on the back-endResolversResolving data in one queryPrisma supports MySQL and PostgreSQLHow do you control access to the GraphQL endpoint that Prisma gives you?Biggest miscommunication about PrismaPrisma makes it easier for you to make your own GraphQL serverApplication schemasHow do you blend your own resolvers with Prisma?And much, much more!Links:JSJ Episode 257 MJS Episode 055GraphCoolPrismaGraphQLApollo ClientRelayMySQLPostgreSQL@schicklingJohannes’ GitHubSchickling.mePrisma SlackSponsorsKendo UILinodeFreshBooksPicks:CharlesAudibleThe 5 Love Languages of Children by Gary ChapmanFacebook Backyard Homesteader GroupsCharlesMaxWood.comSling TVRoku ExpressAJThe Legend of Zelda: Breath of the WildJohannesFigmaNetlify FunctionsGraphQL EuropeSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max Wood Special Guests: Rachel MacFarlane and Matt BiernerIn this episode, the JavaScript Jabber panelists discuss Visual Studio Code with Rachel MacFarlane and Matt Bierner, who are both developers on Visual Studio Code. They talk about what the workflow at Visual Studio Code looks like, what people can look forward to coming out soon,  and how people can follow along the VS Code improvements on GitHub and Twitter. They also touch on their favorite extensions, like the Docker extension and the Azure extension and their favorite VS Code features.In particular, we dive pretty deep on:Rachel and Matt introMonth to month workflow of Visual Studio CodeVS Code JavaScript, TypeScript, and Mark Down supportWorking on GitHub and within the communityCheck out new features incrementally with insidersCommunity driven workWhat is coming out in Visual Studio Code?GitHub helps to determine what they work onWorking on Grid ViewImproved settings UIHighlighting unused variables in your codeImprovements with JS DocsDartVisual Studio Extension APIHow do people follow along with the VS Code improvements?Follow along on GitHub and TwitterDownload VS Code InsidersHave a general road map of what the plan is for the yearTechnical debt weekWhat do you wish people knew about VS Code?Favorite extensionsDocker extension and Azure extensionAnd much, much more!Links:Visual Studio CodeJavaScriptTypeScriptDartVS Code GitHub@CodeVS Code InsidersDocker extensionAzure extensionRachel’s GitHubMatt’s GitHubMattBierner.com@mattbiernerSponsorsKendo UILinodeFreshBooksPicks:CharlesOrphan BlackAvengers: Infinity WarFishingRachelGitLensMattThe Bronx WarriorsSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: AJ O’NealAimee Knight Special Guests: Greg WhitworthIn this episode, the JavaScript Jabber panelists discuss the effects of JavaScript on CSS with Greg Whitworth. Greg works on Microsoft EdgeHTML, specifically working on the Microsoft Layout team, is on the CSS working group, and is involved with the Houdini task force. They talk about JS engines and rendering engines, what the CSSOM is, why it is important to understand the rendering engine, and much more!In particular, we dive pretty deep on:Greg introWhat is the Houdini task force?Extensible web manifestoDOM (Document Object Model)Layout APIParser APIBabeljQueryBack to basicsJavaScript engine and rendering engineWhat is the CSSOM?Every browser has its separate JS engineBrowsers perspectiveAimee ShopTalk Podcast EpisodeWhy is it important to understand how the rendering engine is working?Making wise decisionsGive control back to browser if possibleWhen you would want to use JavaScript or CSSHard to make a hard or fast ruleCSS is more performantOverview of stepsAnd much, much more!Links:Parser APIBabeljQueryAimee ShopTalk Podcast [email protected]’s GitHub SponsorsKendo UILinodeFreshBooksPicks:AJMicrosoft SurfaceMicrosoft CursorAimeeGreg’s TalkWhat Your Conference Proposal Is Missing by Sarah MeiGregAimee ShopTalk Podcast EpisodeJake Archibald Tasks TalkSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max Wood Special Guests: Matt Hernandez and Amanda SilverIn this episode, the JavaScript Jabber/Adventures In Angular, panelists discuss Visual Studio Code and the VS Code Azure Extension with Matt Hernandez and Amanda Silver at Microsoft Build. Amanda is the director of program management at Microsoft working on Visual Studio and VS Code. Matt works on a mix between the Azure and the VS Code team, where he leads the effort to build the Azure extensions in VS code, trying to bring JavaScript developers to Azure through great experiences in VS Code. They talk about what’s new in VS Code, how the Azure extension works, what log points are, and much more!In particular, we dive pretty deep on:Amanda introMatt introWhat’s new in VS Code?VS Code coreVS Live ShareShared TerminalNow have Linux supportLive Share is now public to the world for freeWhat would you use Shared Terminal for?Are there other things coming up in VS Code?Constantly responding to requests from the communityLive Share works for any languageHow does the Azure extension work?Azure App ServiceStorage extensionAzure Cosmos DBWhat are log points?All a part of a larger plan to create a better experience for JS developersVisual debuggersIs it the same plugin to support everything on Azure?Want to target specific services that node developers will take advantage ofAnd much, much more!Links:Visual StudioVS CodeAzureLive ShareAzure Cosmos DBMicrosoft BuildAzure App ServiceAmanda’s GitHub@amandaksilverMatt’s GitHub@fiveisprimePicks:CharlesOrphan BlackShout out to VS Code teamBattle of the BooksMattThe Customer-Driven Playbook by Travis LowdermilkThe Speed of Trust by Stephen M.R. CoveyYes, And by Kelly LeonardDigital Marketing For Dummies by Ryan DeissEd Gets His Power Back KickstarterAmandaMicrosoft Quantum Development Kit for Visual Studio CodeIggy Peck, ArchitectTek by Patrick McDonnellSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: AJ ONealAimee KnightJoe Eames Special Guests: Kyle SimpsonIn this episode, the JavaScript Jabber panelists discuss light functional JavaScript with Kyle Simpson. Kyle is most well-known for writing the books You Don’t Know JS and is on the show today for his book Functional-Light JavaScript. They talk about what functional programming is, what side-effects are, and discuss the true heart behind functional programming. They also touch on the main focus of functional programming and much more!In particular, we dive pretty deep on:You Don’t Know JSFunctional-Light JavaScriptFrom the same spirit as first booksJavaScript Documents journey of learningWhat does Functional Programming mean?Functional programming is being re-awokenMany different definitionsHistory of functional programmingProgramming with functionsWhat is a function?“A collection of operations of doing some task” is what people think functions areWhat a function really isMap inputs to outputsWhat is a side-effect?Side-effects should be intentional and explicitThe heart of functional programmingRefactoringCan’t write a functional program from scratchWhat functional programming focuses onMaking more readable and reliable codePulling a time-stampDefining a side-effectAnd much, much more!Links:You Don’t Know JSFunctional-Light JavaScriptJavaScriptKyle’s GitHub@getifyPicks:AimeeWhat Does Code Readability Mean?@FunctionalKnoxHTTP 203 Podcast AJIKEAJoeBarking Up the Wrong Tree by Eric BarkerWorkshops in generalKyleGDPRThe start-up’s guide to the GDPRHatchFluent ConfSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAimee KnightAJ ONeal Special Guests: Dotan NahumIn this episode, the JavaScript Jabber panelists discuss Hygen with Dotan Nahum. Dotan has worked within open source community, where he created Hygen. They talk about what Hygen is, how it came to be, and code generators in general. He was inspired by the Rails generator to create his own generator and took his inspiration from 12 years prior to creating Hygen. They also touch on how to share generators in separate packages and much more!In particular, we dive pretty deep on:Dotan introWhat is Hygen?Code generatorsRails in 2006Ruby on Rails 15-minute blog videoPHP and PythonCarried Rails wow moment with him into creating HygenWanted Rails generators everywhereCan you also modify files?Took the good things from Rails generatorThe fact that front-end apps have architecture is newReduxThe solution of generating codeA component is a ray of files and assetsJavaScript gives you great freedomA standardized way of doing componentsGraphQLEverything lives in the “day job” projectHow the Hygen template is formattedCan have a shell actionIs there a way to share generators in a separate package?GoAnd much, much more!Links:HygenRailsRuby on Rails 15-minute blog videoPythonReduxJavaScriptGraphQLGo@jondotDotan’s GitHubDotan’s MediumPicks:CharlesFluent ConfHot JarDevChat.tvEthereumAimeeDeep-copying in JavaScriptAJLet’s EncryptNintendo SwitchBreath of the WildDotanasdfBrew CaskSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max Wood Special Guests: Evan HahnIn this episode, the JavaScript Jabber panelists discuss securing Express apps with Helmet.js with Evan Hahn. Evan is a developer at Airtable, which is a company that builds spreadsheet applications that are powerful enough that you can make applications with. He has also worked at Braintree, which does payment processing for companies. They talk about what Helmet.js is, when you would want to use it, and why it can help secure your Express apps. They also touch on when you wouldn’t want to use Helmet and the biggest thing that it saves you from in your code.In particular, we dive pretty deep on:Evan introJavaScript What is Helmet.js?Node and ExpressWhy would you use the approach of Middleware?Helmet is not the only solutionHttp headersCurrent maintainer of Helmet.jsnpmHas added a lot to the project, but is not the original creatorOutbound HTTP response headersHelmet doesn’t fully secure your app but it does help secure itHow does using Helmet work?Are there instances when you wouldn’t want to use Helmet?No cash middlewareWhere do you set the configuration options?Top level Helmet module12 modulesWhat is the biggest thing that Helmet saves you from?Content security policy codeAnd much, much more!Links:AirtableBraintreeJavaScriptHelmet.jsNodeExpressnpmEvan’s Website@EvanHahnEvan’s GitHubPicks:CharlesCameraZoom H6Shure SM58DevChat.tv YoutubeReact Round UpEvanClojureFortuneKantaro: The Sweet Tooth SalarymanSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodCory HouseAJ O’NealAimee Knight Special Guests: Greg KushtoIn this episode, the JavaScript Jabber panelists discuss thwarting insider threats with Greg Kushto. Greg is the vice president of sales engineering for Force 3 and has been focused on computer security for the last 25 years. They discuss what insider threats are, what the term includes, and give examples of what insider threats look like. They also touch on some overarching principles that companies can use to help prevent insider threats from occurring.In particular, we dive pretty deep on:Greg introInsider threats are a passion of hisMost computer attacks come from the inside of the companyInsider threats have changed over timeWhat does the term “insider threats” include?Using data in an irresponsible mannerWho’s fault is it?Blame the company or blame the employee?Need to understand that insider threats don’t always happen on purposeHow to prevent insider threatsVery broad termAre there some general principles to implement?Figure out what exactly you are doing and documenting itDocumentations doesn’t have to be a punishmentKnow what data you have and what you need to do to protect itHow easy it is to get hackedPractical things to keep people from clicking on curious linksThe need to change the gameFighting insider threats isn’t fun, but it is necessaryAnd much, much more!Links:Force 3Greg’s LinkedIn@Greg_KushtoGreg’s BLogPicks:CharlesHaveIBeenPwned.comPlural SightElixir podcast coming soonNG confMicroConfRubyHackMicrosoft BuildCoryPlopVS code sync pluginAimeeAwesome Proposals GitHubAJ O’NealFluffy PancakesThe Mind and the Brain by Jeffrey M. SchwartzGregStormCastSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodCory HouseAimee Knight Special Guests: Ben TitzerIn this episode, the JavaScript Jabber panelists discuss WebAssembly and JavaScript with Ben Titzer. Ben is a JavaScript VM engineer and is on the V8 team at Google. He was one of the co-inventors of WebAssembly and he now works on VM engineering as well as other things for WebAssembly. They talk about how WebAssembly came to be and when it would be of most benefit to you in your own code.In particular, we dive pretty deep on:Ben introJavaScriptCo-inventor of WebAssembly (Wasm)Joined V8 in 2014asm.jsBuilt a JIT compiler to make asm.js fasterTurboFanWhat is the role of JavaScript? What is the role of WebAssembly?SIMD.jsJavaScript is not a statically typed languageAdding SIMD to Wasm was easierEasy to add things to WasmWill JavaScript benefit?Using JavaScript with Wasm pros and consPros to compiling with WasmStatically typed languagesThe more statically typed you are, the more you will benefit from WasmTypeScriptIs WebAssembly headed towards being used in daily application?Rust is investing heavily in WasmWebAssembly in gamingAnd much, much more!Links:JavaScriptV8WebAssemblyasm.jsTurboFanTypeScriptRustWebAssembly GitHubBen’s GitHubPicks:CharlesReady Player One MovieDevChat.tv YouTubeAlexa Flash Briefings: Add skill for “JavaScript Rants”Corynpm Semantic Version CalculatorKent Beck TweetAimeeMDN 418 Status codeQuantity Always Trumps Quality blog postBenAmerican PoliticsSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Joe EamesCory HouseAimee Knight Special Guests: Ben ClinkinbeardIn this episode, the JavaScript Jabber panelists talk about D3.js with Ben Clinkinbeard. D3.js is a JavaScript library that has you use declarative code to tell it what you want and then it figures out all of the browser inconsistencies and creates the notes for you. He talks about the two main concepts behind D3, scales and selections, which once you understand make D3 a lot more user friendly. He then touches on SPGs and discusses his Learn D3 in 5 Days course.In particular, we dive pretty deep on:What is D3.js?Stands for Data Driven DocumentsJavaScriptHow much of the learning curve is attributed to learning D3?SPG2 main concepts behind D3: scales and selectionsIs learning about SPGs a prerequisite to leaning D3?How serious are you talking when saying idiosyncrasies?SPG tagUnderstanding positioning in SPGPositions with CSS transformsAre you required to use SPG?Not required to use SPG with D3CanvasSPG is vector basedSPG utility functionResponseivefyLearn D3 in 5 Days courseIs there and overlap with D3 and React?And much, much more!Links:D3.jsJavaScriptResponsivefyLearn D3 in 5 Days courseReact @bclinkinbeardBen’s GitHubPicks:CoryReact cheat sheet“Why software engineers disagree about everything” by Haseeb QureshiJoe Eames“JavaScript vs. TypeScript vs. ReasonML” by Dr. Axel RauschmayerAimee“How To Use Technical Debt In Your Favor”Neuroscience News TwitterBenComLinkSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAimee KnightAJ ONeal Special Guests: Peggy RayzisIn this episode, the JavaScript Jabber panelists talk about Apollo with Peggy Rayzis. Peggy is an open source engineer on the Apollo team where she primarily focuses on client stuff, working on Apollo Client, and also other libraries. Previously, she was a UI engineer at Major League Soccer where she worked primarily with React and React Native. She discusses what GraphQL is and how it is used, as well as how they use it in the Apollo team to make their lives as developers easier. They also touch on when it would work best to use GraphQL and when it is not ideal to use it.In particular, we dive pretty deep on:AiA 127 EpisodePeggy introWhat is GraphQL?What is a Typed Query Language?What is a schema?Where do schemas get defined?GraphQL SDLApollo Stack and Apollo ServerTracing and cash controlApollo EngineHow GraphQL Replaces ReduxGraphQL cuts down on front-end managementApollo Link StateThe best code is no codeApollo Client allows for greater developer productivityDoes the conversation change if you’re not using Redux or in a different ecosystem?When is the right time to use this?Data doesn’t have to be graph shaped to get the most out of GraphQLAnalyze schema with Apollo EngineIs there a way to specify depth?Max Stoiber blog postHow would people start using this?HowtoGraphQL.comAnd much, much more!Links:React Dev SummitJS Dev SummitApolloAiA 127 EpisodeApollo ClientMajor League SoccerReactReact NativeGraphQLGraphQL SDLApollo ServerApollo EngineHow GraphQL Replaces ReduxApollo Link StateReduxMax Stoiber blog postHowtoGraphQL.com@PeggyRayzisPeggy’s GitHubPeggy’s MediumPicks:CharlesGraphQL RubyWordPress GraphQLHogwarts Battles Board GamePandemic LegacyRisk LegacyAimeeHow GraphQL Replaces ReduxJavaScript Meetup in LAAJSimple.comBroccoliWallet.comThe Four by Scott GallowayPeggyWorkshop.meThanks for the Feedback by Douglas StoneSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodCory HouseAimee KnightJoe EamesAJ O'NealIn this episode, the JavaScript Jabber panelists talk about the Framework Summit. It was the brainchild of Merrick Christensen. This summit includes talks on multiple different frameworks all in a two-day conference, which allows you to get exposed to new frameworks while still learning more about the framework your job requires you to use. Another goal of the conference is that it will be able to open people’s eyes up to the different frameworks available to them and show that no one framework is superior to another.In particular, we dive pretty deep on:What is the Framework Summit?The framework you use plays a huge role in your programmingFor people who want to learn about more than one frameworkAllows you to exploreThe format of the conferencePark City, Utah in October 2018Helps you answer which framework should you use?Goal is to open people’s eyes up to other frameworksDecrease internet arguments over which framework is betterFluent ConferenceGet to have conversation with other people who work in your frameworkMaking connectionsReact Rally Talk Evan CzaplickiThe context mattersBeing able to deep dive into the different frameworksUsing frameworks in conjunction with one anotherHave you seen “religionist” themes in programming frameworks?Why Good People Are Divided by Politics and Religion by Jonathan HaidtSome people will never look beyond their frameworksIf it’s working, why would you mess with it?And much, much more!Links:React Dev SummitJS Dev SummitFramework SummitAngularReactEmberJavaScriptFluent ConferenceReact Rally Talk Evan CzaplickiWhy Good People Are Divided by Politics and Religion by Jonathan Haidt@FrameworkSummitPicks:CharlesParked Out By the Lake Dustin ChristensenDevChat.tvNewspaper by ThemeforestCoryQuokkaAimeeRepublic of Tea – Apple Cider Vinegar TeaThe Way of TestivusJoeEvan Czaplicki TalkAJDinosaursCough Syrup by Young the GiantSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAimee KnightJoe EamesAJ O'Neal Special Guests: Orta TheroxIn this episode, the JavaScript Jabber panelists talk about the tool Danger with Orta Therox. Danger allows you to create cultural rules about your pole request workflow. They discuss what Danger is, how it works, and how it can help you to catch errors and speed up code review. Danger lets you erase discussions so that you can focus on the things that you should really be focusing on, like the code. They also compare Danger to other ways of doing test converge.In particular, we dive pretty deep on:What is DangerJS?Think of it as being on the PR levelProvides an eval contextUsed on larger projectsReact, React Native, Apollo, and RxJSExperimenting with moving Danger onto a serverDanger can run as a linting stepPre-commit hooksPrettierHow do you use Danger on your own machine?Danger Ruby vs Danger JSNPM installHow is using Danger better that other ways of test coverage?What kinds of rules can you write for this system?Can use with Ruby or JavaScriptReact StorybooksRetrospectivesAnd much, much more!Links:React Dev SummitJS Dev SummitDanger JSReactReact NativeApolloRxJSPrettierDanger RubyRubyJavaScriptOrta’s GitHubArtsy BlogPicks:CharlesHogwarts Battle Board GameSushi Go Party! GameNYC tipsAimeeMax Stoiber BlogThe Ultimate Guide to Kicking Ass on Take-home Coding ChallengesJoeSaltCONStuffed Fables Board GameAJUniFi AC LiteFullmetal AlchemistOrtaThe WireWorm Web SerialSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAimee KnightJoe EamesCory HouseAJ O'Neal Special Guests: NoneIn this episode, the JavaScript Jabber panelists talk about React: The Big Picture, Cory’s course on Pluralsight and what React is all about. They discuss both the pros and cons when it comes to using React and when it would be the best to use this library. They also encourage programmers to use React in a more consistent way so that people can share components.In particular, we dive pretty deep on:What is React: The Big Picture course?ReactThe frameworks work with each otherReason and ElmHow to decide when using React is the best option?React tradeoffsJavaScriptReact expects you to do a little more typing and workReact is very close to JavaScriptReact pushes you towards a single file per componentReact Round UpAre the Code Mods as wonderful as they sound?AngularCreate React AppWhat are Code Mods?Lack of opinionated approach in ReactUsing React in a more consistent wayMobX and ReduxStart off using just plain ReactWhen wouldn’t you want to use React?And much, much more!Links:React: The Big PictureCory’s PluralsightReasonElmReactJavaScriptReact Round UpCreate React AppAngularMobXReduxFramework Summit 2018Angular: The Big PictureReact Dev SummitPicks:CharlesHunting HitlerThe Greatest Showman: Sing-a-longAimee“Why being a perfectionist is an obstacle (and how to beat it)” by Gui Fradin“How to understand the large codebase of an open-source project?” blog postJoeMarital Bliss Card GameAJPplwink.comSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAimee KnightCorey HouseAJ O'Neal Special Guests: Ben Coe, Aaron Abramov, and Issac SchleuterIn this episode, the JavaScript Jabber panelists talk with Ben Coe, Aaron Abramov, and Issac Schleuter about test coverage and testing tools. They talk about the different tools and libraries that they have contributed to the coding community, such as NYC, conf, and Jest. They also discuss what test coverage is actually about and when using test coverage tools is necessary.In particular, we dive pretty deep on:What have you contributed to the testing tools community?npmNYC tool and instanbul projectconfJestThese libraries were developed to be easy and have “batteries included”False positives with test coverageEncourage testing practices that don’t practice in a superficial wayTest coverage is about making sure you test every state a public API can get intoThink through the test you’re writing firstBarriers against testingDon’t spike the code too quicklyProvides guardrails for newer developers to contribute to open source projectsUse tests to understand the systemHow to spend your time betterWhen you need testsValue is very short termTDDAnd much, much more!Links:@BenjaminCoe@AaronAbramov_Issac’s GitHubPicks:CharlesReact RoundupViews on VueAdventures in AngularReact Dev Summit 2018AimeeGalentine’s DayDnote CLIAJThe Hero of Ages by Brandon SandersonCoreyWe are hive project guidelinesTip: You can install node as a dependency on your projectBenHack Illinois 2018C8AaronReasonIssacThe Tap 100Krypton AppFriendly Fire PodcastsSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAimee KnightAJ O'Neal Special Guests: Kitson KellyIn this episode, the JavaScript Jabber panelists talk with Kitson Kelly about evaluating web frameworks. Kitson is currently in Australia working for ThoughtWorks as a principle technologist. He has written many articles on frameworks and urges that people don’t get stuck on one framework in their programming. He talks about how using only frameworks that you know could hurt you in the long run. This episode is great for understanding when to use certain JavaScript frameworks and how branching out from what is comfortable might make your job easier.In particular, we dive pretty deep on:Articles on web frameworksHow do you pick a JavaScript framework to use?The framework depends on your changing needsRecommending less popular frameworksAngular, Ember, ReactReact vs ReduxCertain domains with different frameworks?Each framework takes a different approachHow to decide which framework to use?Only give it a couple days to see if your app works with the frameworkIs it ever appropriate to not use a certain framework?Frameworks are there to make your job easierDon’t be afraid to try new frameworksChoose a framework that will “be there tomorrow”What is the future for frameworks?Experiment and be honest with what you needAnd much, much more!Links:LinodeThoughtWorksKendo UILootCrate@KitsonKKitson’s GitHubPicks:CharlesFacebookThe 12 Week Year by Brian P. MooreGoogle Drive for BusinessAimeeWould College Students Retain More If Professors Dialed Back The Pace?URL to PDF ConverterCSS HistoryAJTylenol Cold and Flu SevereKitsonMicrosoft AzureZypeSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAimee KnightCory HouseAJ O'NealJoe EamesAaron Frost Special Guests: Dave GeddesIn this episode, the JavaScript Jabber panelists talk with Dave Geddes about CSS Grids. Dave quit his job about a year ago and has been living the entrepreneur and programmer life since then. Now, he builds mastery games to help people learn CSS. Dave discusses the differences between Flexbox and CSS Grid and how the games that he creates can help people learn CSS Grid in a fun and interactive way.In particular, we dive pretty deep on:CSS Mastery gamesFlexboxZombies.comGridCritters.comUses spaced repetition and delayed recall to learnCSS GridFlexboxCSS Grid as the cake and Flexbox as the frostingEdge specWhat Flexbox can doSub-GridsGeddski.comNesting GridsOld Grid vs New Grid layoutWhy would you move from Flexbox to CSS Grid?CSS Grid toolsGridByExample.comEducation and GamificationPick a UI that interests youFor a discount on Grid Critters: enter JS Jabber for 20% offAnd much, much more!Links:LinodeFlexboxZombies.comGridCritters.comGeddski.comGridByExample.comFreshBooks@GeddskiPicks:CharlesR Pods EarphonesAimeeNEU Cleanse“At Age 6, Girls Are Less Likely to Identify Females As ‘Really, Really Smart’”CoryCory TweetAJHow to Start a StartupMade in America by Sam WaltonJoeThe Dungeoneers by John David AndersonNG ConfAaronFire and Fury by Michael WolffDaveThey Are BillionsSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAimee KnightCory HouseAJ O'NealJoe EamesSpecial Guests: NoneIn this episode, the JavaScript Jabber panelists speak on where they are what they are up to today. Aimee is still in Nashville, Tennessee, and it is currently working at Built Technologies and is working with JavaScript. Cory is still authoring courses for Pluralsite, has more recently been doing consulting with React, and is the principal engineer at Cox Automotive. Joe is doing a lot of Pluralsight work, puts together conferences, and is working on a new podcast with Charles. AJ recently did some side work with Dash, is interested in working on a new domain service, and recently got married. Charles is currently at ngATL conference, and has been attending a lot of conferences recently. He is also starting to head over to the video realm and is creating a new podcast called React Roundup and a View Podcast with Joe. They also talk about what they each have planned in the upcoming year for their careers and their lives.In particular, we dive pretty deep on:Built TechnologiesJavaScriptFront End and Full StackPluralsiteReact consultingCox AutomotiveFront end appsView and React podcastAngular JS to AngularPluralsight coursesBig Picture React coursesFork of Bitcoin called DashNew domain servicengATLReact Roundup PodcastNew podcasts on artificial intelligence, IOT, augmented and virtual reality game development, pythonNode, JavaScript, and RustAnd much, much more!Links:LinodeBuilt TechnologiesPluralsiteCox AutomotiveDashngATLDevChat.tv YoutubeFreshBooksPicks:CharlesATR2100 MicrophoneZoom H6Apple AirPodsngATLngGirlsAimeeImproving Ourselves to DeathWhat Does Code Readability Mean?CoryJavaScript Tip Tweet AJHow to Start a Startup YouTube SeriesSingham Movie JoeWebFlow.comSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: AJ O’NealJoe EamesAimee KnightSpecial Guests: Chris FerdinandiIn this episode, JavaScript Jabber panelist speak with Chris Ferdinandi. Chris teaches vanilla JavaScript to beginners and those coming from a design background. Chris mentions his background in Web design and Web Develop that led him JavaScript development. Chris and the JSJ panelist discuss the best ways to learn JavaScript, as well as resources for learning JavaScript. Also, some discussion of technologies that work in conjunction with vanilla JavaScript.In particular, we dive pretty deep on:Teaching JavaScript - Beginners and Design patronsWeb Design and Web DevelopmentCSS Tricks Todd MottoHow to do jQuery Things without jQueryDoing things like mentors (Todd)When JavaScript makes sense.CSS is easier to learn then JS?Being good at CSS and JS at the same time?How about Node developers?jRuby, DOMDocumentationAnd much more!Links:https://github.com/cferdinandihttps://gomakethings.com @ChrisFerdinandihttps://www.linkedin.com/in/cferdinandi Picks:AJDiscover CardMistborn AimeeYour Smart Phone is Making You Stupid…Crypto CurrencyJoeMystic ValeKediChrishttps://gomakethings.comTeva MushSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodCory HouseJoe EamesAimee KnightSpecial Guests: John PapaIn this episode, JavaScript Jabber panelist speak with John Papa. John has been doing web programming for over twenty years on multiple platforms and has been contributing to the developer communities through conferences, authoring books, videos and courses on Pluralsight.John is on the show to discuss an articles he wrote on A Look at Angular Along Side Vue, and another article on Vue.js  with TypeScript. John talks about the new features with the different versions of Angular technologies, anxiety in the different features, comparisons between the technologies and use case with Angular.In particular, we dive pretty deep on:A look at Angular Along Side Vue - ArticleAngular 5, Amber,Vue,  React, AngularAngular 2 - different featuresCLISpell WebpackComparisons - Why the anxiety?Opinions of Angular and sprinkling in other technologiesVue is the easy to use with AngularAre there breakpoints with the uses case?Choosing technologiesTalk about working with Vue and AngularDSL - Domain Specific LanguageVue and 3rd party librariesTalk about Vue working with TypeScriptVue.js  with TypeScriptVue with TypeScript looks similar to AngularVeturWhat does 2018 have in store for Angular?Native apps and web functionalityAnd much more!Links:https://johnpapa.netVue.js  with TypeScriptA Look at Angular Along Side Vue@john_papahttps://github.com/johnpapaPicks:Coreycypress.ioCharlesE Myth RevisitedProfit First DunkirkAimeeCrucial Conversations Ripple or XRPJoeThe Greatest ShowmanBetter Late Then NeverVue7 Languages In 7 Weeks  - BookJohnJumanji 2017Emotional IntelligenceSpecial Guest: John Papa. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodJoe EamesAimee KnightSpecial Guests: Russell Goldenberg and Adam PearceIn this episode, JavaScript Jabber panelist speak with Russell Goldenberg and Adam Pearce Russell creates visualizations, interactive graphics, and documentaries for the web. Currently an editor at The Pudding.  Adam is a graphics editor at The New York Times and a journalist engineers/developer  Russell and Adam are on the show to talk about what Scrollytelling is, as well as Scrollama. Scrollama is a modern and lightweight JavaScript library for scrollytelling using IntersectionObserver in favor of scroll events. This is a great episode to understand another technology/tool created with JavaScript.In particular, we dive pretty deep on:What is Scrollytelling!Graph Scroll libraryWhat is the intersection Observerable?How long does it take to build an interactive graphic…?How do you test something like this?Test on a lot of different devicesCan you do automated testing?Do you have to understand the use cases or can you implement quickly?Recommendation for getting started?Is this a skill set people have to have before that some on board?How do design these interactions?Scroll jackingWhat JS developers should know about this technology.Position stickyWhat are other uses cases?What can devs use it for?Tax calculatorAnd much more!Links: https://github.com/russellgoldenberg/scrollamahttps://pudding.cool/process/introducing-scrollama/ @codenberg @adamrpearcehttps://pudding.cool/http://russellgoldenberg.github.iohttps://github.com/1wheel?direction=desc&sort=created&tab=starshttps://roadtolarissa.comPicks:AdamDominion - Broad GameCharlesSmokerTiny Epic GalaxiesIndiegogo Dev Chat TVAimeeDeadlinesQuest Protein PowderJoeGiving!Board Game - AzulRusselCrokinoleBust OutSpecial Guests: Adam Pearce and Russell Goldenberg. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodCory HouseJoe EamesAimee KnightSpecial Guests: Azat MardanIn this episode, JavaScript Jabber panelist speak with Azat Mardan. Azat is a return guest, previously on JSJ Episode 230. Azat is an author of 14 books on Node JS, JavaScript, and React JS. Azat works at Capital One on the technology team. Azat is the founder and creator of Node University.Azat is on the show to talk about changes in React and licensing. Some of the topics cover Facebook,  licensing with React, using the wrong version of React, patent wars, and much more in-depth information on current events in React.In particular, we dive pretty deep on:Facebook - Licensing with ReactUsing the Wrong version of React in some companiesBSD licensingPatent warsFacebook developing ReactDifference in Preact and InfernoRewriting applicationsWhat did Capital One do about the changes?React 16Pure ReactWas the BSD patents - Med and Sm CompaniesPatents explainedReact Developers at FacebookFiber - New Core ArchitectureAnd much more!Links:http://azat.cohttps://node.universityhttps://devchat.tv/js-jabber/230-jsj-node-at-capital-one-with-azat-mardanPicks:CoryAxel Rauschmayer postPrettierCharlesIndiegogo for Dev Chatforum.devchat.tvAimeeDev TeesHacker News - Question on Stack Exchange and Estimates JoeHeroku El Camino ChristmasAzatPMP Azat - Short LectureSpecial Guest: Azat Mardan. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max Wood Cory HouseJoe EamesAimee Knight  Special Guests: Ryan GloverIn this episode, JavaScript Jabber panelist speak with Ryan Glover. Ryan is on JavaScript Jabber to talks about Entrepreneurship as a developer.  Ryan runs Clever Beagle in Chicago Illinois. Clever Beagle is a mentorship company that helps people build their first software Product. Ryan and the panel discuss the many roads of entrepreneurship, startup business ideas, servicing and teaching the community, how to’s, and psychological challenges, hiring, seeing your ideas through to the end, and privilege. In particular, we dive pretty deep on:How do you get started as an entrepreneur? Clever BeagleThe Meteor ChefWhere are people getting stuck on the builds? Fear, unknownsSimple, but not easy Drive and ability to step into the unknownSurvival of the fittestHire before you are already Losing your marblesStarting on a smaller scaleHow do I know my idea is going to work? Book - Brick by BrickMultiple lines of businessManaging a portfolio of business Revenue streams Marketing QuitterWhen do I quit? 6-12 months of cash before you quitMaking mistakes in entrepreneurship?Be a reader and studyGo out a read books! Experiential not taught Luck and PrivilegeVideo - Life of Privilege Explained in a $100 RaceProcrastinate on PurposeAnd much more! Links:Clever Beagle The Meteor Chefhttps://www.linkedin.com/in/ryanggloverhttp://www.ryanglover.netBrick by BrickQuitterProcrastinate on PurposeDo Thing That Don’t Scale@rgloverPicks:CoryThe Power of MomentsThe 50th LawCharlesReactDevSummit.comIndiegogo for Dev Chat.NetRocksAimeeLife of Privilege Explained in a $100 RaceJoeEverybody LiesMurder on the Orient Express RyanTurning Pro - Steven Pressfield seriesThe Power of Beliefs in BusinessSpecial Guest: Ryan Glover. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAJ O’NealJoe EamesSpecial Guests: Adam BaldwinIn this episode, JavaScript Jabber panelist speak with Adam Baldwin. Adam is a return guest and has many years of application security experience. Currently, Adam runs the Node Security Project/Node Security Platform, and Lift Security. Adam discusses the latest of security of Node Security with Charles and AJ. Discussion topics cover security in other platforms, dependencies, security habits, breaches, tokens, bit rot or digital atrophy, and adding security to your development.In particular, we dive pretty deep on:What is  the Node Security Project/Node Security PlatformDependency treesNPMTokens and internal dataWhat does Node Security do for me?NPX and NSPCommand Line CILBit Rot or Digital AtrophyHow often should you check repos.AdvisoriesIf I NPM install?Circle CI or TravisNSP CheckWhat else could I add to the securities?Incorporate security as you build thingsHow do you find the vulnerabilities in the NPM packagesTwo Factor authentication for NPMWeak PasswordsOL Dash?Install ScriptsFavorite Security Story?And much more!Links:Node Security Lift Securityhttps://github.com/evilpacket@nodesecurity@liftsecurity@adam_baldwinPicks:AdamKey BaseHave I been Pwned?CharlesNettie Pot convo.comAJThis Episode with Adam BaldwinFree the Future of Radical PriceMade In America Sam WaltonSonic - VGM AlbumJoePych - MovieNG ConfWhy We Don’t SuckSpecial Guest: Adam Baldwin. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodSpecial Guests: Nishant ThackerIn this episode, JavaScript Jabber speaks with Nishant Thacker. Nishant is the technical product manager for all things big data at Microsoft. Nishant mentions the many new technologies and announcements he is in-charge of at Microsoft.Nishant is on the show to talk about Big Data and gives advice on how to process data and acquire deep insight of your customers. This is a great episode to understand the development of data systems that are the backbone of some marketing tools.In particular, we dive pretty deep on:Processing MetricsProcessing into report and usable informationData lakeCollecting data pointsCreating and maintaining the data lake in its raw formScale up engines and limitsCommodity machines and leverageBig data means to scale outSpecialized engines for audio and video filesHow to have a cohesive report?Writing and Querying across dataStoring raw data and retrieve dataData clusterWhat does the data box look like?And much more!Links:https://www.linkedin.com/in/nishantthacker@nishantthackerPicks:NishantRobot ICharlesZoom H6Shure SM 58Lavalier MicsSpecial Guest: Nishant Thacker. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodSpecial Guests: Kirill GavrylyukIn this episode, JavaScript Jabber speaks with Kirill Gavrylyuk. Kirill is a dev manager at Cosmos DB, and works professionally with Azure CosmosDB. Kirill is on JavaScript Jabber to talk about what CosmosDB is in the world of development technology. Chuck and Kirill discuss the nuances of this database technology, how it is implemented, and how to manage and migrate data, among other great features.In particular, we dive pretty deep on:What is Cosmos DB?Bring your data anywhere your users areIt is a websiteMultimodel databaseWorks with Mongodb CassandraStarted as database DBThroughputKey data pairsSwitching from MongoDB to AzureHow do you decide what goes into this? It looks like an everything database.Migration pathUses cases, problems solvedSupporting APIsDoes it only exist in the Cloud? An emulator is available.Subscription info.And much more!Links:@kirillg-msfthttps://www.linkedin.com/in/kirillgavrylyukPicks:KirillShared Debugging with VS Code - KeynoteCharlesUSB Powered Monitor on Amazon    Special Guest: Kirill Gavrylyuk. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel:Charles Max Wood Aimee KnightAJ O’NealJoe Eames Special Guests: Gareth McCumskeyIn this episode, JavaScript Jabber speaks with Gareth McCumskey about Serverless For JavaScript. Gareth leads the dev team at Expat Explore in Cape Town, South Africa. Gareth and this team specialize in exploring the Serverless realm in JavaScript. The JavaScript Jabbers panel and Gareth discuss the many different types of serverless systems, and when to implement them, how serverless system work, and when to go in the direction of using Serverless. In particular, we dive pretty deep on:What does it mean to be Serverless? Since platform as a service.Microservice on Docker Firebase“no backend” Backend systems Cloud functions and failure in systems How do you start to think about a serverless system? How do decide what to do?AWS Lambda Working in a different vendorNode 4 Programming JS to deploy Using libraries for NPMHow is works with AWS LambdaWhere is the database?More point of failure? Calls to Slack?AuthenticationMicro ServicesElastic Bean StalkStatic Assets, S3, ManagingTesting the services Integration testingAnd much more! Links:@[email protected]://github.com/garethmccserverless.comPicks:AimeeServerless Architectures NG-BE Conference AJDocumentary on EnronHard Thing about Hard Things CharlesServerless FrameworkThe Storm Light Achieves Avengers: Infinity WarGarethBuilding MicroServices Skeptics Guide To The Universe PodcastExpate Explore Joe Wonder -  MovieGloom In Space - Board Game  Special Guest: Gareth McCumskey. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: Charles Max WoodAimee KnightCorey HouseJoe EamesSpecial Guests: In this episode, JavaScript Jabber speaks with Dirk Hohndel about Open Source Software. Dirk is the Chief Open Source Officer at VMWare and has been working with open source for over 20 years. Dirk duties as the Chief Open Source Officer is to engage with the open source community and help promote the development between the community, companies, and customers.Dirk provides historical facts about open sources to current processes. The discussion covers vision and technological advances with languages, security, and worries of using open source software, view/consumption and burnout on maintaining a project. This is a great episode to learn about more different avenues of Open Source.In particular, we dive pretty deep on:What does the Chief Open Source Officer do?What is really different and has stayed the same in open source?Technological advancesGood engineering and looking ahead or forward100 million lines of code running a car…This is in everything..Production environmentsSecurityBugs in the software and the security issuesScaling and paying attentionWhere should we be worried about open sourceNotation and data setsWrite maintainable softwareHow does VMWare think about open source?View and Consumption of open sourceThe burnout of open source projects - how to resolve this abandonmentTo much work to maintain open source  - not a money issueScaling the team workload not the moneyContribution and giving backCompanies who do and don’t welcome open sourceWhat to do to make a project open source?Adopting an APIAnd much more!Links:@_drikhhVMWareDrikhh - everywhere!https://github.com/dirkhhPicks:AimeeDe Contact Dodow DirkTrack This Critical ThinkingCharlesNicholas Zakas - Books CoreyFun Fun Function ShowJoeDice ForgeConcept of empathy  Special Guest: Dirk Hohndel. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel:Charles Max WoodSpecial Guests: Chris DiasPJ MeyerIn this episode, Charles is at Microsoft Connect 2017 in NYC. Charles speaks with Chris Dias and PJ Meyer about Visual Studio Code and Live Sharing. Chris and PJ explain more on their demo at Microsoft Connect on Live Collaborative Editing and Debugging. Learn more about the new features with Visual Studio Code and the efficient workflows with screen sharing, and much more.In particular, we dive pretty deep on:Demo of Live Collaborative Editing and Debugging explainedNew Features with VS CodeDeveloper productiveDebugging pain pointsGetting feedbackNew in VS CodeLanguage support and Java DebuggerLive ShareDebugging from different machines and platformsMulti-Stage Docker FileTypeScript compilerMore on debugging with Cosmos dbDebugging in the Cloud?Docker ExtensionsData BricksUpdated python toolsComing up with Visual Studio Code in the next 6 monthsTypeScript and RefactoringGetting the word out about code -  Word of mouth?Number of people using VS Code?Envision for what VS Code is becoming?Preparing for a keynote and processes?And much more!Links:https://code.visualstudio.comhttps://github.com/chrisdiasGitHub.com/microsoft@codePicks:ChrisPizzaPJDeliCharlesCoupon Pass for tourist in NYC Special Guests: Chris Dias and PJ Meyer. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Charles Max WoodSpecial Guests: Amanda SilverIn this episode, Charles is at Microsoft Connect 2017 in NYC. Charles speaks with Amanda Silver. Amanda is deemed the  TypeScript and future of JavaScript guru, and this year's speakers at Microsoft Connect with Visual Studio Live Share. Amanda shares what is new with TypeScript and how that is a kind of subscript to JavaScript. Amanda explains the big picture of TypeScript’s inception and where she believes the language will be most efficient and effective for JavaScript and TypeScript developers.In particular, we dive pretty deep on:What is new in TypeScript?Keep JavaScript and TypeScript alignedTypeScript is implemented to create larger scaled applicationsIntegration with VS Code, etc.Building better tools for JavaScript DevelopersWhen would this be taken on by usersDefaults in Visual StudioTypeScript replacing JavaScript type serviceTypeScript is written in TypeScriptChakra runtimeDiasporaThe different faces of JavaScriptOptimized JavaScript runtimeLanguages should be created with toolingA satisfying tooling experienceFoot GunsNew TokensEco-systems and metadataMulti-phaseMinimum common denominator constantly changingCollaborating on the same codeOpen Source and the impactHow to move to open sourceContributingThe next thing for TypeScriptThe future of JavaScriptAnd much more!Links:@amandaksilver Picks:AmandaVisual Studio Live ShareInstinct of learning technologyCharlesVisual Studio Live ShareAI   Special Guest: Amanda Silver. Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.