Roseberry, Kimberly, author

Clean Energy Regulator (Australia), author, issuing body

According to the consumer survey, more than a third of Apple customers showed interest in paying as much as $600 extra for a foldable iPhone

The tech giant also noted that there has been a sharp spike in fraudulent ads for in-demand products like face masks amid the COVID-19 pandemic that has claimed lakhs of lives globally

Daylight saving time went into effect in the United States on March 31, 1918 during World War I as part of the war effort and many thought it would end when the war ended. Farmers across the country petitioned to end national daylight saving time in 1919 but President Wilson vetoed the repeal stating it “would be of very grave inconvenience to the country.” He would go on to reject the bill a second time on August 15, 1919. Read more about it and follow us on Twitter @librarycongress #ChronAm!

Not enjoying the Thanksgiving spirit? Here's an unusual poem by Clarence V. Odell describing the turkey-eat-turkey dynamic of a 'gobble,' another name for a flock of the big birds (also known as a 'rafter').

"NINE greedy gobblers having a fete,
One ate his head off, then there were eight...."

Pity the turkeys... it rarely ends well for them!

Read more about it and follow us all the time on Twitter @librarycongress #ChronAm!

Blackburn, William H

Black, Silvia Beatriz

Norman, M. A

International Symposium on Biohydrometallurgy (14th : 2001 : Ouro Preto, Minas Gerais, Brazil)

Tropicana Joint Venture

Cocks, Robert J., author

Sobhy, Ahmed, author

Police Commissioner Ch. Dwaraka Tirumala Rao on Friday suspended two Armed Reserve (AR) police constables, P. Kiran Kumar and V. Naresh, for allegedly

Vapour began leaking after midnight but help came only at dawn, they allege

The panelists talk to Glenn Block about Azure.

Use this link and code JAVAJAB to get 20% off your registration for FluentConf 2013! Panel Brian Hogan (twitter github blog) AJ O’Neal (twitter github blog) Joe Eames (twitter github blog) Merrick Christensen (twitter github) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 00:55 - Brian Hogan Introduction HTML5 and CSS3: Develop with Tomorrow's Standards Today by Brian Hogan tmux: Productive Mouse-Free Development by Brian Hogan Web Development Recipes by Brian P. Hogan, Chris Warren, Mike Weber, Chris Johnson, Aaron Godin Development Editor with Pragmatic Bookshelf Professor at Chippewa Valley Technical College 01:48 - What Accessibility Means 02:56 - Making Websites Accessible YSlow People vs Users 06:06 - “The Right Things” VersaBraille Responsive Web Design 09:00 - Tools & Techniques Fahrner Image Replacement (FIR) Web Fonts ⌘+ 14:56 - Manipulating the DOM ARIA - HTML5 Ember.js 16:54 - Screen Resolution 19:24 - Typeahead 20:58 - Testing Jaws VoiceOver 23:11 - Resources WebAIM Web Content Accessibility Guidelines (WCAG) Section 508 25:00 - Dealing with different kinds of impairments Transcripts Text Color 28:08 - Ease of Accessibility & Empathy 31:41 - Interactive Pages 35:26 - Making things accessible vs not making things accessible Making experiences better for everyone, period 42:09 - Resources Cont’d Web Content Accessibility Guidelines (WCAG) Pro HTML5 Accessibility by Joe O Conner Design Accessible Web Sites: 36 Keys to Creating Content for All Audiences and Platforms by Jeremy Sydik 42:46 - Understanding Others’ Difficulties Picks Leviathan: Warships (Joe) Star Command (Joe) That Conference (Joe) Lowes (AJ) Friends (AJ) Ticket to Ride (Chuck) 4 Pics 1 Word (Chuck) Continuum (Chuck) AngularJS (Brian) Presentation Manager from Woojijuice (Brian) Next Week JavaScript Jabber: jQuery Mobile with Todd Parker Transcript MERRICK:  Fine, don’t come to my talk. CHUCK:  I won’t. I won’t even come to the conference. [Hosting and bandwidth provided by the Blue Box Group. Check them out at Bluebox.net.] [This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.] CHUCK:  Hey everybody, and welcome to Episode 58 of the JavaScript Jabber Show. This week on our panel, we have AJ O’Neal. AJ:  Coming at you semi-live from ORM. CHUCK:  Joe Eames. JOE:  Hey everybody. CHUCK:  Merrick Christensen. MERRICK:  What’s up? CHUCK:  I’m Charles Max Wood from Devchat.tv. And this week, we have a special guest. And that is Brian Hogan. BRIAN:  Hello. CHUCK:  Since you haven’t been on the show before, do you want to introduce your self really quickly? BRIAN:  Sure, my name is Brian Hogan and I’m a web developer and I like to spend a lot of time hacking on code in Ruby and JavaScript. I also am an author. I’m a development editor with The Pragmatic Bookshelf. And I have a fabulous new gig where I get to teach brand new programmers how to get started programming now. So, that’s what I’m doing myself. CHUCK:  So where’s that at? AJ:  Cool. BRIAN:  That’s at a little technical college in Eau Claire, Wisconsin called Chippewa Valley Technical College. CHUCK:  Oh, cool. Yeah, speaking of your reviewing books for The Pragmatic Bookshelf, Ruby Rogues, we actually interviewed Bruce Williams and John Athayde about The Rails View this morning. They mentioned you, and I was like “Oh, we’re talking to him in a couple of hours.” BRIAN:  Oh, those are some great guys and that’s a great book. CHUCK:  Yup. So, the reason we brought you on the show is because, at least in my case, I know absolutely nothing about building accessible websites.

Panel Nicholas C. Zakas (twitter github blog) Joe Eames (twitter github blog) AJ O’Neal (twitter github blog) Jamison Dance (twitter github blog) Merrick Christensen (twitter github) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 01:24 - Nicholas Zakas Introduction Box Maintainable JavaScript by Nicholas C. Zakas High Performance JavaScript (Build Faster Web Application Interfaces) by Nicholas C. Zakas Yahoo 02:19 - What Makes Maintainable JavaScript? Code Layout Clever Solutions (“Chicken Blood Solutions”) 04:39 - Formatting Thinking, Fast and Slow by Daniel Kahneman Broken Window Theory 07:33 - Architecture aura Nicholas Zakas: The Scalable JavaScript Application Architecture Feature Encapsulation 14:11 - 'High Performance Javascript' and the balance between short-term and long-term knowledge 19:17 - Important conventions for a team to follow Styles Mini Design Patterns Readability 26:14 - Tools & Techniques Style Guide 28:31 - Breaking the continuous integration build 31:14 - Linting JSLint 32:35 - Developing skills for architecting things Experience Personal Trait of Curiosity Component-based and Systems-based software engineers 37:52 - Architecture and Maintainability Testability Backbone.js 43:28 - Creating common conventions that will apply across projects Picks Domo (Joe) Pluralsight (Joe) Game Dev Tycoon (Joe) The Star Wars (Joe) Foundation Actionscript 3.0 Animation: Making Things Move! by Keith Peters (Merrick) ng-conf (Merrick) Kveikur by Sigur Rós (Merrick) makemeasandwich (AJ) Sleep (AJ) Jekyll Themes (Jamison) Growing Object-Oriented Software, Guided by Tests by Steve Freeman (Jamison) A Canticle For Leibowitz by Walter M. Miller Jr. (Jamison) DevChat.tv (Chuck) Thinking, Fast and Slow by Daniel Kahneman (Nicholas) StePhest Colbchella '013 - Time to Dance (Nicholas) Evolution of Music - Pentatonix (Nicholas) Next Week Meteor.js with Marcus Phillips and Fred Zirdung Transcript [Hosting and bandwidth provided by the Blue Box Group. Check them out at BlueBox.net.]  [This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.]  [This podcast is sponsored by JetBrains, makers of WebStorm. Whether you’re working with Node.js or building the frontend of your web application, WebStorm is the tool for you. It has great code quality and code exploration tools and works with HTML5, Node, TypeScript, CoffeeScript, Harmony, LESS, Sass, Jade, JSLint, JSHint, and the Google Closure Compiler. Check it out at JetBrains.com/WebStorm.] CHUCK:  Hey everybody and welcome to episode 75 of the JavaScript Jabber show. This week on our panel, we have Joe Eames. JOE:  Hey, everyone. CHUCK:  AJ O’Neal. AJ:  I can hit unmute. I'm here. CHUCK:  Jamison Dance. JAMISON:  Hello, friends. CHUCK:  Merrick Christensen. MERRICK:  Hey, guys. CHUCK:  I’m Charles Max Wood from DevChat.TV. This week, we have a special guest, that’s Nicholas Zakas. NICHOLAS:  Yup, you got it. CHUCK:  So, since you haven’t been on the show before, do you want to introduce yourself? NICHOLAS:  Sure. I'm a software engineer that is working for Box currently. I think a lot of people probably know me from the books that I've written, mostly on the topic of JavaScript and the talks that I've given also on that topic. And a lot of that relates back to my work when I was at Yahoo. I was there for about five years and was the lead on the Yahoo homepage redesign. And a lot of what I do is really just try to solve problems in real life and then share what I did with everybody else in whatever way I think is most appropriate - writing or speaking or coming on podcasts. CHUCK:  Yes, you're being modest. You have a book,

Dominic Szablewski joins the Jabber gang to talk about Impact.js, game development, html5, and strategy.

The panelists speak with Brian Woodward and Job Schlinkert about Assemble.io.

The panelists talk to Elliot Kember about asynchronous UI and non-blocking interactions.

02:51 - Marcus Blankenship Introduction

• Twitter
• Blog

03:09 - Panelist Worst Boss Experiences

13:06 - Developer Anarchy vs Having a Hierarchy

• SE-Radio Episode 253: Fred George on Developer Anarchy
• The Valve Playbook

20:57 - Transitioning Managers

• Impostor Syndrome

26:05 - Manager Influence

28:33 - Management vs Leadership

• Leader-Member Exchange Theory

34:37 - Interpersonal Relationships and Happiness

38:24 - What kind of feedback do managers want from their employees?

• Timesheets

46:17 - Am I manager material? Am I ready to go into management?

48:06 - Following a Technical Track

51:55 - Why would anyone ever want to be a department manager?

Picks

A Plain English Guide to JavaScript Prototypes (Aimee)
Oatmega (Aimee)
Luck by Tom Vek (Jamison)
The 27 Challenges Managers Face: Step-by-Step Solutions to (Nearly) All of Your Management Problems by Bruce Tulgan (Marcus)
React Rally Call for Proposals (Jamison)
React Rally (Jamison)
Multipliers: How the Best Leaders Make Everyone Smarter by Liz Wiseman (Dave)
Soft Skills Engineering Podcast (Dave)

Check out Newbie Remote Conf!

02:11 - Heiko Behrens Introduction

• Twitter
• GitHub
• Blog

02:42 - François Baldassari Introduction

• Twitter
• GitHub

03:04 - JavaScript and Pebble

• Espruino
• jerryscript

06:40 - Watch vs Phone

• Pebble.js

09:32 - Memory Constraints and Code Size Limitations

• APIs
• rockyjs
• tween.js

26:24 - Advantages of Writing in JavaScript

32:09 - Capabilities of the Watch

• iPhreaks Episode #153: Using Mobile Devices to Manage Diabetes with Scott Hanselman

37:08 - Running Web Servers

39:29 - Resources

• rockyjs
• Newsletter
• Pebble Slack Channel
• Pebble Developer Page
• @PebbleDev
• Pebble TicToc Source

41:58 - Voice Capabilities

43:06 - UI For the Round Face vs Square Face

46:18 - Future Pebble Milestones

Picks

• Vortex Poker 3 (Jamison)
• Thao & The Get Down Stay Down (Jamison)
• Maciej Ceglowski: Barely succeed! It's easier! (Jamison)
• The Way of Kings Trilogy by Brandon Sanderson (Joe)
• Juniors Are Awesome (Aimee)
• octotree (Aimee)
• Fully Alive by Ken Davis (Chuck)
• Sara Soueidan (Heiko)
• Jake Archibald: Using the service worker (Heiko)
• beyond tellerrand’s Videos (Heiko)
• Fabien Chouteau: Make with Ada: Formal proof on my wrist (François)
• pebble.rs (François)
• The World of Yesterday by Stefan Zweig (François)

See Also

• iPhreaks Show Episode #146: Pebble with Heiko Behrens and Daniel Rodríguez Troitiño

React Remote Conf and Angular Remote Conf

03:15 - Justin Searls Introduction

• Twitter
• GitHub
• Blog
• Test Double
• JavaScript Jabber Episode #038: Jasmine with Justin Searls

04:13 - Testing

• testdouble.js
• teenytest
• Sinon.JS

08:44 - Mocking

• Growing Object-Oriented Software, Guided by Tests by Steve Freeman and Nat Pryce
• Jim Weirich

14:45 - Starting These Concepts as a Junior Developer

• Test-driven Development

17:55 - testdouble.js vs. sinon.js

• NIH = Not Invented Here

26:39 - Duck Typing, Monkey Patching, Duck Punching

32:22 - Node.js Negativity

• Design, Resources
  • Martin Fowler’s Refactoring and Patterns Books
  • Domain-Driven Design: Tackling Complexity in the Heart of Software by Eric Evans

42:52 - Community

45:08 - The AAA Rule: Arrange, Act, Assert

51:19 - Error Messages

Picks

• Unemployment (Jamison)
• React Rally (Jamison)
• Julia Evans' Tweet: how to be a wizard programmer  (Jamison)
• See the good in people (Aimee)
• Sinon.JS (Joe)
• How to Stay Motivated: Developing the Qualities of Success by Zig Ziglar (Chuck)
• The Harry Potter Series (Chuck)
• RetroPie (Justin)
• How Elm can Make you a Better JavaScript Programer (Justin)
• NEJS Conf (Justin)

1:05 - Introducing Lee Byron

• • Ruby Rogues episode

1:55 - Immutable.js

4:35 - Modifying data and operations using Immutable.js

7:40 - Explaining Big-O notation in layman’s terms

11:30 - Internal tree structures and arrays

15:50 - Why build with Immutable.js?

23:05 - Change detection with a mutable

25:00 - Computer science history

34:35 - Other positives to using mutables

37:50 - Flux and Redux

39:50 - When should you use a mutable?

46:10 - Using Immutable.js instead of the built-in Javascript option

51:50 - Learning curves and learning materials

• Docs

54:50 - Bowties

• Knotty Co

Picks:

Contractor by Andrew Ball

17 Hats (Charles)

Asana (Charles)

Call of Duty Infinite Warfare (Joe)

LEGO Star Wars (Joe)

Advent of Code (Lee)

On today's JavaScript Jabber Show, Charles and Aimee discuss Development in a Public Institution with Shawn Clabough. Shawn is a developer and developer manager at Washington State University. He works with the research office, and has been in the industry for 20 years. Tune in to this exciting episode!

JSJ 269 Reusable React and JavaScript Components with Cory House

On today’s episode of JavaScript Jabber, we have panelists Joe Eames, Aimee Knight, Charles Max Wood, and playing the part of both host and guest, Cory House. Encourage your team to investigate reusable components, whether that’d be React, Angular, Vue, or Ember. Tune in!

[00:01:35] – Overview

We can finally write reusable components that it is really lightweight. It doesn’t take much framework-specific code to get things done.

Around 3 years ago, the idea of web component standard was all front-end developers could share our components with each other whether someone is in Angular or React. Web components continue to be an interesting standard but people continue to reach for JavaScript libraries instead – React, Angular, Vue. 

[00:04:50] – Browser support issue

The story in JavaScript libraries is easier. You have more power, more flexibility, more choices, and get superior performance, in certain cases, by choosing a JavaScript library over the standard right now. If you try to use the web components standard, you have to Polyfill-in some features so you can run things across browser. You also won’t get JavaScript features like intelligently splitting bundles and lazy load different components.

Whether you’re in Angular or React, you have this model of putting your data in your curly braces. That setup is non-existent in standardized web components. You have to play the game of putting and pulling data into and out the DOM using DOM selectors. You actually take a step backward in developer ergonomics when you choose to leverage the platform instead.

[00:07:50] – Polymer

The reason that Polymer is useful is it adds some goodness on top of web components. One of those things is that it makes it easier to bind in data and not having to do things like writing a DOM query to be able to get your hands on this div and put this text inside of it. With Polymer, you can do something that feels more like Angular, where you can put in your curly braces and just bind in some data into that place. Polymer ends up adding some nice syntactic sugar on top of the web components standard just to make it easier to create web components. Polymer is also used to bundle in Polyfill for the features across browser.   

[00:14:20] – Standards are dead

No. The standard itself has been embraced at different levels by different libraries. What you can see for the near future is popular libraries leveraging pieces of the web components platform to do things in a standard-spaced way. Effectively, Angular, Vue, Aurelia, are going to be abstractions over the web components standard. Arguably the most popular way to do components today is React. But React completely ignores the web components standard. When you look at React, you can’t see what piece of the web components standard would fundamentally make React a better component library.

Cory can’t seem to run to anybody that is actually using the standard in production to build real applications. People continue to reach for the popular JavaScript libraries that we so often hear about.

[00:17:05] – Libraries making reusable components

There is a risk that it would have been a waste for people writing components on Angular, for React, for Vue. But it’s not necessarily safer writing on the web component standard when you have so few people leveraging that standard. There’s always the risk that that standard may shift as well.

As an example, Cory’s team created approximately 100 reusable components in React. If they end up moving to a hot new library, the components are really just functions that take parameters and contain HTML. There is little there

[00:21:20] – Why opt for reusable components

Reusable components are inherently useful in a situation where you’re going to be doing something more than once. If you think about any work that you do as a software developer, we’d like to think that we’re coming in and creating new things but often it is groundhogs day. There are all sorts of opportunities for reuse.

As a company, we want to encapsulate our forms in reusable components so it’s literally impossible for our software developers to do something that goes against our standard. That’s the power of reusable components.  

[00:31:20] – Rigid component vs. flexible component

As component developers, if we try to create a reusable component in a vacuum, bad things happen. If you’re going to do a reusable component, start by solving a specific problem on a given application. If we think that a component’s going to be useful in multiple places, we put it in a folder called reusable right there in our application source folder.

We try to follow that rule of three as well. If we’ve taken that component and used it in 3 places, that’s a good sign that we should extract it out, put it in our NPM package, that way, everybody has this centralized component to utilize. At that point, it has been tested. It’s been through the fire. People have used it in the real world in a few places so we can be confident that the API is truly flexible enough.

Be as rigid as you can upfront. Once you add features, it’s really hard to take features away. But it’s quite easy to add features later. If you start with something rigid, it’s easier to understand. It’s easier to maintain and you can always add a few more switches later.

[00:36:00] – Reusable components

The reason that we can’t reuse code is every time a new project comes up, people are spending up their own ideas rather than leveraging standards that should have been put in place previously.

We’ve had the technical ability to do this for a long time. We just haven’t been around long enough for consolidation to happen, for standardization to happen. You look at how quickly things are changing in our industry. For instance, a couple of years ago, everybody had pretty much decided that two-way binding was the way to build web applications. And then, React came along and shook that up. So today, you have different ways of thinking about that issue.

[00:42:45] – Component development on teams

Aimee’s team has component development and they’re using Angular 1.6. All of our base components are sitting in a seed application. We just go in when we want to create a new property and we just extend all of those components with specific functionalities that we need.

[00:47:45] – Mobile to web crossover

Cory’s team is creating React components but it’s not leveraged on a mobile application. But people use React Native components on the web. And in fact, if you use create-react-app today, you can do that right now. It’s wired up to work in React Native components. In that way, you can literally have these same components running on your Native mobile apps as you do on your web application.

[00:50:00] – Challenge

Cory’s challenge for everybody listening is sit down with your team and have a quick conversation about whether you think components make sense. Look back at the last few months of development and say, "if we have a reusable component library, what would be in it? How often have we found ourselves copying and pasting code between different projects? How much benefit would we get out of this story?"

Once you’ve realized the benefits of the component model, both in the way that makes you think about your application, in a way that it helps you move faster and faster over time, I really think you won’t go back to the old model. I’d encourage people to investigate reusable components, whether that’d be React, Angular, Vue or Ember.

Picks

Cory House

• Creating Reusable React Components on Pluralsight
• Ted Talk: Why You Should Define your Fears Instead of Your Goals by Tim Ferriss

Joe Eames

• UI-Router
• Persistence

Aimee Knight

• Ask HN: People who completed a boot camp 3+ years ago, what are you doing now?
• NgAtlanta

Charles Max Wood

• Upwork.com

JSJ 269 Reusable React and JavaScript Components with Cory House

On today’s episode of JavaScript Jabber, we have panelists Joe Eames, Aimee Knight, Charles Max Wood, and playing the part of both host and guest, Cory House. Encourage your team to investigate reusable components, whether that’d be React, Angular, Vue, or Ember. Tune in!

[00:01:35] – Overview

We can finally write reusable components that it is really lightweight. It doesn’t take much framework-specific code to get things done.

Around 3 years ago, the idea of web component standard was all front-end developers could share our components with each other whether someone is in Angular or React. Web components continue to be an interesting standard but people continue to reach for JavaScript libraries instead – React, Angular, Vue. 

[00:04:50] – Browser support issue

The story in JavaScript libraries is easier. You have more power, more flexibility, more choices, and get superior performance, in certain cases, by choosing a JavaScript library over the standard right now. If you try to use the web components standard, you have to Polyfill-in some features so you can run things across browser. You also won’t get JavaScript features like intelligently splitting bundles and lazy load different components.

Whether you’re in Angular or React, you have this model of putting your data in your curly braces. That setup is non-existent in standardized web components. You have to play the game of putting and pulling data into and out the DOM using DOM selectors. You actually take a step backward in developer ergonomics when you choose to leverage the platform instead.

[00:07:50] – Polymer

The reason that Polymer is useful is it adds some goodness on top of web components. One of those things is that it makes it easier to bind in data and not having to do things like writing a DOM query to be able to get your hands on this div and put this text inside of it. With Polymer, you can do something that feels more like Angular, where you can put in your curly braces and just bind in some data into that place. Polymer ends up adding some nice syntactic sugar on top of the web components standard just to make it easier to create web components. Polymer is also used to bundle in Polyfill for the features across browser.   

[00:14:20] – Standards are dead

No. The standard itself has been embraced at different levels by different libraries. What you can see for the near future is popular libraries leveraging pieces of the web components platform to do things in a standard-spaced way. Effectively, Angular, Vue, Aurelia, are going to be abstractions over the web components standard. Arguably the most popular way to do components today is React. But React completely ignores the web components standard. When you look at React, you can’t see what piece of the web components standard would fundamentally make React a better component library.

Cory can’t seem to run to anybody that is actually using the standard in production to build real applications. People continue to reach for the popular JavaScript libraries that we so often hear about.

[00:17:05] – Libraries making reusable components

There is a risk that it would have been a waste for people writing components on Angular, for React, for Vue. But it’s not necessarily safer writing on the web component standard when you have so few people leveraging that standard. There’s always the risk that that standard may shift as well.

As an example, Cory’s team created approximately 100 reusable components in React. If they end up moving to a hot new library, the components are really just functions that take parameters and contain HTML. There is little there

[00:21:20] – Why opt for reusable components

Reusable components are inherently useful in a situation where you’re going to be doing something more than once. If you think about any work that you do as a software developer, we’d like to think that we’re coming in and creating new things but often it is groundhogs day. There are all sorts of opportunities for reuse.

As a company, we want to encapsulate our forms in reusable components so it’s literally impossible for our software developers to do something that goes against our standard. That’s the power of reusable components.  

[00:31:20] – Rigid component vs. flexible component

As component developers, if we try to create a reusable component in a vacuum, bad things happen. If you’re going to do a reusable component, start by solving a specific problem on a given application. If we think that a component’s going to be useful in multiple places, we put it in a folder called reusable right there in our application source folder.

We try to follow that rule of three as well. If we’ve taken that component and used it in 3 places, that’s a good sign that we should extract it out, put it in our NPM package, that way, everybody has this centralized component to utilize. At that point, it has been tested. It’s been through the fire. People have used it in the real world in a few places so we can be confident that the API is truly flexible enough.

Be as rigid as you can upfront. Once you add features, it’s really hard to take features away. But it’s quite easy to add features later. If you start with something rigid, it’s easier to understand. It’s easier to maintain and you can always add a few more switches later.

[00:36:00] – Reusable components

The reason that we can’t reuse code is every time a new project comes up, people are spending up their own ideas rather than leveraging standards that should have been put in place previously.

We’ve had the technical ability to do this for a long time. We just haven’t been around long enough for consolidation to happen, for standardization to happen. You look at how quickly things are changing in our industry. For instance, a couple of years ago, everybody had pretty much decided that two-way binding was the way to build web applications. And then, React came along and shook that up. So today, you have different ways of thinking about that issue.

[00:42:45] – Component development on teams

Aimee’s team has component development and they’re using Angular 1.6. All of our base components are sitting in a seed application. We just go in when we want to create a new property and we just extend all of those components with specific functionalities that we need.

[00:47:45] – Mobile to web crossover

Cory’s team is creating React components but it’s not leveraged on a mobile application. But people use React Native components on the web. And in fact, if you use create-react-app today, you can do that right now. It’s wired up to work in React Native components. In that way, you can literally have these same components running on your Native mobile apps as you do on your web application.

[00:50:00] – Challenge

Cory’s challenge for everybody listening is sit down with your team and have a quick conversation about whether you think components make sense. Look back at the last few months of development and say, "if we have a reusable component library, what would be in it? How often have we found ourselves copying and pasting code between different projects? How much benefit would we get out of this story?"

Once you’ve realized the benefits of the component model, both in the way that makes you think about your application, in a way that it helps you move faster and faster over time, I really think you won’t go back to the old model. I’d encourage people to investigate reusable components, whether that’d be React, Angular, Vue or Ember.

Picks

Cory House

• Creating Reusable React Components on Pluralsight
• Ted Talk: Why You Should Define your Fears Instead of Your Goals by Tim Ferriss

Joe Eames

• UI-Router
• Persistence

Aimee Knight

• Ask HN: People who completed a boot camp 3+ years ago, what are you doing now?
• NgAtlanta

Charles Max Wood

• Upwork.com

Panel:

Joe 

Amy 

Charles 

Special Guests: 

Eric Simmons 

Albert Pai

In this episode, JavaScript Jabbers talk to Eric Simmons and Albert Pai, the co-founder of thinkster.io, where their team teaches the bleeding edge of javascript technology’s various frameworks and backend. Also, with the recent creation of Stalkblitz, which is the center topic of today discussion. 

Stackblitz it an online VS Code IDE for Angular, React, and a few more others are supported. This is designed to run web pack and vs code inside your browser at blazing fast speeds. Eric and Albert dive into the many different advantages and services available by StackBlitz and thinker.io. 

In particular, we dive pretty deep on:

• Similarities  and differences to Heroku 
• System JS 
• Stacklets  
• Testing and creating an in-browser system file system
• Creating a type of VS Code experience, Working Off Line 
• Updating of the Stacklets
• Deployment tools or exporting 
• Hot Reloading
• Integrated terminals
• Monaco
• Language Services 
• How do you architect this implementation 
• The innovation of browsers
• Guy Bedford 
• Financing vs. Chipotle Burritos 
• Will this product in the future cost money

Links

• thinkster.io
• https://medium.com/@ericsimons/stackblitz-online-vs-code-ide-for-angular-react-7d09348497f4
• @stackblitz 
• stackblitz.com

Picks

Amy

• Promises Series by Andrew Del Prete
• Crossfit 

Joe

• Wholesome Meme
• Sara Cooper

Charles

• Pivotal Tracker 
• MatterMost 
• asana.com
• Zapier

Eric 

• realworld.io 
• David East 

Albert 

• thinkster.io
• Thing Explainer

Panel:

Aimee Knight

AJ O’Neal

Charles Max Wood

Special Guests: 

Ari Lerner

In this episode, Java Script Jabbers speak with Ari Lerner. Ari is the author of NG Book: The Complete Book on AugularJS, Full Stack React,  and a few others.  Ari co-runs newline.co a platform that teaches about the Block Chain, Ethereum, New Contracts, etc. Ari mentions a few upcoming books on Machine Learning, Elixir, and react Native.

Ari gives a rundown on what the Block Chain is about, and an explanation of a Hash. Ari explains the value of a Hash and 6-bit strings of a Hash. Also, Ari explains the exchange of currency in Bitcoin and the rate of exchange in the Block Chain. Next Ari covers web 3.0 and much more.

In particular, we dive pretty deep on:

• What is the Block Chain?
• A Hash?
• The blockchain is an order of ledger.
• The blockchain is a  list of transactions
• How is a Hash used?
• Sha 256
• Bitcoin and Block Chains
• What If two machines get the same answer?
• Describe a transaction in a blockchain?
• Exchanging currency
• The cost of Bitcoin
• Web 3.0
• Everything on the Block Chain is public!
• Where else is Block Chain is used besides bitcoin type currency
• Public Key.
• What should JS developer be doing to prepare?
• And much more!

Links:

• https://www.ng-book.com/
• http://www.newline.co.bw/
• The History of Money
• @Auser
• Stack.io

Picks:

Amiee

• Article -  Learn Block Chain by Building One
• The Source Bar

Charles

• Microsoft Connect - Meet up at 7pm
• Stranger Thing Season 2

AJ

• Spice Labels and Spice Jars
• Marriage

Ari

• Moving to NYC
• Learn Block Chain by Building One

Panel:

• Charles Max Wood
• Cory House
• Aimee Knight

Special Guests: Ben Titzer

In this episode, the JavaScript Jabber panelists discuss WebAssembly and JavaScript with Ben Titzer. Ben is a JavaScript VM engineer and is on the V8 team at Google. He was one of the co-inventors of WebAssembly and he now works on VM engineering as well as other things for WebAssembly. They talk about how WebAssembly came to be and when it would be of most benefit to you in your own code.

In particular, we dive pretty deep on:

• Ben intro
• JavaScript
• Co-inventor of WebAssembly (Wasm)
• Joined V8 in 2014
• asm.js
• Built a JIT compiler to make asm.js faster
• TurboFan
• What is the role of JavaScript? What is the role of WebAssembly?
• SIMD.js
• JavaScript is not a statically typed language
• Adding SIMD to Wasm was easier
• Easy to add things to Wasm
• Will JavaScript benefit?
• Using JavaScript with Wasm pros and cons
• Pros to compiling with Wasm
• Statically typed languages
• The more statically typed you are, the more you will benefit from Wasm
• TypeScript
• Is WebAssembly headed towards being used in daily application?
• Rust is investing heavily in Wasm
• WebAssembly in gaming
• And much, much more!

Links:

• JavaScript
• V8
• WebAssembly
• asm.js
• TurboFan
• TypeScript
• Rust
• WebAssembly GitHub
• Ben’s GitHub

Picks:

Charles

• Ready Player One Movie
• DevChat.tv YouTube
• Alexa Flash Briefings: Add skill for “JavaScript Rants”

Cory

• npm Semantic Version Calculator
• Kent Beck Tweet

Aimee

• MDN 418 Status code
• Quantity Always Trumps Quality blog post

Ben

• American Politics

Panel:

• Charles Max Wood
• Alyssa Nicholl
• Ward Bell

Special Guests: David Cramer

In this episode, the JavaScript Jabber panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more!

In particular, we dive pretty deep on:

• David intro
• Founder and CEO of Sentry
• What is Sentry?
• Working with PHP
• De-bugger for production
• Focus on workflow
• Goal of Sentry
• Triaging the problem
• Workflow management
• Sentry started off as an open-source side project
• Instrumentation for JavaScript
• Ember, Angular, and npm
• Got their start in Python
• Logs
• Totally open-source
• Most compatible with run-time
• Can work with any language
• Deep contexts
• Determining the root cause
• And much, much more!

Links:

• Sentry
• JavaScript
• Ember
• Angular
• npm
• Python
• Sentry’s GitHub
• @getsentry
• David’s GitHub
• David’s Website
• @zeeg

Sponsors

• Kendo UI
• FreshBooks
• Loot Crate

Picks:

Charles

• Socks as Swag

David

• VS Code
• Kubernetes