JavaScript Jabber

JavaScript Jabber

Download on the App Store

JavaScript Jabber episodes

  • JSJ 339: Node.js In Motion Live Video Course from Manning with PJ Evans
    Panel: 
    • Aimee Knight
    • AJ O’Neal
    • Charles Max Wood
    Special Guest: PJ EvansIn this episode, the panel talks with PJ Evans who is a course developer and an instructor through Manning’s course titled, “Node.js in Motion.” This course is great to learn the fundamentals of Node, which you can check out here! The panel and PJ talk about this course, his background, and current projects that PJ is working on. Check out today’s episode to hear more!Show Topics:0:00 – Advertisement: KENDO UI 0:36 – Chuck: Welcome and our panel consists of Aimee, AJ, myself, and our special guest is PJ Evans. Tell us about yourself and your video course! NODE JS in Motion is the title of the course. Can you tell us more?1:29 – PJ: It’s a fantastic course. 2:25 – Chuck: You built this course and there is a lot to talk about.2:36 – Aimee: Let’s talk about Node and the current state. 2:50 – Chuck: Here’s the latest features, but let’s talk about where do you start with this course? How do you get going with Node? What do people need to know with Node?3:20 – Aimee.3:24 – PJ talks about Node and his course! 4:02 – PJ: The biggest headache with Node is the...4:13 – Chuck.4:19 – PJ: I am sure a lot of the listeners are familiar with callback hell.4:50 – Aimee: Let’s talk about the complexities of module support in Node!5:10 – PJ: It’s a horrible mess.5:17 – Aimee: Maybe not the tech details but let’s talk about WHAT the problem is?5:31 – PJ: You are talking about Proper Native ES6 right?They are arguing about how to implement it. 6:11 – PJ: My advice is (if you are a professional) is to stick with the LT6 program. No matter how tensing those new features are!6:46 – Aimee: It could be outdated but they had to come back and say that there were tons of complexities and we have to figure out how to get there.7:06 – PJ: They haven’t found an elegant way to do it.7:15 – Panel: If it’s a standard why talk about it?Seriously – if this is a standard why not implement THE standard?7:38 – PJ.8:11 – Panel.8:17 – Aimee: I would love to talk about this, though!8:24 – Chuck: I want to talk about the course, please.8:30 – PJ.8:54 – Chuck: We will keep an eye on it.9:05 – PJ.9:16 – PJ: How is it on the browser-side?9:33 – Aimee: I don’t want to misspeak.9:41 – Chuck: I don’t know how complete the forms are.9:49 – Aimee: I don’t want to misspeak.9:56 – PJ: I just found the page that I wanted and they are calling it the .MJS or aka the Michael Jackson Script. You can do an import from...Some people think it’s FINE and others think that it’s a TERRIBLE idea.10:42 – Chuck: “It sounds like it’s a real THRILLER!” 10:52 – Panel.11:25 – Panel: When you start calling things the Michael Jackson Solution you know things aren’t well.11:44 – Aimee: Just to clarify for users...11:57 – Chuck: I want to point us towards the course: NODE.JS.Chuck asks two questions. 12:34 – PJ: The concepts aren’t changing, but the information is changing incredibly fast. The fundamentals are fairly settled.13:22 – Chuck: What are those things?13:28 – PJ talks about how he structured the course and he talks about the specifics.  15:33 – Chuck: Most of my backend stuff is done in Ruby. Aimee and AJ do more Java then I do.15:55 – Panel: I think there is something to understanding how different Node is. I think that Node is a very fast moving train. Node has a safe place and that it’s good for people to know about this space.16:34 – Aimee: Not everyone learns this way, but for me I like to understand WHY I would want to use Node and not another tool. For me, this talk in the show notes really helped me a lot. That’s the core and the nature of NODE.17:21 – PJ: Yes, absolutely. Understanding the event loop and that’s aimed more towards people from other back ends. Right from the beginning we go over that detail: Here is how it works, we give them examples, and more.18:08 – Aimee: You can do more than just create APIs. Aimee mentions Vanilla Node. 18:50 – PJ: To get into frameworks we do a 3-line server. We cover express, and also Sequelize ORM. 19:45 – Advertisement – Sentry.io 20:43 – Chuck: I never used Pug.20:45 – PJ: PUG used to be called JADE. 20:56 – Aimee.21:14 – PJ: Express does that for you and I agree with you. I advocate a non-scripted approach, I like when frameworks have a light touch.22:05 – Aimee: That’s what I liked about it. No offense, Chuck, but for me I didn’t like NOT knowing a lot of what was not happening under the hood. I didn’t want to reinvent the wheel, but I wanted to build at a lower level.22:40 – PJ: I had the same experience. I wanted to figure out why something wasn’t working.23:24 – Panel: I had a friend who used Rails...he was cautious to make a switch. This past year he was blown away with how much simpler it was and how fast things were.24:05 – Aimee: I feel like if you want to learn JavaScript then Node might be easier on the frontend.24:21 – Chuck: No pun intended.No, but I agree. I like about Rails is that you had well-understood patterns. But the flipside is that you have abstractions...To a certain degree: what did I do wrong? And you didn’t follow the pattern properly.25:57 – Panel: With Node you get a little bit of both. To me it’s a more simple approach, but the downside is that you have 100’s of 1,000’s of modules that almost identical things. When you start reaching out to NPM that...26:29 – PJ: Yes the module system of NPM is the best/worst thing about NODE. I don’t have an answer, honestly.There is a great article written that made me turn white. Here is the article! 28:12 – Panel: The same thing happened with the ESLint. That was the very problem that he was describing in the article.28:50 – PJ: Yep, I put that in the chat there – go ahead and read it! It’s not a problem that’s specific to Node, there are others. It’s the way we do things now.29:23 – Chuck: We have the NODE Security project. A lot of stuff go into NPM everyday.29:43 – PJ: We cover those things in the course.29:53 – Chuck: It’s the reality. Is there a place that people get stuck?30:00 – PJ answers the question.30:23 – Aimee.30:55 – PJ: I am coding very similar to my PHP days.31:20 – Aimee.32:02 – PJ: To finish off my point, I hope people don’t loose sight.32:18 – Aimee.32:20 – PJ: I am working on a project that has thousands of requests for...32:53 – Chuck: Anything you WANTED to put into the course, but didn’t have time to?33:05 – PJ: You can get pretty technical. It’s not an advanced course, and it won’t turn you into a rock star. This is all about confidence building. It’s to understand the fundamentals.It’s a runtime of 6 hours and 40 minutes – you aren’t just watching a video. You have a transcript, too, running off on the side. You can sit there and type it out w/o leaving – so it’s a very interactive course.34:26 – Chuck: You get people over the hump. What do you think people need to know to be successful with Node?34:38 – PJ answers the question. PJ: I think it’s a lot of practice and the student to go off and be curious on their own terms.35:13 – Chuck: You talked about callbacks – I am thinking that one is there to manage the other?35:31 – PJ answers the question. PJ: You do what works for you – pick your style – do it as long as people can follow you. Take the analogy of building a bridge.36:53 – Chuck: What are you working on now?37:00 – PJ: Educational tool called SCHOOL PLANNER launched in Ireland, so teachers can do their lesson planning for the year and being built with Express.Google Classroom and Google Calendar.39:01 – PJ talks about Pi and 4wd. See links below. 40:09 – Node can be used all over the place!40:16  - Chuck: Yes, the same can be said for other languages. Yes, Node is in the same space.40:31 – PJ: Yep!40:33 – Chuck: If people want to find you online where can they find you?40:45 – PJ: Twitter! Blog! 41:04 – Picks!41:05 – Advertisement – eBook: Get a coder job! Links:
    • JavaScript
    • jQuery


    Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.
    50 min
  • MJS 084: Henry Zhu

    Panel: Charles Max Wood

    Guest: Henry Zhu

    This week on My JavaScript Story, Charles speaks with Henry Zhu who is working full-time on Babel! They discuss Henry’s background, past/current projects, Babel, and Henry’s new podcast. Check-out today’s episode to hear more!

    In particular, we dive pretty deep on:

    0:00 – Advertisement: Get A Coder Job!

    1:00 – Chuck: Today we are talking with Henry Zhu! You are the maintainer of Babel – and we have had you on the show before. Anything else?

    1:25 – Henry: I used to work with Adobe and now live in NY.

    1:44 – Chuck: Episode 321 we talked to you and you released Babel 7. Tell us about Babel, please.

    2:01 – Henry: It’s a translator for programming languages and it’s a compiler. It only translates JavaScript to JavaScript. You would do this because you don’t know what your users’ are using. It’s an accessibility thing as well.

    3:08 – Chuck: Later, we will dive into this some more. Let’s back-up: how did you get into programming?

    3:22 – Henry: I think I was in middle school and I partnered with a friend for science class and we made a flash animation about earthquakes. Both of my parents worked in the field, too. They never really encouraged me to do it, but here I am.

    4:07 – Chuck: How did you get into Java?

    4:11 – Henry: I made some games and made a Chinese card game. Then in college I went to a bunch of Hackathons. In college I didn’t major into computer science, but I took a bunch of classes for fun. I learned about Bootstrap and did a bunch of things with that.

    5:12 – Chuck: How did you settle on JavaScript?

    5:28 – Henry: It was my experience – you don’t have to download anything. You can just open things up in the console and it’s easy to share. I think I like the visual part of it and their UI.

    6;07 – Chuck: At some point you ran across Babel – how did you get into that?

    6:17 – Henry: After college I wanted to do software. I threw out my degree of industrial engineering. I tried to apply to Google and other top companies. I applied to various places and picked something that was local. I met Jonathan Neal and he got me into open source. Through that, I wanted to contribute to Angular, but it was hard for me. Then I found a small issue with a linting error. After that I made 30 commits to Angular. I added a space here and there. JSES is the next thing I got involved with. There is one file for the rule itself and one for the test and another for the docs. I contributed there and it was easy. I am from Georgia and a year in I get an email through Adobe. They asked if I wanted to work through Enhance in Adobe. I moved to NY and started working here. I found JS LINT, and found out about Babel JS LINT. And that’s how I found about Babel.

    9:24 – Chuck: Was Sebastian still running the project at the time?

    9:33 – Henry.

    10:53 – Chuck: It seems like when I talk with people that you are the LEAD on Babel?

    11:07 – Henry: I guess so, because I am spending the most time on it. I also quit the job to work on it. However, I want people to know that there are other people out there to give you help, too.

    11:45 – Chuck: Sebastian didn’t say: this is the guy that is the lead now. But how did that crystalize?

    12:12 – Henry: I think it happened by accident. I stumbled across it. By people stepping down they stepped down a while ago and others were helping and making changes. It was weird because Sebastian was going to come back.

    It’s hard when you know that the person before had gotten burnt-out.

    14:28 – Chuck: What is it like to go fulltime on an open source project and how do you go about it?

    14:34 – Henry: I don’t want to claim that you have to do it my way. Maybe every project is different. Maybe the focus is money. That is a basic issue. If your project is more of a service, then direct it towards that. I feel weird if I made Babel a service. For me it feels like an infrastructure thing I didn’t want to do that.

    I think people want to do open source fulltime, but there are a lot of things to take into consideration.

    16:38 – Chuck.

    16:50 – Guest.

    16:53 – Henry.

    16:55 – Chuck: How do you pay the bills?

    17:00 – Henry: Unlike Kickstarter, Patreon is to help donate money to people who are contributing content.

    If you want to donate a lot then we can tweak it.

    19:06 – Chuck: Is there something in particular that you’re proud of?

    19:16 – Henry: I worked on JS ES – I was a core team member of that. Going through the process of merging them together was quite interesting. I could write a whole blog post about that. There are a lot of egos and people involved. There are various projects.

    Something that I have been thinking about...

    20:53 – Chuck: What are you working on now?

    20:58 – Henry: We released 7 a while ago and 7.1. Not sure what we are going to do next. Trying to figure out what’s important and to figure out what we want to work on. I have been thinking long-term; for example how do we get reviewers, among other things. I can spend a lot of time fixing bugs, but that is just short-term. I want to invest ways to get more people in. There is a lot of initiatives but maybe we can do something new. Maybe pair with local universities. Maybe do a local Meetup? Learning to be okay with not releasing as often. I don’t want to put fires out all day. Trying to prioritize is important.

    23:17 – Chuck.

    23:2 – Henry: Twitter and other platforms.

    23:37 – Chuck: Picks!

    23:38 – Advertisement – Fresh Books! 30-Day Trial!

    24:45 – Picks.

    Links:

    • React
    • Angular
    • Vue.js
    • JavaScript
    • Ember
    • Elm
    • jQuery
    • Henry Zhu’s Twitter
    • Henry Zhu’s GitHub
    • Henry Zhu’s Website
    • Patreon to Donate Towards Babel
    • Babel
    • Babel JS
    • Sponsors:

      • Cache Fly
      • Get A Coder Job
      • Fresh Books
      • Picks:

        Henry

        • My own podcast – releasing it next week
        • Podcast about Faith and Open Source
        • Charles

          • Ruby Rogues’ cohost + myself – Data Podcast – DevChat.Tv
          • Reworking e-mails
          • 28 min
          • JSJ 338: It’s Supposed To Hurt, Get Outside of Your Comfort Zone to Master Your Craft with Christopher Buecheler
            Panel: 
            - http://www.aimeemarieknight.com
            - AJ O’Neal
            - Aaron Frost
            - https://2013.boston.wordcamp.org/speakers/
            Special Guests: https://www.linkedin.com/in/cwbuecheler In this episode, the panel talks with https://www.linkedin.com/in/cwbuecheler who is an author, blogger, web developer, and founder of CloseBrace. The panel and Christopher talk about stepping outside of your comfort zone. With a technological world that is ever changing, it is important to always be learning within your field. Check out today’s episode to learn more!Show Topics:0:00 – https://www.telerik.com/kendo-ui?utm_campaign=kendo-ui-awareness-jsjabber&utm_medium=social-paid&utm_source=devchattv 1:08 – Aimee: Our guest is Christopher Buecheler – tell us about yourself and what you do.1:22 – https://www.linkedin.com/in/cwbuecheler I run a site and help mid-career developers. I put out a weekly newsletter, too.2:01 – Aimee: It says that you are a fan of “getting comfortable being uncomfortable”?2:15 – Guest: I am a self-taught developer, so that means I am scrambling to learn new things all the time. You are often faced with learning new things. When I learned React I was dumped into it. The pain and the difficulty are necessary in order to improve. If you aren’t having that experience then you aren’t learning as much as you could be.3:26 – Aimee: I borrow lessons that I learned from ice-skating to programming.3:49 – Guest: I started running a few years ago for better health. It was exhausting and miserable at the start and wondered why I was doing it. Now I run 5 times a week, and there is always a level of being uncomfortable, but now it’s apart of the run. It’s an interesting comparison to coding. It’s this idea of pushing through.5:01 – Aimee: If you are comfortable you probably aren’t growing that much. In our industry you always have to be learning because things change so much!5:25 – Guest: Yes, exactly. If you are not careful you can miss opportunities.6:33 – Panel: You have some ideas about frameworks and libraries – one thing that I am always anxious about is being able to make sense of “what are some new trends that I should pay attention to?” I remember interviewing with someone saying: this mobile thing is just a fad. I remember thinking that she is going to miss this opportunity. I am worried that I am going to be THAT guy. How do you figure out what sort of things you should / shouldn’t pay attention to?7:47 – Guest: It is a super exhausting thing to keep up with – I agree. For me, a lot of what I pay attention to is the technology that has the backing of a multi-million dollar company then that shows that technology isn’t going anywhere, anytime soon. The other thing I would look at is how ACTIVE is the community around it?9:15 – Panel: Is there a strategic way to approach this? There is so many different directions that you can grow and push yourself within your career? Do you have any kinds of thoughts/tips on how you want your career to evolve?10:00 – Guest: I am trying to always communicate better to my newsletter audience. Also, a good approach, too, is what are people hiring for? 11:06 – Aimee: Again, I would say: focus on learning.11:30 – Panel: And I agree with Aimee – “learn it and learn it well!”12:01 – Panel: I want to ask Chris – what is https://blog.closebrace.com 12:17 – Guest: I founded it in November 2016, and started work on it back in 2013.14:20 – Panel: It was filled with a bunch of buzz worthy words/title.14:32 – Guest continues his thoughts/comments on https://blog.closebrace.com 16:54 – Panel: How is the growth going?17:00 – Guest: It is growing very well. I put out a massive, massive tutorial course – I wouldn’t necessarily advice that people do this b/c it can be overwhelming. However, growth this year I have focused on marketing. I haven’t shared numbers or anything but it’s increased 500%, and I am happy about it.18:05 – Panel: Are you keeping in-house?18:13 – Guest: I think it would be cool to expand, but now it is in-house. I don’t want to borrow Egg Head’s setup. I would love to cover MORE topics, though.19:05 – Panel: You are only one person.19:08 – Guest: If I can get the site creating more revenue than I can hire someone to do video editing, etc.19:35 – Panel: I think you are overthinking it.19:45 – Guest.19:47 – https://sentry.io/welcome/ 20:47 – Guest.21:30 – Aimee: There are SO many resources out there right now. Where do you think you fit into this landscape?21:44 – The landscape is cluttered, but I feel that I am different b/c of my thoroughness. I don’t always explain line by line, but I do say how and why things work. I think also is my VOICE. Not my radio voice, but the tone and the approach you take with it.23:25 – Panel: I was trying to copy folks in the beginning of my career. And at some point I realized that I needed to find my own style. It always came down to the reasons WHY I am different rather than the similarities. Like, Chris, you have these quick hits on CloseBrace, but some people might feel like they don’t have the time to get through ALL of your content, because it’s a lot. For me, that’s what I love about your content.24:46 – Christopher: Yeah, it was intentional.25:36 – Panel: Good for you.25:49 – https://www.linkedin.com/in/cwbuecheler I am super device agnostic: Android, Mac, PC, etc. I have a lot of people from India that are more Microsoft-base.26:28 – Aimee: I think Egghead is pretty good about this...do you cover testing at all with these things that you are doing? It’s good to do a “Hello World” but most of these sites don’t get into MORE complex pieces. I think that’s where you can get into trouble. It’s nice to have some boiler point testing, too.27:18 – Guest answers Aimee’s question. 28:43 – Aimee: We work with a consultancy and I asked them to write tests for the things that we work with. That’s the value of the testing. It’s the code that comes out.29:10 – Panel: Can you explain this to me. Why do I need to write tests? It’s always working (my code) so why do I have to write a test?29:39 – Guest: When working with AWS I was writing...31:01 – Aimee: My biggest thing is that I have seen enough that the people don’t value testing are in a very bad place, and the people that value testing are in a good place. It even comes back to the customers, because the code gets so hard that you end up repeatedly releasing bugs. Customers will stop paying their bills if this happens too often for them.33:00 – Panel: Aimee / Chris do you have a preferred tool? I have done testing before, but not as much as I should be doing.33:25 – Aimee: I like https://jestjs.io and https://github.com/smooth-code/jest-puppeteer 33:58 – Guest: I like https://jestjs.io, too.34:20 – Aimee: Let’s go to PICKS!34:35 – 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
            - http://closebrace.com
            - https://jestjs.io
            - https://github.com/smooth-code/jest-puppeteer
            - https://podflix.app
            - https://github.com/wting/autojump
            - https://brutalist-web.design
            - https://www.youtube.com/watch?v=QrR_gm6RqCo
            - https://balloonfiesta.com
            - https://www.docz.site
            - http://closebrace.com
            - http://cwbuecheler.com
            - https://www.linkedin.com/in/cwbuecheler
            - https://github.com/cwbuecheler
            - https://gomakethings.com
            Sponsors:
            -

            Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.
            44 min
          • MJS 083: Christine Legge

            Panel: Charles Max Wood

            Guest: Christine Legge

            This week on My JavaScript Story, Charles speaks with Christine Legge who is a computer software engineer who works for Google in New York. Previous employment includes Axiom Zen, and Vizzion, Inc. She and Chuck talk about her background, past and current projects, and her future goals.

            In particular, we dive pretty deep on:

            1:07 – Hello!

            1:10 – Chuck: You were on Episode 328 in the past. Tell us about yourself!

            1:24 – Christine: I started working with Google about 2 weeks ago. In the past I worked in Vancouver, Canada.

            2:05 – Chuck: Let’s start with how you got into programming?

            2:14 – Christine: When I was in HS I wasn’t interested at all into computers. I wanted to do applied math in Toronto Canada for college. For engineering you have to take an introduction to programming in the 1st year. I had a 4-hour computer science course in the morning and I dreaded it. I dropped out 3 months later b/c I didn’t like the program. Surprisingly, enough, I did like the computer science course. I went back to Vancouver and I said to my parents that I wanted an office job. I went to the YMCA center and wanted to be hired. The man there asked if I had any interest in data entering, and I started working for him. I worked 4 hours a week with him where he taught me C+. I decided to go back to school for it.

            5:37 – Chuck: What did you like about it?

            5:43 – Christine: I liked the problem solving part of it. I like how you can break things down. The technology doesn’t interest me that much, but I like the problem-solving aspect. The guy wasn’t that up-to-date with the newest technologies either.

            6:53 – Chuck: You have a 4-year degree in computer science.

            7:05 – Yes that and statistics, too.

            7:13 – Chuck: I was going to say “nerd.”

            How do you go from desktop applications to web apps?

            7:25 – Christine: I worked with a company part-time and fulltime depending on the year/season.

            I didn’t know what web development was but I thought that THAT was computer science. I thought that if I knew how to do web development then I was going to be good to go. This company asked: What do you want to do? And I answered that I wanted to do web development b/c I thought that’s what I was lacking. I basically got thrown into it. I didn’t understand anything at all. It took me to write one line of CSS and it took 4 hours.

            10:35 – Why did JavaScript attract you more so than C# or other languages that you’ve used?

            10:43 – It’s simpler and you don’t need a lot of setup; from top to bottom. I am working in typescript, I like it even more, but I like how Java is more free to do what you want. I like functional programming in JavaScript. I like the big community for Java, and there are tons of applications for it. I really like how flexible the language is. You can do functional and oriented or you can combine the two. You aren’t constrained.

            12:00 – Chuck: You get in, you work through JavaScript, were you only doing backend?

            12:14 – Christine: Yep, backend.

            13:00 –Chuck: I know you talked at the conference, and what are you most proud of?

            13:14 – Christine: To be honest, no. My mentor (Pablo) at the last company – he wrote a book about D3. He started learning and writing the book. To me that I had thought that all these people are experts from the get go. I realized that everyone has to start somewhere to eventually become an expert. I do want to make an impact even outside of my job. I don’t have anything new that I’ve been working on. It’s a goal for me within the next couple of months.

            15:30 – Chuck: I understand that.

            15:36 – Christine: I haven’t found that balance, yet. When I gave that talk during Developer Week I was moving and stressed out. “I am NEVER doing this again!” It was over and it was very rewarding. People gave good feedback, and I would like to do that again.

            16:56 – Chuck: People have different experience with that kind of stuff. People are interested in different things. So you’ve been working on moving and all that stuff right? What would you like to dive back into?

            17:32 – Christine: Yes we are using Angular 2 and typescript and a Reactive Library. Angular is interesting to me. I would like to dive into the dependency injection in Angular. I really like typescript.

            19:24 – Chuck: Have you looked at resources?

            19:39 – Christine: I read the documentation so far. Like for React I just read the documentation but I haven’t found a central source just, yet. Not a single source. The docs are okay to get started but I haven’t found that they were enough.

            20:50 – Chuck: This is about your story. I worked through the Tour of Heroes, and that helped me with Angular. It’s in the Angular Documentation.

            21:23 – Christine: When you are starting at a new job I want to make sure I’m settled-in. And now I want to start thinking at a high-level of how these things work. I think the cool thing working here is that you can talk to the people who are working on Angular and get some insight that way.

            22:27 – Chuck: People are usually very approachable.

            22:34 – Christine: Yes, I agree. To be apart of the communities people want you to use their stuff.

            22:48 – Chuck: Do you have another talk in mind when you are ready to give your next talk?

            22:59 – Christine: Not sure. I have one thing on my list right now and that’s it.

            23:42 – Chuck: I haven’t looked at RJX documentation but I think it’s pretty easy to pick-up. Ben who is the main developer RJX joined the team last year.

            24:04 – Christine: It’s a lot of promises. When I figure it out that’s how something would work if it were a promise then I can usually get there.

            24:25 – Chuck: Yeah.

            24:38 – Christine: I kind of want to make connections in the office rather than me trying to do myself. I don’t want to waste time. Working on those connections would be good.

            25:20 – Chuck: Let’s do some picks!

            25:30 – Advertisement – Fresh Books! 30-Day Trial!

            Links:

            • React
            • Angular
            • Vue.js
            • JavaScript
            • Ember
            • Elm
            • jQuery
            • Christine Legge’s LinkedIn
            • Christine Legge’s Twitter
            • Christine Legge’s GitHub
            • Sponsors:

              • Cache Fly
              • Get A Coder Job
              • Fresh Books
              • Picks:

                Charles

                • My Calendar Software – BusyCal and Google Calendar
                • Google Calendar just started appointment slots
                • Christine

                  • Podcast: The Pitch
                  • Podcast: How I Built This
                  • 35 min
                  • JSJ 337: Microstates.js – Composable State Primitives for JavaScript with Charles Lowell & Taras Mankovski
                    Panel: 
                    • Aimee Knight
                    • Charles Max Wood
                    • Joe Eames
                    • AJ O’Neil
                    • Chris Ferdinandi 
                    Special Guests: Charles Lowell (New Mexico) & Taras Mankovski (Toronto)In this episode, the panel talks with two special guests Charles and Taras. Charles Lowell is a principle engineer at Frontside, and he loves to code. Taras works with Charles and joined Frontside, because of Charles’ love for coding. There are great personalities at Frontside, which are quite diverse. Check out this episode to hear about microstates, microstates with react, Redux, and much more!Show Topics:1:20 – Chuck: Let’s talk about microstates – what is that?1:32 – Guest: My mind is focused on the how and not the what. I will zoom my mind out and let’s talk about the purposes of microstates. It means a few things. 1.) It’s going to work no matter what framework you are using. 2.) You shouldn’t have to be constantly reinventing the wheel. React Roundup – I talked about it there at this conference. Finally, it really needs to feel JavaScript. We didn’t want you to feel like you weren’t using JavaScript. It uses computer properties off of those models. It doesn’t feel like there is anything special that you are doing. There are just a few simple rules. You can’t mutate the state in place. If you work with JavaScript you can use it very easily. Is that a high-level view?7:13 – Panel: There are a lot of pieces. If I spoke on a few specific things I would say that it enables programming with state machines.7:42 – Panel: We wanted it to fell like JavaScript – that’s what I heard.7:49 – Aimee: I heard that, too.7:59 – Guest.8:15 – Aimee: Redux feels like JavaScript to me.8:25 – Guest: It’s actually – a tool – that it feels natural so it’s not contrived. It’s all JavaScript.8:49 – Panel.9:28 – Guest: Idiomatic Ember for example. Idiomatic in the sense that it gives you object for you to work with, which are simple objects.10:12 – Guest: You have your reducers and your...we could do those things but ultimately it’s powerful – and not action names – we use method names; the name of the method.11:20 – Panel: I was digging through docs, and it feels like NORMAL JavaScript. It doesn’t seem like it’s tied to a certain framework or library platform?11:45 – Guest: Yes, we felt a lot of time designing the interfaces the API and the implementation. We wanted it to feel natural but a tool that people reach for.(Guest continues to talk about WHY they created microstates.)Guest: We wanted to scale very well what you need when your needs to change.13:39 – Chuck: I have a lot of friends who get into React and then they put in Redux then they realize they have to do a lot of work – and that makes sense to do less is more.14:17 – Guest: To define these microstates and build them up incrementally...building smaller microstates out of larger ones.Guest continued: Will we be able to people can distribute React components a sweet array of components ready for me to use – would I be able to do the same for a small piece of state? We call them state machines, but ultimately we have some state that is driving it. Would we be able to distribute and share?16:15 – Panel: I understand that this is tiny – but why wouldn’t I just use the native features in specific the immutability component to it?16:42 – Guest: I’m glad you asked that question. We wanted to answer the question...Guest: With microstates you can have strict control and it gives you the benefit of doing sophisticated things very easily.18:33 – Guest: You mentioned immutability that’s good that you did. It’s important to capture – and capturing the naturalness of JavaScript. It’s easy to build complex structures – and there is an appeal to that. We are building these graphs and these building up these trees. You brought up immutability – why through it away b/c it’s the essence of being a developer. If you have 3-4-5 levels of nesting you have to de-structure – get to the piece of data – change it – and in your state transition 80% of your code is navigating to the change and only 20% to actually make the change. You don’t have to make that tradeoff.21:25 – Aimee: The one thing I like about the immutability b/c of the way you test it.21:45 – Guest: There a few things you can test. 23:01 – Aimee: You did a good job of explaining it.23:15 – Guest: It makes the things usually hard  easy! With immutability you can loose control, and if that happens you can get so confused. You don’t have a way to have a way to navigate to clarity. That’s what this does is make it less confusing. It gives you order and structure. It gives you a very clear path to do things you need to do. If there is a property on your object, and if there is a way to change it...25:29 – Guest: The only constant is change no matter what framework you are working on.24:46 – Chuck: We are talking about the benefits and philosophy. What if I have an app – and I realize I need state management – how do I put microstates into my app? It’s using Angular or React – how do I get my data into microstates?26:35 – Guest: I can tell you what the integration looks like for any framework. You take a type and you passed that type and some value to the create function so what you get is a microstate.(The Guest continues diving into his answer.)28:18 – Guest: That story is very similar to Redux, basically an event emitter. The state changes on the store.Maybe this is a good time to talk about the stability benefits and the lazy benefits because microstates is both of those things.Stability – if I invoke a transition and the result is unchanged – same microstate – it doesn’t emit an event. It recognizes it internally. It will recognize that it’s the same item. Using that in Ember or Redux you’d have to be doing thousands of actions and doing all that computation, but stability at that level.Also, stability in the sense of a tree. If I change one object then that changes it won’t change an element that it doesn’t need to change.31:33 – Advertisement: Sentry.io32:29 – Guest: I want to go back to your question, Chuck. Did we answer it?32:40 – Chuck: Kind of.32:50 – Guest.32:59 – Guest: In Angular for example you can essentially turn a microstate...33:51 – Guest: You could implement a connect, too. Because the primitive is small – there is no limit.34:18 – Chuck summarizes their answers into his own words.34:42 – Guest: If you were using a vanilla React component – this dot – I will bind this. You bind all of these features and then you pass them into your template. You can take it as a property...those are those handlers. They will perform the transition, update and what needs to be updated will happen.35:55 – Chuck: Data and transitions are 2 separate things but you melded them together to feel like 1 thing. This way it keeps clean and fast.36:16 – Guest: Every framework helps you in each way.Microstates let’s you do a few things: the quality of your data all in one place and you can share.38:12 – Guest: He made and integrated Microstates with Redux tools.38:28 – Guest talks about paths, microstates to trees.39:22 – Chuck.39:25 – Panel: When I think about state machines I have been half listening / half going through the docs. When I think of state machines I think about discreet operations like a literal machine. Like a robot of many steps it can step through. We have been talking about frontend frameworks like React - is this applicable to the more traditional systems like mechanical control or is it geared towards Vue layered applications?40:23 – Guest: Absolutely. We have BIG TEST and it has a Vue component.41:15 – Guest: when you create a microstate from a type you are creating an object that you can work with.42:11 – Guest: Joe, I know you have experience with Angular I would love to get your insight.42:33 – Joe: I feel like I have less experience with RX.js. A lot of what we are talking about and I am a traditionalist, and I would like you to introduce you guys to this topic. From my perspective, where would someone start if they haven’t been doing Flux pattern and I hear this podcast. I think this is a great solution – where do I get started? The official documents? Or is it the right solution to that person?43:50 – Guest: Draw out the state machine that you want to represent in your Vue. These are the states that this can be in and this is the data that is required to get from one thing to the other. It’s a rope process. The arrow corresponds to the method, and...44:49 – Panel: It reminds me back in the day of rational rows.44:56 – Guest: My first job we were using rational rows.45:22 – Panelist: Think through the state transitions – interesting that you are saying that. What about that I am in the middle – do you stop and think through it or no?46:06 – Guest: I think it’s a Trojan horse in some ways. I think w

                    Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.
                    1 hr 19 min
                  • MJS 082: Benjamin Hong

                    Panel: Charles Max Wood

                    Guest: Benjamin Hong

                    This week on My JavaScript Story, Charles speaks with Benjamin Hong who is a Senior UI Developer at Politico where he lives in the Washington, D.C. area. He has worked with other companies including Treehouse, Element 84, and Udacity. Charles and Benjamin talk about his past and current projects, and how it’s different working for the government vs. working for a business. Check it out!

                    In particular, we dive pretty deep on:

                    1:06 – Chuck: Tell us a brief introduction, please.

                    1:23 – Ben: I am a lead frontend developer at Politico.

                    1:43 – Chuck: It’s an area that can affect everyone. How did you get into developing?

                    1:52: Ben: I had everything you can think of to develop at first.

                    2:10 – Chuck: For me it was a TI90 calculator!

                    2:18 – Chuck: Was it somebody or something that pushed you towards this area?

                    2:32 – Ben: I wanted to change something with the theme, Googled it, and it went from there, and the Marquis Tag.

                    2:51 – Chuck: And the Blink Tag! The goodies. So you got the he HTML book – and what website did you build that was your first big project?

                    3:07 – Ben: It was fiddling around, but it was fortune cookie universe.

                    3:20 – Chuck: You will have to recreate it!

                    3:27 – Ben: I think this was 1993/1995 timeframe.

                    3:40 – Chuck: Yep, me too same time frame. If you had something move on your website it was so cool. You went to building...

                    4:02 – Ben: JavaScript was a roadblock for me. There was nobody to correct me. I had a JavaScript book and it was a massive failure.

                    4:33 – Chuck: You took a break and you came back?

                    4:40 – Ben: Oh – people will PAY you to do this?!

                    4:54 – Chuck: Did you go to college?

                    5:01 – Ben: Yes, I have a Master’s in a different field. I was always a tech junkie. I just wanted to put things together.

                    5:20 – Chuck: Take us through your journey through JS?

                    5:30 – Ben: I started off with the jQuery piece of it. I needed Java, and it took me awhile to wrap my head around it at first. Through the trial and process of trying to get into Angular and React, too.

                    6:19 – Chuck: Did you play with Backbone, Knockout, or Ember?

                    6:32 – Ben: I did do SOME Ember and some Knockout. Those were my first interactions.

                    6:49 – Chuck: What got you into the profession? How did you get from your Master’s to being a tech guy?

                    7:14 – Ben: From the Master’s field I learned a lot about human experience, and anted to breed the two together. Also, consulting and helping to build things, too.

                    7:44 – Charles: What was the career change like?

                    7:53 – Ben: I went to the federal government at first around the recession – it was good having a stable job. I was bored, though. While I was working for the government I was trying to get my foot in the door. From there I have been building my way up.

                    8:30 – Ben: I was working on Medicare.gov and then later...

                    8:46 – Charles: We won’t use the word “disaster”!

                    What is it like to work for the government?

                    9:20 – Ben: Yep. The federal government is a different area because they are stake holders. They were about WHO owned the content, and who do we have to talk to get something approved. It was not product oriented like a business. I made my transition to Politico, because I wanted to find solutions and diversify the problems I was having.

                    10:31 – Chuck: Have you been there from the beginning?

                    10:39 – Ben answers the question.

                    Ben: They were looking for frontend developers

                    10:54 – Chuck: You are the lead there now. What was that like with the transition?

                    11:08 – Ben talks about the beginnings stages of his time with Politico and the current situation. He talks about the different problems, challenges, and etc.

                    11:36 – Chuck: Do you consider yourself a news organization or?

                    11:47 – Ben: We have Politico Pro, too. I have been working with this site more so. There are updates about campaign and voting data. People will pay a fee.

                    12:25 – Chuck: Do they pain themselves as leaning one way or another or nonpartisan?

                    12:38 – Ben: We are objective and nonpartisan.

                    12:51 – Chuck: I know, I was hesitant to ask. What’s the mission of the company and into what you do?

                    13:09 – Ben: The projects get dumped to us and we are about solving the problems. What is the best route for solving it? I had to help pioneer the new framework into the tech staff is one of my roles.

                    13:48 – Chuck: What’s your tech stack?

                    13:55 – Ben: JavaScript and Vue.js. We are experimenting with other software, too.

                    14:16 – Chuck: We should get you talking about Vue on the other show!

                    Are you working at home?

                    14:32 – Ben answers the question.

                    Ben: One thing I am helping with Meetup. Community outreach is important and I’m apart of that.

                    15:09 – Chuck: Yep, it’s interesting to see various fields into the tech world. I am not one of those liberal arts majors, I do have a computer science degree. It’s interesting to see the different perspectives. How little it is for someone to be able to dive-in right away.

                    What are you working on?

                    16:09 – Ben: Meetup population and helping with the work at Politico.

                    16:27 – Chuck: Reusable components. Are those opensource or only internal?

                    16:41 – Ben: They are now opensource but we are seeing which portions can be opensource or not.

                    17:01 – Chuck: Different companies have come out and offered their opensource.

                    Where do they find you?

                    17:20 – BenCodeZen! They are more than welcome to message me.

                    17:36 – Chuck: Any advice on newbies to this field?

                    17:46 – Ben: Attending those meetings and making those connections.

                    18:18 – Chuck: I have been writing a book on HOW to get a job as a coder. That’s the same advice that I am giving, too.

                    18:46 – Chuck: Picks!

                    18:51 – Advertisement – Fresh Books! 30-Day Trial!

                    Links:

                    • React
                    • Angular
                    • Vue.js
                    • JavaScript
                    • Ember
                    • Elm
                    • jQuery
                    • BenCodeZen
                    • Ben’s LinkedIn
                    • Ben’s Crunch Base
                    • Sponsors:

                      • Cache Fly
                      • Get A Coder Job
                      • Fresh Books
                      • Picks:

                        Charles

                        • Framework Summit – UT (Ember, Elm, and tons more!)
                        • Microsoft Ignite
                        • Code Badge
                        • Ben

                          • Conference in Toronto
                          • Conference in Atlanta, GA (Connect Tech)
                          • Conference in London – Vue
                          • 23 min
                          • JSJ 336: “The Origin of ESLint” with Nicholas Zakas
                            Panel: 
                            • Aimee Knight
                            • Charles Max Wood (DevChat TV)
                            • Christopher Ferdinandi (Boston)
                            • Cory House (Kansas City)
                            • Joe Eames
                            Special Guests: Nicholas Zakas In this episode, the panel talks with Nicholas Zakas who writes on his site, Human Who Codes. He is the creator of ESLint, also the author of several books, and he blogs, too. He was employed through Box and today he talks about ESLint in full detail! Check it out! Show Topics:0:05 – Advertisement: KENDO UI 0:37 – Hello! The panel is...(Chuck introduces everyone).1:04 – Nicholas who are you?1:17 – Nicholas: Yeah it’s been about 5 years and then you invited me again, but I couldn’t come on to talk about ESLint back then. That’s probably what people know me most for at this point. I created ESLint and I kicked that off and now a great team of people is maintaining it.1:58 – Chuck: What is it?2:04 – It’s a Linter for JavaScript. It falls into the same category as JSLint. The purpose of ESLint is to help you find problems with your code. It has grown quite a bit since I’ve created it. It can help with bugs and enforcing style guides and other things.2:53 – Where did it come from?2:57 – Guest: The idea popped into my head when I worked at Pop. One of my teammates was working on a bug and at that time we were using...Nothing was working and after investigating someone had written a JavaScript code that was using a native code to make an Ajax request. It wasn’t the best practice for the company at the time. For whatever reason the person was unaware of that. When using that native XML...there was a little bit of trickiness to it because it was a wrapper around the...We used a library to work around those situations and add a line (a Linter) for all JavaScript files. It was a text file and when you tried to render code through the process it would run and run the normal expression and it would fail if any of the...matched.I am not comfortable using normal expressions to write code for this. You could be matching in side of a string and it’s not a good way to be checking code for problems. I wanted to find a better way.6:04 – Why did you choose to create a product vs. using other options out there?6:15 – Guest: Both of those weren’t around. JSHint was pretty much the defector tool that everyone was using. My first thought was if JSHint could help with this problem?I went back to look at JSHint and I saw that on their roadmap you could create your own rules, and I thought that’s what we need. Why would I build something new? I didn’t see anything on GitHub and didn’t see the status of that. I wanted to see what the plan was, and they weren’t going to get to it. I said that I really needed this tool and I thought it would be helpful to others, too.8:04 – My history was only back when it was customizable.8:13 – Aimee: It’s interesting to see that they are basing it on regular expressions.8:32 – Guest: Interesting thing at Box was that there was...I am not sure but one of the engineers at Box wrote...9:03 – Aimee: I was going to ask in your opinion what do you think ES Lint is the standard now?9:16 – Guest: How easy it is to plug things in. That was always my goal because I wanted the tool not to be boxed in – in anyway.The guest continues to talk about how pluggable ESLint is and the other features of this tool.13:41 – One thing I like about ESLint is that it can be an educational tool for a team. Did you see that being an educational tool?14:24 – Guest: How do you start introducing new things to a team that is running at full capacity? That is something that I’ve wondered throughout my career. As a result of that, I found that a new team there were some problems I the code base that were really hard to get resolved, because when one person recognizes it there isn’t a god way to share that information within a team in a non-confrontational way. It’s better to get angry at a tool rather than a person.Guest goes into what this can teach people.18:07 – Panelist: I am not surprised. Is there a best practice to get a team to start with ESLint?Do you get the whole team in a room and show them the options or take the best guess and turn it on?18:34 – Guest: The thing I recommend is that first and foremost get ESLint in your system with zero rules on. It starts that mindset into your development process. We can do something to automatically check...Get Syntax checking and you will se improvements on the number of bugs that are getting out of production. I recommend using the default the ESLint configuration. This has all of the things that we have found that are most likely errors and runtime errors vs. syntax errors. You can go through with those and sometimes it is easier to run that check with...Using those ESLint rules will clean up a lot of problems that you didn’t know you had with your code. There are too many problems with those rules. I recommend instead of turning them off then put the severity to warning and not error. That is something we started with in the beginning. We turned on as many rules as we could and it drove people crazy. They didn’t feel like when they were committing to a file why should I be...The idea with the different scenario levels you don’t’ want to turn off rules so people don’t know there is a problem. There can be a rule on so people will know that there is a problem, but...Doing that alone will give you a lot of benefit in using ESLint. How do you decide as a team on the rules that are maybe not for finding errors but for stylistic in error? Do we use four spaces, semi-colons, etc. To figure that out I am a big component on finding a pre-existing style guide and adapting it. Get everyone to agree.There is no right or wrong when it comes to stylistic preferences. It really is just getting everyone to do the same thing. I think it was Crawford that said: Whether you drive on the right side of the left side of the road – it doesn’t matter as long as everyone is dong the same thing. I agree with that and it applies to style guides. It can get heated but for the best thing for the team is stick with a guide and work together.24:36 – Aimee: I can go through the options to pick one of the style guides out there and then it will automatically create my configuration for me is helpful. Question: If you had to pick 2 or 3 rules that you are super helpful what would they be?25:30 – Guest: To touch briefly on indentation. Whether you like four spaces or whether you are wild and like tabs, I think the indent rule is very helpful. Just for wiping out and eliminating that discussion through your team. Have your editor setup however they want but on the pre-hook...But my favorite rules I tend to lean towards the ones that saved me.The Guest goes through his favorite rules with ESLint. Check it out!26:51 – Guest mentions his second favorite rule, here!28:24 – Guest mentions his third favorite rule, here!29:03 – Guest mentions the rule that makes him giggle a lot, here!30:07 – Advertisement – Sentry! 31:22 – What is your take on running Fix? Does it make sense to run Fix?32:00 – Guest: It depends and the idea behind Fix is the idea of doing a one time (at the start) fix everything that it can find wrong b/c I don’t want to do it by hand. It morphed into a more of a tool that people are using all the time. I too have mixed feelings about it. I think the greatest value you get out of Fix is that when you first install it or when you enable a new rule. I think in those situations you get a lot of value out of Fix. I think that when people were getting aggressive with their code styles it took us down a path where we...As a pre-commit hook it could be to fix things and part of the built system you wouldn’t want...People are probably wondering: Why doesn’t ESLint doesn’t fix all the time?It can be a team decision: do you want to run Fix at the point that the developer is writing the code, do you want to use Fix as running it as a build when you are bundling? It really seems more of a personal preference. I am on the fence about it. Even though I am leaning more towards...35:16 – Do you run Premier?35:20 – Guest: No I don’t. I don’t have anything against Premier but I think Prettier uses a very interesting space.37:50 – Chuck: What is next for ESLint and what is next for you?37:55 – Guest: Well, to be honest I am not sure what is next for ESLint. I haven’t been involved with keeping it maintained for the last few years. I do help out with feedback with decisions. But in general the ESLint the direction is that let’s add tings that help people avoid language hazards and make sure that ESLint is still pluggable. Lastly, that we will be there to help people and the community. There is this virtuosic cycle and tools like Babble and then tools like ESLint introducing rules adapting new rules and featur

                            Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.
                            1 hr 9 min
                          • MJS 081: Christiané Heiligers

                            Panel: Charles Max Wood

                            Guest: Christiané Heiligers

                            This week on My JavaScript Story, Charles speaks with Dr. Christiané Heiligers who is new to the industry. Her background is in physics where she has her Ph.D. in the field. Listen to today’s episode to hear her background, experience with the different programs/languages, and much more!

                            In particular, we dive pretty deep on:

                            Beginning – Advertisement: Code Badges!

                            1:07 – Christiané: Hello!

                            1:17 – Chuck: I like hearing people’s stories from our community. Tell us where you come from and who you are?

                            1:33 – Christiané: I am from South Africa, and have been in the US for 2 years now. My formal training is in physics. I have been a researcher with lab coats and test tubes. Through immigration, which took 2 years. I couldn’t be still, and started learning code on my own. I enjoyed the art. I had to use Python, and then I was hooked. I enjoyed the functional programming and other things. I had some experience with Ruby on Rails. I enjoy development because its problem solving, methodically approach, and uses your creative side, too. My preference is a Mac, need the Internet and decided to go to camps and take courses.

                            I snagged a job a week before I graduated!

                            4:36 – Chuck: your journey, thus far. You said that you couldn’t be idle – so why code?

                            4:53 – Guest: The UK is cold you don’t want to do anything outside! From South American I couldn’t stand the cold. I kept busy indoors – hint the code. You can’t get bored – frontend or backend.

                            5:28 – Chuck: Can you give us background on the Grace Hopper Academy.

                            5:40 – Guest: Sure! It’s based in NY City.

                            6:26 – Chuck: Did you move somewhere or was it remote?

                            6:30 – Guest: I had to live somewhere e

                            6:51 – Chuck: Where did you

                            6:55 – Guest: NY City. There were 16 of us in the course.

                            7:14 – Chuck: Why did you feel like you had to go to coding school?

                            7:25 – Guest: I am impatient with myself. The home-life you ask yourself: “Am I doing the right thing? Am I going in the right direction?” I wanted to go and pick up some skills.

                            7:56 – Chuck: You go through Grace Hopper – is this how you got into JavaScript?

                            8:11 – Guest: I didn’t know a line of JavaScript.

                            I did my application code line in Ruby.

                            My husband has been in software development my whole life.

                            9:16 – Chuck: What have you done with JavaScript since learning it?

                            9:24 – Guest: Some card playing games for my nieces in South Africa.

                            10:50 – Guest: Stack Overflow is wonderful.

                            11:05 – Chuck.

                            11:11 – Guest: I wasn’t actively contributing, but I did...

                            11:30 – Chuck: What is it like being a prof

                            11:37 – Guest: It’s addictive. When I am writing code in the frontend / backend side. It’s always learning.

                            12:11 – Chuck: What’s next for you?

                            12:18 – Guest: I would love to continue this journey. Maybe into the DevOps, but my passion happens with React. The Hapi Framework.

                            13:10 – Guest: The community is wonderful to work with – everyone is very helpful.

                            13:22 – Chuck: People are usually talking about Express and not Hapi.js.

                            13:35 – Guest: I have some contact names you can call.

                            13:43 – Guest: I am working on a few small projects right now. Some Angular sites that need assistance. Helping out where I can. It’s a small team that I am working with. There is only a few of us.

                            14:31 – Chuck: Usually people stick with one. What’s your experience using the different frameworks?

                            14:40 – Guest: It’s an eye-opener! React vs. Angular.

                            15:07 – Chuck: How can people find you?

                            15:14 – Guest: LinkedIn, Twitter, Tallwave, etc.

                            15:37 – Chuck: Picks!

                            15:40 – Advertisement!

                            Links:

                            • React
                            • Angular
                            • Grace Hopper Academy
                            • Christiané’s Instagram
                            • Christiané’s Facebook
                            • Sponsors:

                              • Code Badge
                              • Cache Fly
                              • Get A Coder Job
                              • Picks:

                                Charles

                                • Podcasts that Chuck listens to:
                                  • Code Newbie
                                  • Our podcasts through DevChat
                                  • Food – Kedo Diet – 2 Keto Dudes
                                  • Christiané Heiligers

                                    • Hapi Framework
                                    • Hapi Slack Channel – Hapi.js
                                    • 20 min
                                    • JSJ 335: “CanJS 4.0” with Justin Meyer
                                      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.
                                      55 min
                                    • MJS 080: Ely Lucas

                                      Panel: Charles Max Wood

                                      Guest: Ely Lucas

                                      This week on My JavaScirpt Story, Charles speaks with Ely Lucas who is a software developer. He loves technologies and mobile technologies among other things. Let’s listen to today’s episode where Chuck and Ely talk about Ionic, Angular, React and many other topics! Check it out!

                                      In particular, we dive pretty deep on:

                                      1:33 – Hello!

                                      1:40 Chuck: Give us a background on who you are, and tell us how famous you are!

                                      2:31 – Chuck: What do you do with Ionic?

                                      2:40 – Ely answers the question.

                                      3:51 – Chuck: How did you get into your field?

                                      3:55 – Ely: When I was a kid and played with video games. Later on I got into web development, like my website. Then I got into a professional-level of developing.

                                      Ely goes into detail about how his passion for developing began and developed.

                                      6:30 – Chuck: Yeah, I’ve talked with people who have gotten into video games, then got into software development.

                                      7:01 – Ely: Someday I would like to develop games.

                                      7:12 – Chuck: Yes, web developing is awesome.

                                      Chuck asks Ely another question.

                                      7:25 – Ely answers the question and mentions web controls.

                                      9:17 – Ely: I thought Ajax was easier.

                                      9:38 – Chuck: When I got into web development jQuery was sort of new. It made things a lot easier.

                                      9:58 – Ely: A lot of people like to sneer at jQuery now, but back in the day it was IT.

                                      10:28 – Chuck: How did you get into Ionic?

                                      10:43 – Ely: I got a fulltime gig working on Ionic; I like the framework. I saw a job application and sent in my résumé. Two days later I got a callback and was amazed. They were hiring remotely. The team liked me and started over a year ago.

                                      11:46 – Chuck asks a question.

                                      11:54 – Ely answers the question.

                                      13:20 – Chuck: Why Ionic?

                                      13:35 – Ely: It was based off of Angular.

                                      15:17 – Chuck: You mentioned...what has the transition been like?

                                      15:32 – Ely talks about past programs he has worked with. He taught React in the early React days.

                                      16:37 – Ely: I have a deep appreciation on React now.

                                      17:09 – Chuck: I like seeing the process that people go through.

                                      17:24 – Ely continues the conversation.

                                      Ely: It is interesting to see the learning process that people go through to arrive in the same place.

                                      18:18 – Chuck: Redux is a good example of this. Anyway, this is near the end of our time.

                                      18:39 – Chuck: Anything else you want to talk about?

                                      18:48 – Ely: Yes, I have been involved in the Denver community. Check us out.

                                      Links:

                                      • Ionic
                                      • jQuery
                                      • JavaScript
                                      • React
                                      • Ely Lucas’ Twitter
                                      • Ely Lucas’ LinkedIn
                                      • Ely Lucas
                                      • Ely Lucas’ GitHub
                                      • Sponsors:

                                        • Get A Coder Job
                                        • Code Badges
                                        • Digital Ocean
                                        • Picks:

                                          Charles

                                          • Audible
                                          • Book: Seven Proven Principles...
                                          • Tony Robbins’ Book: Unshakeable
                                          • Ely

                                            • Fantasy Novel: Shadow of what was lost.
                                            • Ionic
                                            • 36 min

                                            About JavaScript Jabber

                                            From the publisher's feed

                                            Stay current on JavaScript, Node, and Front-End development. Learn from experts in programming, careers, and technology every week.

                                            Become a supporter of this podcast:

                                            More shows like JavaScript Jabber

                                            Freakonomics Radio by Freakonomics Radio + Stitcher

                                            Freakonomics Radio

                                            31,931 Listeners

                                            The Tim Ferriss Show by Tim Ferriss: Bestselling Author, Human Guinea Pig

                                            The Tim Ferriss Show

                                            16,045 Listeners

                                            The Changelog: Software Development, Open Source by Changelog Media

                                            The Changelog: Software Development, Open Source

                                            286 Listeners

                                            Ruby Rogues by Charles M Wood

                                            Ruby Rogues

                                            45 Listeners

                                            The Freelancers' Show by Charles M Wood

                                            The Freelancers' Show

                                            23 Listeners

                                            The a16z Show by Andreessen Horowitz

                                            The a16z Show

                                            1,093 Listeners

                                            Software Engineering Daily by Software Engineering Daily

                                            Software Engineering Daily

                                            623 Listeners

                                            Talk Python To Me by Michael Kennedy

                                            Talk Python To Me

                                            581 Listeners

                                            iPhreaks by Charles M Wood

                                            iPhreaks

                                            17 Listeners

                                            React Native Radio by Jamon Holmgren, Robin Heinze, Mazen Chami

                                            React Native Radio

                                            67 Listeners

                                            Adventures in Angular by Charles M Wood

                                            Adventures in Angular

                                            15 Listeners

                                            JavaScript Jabber by Charles M Wood

                                            JavaScript Jabber

                                            62 Listeners

                                            Ruby Rogues by Charles M Wood

                                            Ruby Rogues

                                            21 Listeners

                                            My JavaScript Story by Charles M Wood

                                            My JavaScript Story

                                            4 Listeners

                                            My Ruby Story by Charles M Wood

                                            My Ruby Story

                                            0 Listeners

                                            Syntax - Tasty Web Development Treats by Wes Bos & Scott Tolinski - Full Stack JavaScript Web Developers

                                            Syntax - Tasty Web Development Treats

                                            983 Listeners

                                            The Indicator from Planet Money by NPR

                                            The Indicator from Planet Money

                                            9,520 Listeners

                                            Tech Brew Ride Home by Morning Brew

                                            Tech Brew Ride Home

                                            959 Listeners

                                            All-In with Chamath, Jason, Sacks & Friedberg by All-In Podcast, LLC

                                            All-In with Chamath, Jason, Sacks & Friedberg

                                            10,177 Listeners

                                            Deep Questions with Cal Newport by Cal Newport

                                            Deep Questions with Cal Newport

                                            1,346 Listeners

                                            Dwarkesh Podcast by Dwarkesh Patel

                                            Dwarkesh Podcast

                                            550 Listeners

                                            Latent Space: The AI Engineer Podcast by Latent.Space

                                            Latent Space: The AI Engineer Podcast

                                            105 Listeners

                                            BG2Pod with Brad Gerstner and Bill Gurley by BG2Pod

                                            BG2Pod with Brad Gerstner and Bill Gurley

                                            454 Listeners

                                            AI + a16z by a16z

                                            AI + a16z

                                            31 Listeners