Panel:

• Aimee Knight
• AJ O’Neal
• Charles Max Wood

Special Guest: PJ Evans

In 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
• React
• Elixir
• Elm
• Vue
• ESLint
• Node.js
• Node Security Project
• Node Security Project - Medium
• Manning Publications: Course by PJ Evans
• PUG
• JSConf EU – talk with Philip Roberts
• Medium Article by David Gilbertson
• Hackster.io – Pi Car
• Pi Moroni
• Holding a Program in One’s Head
• PJ Evans’ Twitter

Sponsors:

• Kendo UI
• Sentry
• Cache Fly
• Get a Coder Job

Picks:

Aimee

• Paul Graham - Blog

AJ

• Rust

Charles

• Tweet Mash-up
• The Diabetes Code

PJ

• Music - Max Richter

Panel: Charles Max Wood

Guest: Rob Eisenberg

This week on My JavaScript Story, Charles speaks with Rob Eisenberg who is a principal software engineer at InVision, and is the creator of Caliburn.Micro, Durandal, and Aurelia. Today, they talk about Rob’s past and current projects among other things.

In particular, we dive pretty deep on:

1:40 – Chuck: Our special guest is Rob Eisenberg. We’ve had you on Adventures on Angular (09 and 80), JavaScript Jabber, and others like Episode 203.

2:36 – Rob: That was over the period of 4 years all of those podcasts. I am getting older.

2:50 – Chuck: Anything that you’ve done that you want to talk about?

3:04 – Rob: I am known for opensource work over the years. Maybe we can talk about my progression through that over the years.

3:25 – Chuck: How did you get into this field?

3:29 – Rob: When I was 8 years old my dad wanted to buy a computer. We went to Sears and we bought our first computer. You’d buy the disk drive and the keyboard looking unit. You could by a monitor, we didn’t, but we used a black and white TV for our monitor. Later we bought the colored monitor and printer. That’s where my fascination started. We set up the computer in my bedroom. We played games. I got intrigued that you could write code to make different games.

It was just magical for me. As being an adult engineer I am trying to go back to that moment to recapture that magical moment for me. It was a great creative outlet. That’s how I first started. I started learning about Q basic and other flavors of Basic. Then I heard about C! I remember you could do anything with C. I went to the library and there wasn’t the Internet, yet. There were 3 books about C and read it and re-read it. I didn’t have any connections nor a compiler. When I first learned C I didn’t have a compiler. I learned how to learn the codes on notebook paper, but as a kid this is what I first started doing. I actually saved some of this stuff and I have it lying around somewhere. I was big into adventure games. That’s when I moved on C++ and printed out my source code! It’s so crazy to talk about it but at the time that’s what I did as a kid. In JHS there was one other kid that geeked-out about it with me. It was a ton of fun.

Then it was an intense hobby of mine. Then at the end of HS I had 2 loves: computers and percussion. I was composing for music, too. I had to decide between music or coding. I decided to go with music. It was the best decision I ever made because I studied music composition. When you are composing for dozens of instruments to play one unified thing. Every pitch, every rhythm, and it all works together. Why this note and why that rhythm? There is an artistic side to this and academia, too. The end result is that music is enjoyed by humans; same for software.

I did 2 degrees in music and then started my Master’s in Music. I then realized I love computers, too, how can I put these two together? I read some things on audio programming, and it stepped me back into programming. At this time, I was working in music education and trying to compose music for gamming. Someone said look at this program called C#! I don’t know cause...how can you get any better than C++?!

In 2003 – I saw a book: teach yourself C# in 24 hours. I read it and I was enthralled with how neat this was! I was building some Windows applications through C#. I thought it was crazy that there was so much change from when I was in college.

17:00 – Chuck: You start making this transition to web? What roped you in?

17:25 – Rob: I realized the power of this, not completely roped in just, yet. Microsoft was working (around this time) with...

19:45 – (Continued from Rob): When Silver Light died that’s when I looked at the web. I said forget this native platform. I came back to JavaScript for the 2^nd time – and said I am going to learn this language with the same intensity as I learned C++ and C#. I started working with Durandal.

21:45 – Charles: Yeah, I remember when you worked with the router and stuff like that. You were on the core team.

21:53 – Rob: The work I did on that was inspired by screen activation patterns.

23:41 – Rob (continued): I work with InVision now.

24:14 – Charles: I remember you were on the Angular team and then you transitioned – what was that like?

24:33 – Rob comments.

25:28 – Rob (continued): I have been doing opensource for about 13 years. I almost burned myself a few times and almost went bankrupt a few times. The question is how to be involved, but run the race without getting burned-out. It’s a marathon not a sprint.

These libraries are huge assets. Thank God I didn’t go bankrupt but became very close.

The more popular something if there are more varieties and people not everyone is so pleasant. It’s okay to disagree. Now what are the different opinions and what works well for your team and project? It’s important to stay to your core and vision. Why would you pick THIS over THAT?

It’s a fun and exciting time if you are

28:41 – Charles: What are you

28:47 – Rob: InVision and InVision studio. It’s a tool for designing screens. I work on that during the day and during the night I work on Aurelia.

30:43 – Chuck: I am pretty sure that we have had people from InVision on a show before.

31:03 – Rob comments.

Rob: How we all work together.

31:20 – What is coming in with Aurelia next?

31:24 – Rob: We are trying to work with as much backwards compatibility as we can. So you don’t see a lot of the framework code in your app code. It’s less intrusive. We are trying next, can we keep the same language, the same levels, and such but change the implementation under the hood. You don’t learn anything new. You don’t have new things to learn. But how it’s implemented it’s smaller, faster, and more efficient. We have made the framework more pluggable to the compiler-level. It’s fully supported and super accessible.

Frameworks will come and go – this is my belief is that you invest in the standards of the web. We are taking that up a notch. Unobtrusiveness is the next thing we want to do. 

We’ve always had great performance and now taking it to the next level. We are doing a lot around documentation. To help people understand what the architectural decisions are and why? We are taking it to the next level from our core. It’s coming along swimmingly so I am really excited. We’ve already got 90% test coverage and over 40,000 tests.

37:33 – Chuck: Let’s get you on JavaScript Jabber!

38:19 – Chuck: Where can people find you?

38:22 – Twitter, and everywhere else. Blog!

39:17 – Chuck: Picks?

39:23 – Rob dives in!

Links:

• jQuery
• Angular
• JavaScript
• Vue
• C++
• C#
• InVision
• Aurelia
• Aurelia Blog by Rob
• Rob Eisenberg’s Twitter
• Rob’s Website
• Rob’s LinkedIn
• Rob’s GitHub
• Rob’s Episode 9
• Rob’s Episode 80
• Rob’s Episode 203

Sponsors:

• Get A Coder Job
• Fresh Books
• Cache Fly

Picks:

Rob

• Database: Orbit DB
• Robit Riddle
• The Wingfeather Saga

Charles

• Used to play: Dungeons and Dragons
• Little Wizards
• Park City, UT
• VRBO

Panel:

• AJ O’Neal
• Joe Eames
• Jesse Sanders

Special Guest: Sean Hunter

In this episode, the panel talks with Sean Hunter who is a software developer, speaker, rock climber, and author of “Aurelia in Action” published by Manning Publications! Today, the panelists and Sean talk about Aurelia and other frameworks. Check it out!

Show Topics:

0:00 – Advertisement: KENDO UI

0:38 – Joe: Hello! Our panelists are AJ, Jesse, myself, and our special guest is Sean Hunter (from Australia)! What have you been doing with your life and what is your favorite movie?

1:45 – Guest talks about Vegemite!

2:20 – Guest: I was in the UK and started using Aurelia, which I will talk about today. I have done some talks throughout UK about Aurelia. Also, the past year moved back to Australia had a baby son and it’s been a busy year. Writing a book and being a new parent has been hard.

3:22 – Panel: Tell us the history of Aurelia, please?

3:31 – Panel: Is it like jQuery, React, Vue or what?

3:44 – Guest: Elevator pitch – Aurelia is a single-page app framework! It’s most similar to Vue out of those frameworks; also, similarities to Ember.js.

4:30 – Guest goes into detail about Aurelia.

6:15 – Panel: It sounds like convention over configuration.

6:42 – Guest: Yes that is correct.

7:21 – Panel: Sounds like there is a build-step to it.

7:39 – Guest: There is a build-step you are correct. You will use Webpack in the background.

9:57 – The guest talks about data binding among other things.

10:30 – Guest: You will have your app component and other levels, too.

10:37 – Panel: I am new to Aurelia and so I’m fresh to this. Why Aurelia over the other frameworks? Is there a CLI to help?

11:29 – Guest: Let me start with WHY Aurelia and not the other frameworks. The style that you are using when building the applications is important for your needs. In terms of bundling there is a CUI and that is a way that I prefer to start my projects. Do you want to use CSS or Webpack or...? It’s almost a wizard process! You guys have any questions about the CLI?

14:43 – Panel: Thanks! I was wondering what is actually occurring there?

15:25 – Guest: Good question. Basically it’s that Aurelia has some built-in conventions. Looking at the convention tells Aurelia to pick the Vue model by name. If I need to tell the framework more information then...

17:46 – Panel: I think that for people who are familiar with one or more framework then where on that spectrum would Aurelia fall?

18:20 – Guest: It’s not that opinionated as Ember.js.

19:09 – Panel: Talking about being opinionated – what are some good examples of the choices that you have and how that leads you down a certain path? Any more examples that you can give us? 

19:38 – Guest: The main conventions are what I’ve talked about already. I can’t think of more conventions off the top of my head. There are more examples in my book.

20:02 – Panel: Your book?

20:10 – Guest: Yep.

20:13 – Panel.

20:20 – Guest. 

21:58 – Panel: Why would I NOT pick Aurelia?

22:19 – Guest: If you are from a React world and you like having things contained in a single-file then Aurelia would fight you. If you want a big company backing then Aurelia isn’t for you.

The guest goes into more reasons why or why not one would or wouldn’t want to use Aurelia.

24:24 – Panel: I think the best sell point is the downplay!

24:34 – Guest: Good point. What does the roadmap look like for Aurelia’s team?

25:00 – Guest: Typically, what happens in the Aurelia framework is that data binding (or router) gets pushed by the core team. They are the ones that produce the roadmap and look forward to the framework. The core team is working on the NEXT version of the framework, which is lighter, easier to use, and additional features. It’s proposed to be out for release next year.

26:36 – Advertisement – Sentry.io

27:34 – Panel: I am going to take down the CLI down and see what it does. I am looking at it and seeing how to teach someone to use it. I am using AU, new command, and it says no Aurelia found. I am stuck.

28:06 – Guest: What you would do is specify the project name that you are trying to create and that should create it for you. 

28:40 – Panel.

28:45 – Panel.

28:50 – Panel: Stand up on your desk and say: does anyone know anything about computers?!

29:05 – Panelists go back-and-forth.

29:13 – Panel: What frameworks have you used in the past?

29:17 – Guest: I was using single-paged apps back in 2010.

31:10 – Panel: Tell us about the performance of Aurelia?

31:17 – Guest: I was looking at the benchmarks all the time. Last time I looked the performance was comparable. Performances can me measured in a number of different of ways.

The guest talks about a dashboard screen that 20 charts or something like that. He didn’t notice any delays getting to the client.

33:29 – Panel: I heard you say the word “observables.”

33:39 – Guest answers the question.

35:30 – Guest: I am not a Redux expert, so I really can’t say. It has similar actions like Redux but the differences I really can’t say.

36:11 – Panel: We really want experts in everything! (Laughs.)

36:25 – Panelist talks about a colleagues’ talk at a conference. He says that he things are doing too much with SPAs. They have their place but we are trying to bundle 8-9 different applications but instead look at them as...

What are your thoughts of having multiple SPAs?

37:17 – Guest.

39:08 – Guest: I wonder what your opinions are? What about the splitting approach?

39:22 – Panel: I haven’t looked at it, yet. I am curious, though. I have been developing in GO lately.

40:20 – Guest: I think people can go too far and making it too complex. You don’t want to make the code that complex.

40:45 – Panel: Yeah when the code is “clean” but difficult to discover that’s not good.

41:15 – Guest: I agree when you start repeating yourself then it makes it more difficult.

41:35 – Panel: Chris and I are anti-framework. We prefer to start from a fresh palette and see if a framework can fit into that fresh palette. When you start with a certain framework you are starting with certain configurations set-in-place. 

42:48 – Joe: I like my frameworks and I think you are crazy!

43:05 – Panel.

43:11 – Joe: I have a love affair with all frameworks.

43:19 – Panel: I think I am somewhere in the middle.

43:49 – Panel: I don’t think frameworks are all bad but I want to say that it’s smart to not make it too complex upfront. Learn and grow.

44:28 – Guest: I think a good example of that is jQuery, right?

45:10 – Panelist talks about C++, jQuery, among other things.

45:34 – Guest: Frameworks kind of push the limits.

46:08 – Panelist talks about JavaScript, frameworks, and others.

47:04 – Panel: It seems simple to setup routes – anything to help with the lazy way to setup?

47:35 – Guest answers question.

48:37 – Panel: How do we manage complexity and how does messaging work between components?

48:54 – Guest: The simple scenario is that you can follow a simple pattern, which is (came out of Ember community) and that is...Data Down & Actions Up!

50:45 – Guest mentions that Aurelia website!

51:00 – Panel: That sounds great! Sounds like the pattern can be plugged in easily into Aurelia.

51:17 – Picks!

51:20 – Advertisement: Get A Coder Job!

END – Advertisement: CacheFly!

Links:

• JavaScript
• React
• Redux
• Webpack
• Elixir
• Ember.js
• Vue
• GO
• jQuery
• Node.js
• Puppeteer
• Cypress
• Utah JS 2018 – Justin McMurdie’s Talk
• Aurelia
• Sean Hunter’s Book!
• Sean Hunter’s Twitter
• Sean Hunter’s Website
• Sean Hunter’s GitHub

Sponsors:

• Kendo UI
• Sentry
• CacheFly

Picks:

Joe

• React Conf.
• Endless Quest

AJ

• Extreme Ownership
• GO Language
• Harry’s and Flamingo

Jesse Sanders

• The Miracle Morning
• React Hooks
• Apple Products

Sean

• Doesn’t Have to Be Crazy at Work
• Discount Code for Aurelia in Action -  hunterpc (40% off Aurelia in Action, all formats)
• Apple Watch

Sponsors

• Triplebyte offers a $1000 signing bonus
• Sentry use the code “devchat” for $100 credit
• Linode
• CacheFly

Panel

• Charles Max Wood
• Aimee Knight
• AJ O’Neal
• Aaron Frost
• Joe Eames

Joined by Special Guest: Gareth McCumskey

Summary

Gareth McCumskey introduces JAMstack and serverless. He goes into great detail on how it works. Aimee Knight and Aaron Frost voice their concerns about going serverless. Aimee thinks it feels dirty. Aaron has concerns about the code, is it actually easier, what use cases would he use it for, and does it actually save money. Gareth addresses these concerns and the rest of the panel considers the positive and negatives of using JAMstack and serverless. Charles Max Wood asks for specific use cases; Gareth supplies many uses cases and the benefits that each of these cases.

Links

• http://herodev.com/
• https://thinkster.io/
• https://jamstack.org/
• https://www.mongodb.com/cloud/stitch
• https://expatexplore.com/
• https://serverless.com/
• https://www.cloud66.com/
• https://aws.amazon.com/dynamodb/
• https://twitter.com/garethmcc
• https://www.facebook.com/javascriptjabber
• https://twitter.com/JSJabber

Picks

Charles Max Wood:

• Join the mailing list
• Watch out for new podcasts
• Send me defunct podcasts you love chuck@devchat.tv

Aimee Knight:

• Productivity Isn’t About Time Management. It’s About Attention Management.
• Quest Nutrition Protein Bars

AJ O’Neal:

• Distant Worlds: Music from Final Fantasy by Nobuo Uematsu
• Legend Of Zelda Concert 2018 Original Soundtrack by Never Land Orchestra  
• How to Diagnose and Fix Everything Electronic by Michael Jay Geier  

Aaron Frost:

• The Go-Giver, Expanded Edition: A Little Story About a Powerful Business Idea

Gareth McCumskey:

• https://www.finalfantasyxiv.com/
• Steam Play on Linux

Joe Eames:

• Expanding your horizons
• Seven Languages in Seven Weeks: A Pragmatic Guide to Learning Programming Languages
• Seven More Languages in Seven Weeks: Languages That Are Shaping the Future
• https://elm-lang.org/

Sponsors

• Triplebyte offers a $1000 signing bonus
• Sentry use the code “devchat” for $100 credit
• Linode
• CacheFly

Panel

• AJ O’Neal

Joined by special guest: Sam Selikoff

Episode Summary

In this episode of JavaScript Jabber, Sam Selikoff, Co-Founder at EmberMap, Inc. starts with giving a brief background about himself and his work followed by a discussion with AJ O’Neal about the Ember community. Sam mentions some of the biggest advantages in using Ember, and what it should and should not be used for. He explains the architecture of Ember apps, addresses some of the performance concerns and then dives into Octane in detail. He talks about a bunch of Ember components, compiler compatibility, relative weight of Ember apps compared to other frameworks, the underlying build system, and security considerations. Sam then helps listeners understand the usage of ES6 classes and decorators in Ember at length. At the end, they discuss component rendering and element modifiers and move onto picks.

Links

• Sam’s website
• Sam on Twitter
• Sam on GitHub

Follow JavaScript Jabber on Devchat.tv, Facebook and Twitter.

Picks

AJ O’Neal:

• Good Mythical Morning - YouTube

Sam Selikoff:

• The Man In the High Castle  
• Tailwind CSS

Sponsors

• Triplebyte offers a $1000 signing bonus

• Sentry use the code “devchat” for $100 credit

• CacheFly

Panel

• Charles Max Wood
• Joe Eames
• Christopher Buecheler
• Aimee Knight
• AJ O’Neal

Joined by special guest: Dan Shappir

Episode Summary

In this episode of JavaScript Jabber, special guest Dan Shappir, Performance Tech Lead at Wix, kicks off the discussion by defining server-side rendering (SSR) along with giving its historical background, and touches on the differences between server rendering and server-side rendering. He helps listeners understand in detail how SSR is beneficial for the web and takes questions from the panel about how it affects web performance in cases where first-time users and returning users are involved, and how does SSR fare against technologies such as pre-rendering. He then elaborates on the pitfalls and challenges of SSR including managing and declaring variables, memory leaks, performance issues, handling SEO, and more, along with ways to mitigate them. In the end, Dan sheds some light on when should developers use SSR and how should they start working with it.

Links

• Dan’s Twitter
• Dan’s GitHub
• SSR
• WeakMap

Follow JavaScript Jabber on Devchat.tv, Facebook and Twitter.

Picks

Christopher Buecheler:

• Tip - Take some time off once in a while

Aimee Knight:

• Learning How to Learn: Powerful mental tools to help you master tough subjects

AJ O’Neal:

• Fatherhood!

Joe Eames:

• Tiny Towns

• The Goldbergs

Charles Max Wood:

• EverywhereJS

• Christopher Buecheler’s books

• Get a Coder Job - Publishing soon!

Dan Shappir:

• Quora

• Corvid by Wix

• You Gotta Love Frontend Conferences

Sponsors

• Sentry use the code “devchat” for 2 months free on Sentry small plan

• CacheFly

Host: Charles Max Wood

Joined By Special Guest: Noam Rosenthal

Episode Summary

Noam has recently started offering his services and experiences independently after 20 hands-on years in the software industry. His most recent position was as a Software Architect working on the Wix Editor at Wix, an Israeli cloud-based web development platform.

Noam was first introduced to programming at the age of seven when he started creating games in Pascal language. He then went onto learn HTML. Charles and Noam talk about how the programming community has changed over the years and how it is a lot easier to access knowledge today. On how to improve as a developer, Noam recommends not staying in the comfort zone of the job description and doing as many volunteer projects as possible.

Noam is also a musician and he plays base in Lost Highways music band. When he isn't coding he is busy producing the songs for their new upcoming album with his band.

Links

• Noam's LinkedIn

• Noam's Twitter

• Noam's Medium

• Rack

• Rust Language

• TensorFlow

• Shadertoy

• Lost Highways

• Ultimate Guitar Tabs

• https://www.facebook.com/javascriptjabber

• https://twitter.com/JSJabber

• https://www.facebook.com/DevChattv

Picks

Noam Rosenthal:

• For developers working with JavaScript - learn another language such as Rust Language

• TensorFlow

• Shadertoy

• Learn to play an instrument

• Ultimate Guitar Tabs

• Do volunteer projects and do not stay in the comfort zone of work

Charles Max Wood:

• Cibola Burn

• The Seven Principles for Making Marriage Work Book by John M. Gottman and Nan Silver

• OBS: Open Broadcaster Software

JSJ BONUS EPISODE: Observables and RxJS Live with Aaron Frost

Mon Jul 29 2019 13:00:56 GMT+0300 (+03)

Episode Number: bonus

Duration: 29:35

https://media.devchat.tv/js-jabber/JSJ_Bonus_Aaron_Frost.mp3

Host: Charles Max Wood

Joined by Special Guest: Aaron Frost

Episode Summary

Aaron Frost joins Charles to talk about what Observables are and why developers should learn about them and use them in their code. He explains the difference between Observables, Promises and Callbacks with an example. Aaron then invites all listeners to attend the upcoming RxJS Live Conference and introduces the impressive speaker line-up. The conference will take place on September 5-6 in Las Vegas and tickets are still available. Aaron also offers a $100 discount to all listeners with the code "chuckforlife". For any questions you can DM Aaron at his Twitter account.

Links

• RxJS Live Conference
• RxJS Conference Tickets
• Aaron's Twitter
• Promises
• Callbacks

Sponsors

• Sentry– use the code “devchat” for $100 credit 

Panel

• Charles Max Wood

• AJ O’Neal

• Joe Eames

• Aimee Knight

With Special Guest: Evan Weaver

Episode Summary

Evan Weaver is the CEO and cofounder of FaunaDB, a serverless database and a great way to get started with GraphQL. Evan talks about what went into building the FaunaDB and his background with Twitter. FaunaDB arose from trying to fix Twitter’s scalability issues, and the panel discusses scalability issues encountered in both large and small companies. They talk about the difference between transient and persistent data. They discuss how to develop locally when using a serverless database and the importance of knowing why you’re using something. Evan talks about how developing locally works with FaunaDB. He addresses concerns that people might have about using FaunaDB since it is not backed by a tech giant. Evan talks about some of the services FaunaDB offers and talks about the flexibility of its tools. He talks about how to get started with FaunaDB and what the authentication is like. Finally, Evan talks about some well known companies that are using FaunaDB and what they are doing with it. 

Links

• FaunaDB

• GraphQL

• Netlify

• AWS Lambda

• Apollo.io

• SQL

• Jamstack 

• Akkeris

• Graphile

Follow DevChat on Facebook and Twitter

Picks

Charles Max Wood:

• Captain Sonar

• Canny

• JSJ Reccomendations

Aimee Knight:

• Falling in Reverse

Joe Eames:

• Battlestations

Evan Weaver

• Forza Motorsport

• Follow Evan on Twitter and Github @evan

Sponsors

• Sentry use the code “devchat” for 2 months free on Sentry small plan

• Ruby Rogues

• React Native Radio

• CacheFly

Host: Charles Max Wood

Joined by Special Guest: Sam Selikoff

Episode Summary

Sam Selikoff, Co-Founder at EmberMap shares his journey of how he became a developer. Sam was an Economics major in college and he really loved the theory of economics.

When he graduated, he started working as a consultant and while working with data for statistical analysis he found that he enjoyed working with SQL and that how he started his developing career.

Sam explains why he prefers Ember.js framework to other frameworks. He also talks about the projects he is working on currently.

Apart from coding Sam enjoys reading economics books and playing music with his family. He shares some of his favorite books to read on the Theory Of Economics.

Links

• JSJ 364: Ember Octane with Sam Selikoff

• EmberMap Podcast

• Sam's Twitter

Picks

Charles Max Wood

• Podcast Movement

Sam Selikoff

• UPLIFT Desk

• Midsommar Movie

Vitali Zaidman is a full stack developer who works for WellDone Software Solutions and is currently working on a SEO project. Today’s show is about SEO for developers. SEO stands for search engine optimization, which helps your website appear higher on search engines.

 SEO has changed a lot in the past 10 years. It has become much more regulated, and the “dirty tricks” of the past will actually penalize you, so it is important to do it properly. Today the best way to promote yourself on Google besides making good content is for developers to optimize the content, make it small, operational, secure, accessible, and operate on mobile. Much of it goes back to using semantic HTML since Google looks at it before looking at the structure of your website, how valuable it is, and how users interact with it. Having good semantics helps Google determine how valuable it is, so semantic HTML should be a top priority. Semantic HTML can also make your site more accessible to users, which will in turn give you a larger audience. 

The panel talks about some of the challenges of SEO faced by companies. While bigger companies have the privilege of dedicated SEO teams, small companies often lack these specialists. Thankfully, Google has made their guidelines for SEO very accessible and gives you a lot of tools to track your optimization. The panel talks about different methods of SEO, such as including FAQ at the bottom of the web page, optimizing page speed, and image optimization. Structured data like questions and answers enriches the data that is shown for users on the search results page. To score your website’s SEO, Google released the tool PageSpeed Insights, which will assign your website a performance score. 

Google uses two main tools to track a website’s SEO. First, they use real field data. If you opt in to ‘help improve Chrome’s features and performance’ when you install Chrome, it tracks how fast websites load on your Chrome, and they collect this information to understand how webpages load. It is required that your website has a certain amount of visitors to be tracked and added to the database. Second, Google has their own devices that will check your website. Currently, they are using a Moto G4 to test for mobile access, and a slow internet connection. Because of this, it is pretty easy to get a good score on desktop, but difficult to get a good score on mobile. The technology that drives all this is called Lighthouse. 

Overall, performance is the main thing users look for, so aim for good performance and fast websites. The panel discusses the correlation between performance and SEO. For example, Fox News and CNN are two of the top search results for ‘news’, but they have a dismal Google PSI score. They conclude that performance shouldn’t be ignored, but be careful about directly correlating performance and SEO. They also caution against getting obsessed over certain aspects of SEO by themselves. 

Panelists

• Dan Shapir

• Aimee Knight

• Charles Max Wood

With special guest: Vitali Zaidman

Sponsors

• Tidelift

• Sentry use the code “devchat” for 2 months free on Sentry’s small plan

• Elixir Mix

Links

• SEO

• JSON

• Google Webmaster guidelines

• Google PageSpeed Insights

• Chrome CrUX

• Lighthouse

• Here's How the Google Speed Update Will Impact Your Site

• SEO for Developers - A Quick Overview

• Google Quality Guidelines

Follow DevChatTV on Facebook and Twitter

Picks

Aimee Knight:

• Spotify CLI

Dan Shapir:

• Chrome Dev Summit 2019

• Dan Shapir on Twitter

• The Anubis Gates

Charles Max Wood:

• St. George Marathon

Vitali Zaidman: 

• Vitali’s website

• Arzamas Academy

• Follow Vitali on Medium and Twitter

Today the panel is talking about security features that are being added to Node 13. AJ talks about the background and what he’s working with Let’s Encrypt. He talks about changes that Node has made to the TLS module. TLS is a handshake that happens between a client and a server. They exchange certificates, generate some random numbers to use for encryption, and TLS handles the encryption. The move to HTTP/2 is all about fixing legacy bugs and legacy features from the SSL days and reducing the number of handshakes.

AJ talks about the difference between TLS and HTTPS. While TLS reduces the handshakes between client and server, HTTPS is just HTTP and has no knowledge that TLS is going on. HTTP/2 is more baked in as both encryption and compression are part of the specification and you get it automatically. HTTP/2 is also supposed to be faster because there’s fewer handshakes, and you can build heuristic based web servers. Since browsers have varying degrees of compatibility, a smart HTTP/2 server will classify the browser and anticipate what files to send to a client based on behavior and characteristics without the client requesting them

A lot of these new features will be built into Node, in addition to some other notable features. First, there will now be set context on the TLS object. Second, if you’re connected to a server, and the server manages multiple domains, the certificate will have multiple names on it. Previously, each different server name had a different network request, but now a .gitcertificate will let you get all the metadata about the certificate, including the primary domain and all the secondary domains and reuse the connections. 

These new features are a great improvement on the old Node. Previously, the TLS module in Node has been an absolute mess. These are APIs that have been long neglected, and are long overdue core editions to Node. Because of these additions, Node Crypto has finally become usable. HTTP/2 is now stable, usable, and has backwards compatable API, and a dictionary of headers to make it more efficient in compression.

The conversation turns back to certificates, and AJ explains what a certificate is and what it represents. A certificate has on it a subject, which is a field which contains things like common name, which in the case of HTTPS is the server name or host name. then it will have subject alternative names (SAN), which will have a list of other names that are valid on that certificate. Also included on the certificate is the name of the authority that issued the certificate. AJ talks about some of the different types of certificates, such as DV, OV, and EV certificates. They differentiate between encryption and hashing. Hashing is for verifying the integrity of data, while encryption can be used either as signing to verify identity or to keep data owned privately to the parties that are part of the connection. Encryption does not necessarily guarantee that the data is the original data. The show concludes with AJ talking about how he wants to make encryption available to the average person so that everyone can share securely. 

Panelists

• Steve Edwards

• AJ O’Neal

• Charles Max Wood

Sponsors

• Tidelift

• Sentry use the code “devchat” for 2 months free on Sentry’s small plan

• Ruby Rogues

Links

• Let’s Encrypt

• Greenlock

• HTTP/2

• Node.js

• Node Crypto

• JWK

• LZMA

• Gzip

• Broccoli.js

• HTTPS

• GCM

• ASN.1

• OWASP list

• jwt.io

• Diffie Hellman Key Exchange

• Khana Academy Diffie-Hellman Key Exchange pt.2

Follow DevChatTV on Facebook and Twitter

Picks

Steve Edwards:

• Panasonic SD-YD250 bread machine

AJ O’Neal:

• Greenlock v.3

• Samsung Evo 4 TOB paired with 2012 Macbook Pro

• Dave Ramsey on Christian Healthcare Ministries

Charles Max Wood: 

• Velcro straps

• Mac Pro Upgrade Guide

In this episode of JavaScript Jabber the panel interviews Sean Grove from OneGraph; asking him questions about GraphQL tooling and common complaints about GraphQL. Sean starts by explaining what GraphQL is and how it benefits frontend developers. GraphiQL is a frontend open sourced tool produced by OneGraph, Sean explains how this handy tool simplifies GraphQL. 

Authentication and authorization are one of the biggest criticisms of GraphQL. Sean walks the panel through the solution, getting a schema definition language and adding directives to build a simple authentication and authorization. The panel defines authentication and authorization and explains the difference. 

The next issue common with GraphQL that the panel discusses is migration. Sean explains how OneGraph helps with migration using a Rust network layer and how it works. They also discuss how to migrate without this tool. Without the tool it is painful and he recommends incremental migration. 

Sean explains that another problem in GraphQL is poor documentation. He explains why the documentation is poor and explains how they hope to fix it at OneGraph. The last issue they cover is the length of queries. Sean tells the panel how they can handle this problem with depth analysis or persistent queries. The episode ends with an elevator pitch for Reason. 

Panelists

• Aimee Knight

• AJ O’Neal

• Charles Max Wood

• Dan Shappir

Guest

• Sean Grove

Sponsors

• Split

• CacheFly

____________________________________________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

____________________________________________________________

Links

• https://github.com/graphql/graphiql 

• https://devchat.tv/js-jabber/jsj-401-hasura-with-tanmai-gopal/ 

Follow DevChatTV on Facebook and Twitter

Picks

Aimee Knight:

• http://ergonomictrends.com/hand-wrist-exercises-computer-users/ 

• Cats in your lap

AJ O’Neal:

• The Grievance Studies Affair 

• Go Proverbs 

• Music

Dan Shappir:

• Guatemala

• Tigana 

Sean Grove:

• Yuki Li: “Breaking Out of Box” 

Charles Max Wood:

• A Christmas Story

• Rudolf the Red-Nosed Reindeer

• The Little Drummer Boy

• Santa Claus Is Comin' to Town

• The Ultimate Gift

• Frosty the Snowman

Burke Holland works for Microsoft on the Azure team in developer relations. He starts the show talking about how he got started in serverless. He’s careful to note that just because things are marketed as serverless doesn’t always make them so. In order for something to be serverless, it must be sufficiently abstracted in terms of technology, only require payment for what is used, and infinitely scalable. He talks about the statelessness of serverless, and the panel discusses what it means to be stateless. Burke reminds listeners that serverless is not for long-lived operations, but there are features in serverless providers that can help you get around this. Burke talks about how writing serverless code differs from standard or previous coding approaches and practices. He advises that serverless functions are best kept small, and talks about how to fit them in with other kinds of APIs. 

The panelists talk about the multi-cloud and why people would want to be on multiple cloud servers. Burke talks about what Microsoft has done with Serverless Frameworks to accomplish multi-cloud compatibility. The JavaScript experts discuss the advantages and disadvantages of picking JavaScript over other languages, and Burke talks about why he prefers TypeScript and the Easy-Off feature. They talk about speed on a serverless platform, especially concerning the cold start time, which Azure is relentlessly trying to lower. He does talk about some things that can be done to decrease load time and about premium functions. The panel discusses how to debug serverless functions and tools that are available, such as the Azure Functions extension. 

They talk about ways to set up more secure functions to keep things from racking up charges. Burke talks about some things Microsoft does internally to control cloud costs, such as sending monthly reports with reminders to delete and using tools like Azure Reaper to delete short-lived projects. Azure can also put spending caps on subscriptions, but when you hit that cap you can’t serve any more requests. Burke concludes by saying that most of the time, going serverless is a lower-cost way to improve productivity, and because it’s event-driven, it allows you to tie into things that you’re already doing in the cloud. Serverless almost always justifies itself from an ease of use point of view and a cost point of view. 

Panelists

• Aimee Knight

• Steve Edwards

• Dan Shapir

• AJ O’Neal

• Charles Max Wood

Guest

• Burke Holland

Sponsors

• G2i

• Split

____________________________

> "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

____________________________________________________________

Links

• Microsoft Azure

• Swagger

• GraphQL

• Kong

• Serverless Frameworks

• TypeScript

• Serverless Doesn’t Have to Be an Infuriating Black Box

• Azure Functions

• CosmoDB

• Is Serverless Really as Cheap as Everyone Claims?

• Azure Reaper

Picks

Steve Edwards:

• Louis L'Amour books, especially The Lonesome Gods

• Ultra Sabers Azure Reaper

Burke Holland:

• Follow Burke on Github

Dan Shapir:

• Taking a vacation

AJ O’Neal:

• Hello World by Hannah Fry

• Ikea Kallax

Charles Max Wood:

• The MaxCoders Guide to Finding Your Dream Developer Job

• Buy Me a Coffee

• Devchat is looking for show hosts and sponsors!

In this episode of JavaScript Jabber the panel interviews security expert, Kevin A. McGrail. He starts by explaining what security frameworks and what they do. The panel wonders how to know if your developers are capable of self-auditing your security or if you need help. Kevin shares recommendations for companies to look at to answer that question. 

Aimee Knight explains the hell she has been in making changes to be compliant with CCPA. The panel considers how policies like this complicate security, are nearly impossible to be compliant with and how they can be weaponized. They discuss the need for technical people to be involved in writing these laws. 

Kevin explains how you can know how secure your systems actually are. He shares the culture of security first he tries to instill in the companies he trains. He also trains them on how to think like a bad guy and explains how this helps developers become security first developers. The panel discusses how scams have evolved and how the same scams are still being run. They consider the importance of automated training and teaching developers to do it right the first time.

Finally, they consider the different ways of authentication, passwords, passphrases, sim card, biometrics. Kevin warns against oversharing or announcing vacations. The panel discusses real-world tactics bad guys use. Kevin explains what he trains people to do and look out for to increase security with both social engineering and technical expertise. 

Panelists

• Aimee Knight

• AJ O’Neal

• Charles Max Wood

• Dan Shappir

• Steve Edwards

Guest

• Kevin A McGrail

Sponsors

• ABOUT YOU | aboutyou.com/apply

• Split

• CacheFly

____________________________________________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

____________________________________________________________

Links

• Ghost in the Wires

• https://www.infrashield.com/

Follow DevChatTV on Facebook and Twitter

Picks

Aimee Knight:

• The More Gender Equality, the Fewer Women in STEM 

AJ O’Neal:

• I'll Let Myself In: Tactics of Physical Pen Testers 

• Copying Keys from Photos, Molds & More 

• The LED Traffic Light and the Danger of "But Sometimes!" 

• Regina Spektor 

• The Weepies 

Dan Shappir:

• This is what happens when you reply to spam email 

• What is Your Password? 

Kevin A McGrail:

• XKCD Security 

• IT Crowd

• https://spamassassin.apache.org/

Steve Edwards:

• XKCD Password Generator 

• Nerd Sniping

Bruce Lawson is an expert in and proponent of semantic HTML. After receiving some good natured ribbing, Bruce walks the panel through the benefits of semantic HTML. He provides several examples on how it's used and in particular how it helps with other issues like accessibility and navigability on your websites.

Panel

• AJ O’Neal
• Aimee Knight
• Charles Max Wood
• Dan Shappir

Guest

• Bruce Lawson

Sponsors

• G2i
• Springboard | Promo code "JABBER" gives $500 off the job-guaranteed Course

____________________________________________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

____________________________________________________________

Links

• WebAIM: Web Accessibility In Mind
• <input type="date">
• The 4 minute business case for accessible online shopping

Picks

AJ O’Neal:

• Better Mic Sound
• Canon T4i 650D
• Canon T5i Course
• Magic Lantern
• Filmic Pro & Promovie

Aimee Knight:

• AddyOsmani.com - Native image lazy-loading for the web!

Charles Max Wood:

• Codineer - 100 days of Vue challenge

Dan Shappir:

• Alex Russell - The Mobile Web: MIA
• Bruce Lawson Website

Bruce Lawson:

• Taffy music band
• Follow Bruce on Twitter @brucel

JavaScript Remote Conf 2020

May 14th to 15th - register now!

Dave Karow is a developer evangelist for Split. He dives into how you can deliver software sustainably without burning out. His background is in performance and he's moved into smooth deliveries. He pushes the ideas behind continuous delivery and how to avoid getting paid to stay late in "free" pizzas.

Panel

• AJ O’Neal

• Aimee Knight

• Charles Max Wood

• Dan Shappir

Guest

• Dave Karow

Sponsors

• G2i | Enjoy the luxuries of freelancing

• Taiko - free and open source browser test automation

• CacheFly

____________________________________________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

____________________________________________________________

Links

• Split.io

• Continuous Delivery

• zeit.co

• The Practical Test Pyramid

• Accelerate

• The Unicorn Project

• Ender's Game

• Ender's Shadow

• Atlassian Summit

• DeliveryConf

• JSJ 418: Security Scary Stories and How to Avoid Them with Kevin A McGrail

• Feature toggle

• split.io Dave Karow

• Progressive Delivery

• Speaker Deck Dave Karow

• Learn Enough Command Line to Be Dangerous

• Beyond Code Bootcamp

Picks

Aimee Knight:

• Designing for Performance

• Early Riser or Night Owl?

Dan Shappir:

• web.dev

AJ O’Neal:

• CineRAID CR-H458

• DataCenter 8TB Drives

• Tiltamax Wireless Follow Focus System

Charles Max Wood

• The Expanse

• Course Creator PRO

Dave Karow:

• Accelerate

Follow JavaScript Jabber on Twitter > @JSJabb

Agritech start-up Brainwired, which provides livestock health monitoring and tracking solution has raised undisclosed funding from Mumbai Angels. The

Barnett, J. A. (James Arthur), 1923-

Moon, Krystyn R., 1974-

Osterbrock, Donald E

Konicek-Moran, Richard

Vinitzky-Seroussi, Vered

Betts, Dion E. (Dion Emile), 1963-

Hudley, Cynthia

Flowers, Sarah, 1952-

Lause, Mark A

Kabir, Nahid Afrose

Mallett, Margaret

Mansfield, Natalie

Teixeira, Joe

Busse, Richard C

Blum, Louise A., 1960-

Ewumbue-Monono, Churchill, 1961-

Lakes, Richard D

Filmer, Deon, author