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

• Triplebyte $1000 signing bonus

• Sentry use code “devchat” for 2 months free

Panel

• Charles Max Wood

• Aimee Knight

• Chris Ferdinandi

• AJ O’Neal

• Christopher Beucheler

Episode Summary

Today the panel discusses the effect of current development practices, such as the heavy reliance JavaScript, on the web. Chris explains why he believes that current development practices are ruining the web. The panelists discuss different situations where they see complications on the web. They discuss the advantages and disadvantages of using an enterprise scale platform like React. The panel discusses Twitter’s move away from their legacy code base to CSS and JavaScript. 

The panelists agree that the way things are built, since it’s so JavaScript heavy, is alienating to people who work with other languages, and in turn other areas like UI are undervalued. They talk about possible reasons things ended up this way and some of the historical perception of a frontend as not a place for ‘real’ development. Because the web is now a serious platform, things associated with the backend has been thrown at the frontend where it doesn’t belong. They talk about changes in the ways programming is viewed now versus the past. 

There is a discussion about how market demands that have influenced the web and if the market value CSS as highly as other languages. They mention some of the Innovations in CSS. Chris shares his solutions for the problems they’ve been discussing, namely using less JavaScript, leaning more heavily on what the browser gives you out of the box, and avoiding dependency where possible. They talk about ways to get involved if you want to take a leaner approach to the web. Ultimately, it is important to embrace things about the past that worked, but sprinkle in new technology when it makes sense

Links

• Stimulus

• React

• Vue

• AppleScript

• Perl

• .NET

• Angular 

Follow DevChat on Facebook and Twitter

Picks

Charles Max Wood:

• Tiny Epic Galaxies

• EverywhereJS

Aimee Knight:

• Complete Guide to Deep Work

Chris Ferdinandi:

• Developer Bait and Switch

• Vanillajslist.com

• Chris will be speaking at Artifact Conference

AJ O’Neal:

• Weird Al: White and Nerdy

• Quantum board game

• Deploy Sites with Only Git and SSH

Christopher Beucheler:

• Material

• Monstress

Sponsors

•  Datadog

• Sentry use code “devchat” for 2 months free

Panel

• Aimee Knight

• Chris Ferdinandi

• Christopher Beucheler

• AJ O’Neal

With Special Guest: Javan Makhmali

Episode Summary

Today’s guest is Javan Makhmali, who works for Basecamp and helped develop Trix. Trix is a rich text editor for the web, made purposefully simple for everyday use instead of a full layout tool. Trix is not the same as Tiny MCE, and Javan discusses some of the differences. He talks about the benefits of using Trix over other native browser features for text editing. He talks about how Trix has simplified the work at Basecamp, especially when it came to crossing platforms. Javan talks more about how Trix differs from other text editors like Google Docs and contenteditable, how to tell if Trix is functioning correctly, and how it works with Markdown.

The panel discusses more specific aspects of Trix, such as Exec command. One of the features of Trix is it is able to output consistently in all browsers and uses semantic, clean HTML instead of classnames. Javan talks about how Trix handles getting rid of the extraneous cruft of formatting when things are copy and pasted, the different layers of code, and the undo feature. He talks about whether or not there will be more features added to Trix. The panel discusses who could benefit from using Trix. The show finishes with Javan talking about Basecamp’s decision to make Trix open source and why they code in CoffeeScript. 

Links

• Trix

• Tiny MCE

• Contenteditable

• Markdown

• SVG

• HTML

• CoffeeScript

Follow DevChat on Facebook and Twitter

Picks

Javan Makhmali:

• API for form submissions

Chris Ferdinandi:

• CSS Grid

• Alex Russel Twitter thread

• How To Live a Vibrant Life with Early Stage Dementia

AJ O’Neal:

• Mario and Chill

• Chip Tunes 4 Autism: Catharsis

• Toilet Auger

Christopher Beucheler: 

• Medium to Own blog

Aimee Knight:

• Absolute Truth Unlearned as Junior Developer

Sponsors

• Datadog  

• Sentry use code “devchat” for 2 months free

Panel

• Aimee Knight

• AJ O’Neal

• Charles Max Wood

With Special Guest: Rene Rubalcava

Episode Summary

Rene is a software developer for ESRI and works in spatial and mapping software. ESRI has been around since 1969 and has seen their work explode since they shifted to providing address and location services. Rene talks about how he thinks about location and mapping when building software around it and things that he has to approach in unique ways. The panel discusses some of their past experiences with location software. Some of the most difficult aspects of this software is changing time zones for data and actually mapping the Earth, since it is not flat nor a perfect sphere. Rene talks about the different models used for mapping the Earth.

Most mapping systems use the same algorithm as Google maps, so Rene talks about some of the specific features of ArcGIS, including the ability to finding a point within a polygon. Rene talks about what routing is, its importance, and how it is being optimized with ArcGIS, such as being able to add private streets into a regular street network.

The panel discusses how the prevalence of smartphones has changed mapping and GPS and some of their concerns with privacy and location mapping. One thing ESRI is very careful about is not storing private information. Rene talks about the kinds of things he has seen people doing with the mapping and location data provided by ArcGIS, including a Smart Mapping feature for developers, mapping planets, indoor routing, and 3D models. 

Links

• Webricate 

• Esri

• ArcGIS

Follow DevChat on Facebook and Twitter

Picks

Rene Rubalcava:

• Old Man’s War series

• Always Be My Maybe

• Rene’s website

AJ O’Neal:

• INTL

• Colorful

• Time zones in Postgress

• Time zones in JavaScript

Aimee Knight:

• Advice to Less Experienced Developers

Charles Max Wood:

• Heber Half Marathon

• Netlify CMS

• Villainous

• Firefox

Sponsors

• Datadog

• Sentry use code “devchat” for 2 months free

Panel

• Aimee Knight

• Chris Ferdinandi

• Joe Eames

• AJ O’Neal

• Charles Max Wood

With Special Guests: Josh Thomas and Mike Hartington

Episode Summary

Today’s guests Josh Thomas and Mike Hartington are developers for Ionic, with Josh working on the open source part of the framework on Ionic. They talk about their new compiler for web components called Stencil. Stencil was originally created out of work they did for Ionic 4 (now available for Vue, React, and Angular) and making Ionic 4 able to compliment all the different frameworks. They talk about their decision to build their own compiler and why they decided to open source it. Now, a lot of companies are looking into using Stencil to build design systems

The panel discusses when design systems should be implemented. Since Ionic is a component library that people can pull from and use themselves, Jeff and Mike talk about how they are using Stencil since they’re not creating a design system.

The panel discusses some of the drawbacks of web components. They discuss whether or not Cordova changes the game at all. One of the big advantages of using Stencil is the code that is delivered to a browser is generated in such a way that a lot of things are handled for you, unlike in other systems.The panelists talk about their thoughts on web components and the benefits of using a component versus creating a widget the old fashioned way. One such benefit of web components is that you can change the internals of how it works without affecting the API. Josh and Mike talk about some of the abilities of Stencil and compare it to other things like Tachyons. There is a short discussion of the line between frameworks and components and the dangers of pre optimization. If you would like to learn more about Stencil, go to stenciljs.com and follow Josh and Mike @Jtoms1 and @mhartington.

Click here to cast your vote NOW for JavaScript Jabber - Best Dev Podcast Award

Links

• Building Design Systems book

• Stencil

• Cordova

• Shadow DOM

• Tachyons 

• Ionic 4

Follow DevChat on Facebook and Twitter

Picks

Aimee Knight:

• What Does Debugging a Program Look Like?

AJ O’Neal:

• Legend of Zelda: Link’s Awakening

• Neon Genesis Evangelion soundtrack

• Prettier

Chris Ferdinandi:

• Kindle Paperwhite

• Company of One

Charles Max Wood:

• Ladders with feet

• Lighthouse

• Acorns

Joe Eames:

• Moment.js

• How To Increase Your Page Size by 1500% article

• Day.js

Josh Thomas:

• Toy Story 4

Mike Hartington:

• Building Design Systems

• Youmightnotneed.com

Sponsors

• Netlify

• RxJS Live 

Panel

• Aimee Knight

• AJ O’Neal

• Charles Max Wood

With Special Guest: Jeff Meyerson

Episode Summary

Jeff Meyerson is the host of the Software Engineering daily podcast and has also started a company called FindCollabs, an online platform for finding collaborators and building projects. Jeff started FindCollabs because he believes there are all these amazing tools but people are not combining and collaborating as much as they could, when so much good could be accomplished together. FindCollabs is especially useful for working on side projects. The panelists discuss the problems encountered when you try to collaborate with people over the internet, such as finding people who are facing similar and gauging interest, skill, and availability. Thankfully, FindCollabs has a feature of leaving reviews and rating your partners so that users can accurately gauge other’s skill level. Users can also leave comments about their experience collaborating with others. The only way you can show competence with an interest is to contribute to another project. FindCollabs is also a good place to look for mentors, as well as for Bootcamp graduates or people going through an online coding course. If you are part of an organization, you can create private projects. The company plans to expand this feature to all users in the future.The panelists talk about their past experiences with collaborating with other people.

Jeff talks about his podcast Software Engineering Daily and how it got started and the focus of the podcast. As someone working in technology, it is important to stay current on up and coming technology, and listening to podcasts is an excellent way to do that. Jeff talks about where he thinks podcasting is going, especially for programmers. The panel discusses some of the benefits of listening to programming podcasts. Jeff talks about how he is prepping Software Engineering Daily for the future. He shares the audience size for Software Engineering Daily and some of the statistics for his different channels. Jeff has also released an app for Software Engineering Daily, and he shares some information on how it was written. Finally, Jeff gives advice for people who want to use FindCollabs and some of the next steps after creating a profile.

Click here to cast your vote NOW for JavaScript Jabber - Best Dev Podcast Award

Links

• FindCollabs

• Greenlock

• Telebit

• SwingCycle

• Software Engineering Daily

Follow DevChat on Facebook and Twitter

Picks

Aimee Knight:

• Burnout and the Brain

AJ O’Neal:

• Saber’s Edge from Final Fantasy by Distant Worlds

• Greenlock on FindCollabs

• Telebit on FindCollabs

Charles Max Wood:

• Adventures in Machine Learning on FindCollabs

• Adventures in Virtual Reality on FindCollabs

• Adventures in Python on FindCollabs

• Adventures in Java on FindCollabs

• Air conditioning

• MFCEO Project

Jeff Meyerson:

• Follow Jeff  @the_prion 

• Listen Notes

• Linbin’s Podcast Playlist

• Hidden Forces Podcast

Sponsors

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

• RxJS Live

Panel

• Charles Max Wood

• Christopher Beucheler

• AJ O’Neal

With Special Guest: John Somnez

Episode Summary

John is the founder of Bulldog Mindset andSimple Programmer, which teaches software developers soft skills, and the author of a couple books. He specializes in creating a personal brand and marketing. He addresses the rumors of him leaving software development and gives an introduction to marketing yourself as a software developer and its importance. The panel discusses their experience with consulting and how marketing themselves has paid off. John talks about the importance of having soft skills. In his opinion, the most important soft skills for programmers are communication, persuasion and influence, people skills and charisma. He talks about highlight those soft skills. The truth is, more and more people are hiring for people skills rather than technical skills. The panel discusses more about the importance of people skills.

John talks about ways to build your personal brand. One of the easiest ways is blogging but he talks about other methods like podcasts YouTube, writing books, and others. A key to building a personal brand is choosing something that you can become the best at, no matter how small it is. The panel shares their experiences of what things have gotten them attention and notoriety and talk about how other influential programmers got famous. They talk about interacting with central platforms like Medium and Github. Building a personal brand for software developers is the same as any other personal brand, such as having a consistent message, consistent logos and color schemes, and repeated exposure). Most people in the software world aren’t willing to do what’s necessary to build a personal brand, so it makes you stand out when you do it. John talks about the importance of controlling your image so that companies want to hire you. John gives a brief overview of his course How to Market Yourself as a Software Developer. 

Click here to cast your vote NOW for JavaScript Jabber - Best Dev Podcast Award

Links

• John Somnez’s books

• Data Grid Girl

• Follow JavaScript Jabber on Facebook and Twitter

Picks

Charles Max Wood:

• To Sell is Human

• How to Win Friends and Influence People

John Somnez:

• Follow John at bulldogmindset.com and simpleprogrammer.com

• The Little Book of Stoicism

• Training Peaks

Christopher Beucheler:

• Strasborg, France

AJ O’Neal

• Distant Worlds: Music from Final Fantasy

• Parallels

• Cam Slide

Sponsors

• Adventures in Blockchain

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

• My Ruby Story

Panel

• Aimee Knight 

• Chris Buecheler

• AJ O’Neal

With Special Guest: Brian Lonsdorf

Episode Summary

Brian Lonsdorf works for Salesforce, specializes in functional programming, and wrote a book called Professor Frisby’s Mostly Adequate Guide to Functional Programming. Brian talks about when he got into functional programming and when in their career others should be exposed to it. He talks about the fundamental tenets of functional programming (static mathematical functions), how it differs from object oriented programming, and how to manipulate data in a functional environment. The panel wonders if it is possible to use functional and object oriented programming together and discuss the functional core imperative shell. Brian talks about what is ‘super functional’ and why JavaScript isn’t, but includes methods for making it work. He shares some of the trade-offs he’s found while doing functional programming. Brian defines a monad and goes over some of the common questions he gets about functional programming, such as how to model an app using functional programming. The show concludes with Brian talking about some of the work he’s been doing in AI and machine learning. 

Links

• Promise

• Functional core, imperative shell

• RxJs

• Monad

• Professor Frisby's Mostly Adequate Guide to Functional Programming

Follow DevChat on Facebook and Twitter

Picks

Aimee Knight:

• After The Burial (band)

Chris Buecheler:

• Minecraft in JavaScript

AJ O’Neal:

• Crazy Little Thing Called Love by Queen

• Greenlock v3 campaign

Brian Lonsdorf:

• Follow Brian @drboolean

• Chris Penner Comonads

Sponsors

• Sustain Our Software

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

• Adventures in Blockchain

Panel

• Charles Max Wood

Episode Summary

In today’s show, Chuck talks about the recent tweet thread about 10x engineers. He goes through each of the points in the tweet and talks about each of them in turn. There are only two points he sort of agrees with, and believes the rest to be absolute garbage. One of the issues with this tweet is that it doesn’t define what a 10x engineer is. Defining a 10x engineer is difficult because it is also impossible to measure a truly average engineer because there are many factors that play into measuring productivity. Chuck turns the discussion to what a 10x engineer is to him and how to find one. A 10x engineer is dependent on the organization that they are a part of, because they are not simply found, they are made. When a 10x engineer is added to a team, the productivity of the entire team increases. Employers have to consider firstly what you need in your team and how a person would fit in. You want to avoid changing the entire culture of your organization. Consider also that a 10x engineer may be hired as a 2x engineer, but it is the employer that turns them into a 10x engineer. Overall, Chuck believes these tweets are asinine because it’s impossible to measure what makes a 10x engineer in the first place, and hiring a person that fits the attributes in the list would be toxic to your company. 

Links

• 10x engineer twitter thread

Follow DevChat on Facebook and Twitter

Picks

Charles Max Wood:

• Copyhackers.com

• Good to Great by Jim Collins

• Keto diet

• Podcast Movement

Episode Summary

Todd Gardner is a software developer, podcaster on the show Script and Style, startup founder,  and comedy host for Pub Conf, a ‘comedy after party for developers’. Since he was last on the show 6 years ago, he has seen his startup TrackJS become quite successful. TrackJS is a JavaScript error monitoring service which gives you visibility into your client side experience. It’s different from other tools because focused on simplicity, so you’ll never need a guy on your team dedicated solely to TrackJS because everyone can use it.

The panel begins by talking about debugging methods and tools. Some rely solely on the debugger built into their platform while others prefer to use a third party service. They discuss the necessity of using a third party debugger and if there are better solutions than just the built in debugger. 

They then discuss what to do after you’ve fixed a bug, such as if it is necessary to write a test to make sure it was completely fixed They talk about things to do to make debugging more effective. Todd and Aimee believe that code needs to begin by being designed for debug-ability. 

The panel discusses issues with invisible boundaries encountered while debugging, such as running out of memory. They talk about ways to mitigate issues that happen outside of your code base. Todd talks about the dangers of ad-blockers, and the panel agrees that it is important to consider how your website will be crippled by the user’s own technology. The end user in a production environment will have a different experience than you did writing it on a professional computer. 

Todd talks about the difference between debugging for the web versus a mobile application. Todd has encountered particular problems with debugging on a remote device, and he talks about how he solved the issue. The show concludes with Todd giving a quick elevator pitch for TrackJS

Panelists

• Chris Ferdinandi

• Christopher Buecheler

• Aimee Knight

• Charles Max Wood

• Steve Emmrich

With special guest: Todd Gardner

Sponsors

• Adventures in Blockchain

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

• React Round Up

Links

• Track JS (free trial available)

• Script and Style podcast

• PubConf

• Console.log

• Blackbox for Firefox and Chrome

• Redux lager

• Remote JS 

Follow DevChat on Facebook and Twitter

Picks

Christopher Buecheler:

• React/TypeScript cheat sheet 

Chris Ferdinandi:

• Pokemon Brawl 

• Space Invaders game

• Gomakethings.com newsletter

Aimee Knight:

• TechLead Youtube channel

Charles Max Wood:

• Atomic Habits

• Getting up at 4 am

Steve Emmrich:

• Trello

• Babushkas and grandmas to help you with your newborn

Todd Gardner:

• PubConf

• Follow Todd @toddhgardner or todd.mn

Episode Summary

Surma is an open web advocate for Google currently working with WebAssembly team. He was invited on the show today to talk about using web workers and how to move work away from the browser’s main thread. His primary platform is bringing multithreading out of the fringes and into the web. 

The panel talks about their past experience with web workers, and many of them found them isolated and difficult to use. Surma believes that web workers should pretty much always be sued because the main thread is an inherently bad place to run your code because it has to do so much. Surma details the differences between web workers, service workers, and worklets and explains what the compositer is. 

The panel discusses what parts should be moved off the main thread and how to move the logic over. Surma notes that the additional cost of using a worker is basically nonexistent, changes almost nothing in your workflow, and takes up only one kilobyte of memory. Therefore, the cost/benefit ratio of using web workers gets very large. They discuss debugging in a web worker and Surma details how debugging is better in web workers. 

Surma wants to see people use workers not because it will make it faster, but because it will make your app more resilient across all devices. Every piece of JavaScript you run could be the straw that breaks the camel’s back. There’s so much to do on the main thread for the browser, especially when it has a weaker processor, that the more stuff you can move away, the better.

The web is tailored for the most powerful phones, but a large portion of the population does not have the most powerful phone available, and moving things over to a web worker will benefit the average phone. Surma talks about his experience using the Nokia 2, on which simple apps run very slow because they are not being frugal with the user’s resources. Moving things to another thread will help phones like this run faster.  

The panel discusses the benefit of using web workers from a business standpoint. The argument is similar to that for accessibility. Though a user may not need that accessibility all the time, they could become in need of it. Making the app run better on low end devices will also increase the target audience, which is helpful is user acquisition is your principle metric for success. 

Surma wants businesses to understand that while this is beneficial for people in countries like India, there is also a very wide spectrum of phone performance in America. He wants to help all of these people and wants companies acknowledge this spectrum and to look at the benefits of using web workers to improve performance.

Panelists

• Charles Max Wood

• Christopher Buecheler

• Aimee Knight

• AJ O’Neal

With special guest: Surma

Sponsors

• Adventures in DevOps

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

• Adventures in Angular

Links

• Web workers

• Service workers

• Worklets 

• Ecto model

• Babel

• Swoosh

• Comlink

• WhatsApp

Follow DevChatTV on Facebook and Twitter

Picks

Charles Max Wood:

• For Love of Mother-Not

Surma:

• Follow Surma @DasSurma on Twitter and at dassur.ma

• WebAssembly Spec

AJ O’Neal:

• The GameCube Ultimate

• Pikmin for Wii and GameCube

• Super Monkey Ball

Christopher Buecheler

• CinemaSins Sincast podcast

Jonathan Lee Martin is an instructor and developer. He got his start in teaching at Big Nerd Ranch doing 1-2 week trainings for mid to senior developers, and then transitioned to 16 week courses for career switchers. He also worked for Digital Crafts for a year, and then wanted to focus on building out his own personal teaching brand. One of his first steps toward building his own brand was to publish his book, Functional Design Patterns for Express.js.The inspiration for Jonathan’s book came from his experience teaching career switchers. He wanted to experiment in the classroom with teaching functional programming in a way that would be very approachable and applicable and dispel some of the magic around backend programming, and that became the template for the book. 

Jonathan loves the minimalist nature of Express.js and talks about its many uses. He believes that it knowing design patterns can take you pretty far in programming, and this view is related to his background in Rails. When he was working in Rails taming huge middleware stacks, he discovered that applying design patterns made builds take less time. He talks about other situations where knowing design patterns has helped. Express.js leans towards object oriented style over functional programming, and so it takes to these patterns well. Express.js has its shortcomings, and that’s where Jonathan’s favorite library Koa comes into play. 

The conversation switches back to Jonathan’s book, which is a good way to start learning these higher level concepts. He purposely made it appealing to mid and senior level programmers, but at the same time it does not require a lot of background knowledge. Jonathan talks about his teaching methods that give people a proper appreciation for the tool. Jonathan talks more about why he likes to use Express.js and chose to use it for his book. He cautions that his book is not a book of monads, but rather about being influenced by the idea of composition over inheritance. He talks about the role of middleware in programming. 

The panel asks about Jonathan’s toolchain and approach to writing books, and he explains how his books are set up to show code. They discuss the different forms required when publishing a book such as epub, MOBI, and PDF. Jonathan found it difficult to distribute his book through Amazon, so he talks about how he built his own server. Charles notes that your method of distributing your book will depend on your goal. If you want to make the most money possible, make your own site. If you want to get it into as many hands as possible, get it on Amazon.

Many of the JavaScript Jabber panelists have had experience publishing books, and Jonathan shares that you can reach out to a publisher after you’ve self-published a book and they can get it distributed. Jonathan believes that If he had gone straight to a publisher, he would have gotten overwhelmed and given up on the book, but the step by step process of self-publishing kept things manageable. The panelists discuss difficulties encountered when publishing and editing books, especially with Markdown. Jonathan compares the perks of self-editing to traditional editing. Though he does not plan to opensource his entire editing pipeline, he may make some parts available. The show concludes with the panelists discussing the clout that comes with being a published author. 

Panelists

• Charles Max Wood

• Christopher Buecheler 

• J.C. Hyatt

With special guest: Jonathan Lee Martin

Sponsors

• Adventures in Blockchain

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

• The Freelancers’ Show

Links

• Big Nerd Ranch

• Digital Crafts

• JSJ 070: Book Club JavaScript Allonge with Reginald Braithwaite

• JavaScript Allonge by Reginald Braithwaite

• Functional Design Patterns for Express JS by Jonathan Lee Martin

• Node.js

• Express.js

• Koa

• Minjs 

• Sinatra

• Http.createserver

• Monads

• Middleware 

• Markdown

• Pandoc

• Diff-match-path library

• Epub

• MOBI

• LaTeX 

• Stripe Checkout

• Fstoppers

• Softcover

• Bookseller API 

Follow DevChatTV on Facebook and Twitter

Picks

Christopher Buecheler:

• Cluisbrace.com newsletter

J.C. Hyatt:

• Corsair wireless charging mouse pad

Charles Max Wood:

• Magnetic whiteboard baskets

• Mrs. Piggle-Wiggle books

Jonathan Lee Martin:

• Eric Elliot JS

• YellowScale

• Follow Jonathan and find his book at jonathanleemartin.com

Guest Paige Niedringhaus has been a developer full time for 3 years, and today she is here to talk about Node 12. One of the things she is most excited about is the ES6 support that is now available, so things that used to require React, Angular, or Vue can now be done in Node. The require function will not have to be used in Node 12. AJ is worried about some of these changes and expresses his concerns. Paige assures him that in the beginning you won’t have to switch things to imports. You may have to change file extensions/types so Node can pick up what it’s supposed to be using. They are also trying to make it compatible with CommonJS.

Node 12 also boasts an improved startup time. The panel discusses what specifically this means. They talk about the code cache and how Node caches the built in libraries that it comes prepackaged with. The V8 engine is also getting many performance enhancements. 

Paige talks about the shift from promises to async. In Node 12, async functions will actually be faster than promises. They discuss some of the difficulties they’ve had in the past with Async08, and especially callbacks. 

Another feature of Node 12 is better security. The transcripted security layer (TLS), which is how Node handles encrypted strains of communication, is upgrading to 1.3. The protocol is simpler to implement, quicker to negotiate sessions between the applications, provides increased end user privacy, and reduces request time. Overall, this means less latency for everybody. 1.3 also gets rid of the edge cases that caused TLS to be way far slower than it needed to be. 

The conversation turns to properly configuring default heap limits to prevent an ‘out of memory’ error. Configuring heap limits is something necessary when constructing an incredibly large object or array of objects. Node 12 also offers formatted diagnostic summaries, which can include information on total memory, used memory, memory limits, and environment lags. It can report on uncaught exceptions and fatal errors. Overall, Node 12 is trying to help with the debugging process. They talk about the different parsers available and how issues with key pairing in Node have been solved. 

Paige talks about using worker threads in Node 12. Worker threads are really beneficial for CPU intensive JavaScript operations. Worker threads are there for those things that eat up all of your memory, they can alleviate the load and keep your program running efficiently while doing their own operations on the sideline, and returning to the main thread once they’ve finished their job. None of the panelists have really used worker threads, so they discuss why that is and how they might use Worker Threads in Node 12. 

In addition, Node 12 is making Native module creation and support easier, as well as all the different binaries a node developer would want to support. Paige makes it a point to mention the new compiler and minimum platform standards. They are as follows:

• GCC minimum 6

• GLIVC minimum 2.17 on platforms other than Mac and Windows (Linux)

• Mac users need at least 8 and Mac OS 10.10

• If you’ve been running node 11 builds in Windows, you’re up to speed

• Linux binaries supported are Enterprise Linux 7, Debian 8, and Ubuntu 14.04

• If you have different requirements, go to the Node website

Panelists

• J.C. Hyatt

• Steve Edwards

• AJ O’Neal

With special guest: Paige Niedringhaus

Sponsors

• Tidelift

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

• Sustain Our Software

Links

• Async

• CommonJS

• njs

• Promise

• Node

• Event Stream

• llhttp

• llparse

• LLVM

• Papa Parse

• Json.stringify 

• Json.parse

• Optimizing Web Performance TLS 1.3

• Overlocking SSL

• Generate Keypair

Follow DevChatTV on Facebook and Twitter

Picks

J.C. Hyatt:

• AWS Amplify framework

• 12 Rules for Life: An Antidote to Chaos by Jordan Petersen

• React and Gatsby workshops

Steve Edwards:

• The Farside comic coming back?

AJ O’Neal:

• Field of Hopes and Strings

• Link’s Awakening

• Dune

Paige Niedringhaus:

• DeLonghi Magnifica XS Automatic Espresso Machine, Cappuccino Maker

• CONNECT.TECH Conference

Follow Paige on Twitter, Medium, and Github

Valeri Karpov is a maintainer on Mongoose, has started a few companies, and works for a company called Booster Fuels. Today’s topic debugging with Async/Await. The panel talks about some of the challenges of debugging with Async. AJ, however, has never encountered the same problems, so he shares his debugging method. 

Valeri differentiates between .catch vs try...catch, and talks about why he prefers .catch. There are two ways to handle all errors in an async function without leading to an unhandled promise rejection. The first is to wrap the entire body of the async function in a try...catch, has some limitations. Calling an async function always returns a promise, so the other approach is calling .catch on the promise to handle any errors that occur in that function body. One of the key differences is if you return a promise within an async function, and that return promise is wrapped in a try...catch, the catch block won’t get called if that promise is rejected, whereas if you call .catch on the promise that the function returns, you’ll actually catch that error. There are rare instances where this can get tricky and unintuitive, such as where you have to call new promise and have resolve and reject, and you can get unexpected behavior.

The panel discusses Valeri’s current favorite JS interview question, which is,  “Given a stream, implement a function called ‘stream to promise’ that, given a stream, returns a promise that resolves to the concatenation of all the data chunks emitted by the stream, or rejects if the stream emits an error event.” It’s really simple to get this qustion right, and really simple to get it wrong, and the difference can be catastrophic. AJ cautions listeners to never use the data event except in the cases Val was talking about, only use the readable event.

The conversation turns to the function of a readable event. Since data always pushes data, when you get a readable event, it’s up to you to call read inside the function handler, and then you get back a chunk of data, call read again and again until the read returns null. When you use readable, you are in control and you avoid piling functions into RAM. In addition, the right function will return true or false to let you know if the buffer is full or not. This is a way to mix imperative style into a stream.

The next discussion topics are the differences between imperative style and reactive style and how a waits and promises work in a normal four loop. A wait suspends the execution of a function until the promise is resolved. Does a wait actually stop the loop or is it just transpiling like a promise and it doesn’t stop the loop. AJ wrote a module called Batch Async to be not as greedy as promise.all but not as limited as other options.

The JavaScript panelists talk about different async iterators they’ve used, such as Babel. They discuss the merits of Babel, especially since baseline Android phones (which a significant portion of the population of the world uses) run UC Browser that doesn’t support Babel, and so a significant chunk of the population of the world. On the other hand, if you want to target a large audience, you need to use Babel.

Since frameworks in general don’t handle async very well, the panel discusses ways to mitigate this. They talk about different frameworks like Vue, React, and Express and how they support async functions. They discuss why there is no way for you to actually cancel an async option in an actual case, how complex canceling is, and what you are really trying to solve for in the cancellation process. 

Canceling something is a complex problem. Valeri talks about his one case where he had a specific bug that required non-generic engineering to solve, and cancelling actually solved something. When AJ has come across cancellation issues, it’s very specific to that use case. The rest of the panelists talk about their experiences with having to cancel something. 

Finally, they talk about their experience with async generator functions. A generator is a function that lets you enter into the function later. This makes sense for very large or long running data sets, but when you have a bounded items, don’t complicate your code this way. When an async generator function yields, you explicitly need to call next in order for it to pick up again. If you don’t call ‘next’, it’s essentially cancelled. Remember that object.keys and object.values are your friends. 

Panelists

• Christopher Buecheler

• AJ O’Neal

• Charles Max Wood

With special guest: Valeri Karpov

Sponsors

• The DevEd Podcast

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

• Adventures in DevOps

Links

• Mongoose

• Express 5

• Node Streams

• Pull Streams

• Masteringjs.io

• MongoDB

• Babel

• HTML

• Webpack

• Vue

• Express

• RxJS

• Console.log

• Json.stringify

• Batchasync.js

• How to Write Batch Async Functions

Follow DevChatTV on Facebook and Twitter

Picks

AJ O’Neal:

• Ethan Garofolo YouTube

Christopher Buecheler:

• Functional Design Patterns for Express.js

Charles Max Wood:

• Microsoft Ignite

• Maxcoders.io

Valeri Karpov:

• Follow Valeri on Twitter @code_barbarian and Github @vkarpov15

• Masteringjs.io

• Jurassic Park: A Novel

In this episode of My JavaScript Story is Charles talks to Mike Hartington. Mike Hartington is a Developer Advocate for Ionic Framework and a Google Developer Expert, but he is most famous in the developer community because of his beard.

Charles asks how Mike got introduced to development. Mike tried to code Tic-Tac-Toe and that was a challenge because knowing the rules to the game and trying to tell a computer the rules are two very two different things.

Mike then majored in Graphic Design at Rhode Island College, and started learning Flash and ActionScript. Mike talks about what kind of projects he created with Flash and ActionScript and then the process of teaching himself JavaScript.

Host: Charles Max Wood

Joined by Special Guest: Mike Hartington

Links

• Mike's Twitter

• Ionic

Sponsors

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

• Adventures in DevOps

• Adventures in Blockchain

• CacheFly

Picks

 Mike Hartington

• Star Wars: The Rise of Skywalker Trailer

Charles Max Wood:

• Atomic Habits by James Clear

• Superfans by Pat Flynn

Gant Laborde is the Chief Innovation Officer of Infinite Red who is working on a course for beginners on machine learning. There is a lot of gatekeeping with machine learning, and this attitude that only people with PhDs should touch it. In spite of this, Gant thinks that in the next 5 years everyone will be using machine learning, and that it will be pioneered by web developers. One of the strong points of the web is experimentation, and Gant contrasts this to the academic approach. 

They conversation turns to Gant’s course on machine learning and how it is structured. He stresses the importance of understanding unicode, assembly, and other higher concepts. In his course he gives you the resources to go deeper and talks about libraries and frameworks available that can get you started right away. His first lesson is a splashdown into the jargon of machine learning, which he maps over into developer terms. After a little JavaScript kung fu, he takes some tools that are already out there and converts it into a website.

Chris and Gant discuss some different uses for machine learning and how it can improve development. One of the biggest applications they see is to train the computers to figure monotonous tasks out while the human beings focus on other projects, such as watching security camera footage and identifying images. Gant restates his belief that in the next 5 years, AI will be everywhere. People will grab the boring things first, then they will go for the exciting things. Gant talks about his creation NSFW.js, an open source train model to help you catch indecent content. He and Chris discuss different applications for this technology.

Next, the panel discusses where machine learning can be seen in everyday life, especially in big companies such as Google. They cite completing your sentences in an email for you as an example of machine learning. They talk about the ethics of machine learning, especially concerning security and personal data. They anticipate that the next problem is edge devices for AI, and this is where JavaScript really comes in, because security and privacy concerns require a developer mindset. They also believe that personal assistant devices, like those from Amazon and Google, will become even more personal through machine learning. They talk about some of the ways that personal assistant devices will improve through machine learning, such as recognizing your voice or understanding your accent. 

Their next topic of discussion is authenticity, and how computers are actually incredibly good at finding deep fakes. They discuss the practice of placing passed away people into movies as one of the applications of machine learning, and the ethics surrounding that. Since developers tend to be worried about inclusions, ethics, and the implications of things, Gant believes that these are the people he wants to have control over what AI is going to do to help build a more conscious data set. 

The show concludes with Gant talking about the resources to help you get started with machine learning. He is a panelist on upcoming DevChat show, Adventures in Machine Learning. He has worked with people with all kinds of skill sets and has found that it doesn’t matter how much you know, it matters how interested and passionate you are about learning. If you’re willing to put the pedal to the metal for at least a month, you can come out with a basic understanding. Chris and Gant talk about Tensorflow, which helps you take care of machine learning at a higher level for fast operations without calculus. Gant is working on putting together a course on Tensorflow. If you’re interested in machine learning, go to academy.infinite.red to sign up for Gant’s course. He also announces that they will be having a sale on Black Friday and Cyber Monday.

Panelists

• Christopher Buecheler

With special guest: Gant Laborde

Sponsors

• React Round Up

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

• Adventures in Angular

Links

• Machine Learning: How To go from Zero to Hero

• NSFW.js

• Tensorflow.js

• PyTorch

• Keras

• Academy.infinite.red

• Gantlaborde.com 

Follow DevChatTV on Facebook and Twitter

Picks

Christopher Buecheler:

• Next.js

• Big Wreck, But For The Sun

Gant Laborde: 

• Nicornot.com

Free 5 day mini course on academy.infinite.red

Carl Mungazi is a frontend developer at Limejump in London. He is a former journalist and switched to programming in 2016. Today the panel is discussing the benefits of reading source code. Carl began reading source code because he came into programming late and from a different field. His first project was with Mithril, and he read the source code and documentation to help him understand it. The panelists discuss how reading the source code has helped them and others to improve their coding. They compare reading and understanding source code to learning a foreign language, and discuss  different methods. 

Carl gives some suggestions for reading source code effectively. He advises people to be patient and step through the code. Accept that you will probably take a wrong path at some point or another, but the more you read, the more you will see patterns in how libraries are structured. He also encourages listeners to approach the authors, as they are often happy to lend a hand. Reading source code is an active approach of stepping through, debugging, putting in break points, checking the stack, and so forth. It’s also important to do outside research. 

Since he has been reading source code, Carl has come to prefer plain JavaScript and libraries with as little code as possible. The panel discusses the benefits of small, simple libraries. Carl gives examples of techniques that he learned from reading a library source code and how he applied it to his own coding style. Reading source code has made him more careful about mixing logic and UI, and now he separates them. He also is more confident in seeing a problem, going to a preexisting library, and just importing the fix for that problem rather than the whole library. Reading source code is really about understanding the code you use in your project. It may slow you down, but you’ll be thankful in the long term because it will help you solve future bugs more efficiently. Carl talks more about his debugging process. He still relies on a debugger, but reading a library helps you to see patterns and guess the output of a function. These patterns persist in other libraries as well. Once you can guess correctly what will happen, you go back to reading the code and find instances where the output is unexpected, and fix it. Carl’s closing thoughts are that through reading source code, he has learned that although code is used differently in each library, they are all written in the same language, and therefore interrelated. This gave him more confidence in reading code because they’re all fundamentally the same. When a bug is discovered, he encourages listeners to look at the source code before googling a solution. 

Panelists

• AJ O’Neal

• Dan Shapir

• Steve Edwards

• Charles Max Wood

Guest

• Carl Mungazi

Sponsors

• Hasura.io 

• Sentry | Use the code “devchat” for $100 credit

• Adventures in Angular

Links

• Mithril.js

• Preact

• Limejump

Picks

AJ O’Neal

• Zen of Python

• The Go Proverbs

• Go with Versions

• Link’s Awakening soundtrack

Dan Shapir

• Programming Pearls book

• Lord of Light

Steve Edwards

• Jabra Elite 65T

Charles Max Wood

• Garth Brooks

• The Rocky movies

Carl Mungazi

• Follow Carl @CarlMungazi and carlmungazi.com

• EcmaScript Spec

• HTML 5.2

• Snarky Puppy

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is available on Amazon. Get your copy here today only for $2.99!

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is available on Amazon. Get your copy here today only for $2.99!

Today the panel is discussing iterating on open source projects. Aimee and AJ recall a conversation they had in the past on this subject and AJ talks about some of his experience iterating with open source. AJ believes that we have an obligation to capture the value of what you create so that we can reinvest and create more value, though he admits that making money in open source is a unique challenge because donations only really work if you have a project that gets billions of downloads a month. As your project grows, it has to change in order to survive, and eventually you will need to get financial support from your project. The panel agrees that some of the main issues with iterating in open source are maintaining the code and getting feedback from users, financial backing, and roadmapping and integrations.

The panel discusses their methods for getting feedback from their users. This feedback is valuable because it can show you things that you missed. They acknowledge that there can be conflicts of interest between those who only use the project and those who financially support it, and you have to make a choice. Unfortunately, someone is probably going to be inconvenienced no matter what choice you make. When making these decisions, you have to consider who it helps, who it frustrates, and who it may cause problems for. The panelists talk about different ways they’ve handled making these decisions in the past. The JavaScript experts talk about the importance of having data on your user base in order to make good choices for your users. They talk about different methods for notifying your users of upcoming changes and how it will affect compatibility, and some of the challenges with communicating with your users. AJ talks about an iteration he thought was a good idea but that a lot of people hated and how he noticed that the new users liked it but the old users did not. They panel agrees that people in general don’t like change. AJ talks about what he learned from this experience. 

Another common issue is integrating with other services. Integrating with cloud services, or at least giving people the option to integrate gives you an opportunity to reach more people and maintain the project long term. AJ gives some final thoughts to close the show, namely that most projects never go anywhere, and that’s ok. If you’ve got something that starts going somewhere, think early on about how you can better serve the community and remember that these people are mostly grateful and semi-willing to support you. He believes that if you are helping people create value, you deserve to see the fruits of your labor. He advises listeners to stay true to your open source ideals, think about your users perspective, and that the earlier you can think about this and make these choices, the better it is for your project

Panelists

• Aimee Knight

• Steve Edwards

• AJ O’Neal

• Charles Max Wood

**To receive your 40% OFF coupon for Manning Publications (good for all our products in all formats) visit us on Facebook - click on "Send A Message"and type "YES"**

Sponsors

• Sentry | Use the code “devchat” for $100 credit

Links

• How-npm-am-i

• React

• Vue.js

• Let’s Encrypt

• Async/await

• Node

Picks

Aimee Knight:

• Debug Like a Ninja

Steve Edwards:

• Jack Ryan 

AJ O’Neal:

• Why I, as a black man, attend KKK meetings

Charles Max Wood:

• It’s a Wonderful Life

• Mr. Kreuger’s Christmas

Daniel Caldas is calling from Singapore. He currently works as a software engineer for Zendesk and has also worked in Portugal and Germany. He has worked primarily on the frontend with Node and JavaScript. He talks about his experience testing JavaScript, how he got started with Jest, and why he likes it. Daniel finds Jest very easy to use and straightforward. He likes that  Jest has a single reference page for documentation. He feels that Jest is largely complete out of the box and has only made a small add on to get rid of Boilerplate in some tests.

Daniel explains what a snapshot, how they work, and why he prefers fixtures over factories. He gives tips on how to set up your tests so that they are easy to follow. He finds it helps to structure your scenarios in the fixture description. He talks about gotchas in Jest. While Jest is largely easy to use, Jest has been around for a while and breaking changes do happen. It’s important to check what version your code base is using. While there are a lot of free sources around Jest online, he advises listeners to stick as close to the official documentation as possible, or to people associated with Jest, and to read recent stuff. As for conventions, Jest has pretty much everything out of the box and the built in conventions make it easy to navigate any project that uses Jest.

Daniel talks about some of the features available in Jest, converting observables into promises, and tricks he has used to make tests easier to put together. He talks about his method for keeping his mocks and stubs straight. He advises listeners to have some organizational rules, such as starting the imports alphabetically, and to always follow those rules. He talks about how he runs tests and what environments he uses. While Jest is normally used for unit testing, Daniel has also used it for end to end tests, and he talks about his experience with an open source project doing both types in Jest. Daniel concludes the show by advising listeners starting with JavaScript and frontend, don’t think too much about the library you’re going to use because you’ll probably end up using Jest. It’s more important to have unit tests and a proper testing framework at the beginning than anything else. He also invites listeners to check out his open source work on Github.

Panelists

• Aimee Knight

• AJ O’Neal

• Charles Max Wood

**To receive your 40% OFF coupon for Manning Publications (good for all our products in all formats) visit us on Facebook - click on "Send A Message"and type "YES"**

Guest

• Danile Caldas

Sponsors

• Sentry | Use the code “devchat” for $100 credit

Links

• Zendesk

• Jest

• React

• Babel

• ESLint

• Async/Await

• Cypress

• React-d3-graph

• Unrevealed tips for unit testing with Jest

Picks

Aimee Knight:

• The Difference Between Fault Tolerance, High Availability, and Disaster Recovery

AJ O’Neal:

• Rubin Report with Lindsay Shepherd

Charles Max Wood:

• White Christmas

• Holiday Inn

Daniel Caldas:

• Home Alone

Carl is a developer from Zimbabwe currently living in London. He explains how he started out as a journalist and wound up doing web development to keep track of news stories coming out in his local area. He leveled up by attending meetups and talking to other developers. He currently works for LimeJump, an energy startup which is creating a virtual power plant by connecting together different power assets

Host: Charles Max Wood

Joined By Special Guest: Carl Mungazi

Sponsors

• Sentry

• CacheFly

______________________________________

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

______________________________________

Links

• Nailing Your First (Info-Product) Launch

• CarlMungazi.com

Picks

Carl Mungazi:

• React Dev Tools

Charles Max Wood:

• Gmelius

• Devchat Workshops

• The Dev Rev Podcast

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

JavaScript Remote Conf 2020

May 14th to 15th - register now!

Paige Niedringhaus started her career as a Digital Marketer before making the move to becoming a software developer at the Home Depot. She current works with React and Node building internal apps for them. This episode discusses the ins and outs of making that transition in a semi-recent world and community.

Host: Charles Max Wood

Joined By Special Guest: Paige Niedringhaus

Sponsors

• G2i | Enjoy the luxuries of freelancing

• CacheFly

______________________________________

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

______________________________________

Links

• JSJ 398: Node 12 with Paige Niedringhaus

• Syntax.

• GitHub testing-library/react-testing-library

• Gatsby

• NextJS

• Interview Cake

• Medium - Paige Niedringhaus

• Follow Paige on Twitter: @pniedri

Picks

Paige Niedringhaus:

• Breville Milk Frother

• Stuff You Should Know

Charles Max Wood:

• Instant Pot

• Sphero BB-8

JavaScript Remote Conf 2020

May 13th to 15th - register now!

Join us as we talk to Joyce Lin, a developer relations advocate with Postman, and we talk about this amazing tool for interacting with APIs. We discuss it’s more well-known features, and also learn about other less well known, but very powerful features that allow users to greatly increase the usefulness of the tool, both for front end and back end developers.

Panel

• Aimee Knight
• Steve Edwards

Guest

• Joyce Lin

Sponsors

• G2i | Enjoy the luxuries of freelancing
• Educative.io | Click here for 10% discount

____________________________________________________________

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

____________________________________________________________

Links

• Postman Roadmap on Trello
• Follow Postman on Twitter >
• Postman | The Collaboration Platform for API Development

Picks

Steve Edwards:

• The Big Red NO! Button Desktop Sound Toy

Joyce Lin:

• Follow Joyce on Twitter > @petuniaGray
• The Science of Well-Being by Yale University | Coursera

Follow JavaScript Jabber on Twitter > @JSJabber

JavaScript Remote Conf 2020

May 13th to 15th - register now!

Matt Crook joins the conversation to talk with the JavaScript Jabber panel to talk about his experience going through Nashville Software School. The panel discusses and asks questions about getting into programming, working through the bootcamp, and what prospects are for bootcamp graduates.

Panel

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

Guest

• Matt Crook

Sponsors

• Taiko
• Educative.io | Click here for 10% discount

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

Picks

AJ O’Neal:

• PostgREST
• The Way of Kings
• VirtualBox
• Bootable Installers for MacOS, Windows, and more

Aimee Knight:

• State of Microservices 2020 Report
• Peloton Bike

Charles Max Wood:

• The Hobbit
• D&D Starter Set
• JavaScript Weekly
• Devchat.tv Remote Meetups
• Devchat.tv Remote Conferences
• Reading to Kids

Steve Edwards:

• It Is Well With My Soul
• Pitbull Gold PRO Skull Shaver
• Brad Balfour

Dan Shappir:

• Gödel, Escher, Bach
• Translating "The Hobbit" in Captivity

Matt Crook:

• Follow Matt on Twitter > @mgcrook, Instagram, LinkedIn
• Swolenormous
• Fireship
• Static Headz
• Yugen

Follow JavaScript Jabber on Twitter > @JSJabber

JavaScript Remote Conf 2020

May 13th to 15th - register now!

The JSJ panel talks with Morad Stern from Wix about personal branding; what it is, why it’s important for developers, and how to build it.

Panel

• Steve Edwards
• AJ O’Neal
• Dan Shappir

Guest

• Morad Stern

Sponsors

• Taiko
• Educative.io | Click here for 10% discount

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

Links

• Obama asks America to learn computer science
• Configuring Apache Solr Multi-core With Drupal and Tomcat on Ubuntu 9.10

Picks

AJ O’Neal:

• Follow AJ on Twitter > @coolaj86
• War Stories | How Crash Bandicoot Hacked The Original Playstation
• Crash Bandicoot Co-Creator Andy Gavin: Extended Interview | Ars Technica
• The Story of Spyro the Dragon | Gaming Historian
• Utah Node.js: Scaling Node.js at Plaid

Steve Edwards:

• Follow Steve on Twitter > @wonder95, Website
• Six13 Uptown Passover - an "Uptown Funk" adaptation for Pesach

Dan Shappir:

• Follow Dan on Twitter > @DanShappir
• Scott Lynch

Morad Stern:

• Follow Morad on Twitter > @morad
• This Is Marketing: You Can't Be Seen Until You Learn to See: Seth Godin

Follow JavaScript Jabber on Twitter > @JSJabber

JavaScript Remote Conf 2020

May 13th to 15th - register now!

Joe Karlsson is a developer advocate at MongoDB. He and the panel walk through the different approaches, uses, and libraries for building IoT with JavaScript

Panel

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

Guest

• Joe Karlsson

Sponsors

• G2i | Enjoy the luxuries of freelancing

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

Links

• Cylon.js - JavaScript framework for robotics, physical computing, and the Internet of Things using Node.js
• Johnny-Five: The JavaScript Robotics & IoT Platform
• Arduino - Home
• Tessel 2
• Tessel Kit for Johnny-Five
• The Programming Language Lua
• Luvit.io
• Gumstix, Inc.

Picks

AJ O’Neal:

• MicroPython - Python for microcontrollers
• Raspberry Pi Reverse Emulator (Part 1)
• Raspberry Pi Reverse Emulator (Part 2)
• Arduino With Python: How to Get Started – Real Python
• Duktape
• How to Diagnose and Fix Everything Electronic
• Getting Started in Electronics
• Make: Electronics (Book)
• Make: Electronics (Component Pack)

Aimee Knight:

• Cutting Your own Hair
• Joe's Appartment

Charles Max Wood:

• The Iron Druid Chronicles Series by Kevin Hearne
• JavaScript Jabber Meetup

Steve Edwards:

• Pearls Before Swine

Dan Shappir:

• JavaScript Remote Conf 2020
• JS VidCon
• Future Sync Conference

Joe Karlsson:

• Follow Joe on Twitter > @JoeKarlsson1
• MongoDB.live

Follow JavaScript Jabber on Twitter > @JSJabber

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

Bloomberg's risk map signals where danger lurks

Sasson, Diane, 1946-

MacFadyen, David, 1964-

Moon, Krystyn R., 1974-

Clark, Victoria, 1961-

Kaminsky, Joel S., 1960-

Konicek-Moran, Richard

Deutscher, Penelope, 1966-

Sachdev, Perminder

Coward, Harold G

Mass, Jeffrey P

Hudley, Cynthia

Chesterman, Simon

Schwedt, Rachel E., 1944-

Flowers, Sarah, 1952-