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

    0
    1528

    Panel:

    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 conferences

    7: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 conferences

    34: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: The main issue I have with jQuery is that people get an immediate satisfaction. What do we do besides this?

    55:58 – Panelist asks Chris further questions.

    56:25 – Chris answers.

    Chris: There are highly frequent websites that aren’t being maintained and they aren’t maintainable anymore.

    57:09 – Panelist: Prototypes were invented because…

    57:51 – Chris: It’s a 20/20 thing.

    58:04 – Panelist: Same thing can be said about the Y2K.

    58:20 – Panelist: Yes, they had to solve that problem that day. The reality is…

    58:44 – Chris: We learned from that whole experience.

    1:00:51 – Chris: There was a lot of fluff around it.

    1:01:35 – Panelist: Being able to see the future would be a very helpful thing.

    1:01:43 – Chris continues the conversation.

    1:02:44 – Chuck: How do people get ahold of you?

    1:03:04 – Twitter is probably the best way.

    1:03:32 – Let’s go to picks!

    1:03:36 – Advertisement

    Links:

    Sponsors:

    Picks :

    Amiee

    AJ

    Joe

    Charles

    Chris