Podcasts Other JavaScript Jabber JSJ 332: You Learned JavaScript, Now What? with Chris Heilmann

JSJ 332: You Learned JavaScript, Now What? with Chris Heilmann

Published: Sept. 25, 2018, 10 a.m.

Panel:\xa0

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.\xa0 He currently resides in Berlin, Germany. Let\u2019s welcome our special guest and listen to today\u2019s episode!Show Topics:2:19 \u2013 Chuck talks.2:41 \u2013 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.\xa05:47 \u2013 Aimee: The overall theme is...5:54 \u2013 Panelist: I really like what you said about helping people not feeling disenfranchised.6:47 \u2013 Chris: There is a lot of peer pressure at peer conferences7:30 \u2013 Aimee chimes in with some comments.7:50: Chris: I think we need to hunt the person down that put...8:03 \u2013 Panelist: A good point to that is, I try to avoid comments like, \u201cWell, like we ALL know...\u201d8:27 \u2013 Chris: There are things NOT to say on stage. It happens, but we don\u2019t want to say certain things while we are teaching people. We are building products with different groups, so keep that in mind.9:40 \u2013 Aimee: My experience in doing this is that I have found it very rewarding to share embarrassing experiences that I\u2019ve had. My advice would to tell people to let their guard down. It\u2019s encouraging for me.10:26 \u2013 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 \u2013 Chuck: Now, I do want to ask this...11:35 \u2013 Chris answers.12:24 \u2013 What makes you say that? (Question to Chris)12:25 \u2013 Chris answers.13:55 \u2013 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\u2019t work with other people, then you are a hindrance.14:31 \u2013 Aimee chimes in.14:53 \u2013 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 \u2013 Chris: Back to the article...18:26 \u2013 Chuck: Yes, I agree. Why go and fight creating a whole system when it exists.18:54 \u2013 Chris chimes in with some comments.19:38 \u2013 Panelist: I still use console logs.19:48 \u2013 Chris: We all do, but we have to...19:55 \u2013 Aimee: In the past year, I can\u2019t tell you how much I rely on this. Do I use Angular? Do I learn Vue? All those things that you can focus on \u2013 tools.10:21 \u2013 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 \u2013 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\u2019s the impact we are having. It\u2019s those things that will make the difference. Those things people will want to work with and solves their problems.23:00 \u2013 Chris adds his comments. He talks about Flash.24:05 \u2013 Chris: The librarian motto: \u201cI don\u2019t know everything, but I can look \u201chere\u201d to find the answer.\u201d We don\u2019t know everything.24:31 \u2013 Aimee: Learn how to learn.24:50 \u2013 Chris: There is a big gap in the market. Scratch is a cool tool and it\u2019s these puzzle pieces you put together. It was hard for me to use that system. No, I don\u2019t want to do that. But if you teach the kids these tools then that\u2019s good.\xa024:56 \u2013 Chuck: Here is the link, and all I had to do was write React components.26:12 \u2013 Chris: My first laptop was 5x more heavy then this one is. Having access to the Internet is a blessing.27:24 \u2013 Advertisement 28:21 \u2013 Chuck: Let\u2019s 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 \u2013 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\u2019s not broken?31:00 \u2013 Chuck talks about his experience.31:13 \u2013 Chris continues his thoughts.Chris: Start growing a community.32:01 \u2013 Chuck: What ways can people get involved within their community?32:13 \u2013 Chris: Meetup. There are a lot of opportunities out there. Just going online and seeing where the conferences34:08 \u2013 Chris: It\u2019s interesting when I coach people on public speaking. Sharing your knowledge and learning experience is great!34:50 \u2013 Chuck: If they are learning how to code then...by interacting with people you can get closer to what you need/want.35:30 \u2013 Chris continues this conversation.35:49 \u2013 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 \u2013 Chuck: How do you find out what is really good content \u2013 what\u2019s worth your time vs. what\u2019s not worth your time?36:36 \u2013Chris says, \u201cThat\u2019s tricky!\u201d Chris answers the question.37:19: Chris: The best things out there right now is...38:45 \u2013 Chuck: Anything else that people want to bring up?39:00 \u2013 Chris continues to talk.42:26 \u2013 Aimee adds in her thoughts.Aimee: I would encourage people to...43:00 \u2013 Chris continues the conversation.Chris: Each project is different, when I build a web app is different then when I build a...45:07 \u2013 Panelist: I agree. You talked about abstractions that don\u2019t go away. You use abstractions in what you use. At some point, it\u2019s safe to rly on this abstraction, but not this one. People may ask themselves: maybe CoffeeScript wasn\u2019t the best thing for me.46:11 \u2013 Chris comments and refers to jQuery.48:58 \u2013 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\u2019t have longevity? I think we are building things too soon and too fast.51:04 \u2013 Chris: When I work in browsers and come up with brand new stuff.52:21 \u2013 Panelist: Your points are great, but there are some additional things we need to talk about. Let\u2019s take jQuery as an example. There is a strong argument that if you misuse the browser...53:45 \u2013 Chris: The

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.