Code-sharing between mobile and web apps with React Native

Using native code and Javascript

What to know about developing with React Native

The importance of tooling

Live and hot-reloading

Updating your app on the fly

Possible difficulties faced by transitioning to React Native

Bridging between native API’s and React Native

Writing apps in Swift or React Native

The future of React Native

How to start a React Native project

Resources:

Frontend Masters

Hired.com

Rollbar

Microsoft Code Push

React Native Radio Episode 8

Tadeu Zagallo’s Website

00:51 Jameson is looking for clients who need front and back end code for apps; @Jergason (Contact him via Direct Message)

04:40 An explanation of Capital One and its operations

6:06 How many Capital One developers are using Node and how it is being implemented

10:30 Process of approval for app/website development

14:15 How the culture at Capital One affects technology within the company

18:25 Using Javascript libraries to manage different currencies

19:40 Venmo and its influence on banking

22:32 Whether banks are prepared to operate in a cashless society

29:44 Using HTML and Javascript for updating projects or creating new ones

35:21 Who picks up Javascript easily and why: “It’s more about grit than raw intelligence.”

44:00 Upgrading via open source codes

45:40 The process for hiring developers

51:35 Typescript vs. non-typescript

PICKS:

“Nerve” Movie

Brave Browser

“Stranger Things” on Netflix

Angular 2 Class in Ft. Lauderdale, Discount Code: JSJ

“Strategy for Healthier Dev” blog post

Health-Ade Beet Kombucha

“The Adventure Zone” podcast

On the Cruelty of Really Teaching Computer Science article by E.W. Dijkstra

“The Freelancer Show” podcast

“48 Days” podcast

Node.university

Azat Mardan’s Website

Azat Mardan on Twitter

CETUSA – Foreign exchange program

3:23 Discussing the purpose and aim of Codewars

7:30 The process for building a program with Codewars

11:07 The UI and editor experience

12:55 The challenges faced when first building Codewars

14:23 Explaining PJAX

16:54 Building code on Codewars

21:24 The expanded use of KATA on Codewars

23:11 Practicing “solving problems” and how it translates to real world situations

34:00 How Codewars proves out the persistence of coders

36:41 How Codewars appeals to collaborative workers

44:40 Teachable moments on Codewars

49:40 Always check to see if Codewars is hiring. Codewars uses Qualified.io, which helps automate the hiring process.

PICKS:

Marrow Sci-fi book

Uprooted Fantasy book

“Write Less Code” blog post

“The Rands Test” blog post

Five Stack software development studio

“Stranger Things” on Netflix

Angular 2 Class in Ft. Lauderdale, Discount Code: JSJ

Lean Analytics book

Code book

Datasmart book

Letting Go book

03:45 What makes the Gun database engine special

07:00 Defining a database

12:58 The CAP Theorem

22:56 What Graphs are and how they function (circular references)

30:32 Gun and rotational disk systems

32:08 Gun’s optimizations for performance in ensuing versions

39:55 The prevalence of open source companies

42:45 Further discussing the CAP Theorem and its nuances

50:33 Gun’s purpose and design

52:13 What a Firebase is

54:22 How to get started with Gun - Visit Gun Tutorial,  Gun's Github Page, and

Gun Node Module

QUOTES:

“I think the database should bend to your application’s demands, rather than you having to bend to the database’s demands.” –Mark Nadal

“…The protocol that GUN defines is something that can be implemented in any language. Because GUN is in the language, you don’t have the context which latency of having to make an HTTP call or socket request…” –AJ O’Neill

“Let’s demystify the black magic of CAP.” –Mark Nadal

PICKS:

Dan North’s Deliberate Learning Video

8Tracks Internet Radio

Pokemon Indigo League on Netflix

Daplie Personal Cloud

Young Frankenstein Movie

Mystic Vale Card Game

JS Remote Conference

React Remote Conference

Farm Heroes Super Saga Game App

1:00 Intro to guests Brian Douglas and Matt Christensen

2:20 Definition of JAMStack

8:12 JAMStack and confusion over nomenclature

12:56 JAMStack and security, reliability and performance

17:05 Example of traffic spike for company Sphero

18:26 Meaning of hyperdynamic

20:35 Future and limits of JAMStack technology

26:01 Controlling data and APIs versus using third parties

28:10 Netlify.com and JAMStack

31:16 APIs, JavaScript framework and libraries recommended to start building on JAMStack

35:13 Resources and examples of JAMStack: netlify.com, Netlify blog, JAMStack radio, JAMStack SF Meetup

QUOTES:

“I think in the next couple of years we’re going to see the limits being pushed a lot for what you can do with this.” - Matt

“Today we’re starting to see really interesting, really large projects getting built with this approach.” - Matt

“If you can farm 100% of your backend off to third parties, I feel like that really limits a lot of the interesting things you can do as a developer.” - Brian

PICKS:

Early History of Smalltalk (Jamison)

React Rally 2016 videos (Jamison)

FiveStack.computer (Jamison)

Falsehoods programmers believe about time (Aimee)

Nodevember conference (Aimee)

48 Days Podcast (Charles)

Fall of Hades by Richard Paul Evans (Charles)

Jon Benjamin Jazz (Brian)

RailsConf 2016 (Brian)

React Native (Brian)

Book of Ye Podcast (Brian)

Aurora by Kim Stanley Robinson (Matt)

Sequoia Capital website

Sphero website

Isomorphic rendering on the Jam Stack by Phil Hawksworth

SPONSORS:

Front End Masters

Hired.com

00:50 Intro to guests Donovan Brown and Jordan Matthiesen

1:14 Javascript and Devops

3:49 Node JS and integrating with extensions

11:16 Learning Javascript coming from another language

15:21 Visual Studio Team Services at Microsoft, integration and unit testing

• Visualstudio.com
• Donovanbrown.com

25:10 Visual Studio Code and mobile development

• Apache Cordova open source project

31:45 TypeScript and tooling

33:03 Unit test tools and methods

38:39 ARM devices and integration

QUOTES:

“It’s not impossible, it’s just a different set of challenges.” - Donovan Brown

“Devops is the union of people, process and products to enable continuous delivery of value to your end users” - Donovan Brown

“Apps start to feel more native. They can actually get form.” - Jordan Matthiesen

PICKS:

Veridian Dynamics (AJ)

Jabberwocky Video (AJ)

Hard Rock Cafe - Atlanta (Charles)

CES (Charles)

3D printers (Donovan)

High-Yield Vegetable Gardening (Jordan)

taco.visualstudio.com

Jordan on Twitter @jmatthiesen

Visualstudio.com

Donovanbrown.com

Donovan on Twitter @donovanbrown

SPONSORS:

Front End Masters

Hired.com

On today's episode, Aimee and Chuck welcome Maximillian "Max" Stoiber to the show. Max hails from Austria and is an expert in open source development at Think Mill. Tune in to JSJ 245 Styled Components and React-Boilerplate with Max Stoiber.

On today's episode, Charles Max Wood, Joe Eames, and Aimee Knight discuss Loading and Optimizing Web Applications with Sam Saccone and Jeff Cross. Tune in to their interesting talk, and learn how you can improve user experience and performance with better loading!

JavaScript Jabber turns 5! On today's episode, Charles Max Wood, AJ ONeil, and Aimee Knight travel down memory lane to reminisce the highlights of the show. Tune in and enjoy the celebration!

On today's episode, Aimee Knight, AJ O'Neal, Cory House, Joe Eames, and Charles Max Wood discuss Azure with Jonathan Carter. Jonathan has been working at Microsoft for 10 years. He currently focuses on Node.js and Azure. Tune in to learn how you can use Azure in building applications and services.

MJS 029: Matt Creager

On this episode, we have another My JavaScript Story, our guest is Matt Creager. Matt works for Manifold. He's here with us today to tell us his story. Stay tuned!

[01:00] – Introduction to Matt Creager

Matt works for an interesting company called Manifold. They sponsored the show.

[01:35] – How did you get into programming?

Before Matt fell in love with programming, he was in love with technology. They bought his first computer. It was a Gateway 2000 and he got access to the internet around the same time. He spent all of his time on that computer because they were moving around so much. That became the way that he stayed in touch with people. He remembers taking it apart and formatting the hard drive accidentally.

His uncle has been in the IT industry since he was a kid too. Matt was always associating him with spending time with his computer programming, a role model, and stabilizer in his life. He was switching tapes. And then, his cousin decided that he was going to start scripting his character’s actions in a game that they were playing. And now, looking back, it was some combination of Lua and C++. He started taking his cousin’s scripts apart to automate his own character in the game. He was 13 or 14.

The first programming book that he bought was a result of not being able to figure out how to get his character what it wants to do. It was one of the C++ bibles. And then, he became active in the forums around the scripting language. He was sharing the scripts and he started to realize that he can harvest stuff in the game and sell it for real cash.

Matt never considered himself technical and never considered programming a career. He was just translating CPU and RAM for people who were shopping for computers. And then, he wanted people to measure theirs so he built tools that took the data they had in an office and turn them into reports. When the manager started using that, it became a nationwide program and suddenly, he was on the map. He was leading a team.

When Blackberry started a technical interview, he realized that he has the answers to these questions. Initially, he was just a Technical Issues Manager. He had a Data Science team and that team was responsible for identifying and prioritizing issues. They were using Node 0.4, very early version of Node. And then, he discovered Angular and dived head first to the Angular community.

[13:10] – BlackBerry got Matt to JavaScript

Matt looked at Node because he was trying to figure out how he could do real time analytics. He wanted these dashboards that data scientists are looking at. That was the stepping stone into JavaScript.

[15:30] – Hackathon

On the side, a couple of local companies started to run hackathons. Matt was going to hackathons all the time. Then, he ended up of hopping from BlackBerry to becoming a full time front-end developer at a start-up.

Matt was talking with one of the organizers at LA Hacks. She was telling him that the reason why people are going to these hackathons is because they want to win and they want to put that fact on their resumes. In his day, that was not hackathons were like. The prizes can act as a negative incentive. They really work hard for the prizes. Sometimes they actually end up becoming more creative as a result because they know they need to use this specific combination of API’s.

[18:45] – Contributions to JavaScript community

When Matt joined GoInstant, it was very early days of RTC. Web sockets are new at that point. You’re probably more familiar with Firebase. In the early days, GoInstant and Firebase are competing for the same developers. They’re working on the same problems. The tools that they are building were real time synchronization between the state you have on the client and the state you have on the server. A lot of those that they build, open-source tools, they went with GoInstant to Salesforce. But they inspired the libraries and a lot of it is probably on the same code base that you now see in libraries that pretty much does the same things with Firebase.

And then, most recently, Matt and the team built Torus. They realized that if they are going to be building smaller applications, going to start to use more cloud services, more services tailored towards developers, and going to manage a lot more credential, a lot of credentials that need to be secured and shared with the teammates, they needed to take those credentials and put them on applications wherever they are running, whether that’s a Docker container or Heroku. That’s his most recent open-source project.

[20:50] – What are you working on now?

Manifold is their latest project. They’re trying to build a market place for developer services. It’s been 3 months. They moved from Torus to building Manifold earlier this year. The official launch hasn’t happened yet. That’s hopefully to come earlier this year – September. If it’s something that you want to try out and experiment with, there is a coupon for My JS. Give it a try before they launch a $25 credit that they can use to provision a logging instance, monitoring, or database. You can use it with any type of services that you might need to build your app.

Picks

Matt Creager

• OpenCollective.com
• Scaphold GraphQL
• Elixir
• Manifold.co
• Twitter, Github: @matt_creager

Charles Max Wood

• AWS Lambda
• Zapier
• Heroku
• Udemy course for Ionic Framework

Panel:

Joe Amies

Aimee Knight

Charles Max Wood

Cory House

Special Guests: 

Scott Wyatt

In this episode, JavaScript Jabbers talk with Scott Wyatt. Scott is the Co-founder, CTO, UEX at Cali StyleTechnologies, and is a Node developer and graphic designer.  Scott is on JavaScript Jabber to talk about Trails.js. and its simplistic build, but many useful functions.

Scott mentions that Trails.js was created by Travis Webb. Scott gives us an introduction to the Trails.js framework, as the Jabbers take apart and dive deep into the build, functions, and uses.  Scott goes into what trail packs are, and the similar or related projects. Scott talks about the ease of using trails to build with, and not ending up in frustration.

In particular, we dive pretty deep on:

• Trails.js is Node Framework and lightweight or Blueprint
• Similar to Redux?
• Is it MVC like Rails
• You don’t need to understand it, it is all under the hood.
• Tuple Space
• Is this sole for server-side rendering?
• Closest projects - Sails
• Avoid problems like React.
• Not dealing with corporations
• Why would you want to use trails instead of other projects like Sails, rails, etc.
• How do you get started - trailjs.io
• Quickest way to learn Trails is to build a Trail Pack
• Don’t be afraid to kill you darlings
• Testing
• It Trails production ready?
• It is a particular type of app where Trails shines?

Links

trailsjs.io

Travis Webb

Picks

Amy

• Full Stack Developers by Brad Frost
• Tracking Macros

Joe

• The Behavior Gap

Charles

• Profit First 
• Keto Diet
• scott-wyatt/GitHub
•  

Cory

• Never write another high Order Component

Scott

• Proxy Engine

Panel:

Amy Knight

Charles Max Wood

Special Guests: 

Nick Disabato

In this episode, Java Script Jabbers talk with Nick Disabato. Nick is a newbie to JavaScript Jabber. Nick is the founder of Draft, an interaction design agency where he does research driven A/B testing of E-commerce business.

This is a practical episode for those who are running a business and doing marketing for the products and services. Nick talks about A/B testing for a number scenarios within the company, such as for websites, funnels, and various marketing mechanisms. Nick further goes into how this helps companies strategically increase revenue by changing things such as websites design or building funnels.

In particular, we dive pretty deep on:

• Testing of changes of Copy, Websites, etc.
• What does it mean of changes, Tools, Framework, Plugins, etc
• Does it matter what tools you use? Framework that works within your stack
• How do make we company money
• Researching for the next test
• Testing for conversion rate to decide which design to go implement - Variant
• Responsibility for the designs
• Feature and getting pay for the service
• Learn more about the resources and Copy Hackers
• Large organization or developers, or a QA department
• Optimization teams
• Usability tests and coming up with A/B tests
• Expertise
• Why should be care?
• And much more!

Links:

Draft

Nick Disabato

@nickd

ConversionXL

AB Testing Manual

Wider Funnels 

Copy Hackers

Picks:

Amiee

• Nodevember 

Charles

• Mike Gehard 
• Admin LTE

Nick

• HotJar.com

Panel:

Amiee Knight

Charles Max Wood

Joe Eames

Special Guests: 

Matthew Creager and Peter Cho

In this episode, JavaScript Jabbers speak with Matthew Ceager and Peter Cho. Matthew and Peter are part of the team at Manifold. Manifold is a marketplace for developer services. Matthew takes care of growth and relations, and Peter oversee products at Manifold.

The panel discusses with Peter and Matthew what Manifold does and the benefits of a Cloud Service. Matthew gives perspective on how developers can get their cloud product on the market compared to open source.  Further discussion goes into how this will help the developer to get their products or services turned into a business quicker and save time  Also learn about when it is the ideal time to move to cloud services vs. running a server yourself.

In particular, we dive pretty deep on:

• Different kinds of definition of Cloud Services
• Anything you would rely on as a third party service
• What is the cloud service ecosystem - Services that connect to an application
• Independent market place -  because it is difficult to turn a product into a business
• Where are people using cloud services or running their own server
• Spinning up a version of it is easier.
• Time verses doing it yourself?
• Experts running the services
• Focusing on your product instead of managing the server and such
• Where does the data live and who has access to that?
• Lock In’s?
• Tourist - Credentials management
• How do I get this setup? Command Line or register online
• And much more!

Links:

Manifold

https://github.com/mattcreager

@manifoldco

@etcpeter

@matt_creager

blog.manifold.com

Picks:

Amiee

• Ryan McDermott

Charles

• GitLab 
• AdminLTE

Joe

• What You Can’t Say

Matt

• Star Trek
• Puppeteer

Peter

• Player Unknown Battle Ground 
• Sourdough   by Robin Sloan

Panel:

Amiee Knight

Charles Max Wood

Special Guests: 

Kye Hohenberger

In this episode, JavaScript Jabbers speak with Kye Hohenberger. Kye is a developer and co-founder of Side Way. One of Kye’s most notable works and library is Emotion, a CSS and JS library.

Kye talks about what CSS and JS library is about in the context of the Emotion library system. Kye discusses why this is practical for the writing process, in comparison to other types of tools that do similar jobs. Kye explains the how this tool reduces the number of lines of code and is compact and clearer.

In particular, we dive pretty deep on:

• What is a CSS and JS library?
• Controlling CSS with JS, what does this solve?
• Style bugs
• What kind of styling are you using vs. complex styles?
• Media query
• A more declarative style
• Using Sass
• Where do you see people using this?
• Class names and you can apply to anything
• How Emotion works!
• Style tags
• Object styles
• What are some of the problems you are solving
• React Emotion - dynamic styles
• How does this compare to other style components?
• Glamor Styles
• How do you test something like this?
• Just Glamor React with Emotion
• Can people use the Babel plugin
• Pure flag and function calls
• And much more!

Links:

• Emotion.sh
• Emotion-js/emotion
• emotion.now.sh
• @TKH44

Picks:

Amiee

• Article on Medium
• Antibiotics and Steroids
• RX Bars 

Charles

• Disney Emoji Blitz 
• How To Get A Job  -  JavaScriptJabber.com

Kye

• Styled System
• Face Paint
• Aussie Bites 

Panel:

Charles Max Wood

Special Guests: 

Chris Dias

PJ Meyer

In this episode, Charles is at Microsoft Connect 2017 in NYC. Charles speaks with Chris Dias and PJ Meyer about Visual Studio Code and Live Sharing. Chris and PJ explain more on their demo at Microsoft Connect on Live Collaborative Editing and Debugging. Learn more about the new features with Visual Studio Code and the efficient workflows with screen sharing, and much more.

In particular, we dive pretty deep on:

• Demo of Live Collaborative Editing and Debugging explained
• New Features with VS Code
• Developer productive
• Debugging pain points
• Getting feedback
• New in VS Code
• Language support and Java Debugger
• Live Share
• Debugging from different machines and platforms
• Multi-Stage Docker File
• TypeScript compiler
• More on debugging with Cosmos db
• Debugging in the Cloud?
• Docker Extensions
• Data Bricks
• Updated python tools
• Coming up with Visual Studio Code in the next 6 months
• TypeScript and Refactoring
• Getting the word out about code -  Word of mouth?
• Number of people using VS Code?
• Envision for what VS Code is becoming?
• Preparing for a keynote and processes?
• And much more!

Links:

• https://code.visualstudio.com
• https://github.com/chrisdias
• GitHub.com/microsoft
• @code

Picks:

Chris

• Pizza

PJ

• Deli

Charles

• Coupon Pass for tourist in NYC

Panel: 

Charles Max Wood

Special Guests: Nishant Thacker

In this episode, JavaScript Jabber speaks with Nishant Thacker. Nishant is the technical product manager for all things big data at Microsoft. Nishant mentions the many new technologies and announcements he is in-charge of at Microsoft.

Nishant is on the show to talk about Big Data and gives advice on how to process data and acquire deep insight of your customers. This is a great episode to understand the development of data systems that are the backbone of some marketing tools.

In particular, we dive pretty deep on:

• Processing Metrics
• Processing into report and usable information
• Data lake
• Collecting data points
• Creating and maintaining the data lake in its raw form
• Scale up engines and limits
• Commodity machines and leverage
• Big data means to scale out
• Specialized engines for audio and video files
• How to have a cohesive report?
• Writing and Querying across data
• Storing raw data and retrieve data
• Data cluster
• What does the data box look like?
• And much more!

Links:

• https://www.linkedin.com/in/nishantthacker
• @nishantthacker

Picks:

Nishant

• Robot I

Charles

• Zoom H6
• Shure SM 58
• Lavalier Mics

Panel: 

Charles Max Wood

Guest: Nick Disabato

This week on My JavaScript Story, Charles speaks with Nick Disabato. Nick is a return guest how was recent on JavaScript Jabber episode 283   talking about AB testing. Also, Nick is an interaction designer from Chicago and runs a consultancy called Draft, who do research AB testing for online stores to increase conversion rate without increase ad spend. Nick talks about his current work, and his journey into programming, more on testing, and contributions to the JavaScript Community.

In particular, we dive pretty deep on:

• How much programming do you do day today?
• Programming activities
• Interacting with programmers to deliver products
• What was your introduction to programmer
• Logo - Turtle
• Cue Basic
• How did that get you to where you are today?
• Did not want to be a mathematician
• Never been to art school?
• Being a creative person but not visual
• Describe the creative, design, position you are in.
• Wire Frames
• Verbal communication
• Web development, etc.
• Front facing pages
• How did you get into JavaScript and how much do you have to know?
• Where are the bottlenecks?
• Which framework is the best?
• What are you working on now?
• and much, much more!

Links: 

• https://draft.nu
• https://nickd.org/bio/
• draftsletters.com
• @nickd

Picks

Charles

• Dash Pro 
• convo.com

Nick

• Visual Web Optimizer 
• Designing for Accessibility 

Panel: 

Charles Max Wood

Cory House

Joe Eames

Aimee Knight

Special Guests: Azat Mardan

In this episode, JavaScript Jabber panelist speak with Azat Mardan. Azat is a return guest, previously on JSJ Episode 230. Azat is an author of 14 books on Node JS, JavaScript, and React JS. Azat works at Capital One on the technology team. Azat is the founder and creator of Node University.

Azat is on the show to talk about changes in React and licensing. Some of the topics cover Facebook,  licensing with React, using the wrong version of React, patent wars, and much more in-depth information on current events in React.

In particular, we dive pretty deep on:

• Facebook - Licensing with React
• Using the Wrong version of React in some companies
• BSD licensing
• Patent wars
• Facebook developing React
• Difference in Preact and Inferno
• Rewriting applications
• What did Capital One do about the changes?
• React 16
• Pure React
• Was the BSD patents - Med and Sm Companies
• Patents explained
• React Developers at Facebook
• Fiber - New Core Architecture
• And much more!

Links:

• http://azat.co
• https://node.university
• https://devchat.tv/js-jabber/230-jsj-node-at-capital-one-with-azat-mardan

Picks:

Cory

• Axel Rauschmayer post
• Prettier

Charles

• Indiegogo for Dev Chat
• forum.devchat.tv

Aimee

• Dev Tees
• Hacker News - Question on Stack Exchange and Estimates 

Joe

• Heroku 
• El Camino Christmas

Azat

• PMP 
• Azat - Short Lecture

Panel: 

Charles Max Wood

Aimee Knight

Cory House

AJ O'Neal

Joe Eames

Special Guests: None

In this episode, the JavaScript Jabber panelists speak on where they are what they are up to today. Aimee is still in Nashville, Tennessee, and it is currently working at

Built Technologies and is working with JavaScript. Cory is still authoring courses for Pluralsite, has more recently been doing consulting with React, and is the principal engineer at Cox Automotive. Joe is doing a lot of Pluralsight work, puts together conferences, and is working on a new podcast with Charles. AJ recently did some side work with Dash, is interested in working on a new domain service, and recently got married. Charles is currently at ngATL conference, and has been attending a lot of conferences recently. He is also starting to head over to the video realm and is creating a new podcast called React Roundup and a View Podcast with Joe. They also talk about what they each have planned in the upcoming year for their careers and their lives.

In particular, we dive pretty deep on:

• Built Technologies
• JavaScript
• Front End and Full Stack
• Pluralsite
• React consulting
• Cox Automotive
• Front end apps
• View and React podcast
• Angular JS to Angular
• Pluralsight courses
• Big Picture React courses
• Fork of Bitcoin called Dash
• New domain service
• ngATL
• React Roundup Podcast
• New podcasts on artificial intelligence, IOT, augmented and virtual reality game development, python
• Node, JavaScript, and Rust
• And much, much more!

Links:

• Linode
• Built Technologies
• Pluralsite
• Cox Automotive
• Dash
• ngATL
• DevChat.tv Youtube
• FreshBooks

Picks:

Charles

• ATR2100 Microphone
• Zoom H6
• Apple AirPods
• ngATL
• ngGirls

Aimee

• Improving Ourselves to Death
• What Does Code Readability Mean?

Cory

• JavaScript Tip Tweet
•  

AJ

• How to Start a Startup YouTube Series
• Singham Movie
•  

Joe

• WebFlow.com

Panel: Charles Max Wood

Guest: JC Hiatt

This week on My JavaScript Story, Charles speaks with JC Hiatt. JC is a 25-year-old software consultant from Jackson, Mississippi. He first got into programming in the 7^th grade when he had the desire to create a website. He has since done a lot of work with WordPress, helped to found DevLifts, and much more. Now, he is doing a lot of little things to help make an impact on the programming world, including running multiple podcasts and creating tutorials for new programmers.

In particular, we dive pretty deep on:

• How did you get into programming?
• w3schools.com
• HTML and CSS
• What got you into JavaScript?
• Hackers
• HackThisSite.com
• jQuery
• WordPress
• What are you most proud of?
• Tutorial involving React and WordPress
• Consulting
• Cryptocurrencies Podcast: HODL Daily
• DevLifts and DevLifts Podcast
• Cryptocurrency interest
• Balance
• And much, much more!

Links: 

• Linode
• w3schools.com
• DevLifts Website and Podcast
• HODL Daily Podcast
• FreshBooks
• JCHiatt.com
• @JCHiatt
•  

Picks

JC

• CSS Grid
• The Punisher

Charles

• Artemis by Andy Weir
• Star Wars: The Last Jedi
• React Dev Summit

Panel: 

Charles Max Wood

Aimee Knight

AJ O'Neal

Special Guests: Kitson Kelly

In this episode, the JavaScript Jabber panelists talk with Kitson Kelly about evaluating web frameworks. Kitson is currently in Australia working for ThoughtWorks as a principle technologist. He has written many articles on frameworks and urges that people don’t get stuck on one framework in their programming. He talks about how using only frameworks that you know could hurt you in the long run. This episode is great for understanding when to use certain JavaScript frameworks and how branching out from what is comfortable might make your job easier.

In particular, we dive pretty deep on:

• Articles on web frameworks
• How do you pick a JavaScript framework to use?
• The framework depends on your changing needs
• Recommending less popular frameworks
• Angular, Ember, React
• React vs Redux
• Certain domains with different frameworks?
• Each framework takes a different approach
• How to decide which framework to use?
• Only give it a couple days to see if your app works with the framework
• Is it ever appropriate to not use a certain framework?
• Frameworks are there to make your job easier
• Don’t be afraid to try new frameworks
• Choose a framework that will “be there tomorrow”
• What is the future for frameworks?
• Experiment and be honest with what you need
• And much, much more!

Links:

• Linode
• ThoughtWorks
• Kendo UI
• LootCrate
• @KitsonK
• Kitson’s GitHub

Picks:

Charles

• Facebook
• The 12 Week Year by Brian P. Moore
• Google Drive for Business

Aimee

• Would College Students Retain More If Professors Dialed Back The Pace?
• URL to PDF Converter
• CSS History

AJ

• Tylenol Cold and Flu Severe

Kitson

• Microsoft Azure
• Zype

Panel: Charles Max Wood

Guest: Azat Mardan

This week on My JavaScript Story, Charles speaks with Azat Mardan. Azat is the author of 14 books on Node JS, JavaScript, and React JS. He also founded Node University, speaks at conferences, and works at Capitol One. Azat first got into programming when he was in college and his major was Informatics in eastern Europe and then when he graduated, he taught himself JavaScript and PHP and did some freelance work. Once he came to the United States, he got his master’s degree in Information Systems Technology and was building websites for country embassies. His main advice to people new to programming and IT is to just focus on one thing and give yourself enough time to get comfortable with that technology, and then move on to a new technology to conquer.

In particular, we dive pretty deep on:

• How did you get into programming?
• Major in informatics
• PHP, JavaScript, CSS, and HTML
• Freelancing
• Masters in Information Systems Technology
• C++ class
• FDIC
• Advice to new programmers
• The importance of focus
• His startup experience
• Ruby on Rails
• Mac vs Windows
• Taught himself different frameworks and languages
• Location matters
• MongoDB
• The best way to learn is to teach others
• What was it about JavaScript that really clicked for you?
• JavaScript has expressiveness
• The Talent Code
• What led you to React?
• Which contributions are you most proud of?
• And much, much more!

Links: 

• Node University
• The Talent Code
• Azat’s Blog: WebAppLog.com

Picks

Charles

• Gardenscapes
• Starcraft II
• The Osiris Method

Azat

• Echo JS

Panel:

• Charles Max Wood
• Aimee Knight
• Joe Eames
• AJ O'Neal
• Special Guests: Orta Therox

In this episode, the JavaScript Jabber panelists talk about the tool Danger with Orta Therox. Danger allows you to create cultural rules about your pole request workflow. They discuss what Danger is, how it works, and how it can help you to catch errors and speed up code review. Danger lets you erase discussions so that you can focus on the things that you should really be focusing on, like the code. They also compare Danger to other ways of doing test converge.

In particular, we dive pretty deep on:

• What is DangerJS?
• Think of it as being on the PR level
• Provides an eval context
• Used on larger projects
• React, React Native, Apollo, and RxJS
• Experimenting with moving Danger onto a server
• Danger can run as a linting step
• Pre-commit hooks
• Prettier
• How do you use Danger on your own machine?
• Danger Ruby vs Danger JS
• NPM install
• How is using Danger better that other ways of test coverage?
• What kinds of rules can you write for this system?
• Can use with Ruby or JavaScript
• React Storybooks
• Retrospectives
• And much, much more!

Links:

• React Dev Summit
• JS Dev Summit
• Danger JS
• React
• React Native
• Apollo
• RxJS
• Prettier
• Danger Ruby
• Ruby
• JavaScript
• Orta’s GitHub
• Artsy Blog

Picks:

Charles

• Hogwarts Battle Board Game
• Sushi Go Party! Game
• NYC tips

Aimee

• Max Stoiber Blog
• The Ultimate Guide to Kicking Ass on Take-home Coding Challenges

Joe

• SaltCON
• Stuffed Fables Board Game

AJ

• UniFi AC Lite
• Fullmetal Alchemist

Orta

• The Wire
• Worm Web Serial

Panel: Charles Max Wood

Guest: Jonathan Carter

This week on My JavaScript Story, Charles speaks with Jonathan Carter. Jonathan is a PM at Microsoft and has been a web developer for over 15 years. At Microsoft, he’s had the opportunity to work on tooling, platform pieces for JavaScript applications, and many other things. He first got into programming when his uncle let him shadow him and the IT department he had working for him, and this is where he was first introduced to software and the idea of working with computers as a career. They talk about his proudest accomplishments within the JavaScript community as well as what he is working on now.

In particular, we dive pretty deep on:

• Jonathan intro
• Asure
• How did you first get into programming?
• Interest in creating a website
• Dual enrollment in high school at local community college
• Started off with VB6
• Uncle was very active in his programming start
• .net
• Scrappy boredom mixed with curiosity led to him actually getting into software
• Everyone comes into programming differently
• Your past is important in explaining where you have ended up
• Node.js on Asure
• How did you get into JavaScript?
• Worked at a newspaper in the software division
• Ajax
• jQuery
• Wanted to write better apps
• CodePush
• Stayed in JavaScript community because it brings him inspiration and excitement
• Likes to be able and look back on his past projects
• App development for fun
• Is there anything that you are particularly proud of?
• Profiling tools
• Liked building tools that meet people where they are at and simplify their jobs
• Qordoba
• React Native
• And much, much more!

Links:

• JavaScript
• Microsoft
• Asure
• Node.js
• jQuery
• CodePush
• Qordoba
• React Native
• @LostinTangent
• Jonathan’s GitHub

Picks

Charles

• Anti-Pick: Intellibed
• Tuft and Needle

Jonathan

• Notion
• Doomsday by Architects

Panel:

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

Special Guests: Greg Kushto

In this episode, the JavaScript Jabber panelists discuss thwarting insider threats with Greg Kushto. Greg is the vice president of sales engineering for Force 3 and has been focused on computer security for the last 25 years. They discuss what insider threats are, what the term includes, and give examples of what insider threats look like. They also touch on some overarching principles that companies can use to help prevent insider threats from occurring.

In particular, we dive pretty deep on:

• Greg intro
• Insider threats are a passion of his
• Most computer attacks come from the inside of the company
• Insider threats have changed over time
• What does the term “insider threats” include?
• Using data in an irresponsible manner
• Who’s fault is it?
• Blame the company or blame the employee?
• Need to understand that insider threats don’t always happen on purpose
• How to prevent insider threats
• Very broad term
• Are there some general principles to implement?
• Figure out what exactly you are doing and documenting it
• Documentations doesn’t have to be a punishment
• Know what data you have and what you need to do to protect it
• How easy it is to get hacked
• Practical things to keep people from clicking on curious links
• The need to change the game
• Fighting insider threats isn’t fun, but it is necessary
• And much, much more!

Links:

• Force 3
• Greg’s LinkedIn
• @Greg_Kushto
• Greg’s BLog

Picks:

Charles

• HaveIBeenPwned.com
• Plural Sight
• Elixir podcast coming soon
• NG conf
• MicroConf
• RubyHack
• Microsoft Build

Cory

• Plop
• VS code sync plugin

Aimee

• Awesome Proposals GitHub

AJ O’Neal

• Fluffy Pancakes
• The Mind and the Brain by Jeffrey M. Schwartz

Greg

• StormCast

Panel:

• Charles Max Wood

Special Guests: Matt Hernandez and Amanda Silver

In this episode, the JavaScript Jabber/Adventures In Angular, panelists discuss Visual Studio Code and the VS Code Azure Extension with Matt Hernandez and Amanda Silver at Microsoft Build. Amanda is the director of program management at Microsoft working on Visual Studio and VS Code. Matt works on a mix between the Azure and the VS Code team, where he leads the effort to build the Azure extensions in VS code, trying to bring JavaScript developers to Azure through great experiences in VS Code. They talk about what’s new in VS Code, how the Azure extension works, what log points are, and much more!

In particular, we dive pretty deep on:

• Amanda intro
• Matt intro
• What’s new in VS Code?
• VS Code core
• VS Live Share
• Shared Terminal
• Now have Linux support
• Live Share is now public to the world for free
• What would you use Shared Terminal for?
• Are there other things coming up in VS Code?
• Constantly responding to requests from the community
• Live Share works for any language
• How does the Azure extension work?
• Azure App Service
• Storage extension
• Azure Cosmos DB
• What are log points?
• All a part of a larger plan to create a better experience for JS developers
• Visual debuggers
• Is it the same plugin to support everything on Azure?
• Want to target specific services that node developers will take advantage of
• And much, much more!

Links:

• Visual Studio
• VS Code
• Azure
• Live Share
• Azure Cosmos DB
• Microsoft Build
• Azure App Service
• Amanda’s GitHub
• @amandaksilver
• Matt’s GitHub
• @fiveisprime

Picks:

Charles

• Orphan Black
• Shout out to VS Code team
• Battle of the Books

Matt

• The Customer-Driven Playbook by Travis Lowdermilk
• The Speed of Trust by Stephen M.R. Covey
• Yes, And by Kelly Leonard
• Digital Marketing For Dummies by Ryan Deiss
• Ed Gets His Power Back Kickstarter

Amanda

• Microsoft Quantum Development Kit for Visual Studio Code
• Iggy Peck, Architect
• Tek by Patrick McDonnell

Panel:

• Charles Max Wood

Special Guests: Rachel MacFarlane and Matt Bierner

In this episode, the JavaScript Jabber panelists discuss Visual Studio Code with Rachel MacFarlane and Matt Bierner, who are both developers on Visual Studio Code. They talk about what the workflow at Visual Studio Code looks like, what people can look forward to coming out soon,  and how people can follow along the VS Code improvements on GitHub and Twitter. They also touch on their favorite extensions, like the Docker extension and the Azure extension and their favorite VS Code features.

In particular, we dive pretty deep on:

• Rachel and Matt intro
• Month to month workflow of Visual Studio Code
• VS Code JavaScript, TypeScript, and Mark Down support
• Working on GitHub and within the community
• Check out new features incrementally with insiders
• Community driven work
• What is coming out in Visual Studio Code?
• GitHub helps to determine what they work on
• Working on Grid View
• Improved settings UI
• Highlighting unused variables in your code
• Improvements with JS Docs
• Dart
• Visual Studio Extension API
• How do people follow along with the VS Code improvements?
• Follow along on GitHub and Twitter
• Download VS Code Insiders
• Have a general road map of what the plan is for the year
• Technical debt week
• What do you wish people knew about VS Code?
• Favorite extensions
• Docker extension and Azure extension
• And much, much more!

Links:

• Visual Studio Code
• JavaScript
• TypeScript
• Dart
• VS Code GitHub
• @Code
• VS Code Insiders
• Docker extension
• Azure extension
• Rachel’s GitHub
• Matt’s GitHub
• MattBierner.com
• @mattbierner

Sponsors

• Kendo UI
• Linode
• FreshBooks

Picks:

Charles

• Orphan Black
• Avengers: Infinity War
• Fishing

Rachel

• GitLens

Matt

• The Bronx Warriors

Panel:

• Charles Max Wood

Special Guests: Ori Zohar and Gopinath Chigakkagari

In this episode, the JavaScript Jabber panelists discuss Cloud-Hosted DevOps with Ori Zohar and Gopinath Chigakkagari at Microsoft Build. Ori is on the product team at VSTS focusing on DevOps specifically on Azure. Gopinath is the group program manager in VSTS primarily working on continuous integration, continuous delivery, DevOps, Azure deployment, etc. They talk about the first steps people should take when getting into DevOps, define DevOps the way Microsoft views it, the advantages to automation, and more!

In particular, we dive pretty deep on:

• Ori and Gopi intro
• VSTS – Visual Studio Team Services
• VSTS gives developers the ability to be productive
• Developer productivity
• What’s the first big step people should be taking if they’re getting into DevOps?
• The definition of DevOps
• The people and the processes as the most important piece
• DevOps as the best practices
• Automating processes
• What people do when things go wrong is what really counts
• Letting the system take care of the problems
• Have the developers work on what they are actually getting paid for
• Trend of embracing DevOps
• Shifting the production responsibility more onto the developer’s
• Incentivizing developers
• People don’t account for integration
• Continuous integration
• Trends on what customers are asking for
• Safety
• Docker containers
• And much, much more!

Links:

• Azure
• Microsoft Build
• VSTS
• @orizhr
• Ori’s GitHub
• Gopi’s GitHub
• @gopinach

Sponsors

• Kendo UI
• Linode
• FreshBooks

Picks:

Charles

• .NET Rocks!
• Shure SM58 Microphone
• Zoom H6

Ori

• Fitbit
• Pacific Northwest Hiking

Gopinath

• Seattle, WA

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

Panel:

Charles Max Wood

Special Guests: Vesa Juvonen

In this episode, the JavaScript Jabber panel talks to Vesa Juvonen about building SharePoint extensions with JavaScript. Vesa is on the SharePoint development team and is responsible for the SharePoint Framework, which is the modern way of implementing SharePoint customizations with JavaScript. They talk about what SharePoint is, why they chose to use JavaScript with it, and how he maintains isolation. They also touch on the best way to get started with SharePoint, give some great resources to help you use it, and more!

In particular, we dive pretty deep on:

• Vesa intro
• What is SharePoint?
• Has existed since 2009
• People either know about it and use it or don’t know what it is
• Baggage from a customization perspective
• Why JavaScript developers?
• Modernizing development
• SharePoint Framework
• Microsoft Ignite Conference
• Is there a market for it?
• System integrators
• Angular Element and React
• React for SharePoint Framework back-end
• Supports Vue
• React Round Up Podcast
• How do you maintain isolation?
• What’s the best way to get started with SharePoint extensions?
• Office 365 Developer Program
• SharePoint documentation
• SharePoint YouTube
• What kinds of extensions are you seeing people build?
• And much, much more!

Links:

• SharePoint
• JavaScript
• SharePoint Framework
• Microsoft Ignite Conference
• Angular Element
• React
• Vue
• React Round Up Podcast
• Office 365 Developer Program
• SharePoint documentation
• SharePoint YouTube
• @OfficeDev
• @vesajuvonen
• Vesa’s blog
• Vesa’s GitHub
• @SharePoint

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:

Charles

• Zig Ziglar
• Conversations with My Dog by Zig Ziglar
• Pimsleur Lessons on Audible

Vesa

• Armada by Ernest Cline

Panel:

• Charles Max Wood
• AJ ONeal

Special Guests: Kurt Mackey

In this episode, the JavaScript Jabber panel talks to Kurt Mackey about Fly.io. At Fly.io, they are "building a JavaScript platform that gives you the power to build your own CDN." They talk about how Fly.io came to fruition, how CDN caching works, and what happens when you deploy a Fly app. They also touch on resizing images with Fly, how you actually build JavaScript platforms using Fly, and more!

In particular, we dive pretty deep on:

• Fly.io
• Building a programmable CDN
• High level overview of Fly.io
• How did this project come together?
• CDNs didn’t work with dynamic applications
• Has been working on this since 2008
• Extend application logic to the “edge”
• Putting burden of JavaScript “nastiest” onto the web server
• Fly is the proxy layer
• Getting things closer to visitors and users
• CDN caching
• Cache APIs
• Writing logic to improve your lighthouse score
• Have you built in resizing images into Fly?
• Managing assets closer to the user
• Can you modify your own JavaScript files?
• What happens when you deploy a Fly app
• Having more application logic
• DOM within the proxy
• Ghost
• React and Gatsby
• Intelligently loading client JavaScript
• How do you build the JavaScript platform?
• And much, much more!

Links:

• Fly.io
• JavaScript
• Ghost
• Gatsby
• React
• @flydotio
• @mrkurt
• Kurt at ARS Technica
• Kurt’s GitHub

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:

Charles

• GitLab

AJ

• Gitea
• Black Panther

Kurt

• Packet.net
• The Three-Body Problem by Cixin Liu

Panel:

• Joe Eames
• Aimee Knight
• AJ ONeal

Special Guests: Tom Dale

In this episode, the JavaScript Jabber panel talks to Tom Dale about Ember 3.0 and the future of Ember. Tom is the co-creator of Ember and is a principle staff engineer at LinkedIn where he works on a team called Presentation Infrastructure. They talk about being in the customer service role, having a collaborative culture, and all the information on Ember 3.0. They also touch on the tendency towards disposable software, the Ember model, and more!

In particular, we dive pretty deep on:

• How Joe met Tom
• Programmers as rule breakers
• The pressure to conform
• Tom intro
• Staff engineer at LinkedIn
• Customer service role
• Having a way to role improvements out to a lot of different people
• JavaScript and Ember at LinkedIn
• Having a collaborative culture
• All about Ember 3.0
• Banner feature – there is nothing new
• Cracked how you develop software in the open source world that has longevity
• Major competition in Backbone previously
• The Ember community has never been more vibrant
• Tendency towards disposable software
• The idea of steady iteration towards improvement
• The Ember model
• Being different from different frameworks
• Ember adoption rates
• Python 3
• Valuable from a business perspective to use Ember
• Ember community being friendly to newbies
• How much Ember VS how much JavaScript will a new developer have to learn?
• And much, much more!

Links:

• Ember
• LinkedIn
• JavaScript
• Backbone
• Python
• @tomdale
• tomdale.net
• Tom’s GitHub

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:

Joe

• Framework Summit
• Jayne
• React sent Evan You a cake

Aimee

• Maker's Schedule, Manager's Schedule by Paul Graham

AJ

• James Veitch

Tom

• JavaScript Tech Talk
• Drake’s Ties
• Melissa Watson Ellis at Hall Madden

Panel: Charles Max Wood

Guest: Scott Wyatt

This week on My JavaScript Story, Charles speaks with Scott Wyatt. Scott is a VC partner and is the CTO at Cali Style Technologies, works with startups, and was the CTO of the Dollar Beard Club. He first got into programming because his dad was a computer programmer and he really got hooked from a young age writing games and playing on the computer. They talk about the benefit of not living in the hustle and bustle of California and the Silicon Valley, how he got into JavaScript, what was it about JavaScript that hooked him, and more!

In particular, we dive pretty deep on:

• JavaScript Jabber Episode 282
• Scott intro
• Works remotely from Indiana
• The pros to not living in Silicon Valley
• How did you first get into programming?
• Father was a computer programmer
• Strong arts background
• Started coding really young
• How did you get into JavaScript?
• Started out with ActionScript
• JavaScript to jQuery
• The cool part of having a diverse background as a programmer
• What was it that got you into JavaScript?
• Back-end JavaScript
• Node.js
• JavaScript is very versatile
• How did you get into doing something like Trails.js?
• Sails.js
• Fabrix and TypeScript 
• What have you done in JS that you are most proud of?
• Partitioned apps
• Contributing to freedom of information
• What are you working on now?
• And much, much more!

Links: 

• JavaScript Jabber Episode 282
• Cali Style Technologies
• Dollar Beard Club
• JavaScript
• jQuery
• Node.js
• Trails.js
• Sails.js
• Fabrix
• TypeScript
• @ScottBWyatt
• Scott’s GitHub

Sponsors: 

• Loot Crate
• FreshBooks

Picks

Charles 

• Get a Coder Job Course
• Golf Clash
• Golfing
• Planning in sanity time
• Suggest a Topic
• Chuck@DevChat.tv 

Scott

• Gun.js
• Bitcoin

Panel:

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

Special Guests: Chris Heilmann

In this episode, the panel talks with programmer, Chris Heilmann. He has written books about JavaScript, in addition to writing a blog about it and is an educator about this program.  He currently resides in Berlin, Germany. Let’s welcome our special guest and listen to today’s episode!

Show Topics:

2:19 – Chuck talks.

2:41 – Chris: He has talked about JavaScript in Berlin upon an invitation. You can get five different suggestions about how to use JavaScript. The best practices, I have found, are on the projects I am on now. JavaScript was built in ten days. My goal is to help people navigate through JavaScript and help them feel not disenfranchised. 

5:47 – Aimee: The overall theme is...

5:54 – Panelist: I really like what you said about helping people not feeling disenfranchised.

6:47 – Chris: There is a lot of peer pressure at peer conferences

7:30 – Aimee chimes in with some comments.

7:50: Chris: I think we need to hunt the person down that put...

8:03 – Panelist: A good point to that is, I try to avoid comments like, “Well, like we ALL know...”

8:27 – Chris: There are things NOT to say on stage. It happens, but we don’t want to say certain things while we are teaching people. We are building products with different groups, so keep that in mind.

9:40 – Aimee: My experience in doing this is that I have found it very rewarding to share embarrassing experiences that I’ve had. My advice would to tell people to let their guard down. It’s encouraging for me.

10:26 – Chris: It helps to show that you are vulnerable and show that you are still learning, too. We are all learning together. 90% of our job is communicating with others.

11:05 – Chuck: Now, I do want to ask this...

11:35 – Chris answers.

12:24 – What makes you say that? (Question to Chris)

12:25 – Chris answers.

13:55 – Chuck: The different systems out there are either widely distributed or...

You will have to work with other people. There is no way that people can make that on their own. If you can’t work with other people, then you are a hindrance.

14:31 – Aimee chimes in.

14:53 – Chris: They have to be very self-assured. I want to do things that are at the next level. Each developer has his or her own story. I want to move up the chain, so I want to make sure these developers are self-assured.

16:07 – Chris: Back to the article...

18:26 – Chuck: Yes, I agree. Why go and fight creating a whole system when it exists.

18:54 – Chris chimes in with some comments.

19:38 – Panelist: I still use console logs.

19:48 – Chris: We all do, but we have to...

19:55 – Aimee: In the past year, I can’t tell you how much I rely on this. Do I use Angular? Do I learn Vue? All those things that you can focus on – tools.

10:21 – Chris: We are talking about the ethics of interfaces. Good code is about accessibility, privacy and maintainability, among others. Everything else is sugar on top. We are building products for other people.

22:10 – Chuck: That is the interesting message in your post, and that you are saying: having a deep, solid knowledge of React (that is sort of a status thing...). It is other things that really do matter. It’s the impact we are having. It’s those things that will make the difference. Those things people will want to work with and solves their problems.

23:00 – Chris adds his comments. He talks about Flash.

24:05 – Chris: The librarian motto: “I don’t know everything, but I can look “here” to find the answer.” We don’t know everything.

24:31 – Aimee: Learn how to learn.

24:50 – Chris: There is a big gap in the market. Scratch is a cool tool and it’s these puzzle pieces you put together. It was hard for me to use that system. No, I don’t want to do that. But if you teach the kids these tools then that’s good. 

24:56 – Chuck: Here is the link, and all I had to do was write React components.

26:12 – Chris: My first laptop was 5x more heavy then this one is. Having access to the Internet is a blessing.

27:24 – Advertisement

28:21 – Chuck: Let’s bring this back around. If someone has gone through boot camp, you are recommending that they get use to know their editor, debugging, etc.

Chris: 28:47 – Chris: Yes, get involved within your community. GitHub. This is a community effort. You can help. Writing code from scratch is not that necessary anymore. Why rebuild something if it works. Why fix it if it’s not broken?

31:00 – Chuck talks about his experience.

31:13 – Chris continues his thoughts.

Chris: Start growing a community.

32:01 – Chuck: What ways can people get involved within their community?

32:13 – Chris: Meetup. There are a lot of opportunities out there. Just going online and seeing where the conferences

34:08 – Chris: It’s interesting when I coach people on public speaking. Sharing your knowledge and learning experience is great!

34:50 – Chuck: If they are learning how to code then...by interacting with people you can get closer to what you need/want.

35:30 – Chris continues this conversation.

35:49 – Chris: You can be the person that helps with x, y, z. Just by getting your name known then you can get a job offer.

36:23 – Chuck: How do you find out what is really good content – what’s worth your time vs. what’s not worth your time?

36:36 –Chris says, “That’s tricky!” Chris answers the question.

37:19: Chris: The best things out there right now is...

38:45 – Chuck: Anything else that people want to bring up?

39:00 – Chris continues to talk.

42:26 – Aimee adds in her thoughts.

Aimee: I would encourage people to...

43:00 – Chris continues the conversation.

Chris: Each project is different, when I build a web app is different then when I build a...

45:07 – Panelist: I agree. You talked about abstractions that don’t go away. You use abstractions in what you use. At some point, it’s safe to rly on this abstraction, but not this one. People may ask themselves: maybe CoffeeScript wasn’t the best thing for me.

46:11 – Chris comments and refers to jQuery.

48:58 – Chris continues the conversation.

Chris: I used to work on eight different projects and they worked on different interfaces. I learned about these different environments. This is the project we are now using, and this will like it for the end of time. This is where abstractions are the weird thing. What was the use of the abstraction if it doesn’t have longevity? I think we are building things too soon and too fast.

51:04 – Chris: When I work in browsers and come up with brand new stuff.

52:21 – Panelist: Your points are great, but there are some additional things we need to talk about. Let’s take jQuery as an example. There is a strong argument that if you misuse the browser...

53:45 – Chris: The main issue I have with jQuery is that people get an immediate satisfaction. What do we do besides this?

55:58 – Panelist asks Chris further questions.

56:25 – Chris answers.

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

57:09 – Panelist: Prototypes were invented because...

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

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

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

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

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

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

1:01:43 – Chris continues the conversation.

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

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

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

1:03:36 - Advertisement

Links:

• JavaScript
• So you Learned Java Script, what now? – Article
• WebHint
• Article by James Sinclair
• Clank!
• Angular
• GitHub
• Meetup
• Chris Heilmann’s Twitter
• Chris Heilmann’s Website
• Chris Heilmann’s Medium
• Chris Heilmann’s LinkedIn
• Chris Heilmann
• Chris Heilmann’s GitHub
• Smashing Magazine – Chris Heilmann
• jQuery
• CoffeeScript
• React
• Elixir

Sponsors:

• Kendo UI
• Sentry
• Digital Ocean
• Cache Fly
•  

Picks :

Amiee

• Hacker News -  How to deal with dirty side effects in your pure functional JavaScript

AJ

• KeyBase

Joe

• Framework Summit
• Clank
• ASMR

Charles

• Get a Coder Job Course
• The Iron Druid Chronicles
• Framework Summit

Chris

• Web Unleashed Toronto
• Kurzgesagt
• It Is Just You, Everything’s Not Shit

Panel:

• Aimee Knight
• Charles Max Wood
• Joe Eames
• AJ O’Neil
• Chris Ferdinandi 

Special Guests: Charles Lowell (New Mexico) & Taras Mankovski (Toronto)

In this episode, the panel talks with two special guests Charles and Taras. Charles Lowell is a principle engineer at Frontside, and he loves to code. Taras works with Charles and joined Frontside, because of Charles’ love for coding. There are great personalities at Frontside, which are quite diverse. Check out this episode to hear about microstates, microstates with react, Redux, and much more!

Show Topics:

1:20 – Chuck: Let’s talk about microstates – what is that?

1:32 – Guest: My mind is focused on the how and not the what. I will zoom my mind out and let’s talk about the purposes of microstates. It means a few things. 1.) It’s going to work no matter what framework you are using. 2.) You shouldn’t have to be constantly reinventing the wheel. React Roundup – I talked about it there at this conference. 

Finally, it really needs to feel JavaScript. We didn’t want you to feel like you weren’t using JavaScript. It uses computer properties off of those models. It doesn’t feel like there is anything special that you are doing. There are just a few simple rules. You can’t mutate the state in place. If you work with JavaScript you can use it very easily. Is that a high-level view?

7:13 – Panel: There are a lot of pieces. If I spoke on a few specific things I would say that it enables programming with state machines.

7:42 – Panel: We wanted it to fell like JavaScript – that’s what I heard.

7:49 – Aimee: I heard that, too.

7:59 – Guest.

8:15 – Aimee: Redux feels like JavaScript to me.

8:25 – Guest: It’s actually – a tool – that it feels natural so it’s not contrived. It’s all JavaScript.

8:49 – Panel.

9:28 – Guest: Idiomatic Ember for example. Idiomatic in the sense that it gives you object for you to work with, which are simple objects.

10:12 – Guest: You have your reducers and your...we could do those things but ultimately it’s powerful – and not action names – we use method names; the name of the method.

11:20 – Panel: I was digging through docs, and it feels like NORMAL JavaScript. It doesn’t seem like it’s tied to a certain framework or library platform?

11:45 – Guest: Yes, we felt a lot of time designing the interfaces the API and the implementation. We wanted it to feel natural but a tool that people reach for.

(Guest continues to talk about WHY they created microstates.)

Guest: We wanted to scale very well what you need when your needs to change.

13:39 – Chuck: I have a lot of friends who get into React and then they put in Redux then they realize they have to do a lot of work – and that makes sense to do less is more.

14:17 – Guest: To define these microstates and build them up incrementally...building smaller microstates out of larger ones.

Guest continued: Will we be able to people can distribute React components a sweet array of components ready for me to use – would I be able to do the same for a small piece of state? We call them state machines, but ultimately we have some state that is driving it. Would we be able to distribute and share?

16:15 – Panel: I understand that this is tiny – but why wouldn’t I just use the native features in specific the immutability component to it?

16:42 – Guest: I’m glad you asked that question. We wanted to answer the question...

Guest: With microstates you can have strict control and it gives you the benefit of doing sophisticated things very easily.

18:33 – Guest: You mentioned immutability that’s good that you did. It’s important to capture – and capturing the naturalness of JavaScript. It’s easy to build complex structures – and there is an appeal to that. We are building these graphs and these building up these trees. You brought up immutability – why through it away b/c it’s the essence of being a developer. If you have 3-4-5 levels of nesting you have to de-structure – get to the piece of data – change it – and in your state transition 80% of your code is navigating to the change and only 20% to actually make the change. You don’t have to make that tradeoff.

21:25 – Aimee: The one thing I like about the immutability b/c of the way you test it.

21:45 – Guest: There a few things you can test. 

23:01 – Aimee: You did a good job of explaining it.

23:15 – Guest: It makes the things usually hard  easy! With immutability you can loose control, and if that happens you can get so confused. You don’t have a way to have a way to navigate to clarity. That’s what this does is make it less confusing. It gives you order and structure. It gives you a very clear path to do things you need to do. If there is a property on your object, and if there is a way to change it...

25:29 – Guest: The only constant is change no matter what framework you are working on.

24:46 – Chuck: We are talking about the benefits and philosophy. What if I have an app – and I realize I need state management – how do I put microstates into my app? It’s using Angular or React – how do I get my data into microstates?

26:35 – Guest: I can tell you what the integration looks like for any framework. You take a type and you passed that type and some value to the create function so what you get is a microstate.

(The Guest continues diving into his answer.)

28:18 – Guest: That story is very similar to Redux, basically an event emitter. The state changes on the store.

Maybe this is a good time to talk about the stability benefits and the lazy benefits because microstates is both of those things.

Stability – if I invoke a transition and the result is unchanged – same microstate – it doesn’t emit an event. It recognizes it internally. It will recognize that it’s the same item. Using that in Ember or Redux you’d have to be doing thousands of actions and doing all that computation, but stability at that level.

Also, stability in the sense of a tree. If I change one object then that changes it won’t change an element that it doesn’t need to change.

31:33 – Advertisement: Sentry.io

32:29 – Guest: I want to go back to your question, Chuck. Did we answer it?

32:40 – Chuck: Kind of.

32:50 – Guest.

32:59 – Guest: In Angular for example you can essentially turn a microstate...

33:51 – Guest: You could implement a connect, too. Because the primitive is small – there is no limit.

34:18 – Chuck summarizes their answers into his own words.

34:42 – Guest: If you were using a vanilla React component – this dot – I will bind this. You bind all of these features and then you pass them into your template. You can take it as a property...those are those handlers. They will perform the transition, update and what needs to be updated will happen.

35:55 – Chuck: Data and transitions are 2 separate things but you melded them together to feel like 1 thing. This way it keeps clean and fast.

36:16 – Guest: Every framework helps you in each way.

Microstates let’s you do a few things: the quality of your data all in one place and you can share.

38:12 – Guest: He made and integrated Microstates with Redux tools.

38:28 – Guest talks about paths, microstates to trees.

39:22 – Chuck.

39:25 – Panel: When I think about state machines I have been half listening / half going through the docs. When I think of state machines I think about discreet operations like a literal machine. Like a robot of many steps it can step through. We have been talking about frontend frameworks like React - is this applicable to the more traditional systems like mechanical control or is it geared towards Vue layered applications?

40:23 – Guest: Absolutely. We have BIG TEST and it has a Vue component.

41:15 – Guest: when you create a microstate from a type you are creating an object that you can work with.

42:11 – Guest: Joe, I know you have experience with Angular I would love to get your insight.

42:33 – Joe: I feel like I have less experience with RX.js. A lot of what we are talking about and I am a traditionalist, and I would like you to introduce you guys to this topic. From my perspective, where would someone start if they haven’t been doing Flux pattern and I hear this podcast. I think this is a great solution – where do I get started? The official documents? Or is it the right solution to that person?

43:50 – Guest: Draw out the state machine that you want to represent in your Vue. These are the states that this can be in and this is the data that is required to get from one thing to the other. It’s a rope process. The arrow corresponds to the method, and...

44:49 – Panel: It reminds me back in the day of rational rows.

44:56 – Guest: My first job we were using rational rows.

45:22 – Panelist: Think through the state transitions – interesting that you are saying that. What about that I am in the middle – do you stop and think through it or no?

46:06 – Guest: I think it’s a Trojan horse in some ways. I think what’s interesting you start to realize how you implement your state transitions.

48:00 – (Guest continues.)

48:45 – Panel: That’s interesting. Do you have that in the docs to that process of stopping and thinking through your state transitions and putting into the microstate?

49:05 – Guest: I talked about this back in 2016. I outlined that process. When this project was in the Ember community.

49:16 – Guest: The next step for us is to make this information accessible. We’ve been shedding a few topics and saying this is how to use microstates in your project. We need to write up those guides to help them benefit in their applications.

50:00 – Chuck: What’s the future look like?

50:03 – Guest: We are working on performance profiling.

Essentially you can hook up microstates to a fire hose.

The next thing is settling on a pattern for modeling side effects inside microstates. Microstates are STATE and it’s immutable.

52:12 – Guest: Getting documentation. We have good README but we need traditional docs, too.

52:20 – Chuck: Anything else?

52:28 – Guest: If you need help email us and gives us a shot-out.

53:03 – Chuck: Let’s do some picks!

53:05 – Advertisement for Charles Max Wood’s course!

Links:

• Kendo UI
• Frontside
• Redux
• Microstates
• Microstates with React
• Taras Mankovski’s Twitter
• Taras Mankovski’s GitHub
• Taras Mankovski’s LinkedIn
• Taras Mankovski’s Frontside Bio
• Charles Lowell’s Twitter
• Charles Lowell’s GitHub
• Charles Lowell’s Frontside Bio
• Schedule Once
• Ruby on Rails
• Angular
• Get A Coder Job
• YouTube Talks
• Email: cowboyd@frontside.io
• Working with State Machines
• Twitch TV
• BigTest
• Close Brace
• REEF
• The Developer Experience
• YouTube Video

Sponsors:

• Kendo UI
• Sentry.io – 2 months free – DEVCHAT/code
• Get A Coder Job

Picks:

Aimee

• ShopTalk Episode 327
• Professional JavaScript for Web Developers
• Technical Debt
• Stripe

Taras

• Twitch Channel
• Big Test
• Frontside

Charles Lowell

• Chalkboards
• Sargent Art Chalk

Chris

• Close Brace
• LaCroix Water
• Chris’s Git Hub

Joe

• The Developer Experience Bait and Switch
• Good Bye Redux
• Recording Dungeon and Dragons

AJ

• UtahJS Conf
• Start with Why
• The Rust Book
• VanillaJS w/ Chris
• Zero to One

Charles

• Podwrench.com -  beta
• getacoderjob.com

Panel:

Charles Max Woods

Special Guests: Donovan Brown

In this episode, the Charles speaks with Donovan Brown. He is a principal DevOps Manager with Microsoft with a background in application development. He also runs one of the nation’s fastest growing online registration sites for motorsports events DLBRACING.com. When he is not writing software, he races cars for fun. Listen to today’s episode where Chuck and Donovan talk about DevOps, Azure, Python, Angular, React, Vue, and much, much more!

Show Topics:

1:41 – Chuck: The philosophies around DevOps. Just to give you an idea, I have been thinking about what I want to do with the podcasts. Freedom to work on what we want or freedom to work where we want, etc. Then that goes into things we don’t want to do, like fix bugs, etc. How does Microsoft DevOps to choose what they want to do?

2:37 – Guest: We want to automate as much as we can so the developer has less work. As a developer I want to commit code, do another task, rinse and repeating.

Minutes and not even hours later then people are tweeting about the next best thing. Do what you want, where you want. Code any language you want.

4:15 – Chuck: What has changed?

4:19 – Guest: The branding changed. The name wasn’t the most favorite among the people. The word “visual” was a concerned. What we have noticed that Azure will let me run my code no matter where I am. If you want to run Python or others it can run in Azure.

People didn’t need all of it. It comes with depositories, project management, and so much more! People could feel clumsy because there is so much stuff. We can streamline that now, and you can turn off that feature so you don’t have a heart attack. Maybe you are using us for some features not all of them – cool.

7:40 – Chuck: With deployments and other things – we don’t talk about the process for development a lot.

8:00 – Guest talks about the things that can help out with that.

Guest: Our process is going to help guide you. We have that all built into the Azure tab feature. They feel and act differently. I tell all the people all the time that it’s brilliant stuff. There are 3 different templates. The templates actually change over the language. You don’t have to do mental math.

9:57 – Chuck: Just talking about the process. Which of these things we work on next when I’ve got a bug, or a ...

10:20 – Guest: The board system works like for example you have a bug. The steps to reproduce that bug, so that there is no question what go into this specific field. Let the anatomy of the feature do it itself!

11:54 – Chuck comments.

12:26 – Chuck: Back to the feature. Creating the user stories is a different process than X.

12:44 – Guest – You have a hierarchy then, right? Also what is really cool is we have case state management. I can click on this and I expect this to happen...

These are actual tasks that I can run.

13:52 – Chuck: Once you have those tests written can you pull those into your CI?

14:00 – Guest: “Manual tests x0.”

Guest dives into the question.

14:47 – I expect my team to write those test cases. The answer to your question is yes and no.

We got so good at it that we found something that didn’t even exist, yet.

16:19 – Guest: As a developer it might be mind

16:29 – Chuck: I fixed this bug 4x, I wished I had CI to help me.

16:46 – Guest: You get a bug, then you fix a code, etc., etc. You don’t know that this original bug just came back. Fix it again. Am I in Groundhog Day?

They are related to each other. You don’t have a unit test to tell you. When you get that very first bug – write a unit test. It will make you quicker at fixing it. A unit test you can write really fast over, and over, again. The test is passing. What do you do? Test it. Write the code to fix that unit test. You can see that how these relate to each other. That’s the beauty in it.

18:33 – Chuck: 90% of the unit tests I write – even 95% of the time they pass. It’s the 5% you would have no idea that it’s related. I can remember broad strokes of the code that I wrote, but 3 months down the road I can’t remember.

19:14 – Guest: If you are in a time crunch – I don’t have time for this unit test.

Guest gives us a hypothetical situation to show how unit tests really can help.

20:25 – Make it muscle memory to unit test. I am a faster developer with the unit tests.

20:45 – Chuck: In the beginning it took forever. Now it’s just how I write software now.

It guides my thought process.

21:06 – Guest: Yes! I agree.

22:00 – Guest: Don’t do the unit tests

22:10 – Chuck: Other place is when you write a new feature,...go through the process. Write unit tests for the things that you’ve touched. Expand your level of comfort.

DevOps – we are talking about processes. Sounds like your DevOps is a flexible tool. Some people are looking for A METHOD. Like a business coach. Does Azure DevOps do that?

23:13 – Guest: Azure DevOps Projects. YoTeam.

Note.js, Java and others are mentioned by the Guest.

25:00 – Code Badges’ Advertisement

25:48 – Chuck: I am curious – 2 test sweets for Angular or React or Vue. How does that work?

26:05 – Guest: So that is Jasmine or Mocha? So it really doesn’t matter. I’m a big fan of Mocha. It tests itself. I install local to my project alone – I can do it on any CI system in the world. YoTeam is not used in your pipeline. Install 2 parts – Yo and Generator – Team. Answer the questions and it’s awesome. I’ve done conferences in New Zealand.

28:37 – Chuck: Why would I go anywhere else?

28:44 – Guest: YoTeam  was the idea of...

28:57 – Check out Guest

29:02 – Guest: I want Donovan in a box. If I weren’t there then the show wouldn’t exist today.

29:40 – Chuck: Asks a question.

29:46 – Guest: 5 different verticals.

Check out this timestamp to see what Donovan says the 5 different verticals are. Pipelines is 1 of the 5.

30:55 – Chuck: Yep – it works on my Mac.

31:04 – Guest: We also have Test Plant and Artifacts.

31:42 – Chuck: Can you resolve that on your developer machine?

31:46 – Guest: Yes, absolutely! There is my private repository and...

33:14 – Guest: *People not included in box.*

33:33 – Guest: It’s people driven. We guide you through the process. The value is the most important part and people is the hardest part, but once on

33:59 – Chuck: I am listening to this show and I want to try this out. I want a demo setup so I can show my boss. How do I show him that it works?

34:27 – Azure.com/devops – that is a great landing page.

How can I get a demo going? You can say here is my account – and they can put a demo into your account. I would not do a demo that this is cool. We start you for free. Create an account. Let the CI be the proof. It’s your job to do this, because it will make you more efficient. You need me to be using these tools.

36:11 – Chuck comments.

36:17 – Guest: Say you are on a team of developers and love GitHub and things that integration is stupid, but how many people would disagree about...

38:02 – The reports prove it for themselves.

38:20 – Chuck: You can get started for free – so when do you have to start paying for it?

38:31 – Guest: Get 4 of your buddies and then need more people it’s $6 a month.

39:33 – Chuck adds in comments. If this is free?

39:43 – Guest goes into the details about plans and such for this tool. 

40:17 – Chuck: How easy it is to migrate away from it?

40:22 – Guest: It’s GITHub.

40:30 – Chuck: People are looing data on their CI.

40:40 – Guest: You can comb that information there over the past 4 years but I don’t know if any system would let you export that history.

41:08 – Chuck: Yeah, you are right.

41:16 – Guest adds more into this topic.

41:25 – Chuck: Yeah it’s all into the machine.

41:38 – Chuck: Good deal.

41:43 – Guest: It’s like a drug. I would never leave it. I was using TFS before Microsoft.

42:08 – Chuck: Other question: continuous deployment.

42:56 – When I say every platform, I mean every platform: mobile devices, AWS, Azure, etc.

Anything you can do from a command line you can do from our build and release system.

PowerShell you don’t have to abandon it.

45:20 – Guest: I can’t remember what that tool is called!

45:33 – Guest: Anything you can do from a command line. Before firewall. Anything you want.

45:52 – Guest: I love my job because I get to help developers.

46:03 – Chuck: What do you think the biggest mistake people are doing?

46:12 – Guest: They are trying to do it all at once. Fix that one little thing.

It’s instant value with no risks whatsoever. Go setup and it takes 15 minutes total. Now that we have this continuous build, now let’s go and deploy it. Don’t dream up what you think your pipeline should look like. Do one thing at a time. What hurts the most that it’s “buggy.” Let’s add that to the pipeline.

It’s in your pipeline today, what hurts the most, and don’t do it all at once.

49:14 – Chuck: I thought you’d say: I don’t have the time.

49:25 – Guest: Say you work on it 15 minutes a day. 3 days in – 45 minutes in you have a CSI system that works forever. Yes I agree because people think they don’t “have the time.”

50:18 – Guest continues this conversation.

How do you not have CI? Just install it – don’t ask. Just do the right thing.

50:40 – Chuck: I free-lanced and setup CI for my team. After a month, getting warned, we had a monitor up on the screen and it was either RED or GREEN. It was basically – hey this hurts and now we know. Either we are going to have pain or not have pain.

51:41 – Guest continues this conversation.

Have pain – we should only have pain once or twice a year.

Rollback.

If you only have it every 6 months, that’s not too bad.

The pain will motivate you.

52:40 – Azure.com/devops.

Azure DevOps’ Twitter

53:22 – Picks!

53:30 – Advertisement – Get a Coder Job

Links:

• Donovan Brown’s GitHub
• Donovan Brown’s Twitter
• Donovan Brown
• Donovan Brown – Channel 9
• Donovan Brown – Microsoft
• Azure
• YoTeam
• Azure.com/devops
• GitHub
• Azure DevOps’ Twitter

Sponsors:

• Angular Boot Camp
• Digital Ocean
• Get a Coder Job course

Picks:

Charles

• Jet Blue
• Beta Testers

Donovan

• YoTeam
• VSTeam Powershell Module

Sponsors:

• KendoUI
• Sentry use the code "devchat" for $100 credit
• Clubhouse

Panel:

Charles Max Wood

Special Guests: Ed Thomson

In this episode, the Charles speaks with Ed Thomson who is a Program Manager at Azure through Microsoft, Developer, and Open Source Maintainer. Ed and Chuck discuss in full detail about Azure DevOps! Check out today’s episode to hear its new features and other exciting news!

Show Topics:

0:59 – Live at Microsoft Ignite

1:03 – Ed: Hi! I am a Program Manager at Azure.

1:28 – Rewind 2 episodes to hear more about Azure DevOps!

1:51 – Ed: One of the moves from Pipelines to DevOps – they could still adopt Pipelines. Now that they are separate services – it’s great.

2:38 – Chuck talks about features he does and doesn’t use.

2:54 – Ed.

3:00 – Chuck: Repos and Pipelines. I am going to dive right in. Let’s talk about Repos. Microsoft just acquired GitHub.

3:18 – Ed: Technically we have not officially acquired GitHub.

3:34 – Chuck: It’s not done. It’s the end of September now.

3:55 – Ed: They will remain the same thing for a while. GitHub is the home for open source. Repos – we use it in Microsoft. Repositories are huge. There are 4,000 engineers working in these repositories. Everyone works in his or her own little area, and you have to work together. You have to do all this engineering to get there. We bit a tool and it basically if you run clone...

Ed continues to talk about this topic. He is talking about One Drive and these repositories.

6:28 – Ed: We aren’t going to be mixing and matching. I used to work through GitHub. It’s exciting to see those people work close to me.

6:54 – Chuck.

6:59 – Ed: It has come a long way.

7:07 – Chuck: Beyond the FSF are we talking about other features or?

7:21 – Ed: We have unique features. We have branch policies. You can require that people do pole request. You have to use pole request and your CI has to pass and things like that. I think there is a lot of richness in our auditing. We have enterprise focus. At its core it still is Git. We can all interoperate.

8:17 – Chuck.

8:37 – Ed: You just can’t set it up with Apache. You have to figure it out.

8:51 – Chuck: The method of pushing and pulling.

9:06 – Chuck: You can try DevOps for free up to 5 users and unlimited private repos. People are interested in this because GitHub makes you pay for that.

9:38 – Ed and Chuck continue to talk.

9:50 – Ed: Pipelines is the most interesting thing we are working on. We have revamped the entire experience. Build and release. It’s easy to get started. We have a visual designer. Super helpful – super straightforward. Releases once your code is built – get it out to production say for example Azure. It’s the important thing to get your code out there.

10:55 – Chuck: How can someone start with this?

11:00 – Ed: Depends on where your repository is. It will look at your code. “Oh, I know what that is, I know how to build that!” Maybe everyone isn’t doing everything with JavaScript. If you are using DotNet then it will know.

12:05 – Chuck: What if I am using both a backend and a frontend?

12:11 – Ed: One repository? That’s when you will have to do a little hand packing on the...

There are different opportunities there. If you have a bash script that does it for you. If not, then you can orchestrate it. Reduce the time it takes. If it’s an open source project; there’s 2 – what are you going to do with the other 8? You’d be surprised – people try to sneak that in there.

13:30 – Chuck: It seems like continuous integration isn’t a whole lot complicated.

13:39 – Ed: I am a simple guy that’s how I do it. You can do advanced stuff, though. The Cake Build system – they are doing some crazy things. We have got Windows, Lennox, and others. Are you building for Raspberries Pies, then okay, do this...

It’s not just running a script.

15:00 – Chuck: People do get pretty complicated if they want. It can get complicated. Who knows?

15:26 – Chuck:  How much work do you have to do to set-up a Pipeline like that?

15:37 – Ed answers the question in detail.

16:03 – Chuck asks a question.

16:12 – Ed: Now this is where it gets contentious. If one fails...

Our default task out of the box...

16:56 – Chuck: If you want 2 steps you can (like me who is crazy).

17:05 – Ed: Yes, I want to see if it failed.

17:17 – Chuck: Dude, writing code is hard. Once you have it built and tested – continuous deployment.

17:33 – Ed: It’s very easy. It’s super straightforward, it doesn’t have to be Azure (although I hope it is!).

Ed continues this conversation.

18:43 – Chuck: And it just pulls it?

18:49 – Ed: Don’t poke holes into your firewall. We do give you a lot of flexibility

19:04 – Chuck: VPN credentials?

19:10 – Ed: Just run the...

19:25 – Chuck comments.

19:36 – Ed: ...Take that Zip...

20:02 – Ed: Once the planets are finely aligned then...it will just pull from it.

20:25 – Chuck: I host my stuff on Digital Ocean.

20:46 – Ed: It’s been awhile since I played with...

20:55 – Chuck.

20:59 – Ed and Chuck go back and forth with different situations and hypothetical situations.

21:10 – Ed: What is Phoenix?

21:20 – Chuck explains it.

21:25 – Ed: Here is what we probably don’t have is a lot of ERLANG support.

22:41 – Advertisement.

23:31 – Chuck: Let’s just say it’s a possibility. We took the strip down node and...

23:49 – Ed: I think it’s going to happen.

23:55 – Ed: Exactly.

24:02 – Chuck: Testing against Azure services. So, it’s one thing to run on my machine but it’s another thing when other things connect nicely with an Azure set-up. Does it connect natively once it’s in the Azure cloud?

24:35 – Ed: It should, but there are so many services, so I don’t want to say that everything is identical. We will say yes with an asterisk.

25:07 – Chuck: With continuous deployment...

25:41 – Ed: As an example: I have a CD Pipeline for my website. Every time I merge into master...

Ed continues this hypothetical situation with full details. Check it out!

27:03 – Chuck: You probably can do just about anything – deploy by Tweet!

27:15 – Ed: You can stop the deployment if people on Twitter start complaining.

27:40 – Chuck: That is awesome! IF it is something you care about – and if it’s worth the time – then why not? If you don’t have to think about it then great. I have mentioned this before: Am I solving interesting problems? What projects do I want to work on? What kinds of contributions do I really want to contribute to open source?

That’s the thing – if you have all these tools that are set-up then your process, how do you work on what, and remove the pain points then you can just write code so people can use! That’s the power of this – because it catches the bug before I have to catch it – then that saves me time.

30:08 – Ed: That’s the dream of computers is that the computers are supposed to make OUR lives easier. IF we can do that and catch those bugs before you catch it then you are saving time. Finding bugs as quickly as possible it avoids downtime and messy deployments.

31:03 – Chuck: Then you can use time for coding style and other things.

I can take mental shortcuts.

31:37 – Ed: The other thing you can do is avoiding security problems. If a static code analysis tool catches an integer overflow then...

32:30 – Chuck adds his comments.

Chuck: You can set your policy to block it or ignore it. Then you are running these tools to run security. There are third-party tools that do security analysis on your code. Do you integrate with those?

33:00 – Ed: Yep. My favorite is WhiteSource. It knows all of the open source and third-party tools. It can scan your code and...

34:05 – Chuck: It works with a lot of languages.

34:14 – Ed.

34:25 – Chuck: A lot of JavaScript developers are getting into mobile development, like Ionic, and others. You have all these systems out there for different stages for writing for mobile. Android, windows Phone, Blackberry...

35:04 – Ed: Let’s throw out Blackberry builds. We will ignore it.

Mac OS dies a fine job. That’s why we have all of those.

35:29 – Chuck: But I want to run my tests, too!

35:36 – Ed: I really like to use App Center. It is ultimately incredible to see all the tests you can run.

36:29 – Chuck: The deployment is different, though, right?

36:40 – Ed: I have a friend who clicks a button in...

Azure DevOps.

37:00 – Chuck: I like to remind people that this isn’t a new product.

37:15 – Ed: Yes, Azure DevOps.

37:24 – Chuck: Any new features that are coming out?

37:27 – Ed: We took a little break, but...

37:47 – Ed: We will pick back up once Ignite is over. We have a timeline on our website when we expect to launch some new features, and some are secret, so keep checking out the website.

39:07 – Chuck: What is the interplay between Azure DevOps and Visual Studio Code? Because they have plugins for freaking everything. I am sure there is something there that...

39:30 – Ed: I am a VI guy and I’m like 90% sure there is something there.

You are an eMac’s guy?

The way I think about it is through Git right out of the box.

Yes, I think there are better things out there for integration. I know we have a lot of great things in Visual Code, because I worked with it.

40:45 – Chuck: Yes, people can look for extensions and see what the capabilities are.

Chuck talks about code editor and tools. 

41:28 – Ed: ... we have been pulling that out as quickly as possible.

We do have IE extensions, I am sure there is something for VS Code – but it’s not where I want to spend my time.

42:02 – Chuck: Yes, sure.

42:07 – Ed: But everyone is different – they won’t work the way that I work. So there’s that.

42:30 – Ed: That Chuck.

42:36 – Chuck: Where do people get news?

42:42 – Ed: Go to here!

42:54 – Chuck: Where do people find you?

43:00 – Ed: Twitter!

43:07 – Chuck: Let’s do Picks!

43:20 – Advertisement – Fresh Books!

Links:

• GitHub
• Microsoft’s Azure
• Microsoft’s Pipeline
• Azure DevOps
• Erlang
• WhiteSource
• Chuck’s Twitter
• Ed Thomson’s Twitter
• Ed Thomson’s GitHub
• Ed Thomson’s Website
• Ed Thomson’s LinkedIn

Picks:

Ed

• Podcast - All Things Git

Sponsors

• Netlify
• Sentry use the code "devchat" for $100 credit
• Clubhouse

Panel:

• Charles Max Wood
• AJ O’Neal
• Aimee Knight
• Aaron Frost
• Chris Ferdinandi
• Joe Eames
• Tim Caswell

Notes:

This episode of JavaScript Jabber has the panelists reminiscing on the past. First, they discuss the projects they’re working on. Tim has joined MagicLeap doing JavaScript and C++. Aaron Frost is one of the founders of HeroDevs. AJ works at Big Squid, a company that takes spreadsheets and turns them into business actions, and is expecting a daughter. Aimee has been exploring developer advocacy, but wants to focus primarily on engineering. She is currently working at MPM. Joe has taken over the CEO position for thinkster.io, a company for learning web development online. Chris switched from being a general web developer specializing in JavaScript and has started blogging daily rather than once a week, and has seen an increase in sales of his vanilla JavaScript educational products. Charles discusses his long term goal for Devchat.tv. He wants to help people feel free in programming, and help people find opportunities though the Devchat.tv through empowering content.

Next, the panelists discuss their favorite episodes. Some of the most highly recommended episodes are

JSJ 124: The Origin of Javascript with Brendan Eich (1:44:07)

JSJ 161: Rust with David Herman (1:05:05)

JSJ 336: “The Origin of ESLint with Nicholas Zakas” (1:08:01)

JSJ 338: It’s Supposed To Hurt, Get Outside of Your Comfort Zone to Master Your Craft with Christopher Buecheler (43:36)

JSJ 218: Ember.js with Yehuda Katz (42:47)

Last, the panelists discuss what they do to unwind. Activities include working out, reading, playing Zelda and Mario Kart, studying other sciences like physics, painting miniatures, and Dungeons and Dragons.

Picks:

Charles Max Wood

• Villainous Board Game

Joe Eames

• Azul Stained Glass Board Game

AJ O’Neal

• https://www.digikey.com/
• Magnetic Hourglass: Amazon | Hobby Lobby $6 

Aimee Knight

• https://www.nytimes.com/2018/12/24/well/mind/work-schedule-hours-sleep-productivity-chronotype-night-owls.html

Aaron Frost

• Matrix PowerWatch
• https://twitter.com/ChloeCondon

Chris Ferdinandi

• https://learnvanillajs.com/

Tim Caswell

• https://www.magicleap.com/
• https://textonascreen.rocks/
• https://history.lds.org/saints

Sponsors

• Sentry- use the code “devchat” for $100 credit
• Netlify
• Clubhouse
• CacheFly

Episode Summary  

In this episode of JavaScript Jabber, the panelists talk with Tommy Hodgins who specializes in responsive web design. He starts with explaining to listeners what it means by a responsive web layout and goes on to discuss the techniques in using JavaScript in CSS in depth.

He elaborates on dynamic styling of components, event-driven stylesheet templating, performance and timing characteristics of these techniques and describes different kinds of observers – interception, resize and mutation, and their support for various browsers. He also talks about how to go about enabling certain features by extending CSS, comparison to tools such as the CSS preprocessor and Media Queries, pros and cons of having this approach while citing relevant examples, exciting new features coming up in CSS, ways of testing the methods, caffeinated stylesheets, along with Qaffeine and Deqaf tools.

Links

• JS in CSS – Event driven virtual stylesheet manager
• Qaffiene
• Deqaf
• Tommy’s Twitter
• Fizzbuzz

Picks

Joe

• The Captain Is Dead

Aimee

• Developer on Call
• Tip – Try to follow a low-sugar diet

Chris

• Tommy’s snippets on Twitter – JS in CSS
• All things frontend blog
• Gulp project

Charles

• Coaching by Charles in exchange of writing Show Notes or Tags

Tommy

• JS in CSS

Sponsors:

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

Panel:

Charles Max Wood

Special Guest: Brady Gaster

In this episode, Chuck talks with Brady Gaster about SignalR that is offered through Microsoft. Brady Gaster is a computer software engineer at Microsoft and past employers include Logical Advantage, and Market America, Inc. Check out today’s episode where the two dive deep into SignalR topics.

Links:

• Vue
• jQuery
• Angular
• C#
• Chuck’s Twitter
• SignalR
• SignalR’s Twitter
• GitHub SignalR
• Socket.io
• Node-SASS
• ASP.NET SignalR Hubs API Guide – JavaScript Client
• SignalR.net
• Real Talk JavaScript
• Parcel
• Brady Gaster’s Twitter
• Brady Gaster’s GitHub
• Brady Gaster’s LinkedIn

Picks:

Brady

• Team on General Session
• Korg
• SeaHawks
• Brady’s kids
• Logictech spot light
• AirPods

Charles

• Express VPN
• Hyper Drive
• J5 ports and SD card readers
• Podwrench

Sponsors

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

Panel

• Charles Max Wood

Joined by special guest: Aaron Gustafson

Episode Summary 

This episode of JavaScript Jabber comes to you live from Microsoft Ignite. Charles Max Wood talks to Aaron Gustafson who has been a Web Developer for more than 20 years and is also the Editor in Chief at “A List Apart”. Aaron gives a brief background on his work in the web community, explains to listeners how web standardization has evolved over time, where Progressive Web Apps (PWAs) come from, where and how can they be installed, differences between them and regular websites and their advantages. They then delve into more technical details about service workers, factors affecting the boot up time of JavaScript apps, best practices and features that are available with PWAs. 

Aaron mentions some resources people can use to learn about PWAs, talks about how every website can benefit from being a PWA, new features being introduced and the PWA vs Electron comparison. In the end, they also talk about life in general, that understanding what people have gone through and empathizing with them is important, as well as not making judgements based on people’s background, gender, race, health issues and so on.

Links

• Creating & Enhancing Netscape Web Pages
• A List Apart
• A Progressive Roadmap for your Progressive Web App
• Windows Dev Center - Progressive Web Apps
• MDN web docs
• PWA Stats
• PWA Stats Twitter
• Aaron’s website
• Aaron’s Twitter
• https://www.facebook.com/javascriptjabber/
• https://twitter.com/JSJabber

Picks

Aaron Gustafson:

• Homegoing
• Zeitoun

Charles Max Wood:

• Armada 

Sponsors

• Triplebyte offers a $1000 signing bonus

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

• CacheFly

Panel

• AJ O’Neal

• Charles Max Wood

Joined by Special Guest: Anatoliy Zaslavskiy

Summary

Anatoliy Zaslavskiy introduces pickle.js and answers the panels questions about using it. The panel discusses the automated testing culture and employee retention. The panel discusses job satisfaction and why there is so much turn over in development jobs. Charles Max Wood reveals some of the reasons that he left past development jobs and the panel considers how the impact of work environments and projects effect developers. Ways to choose the right job for you and how to better a work situation is discussed. Anatoliy finishes by advocating for junior developers and explaining the value they bring to a company.

Links

• https://github.com/storybooks/storybook

• https://www.picklejs.com/docs/getting-started

• https://opencv.org/

• https://itunes.apple.com/us/app/snapcrap/id1436238261

• https://tolicodes.com/

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

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

• https://twitter.com/JSJabber

Picks

AJ O’Neal

• The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win by Gene Kim

• How to Diagnose and Fix Everything Electronic, Second Edition by Michael Jay Geier  

Charles Max Wood

• https://andyfrisella.com/blogs/mfceo-project-podcast

• https://www.garyvaynerchuk.com/the-askgaryvee-show-podcast/

• The 1-Page Marketing Plan: Get New Customers, Make More Money, And Stand out From The Crowd by Allan Dib

• Skyward by Brandon Sanderson

Anatoliy Zaslavskiy

• Acro yoga

• http://www.cuddleparty.com/

Sponsors

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

Host: Charles Max Wood

Joined By Special Guest: Anatoliy Zaslavskiy

Episode Summary

Anatoliy Zaslavskiy has been interested in computers since he was 7 years old, and began his programming career in high school, doing web development in PHP for the online community for his favorite show  Avatar: The Last Airbender. Anatoliy currently works for Hover as a Frontend developer transforming home photos into 3D models to help visualize what the final project will look like.

Anatoliy shares his journey as a developer with bipolar disorder and tells us how he restructured his career with his employer so he can focus on projects that he enjoys working on. This way he performs at his best and both him and Hover can benefit from his talents. Anatoliy and Charles stress the importance for companies to talk to their developers to understand their nature as both parties benefit from open and honest dialogue.

Links

• JavaScript Jabber 358: Pickle.js, Tooling, and Developer Happiness with Anatoliy Zaslavskiy
• Anatoliy's Website
• Anatoliy's Facebook
• Anatoliy's LinkedIn
• https://www.facebook.com/javascriptjabber
• https://twitter.com/JSJabber
• https://www.facebook.com/DevChattv

Picks

Anatoliy Zaslavskiy:

• XState - JavaScript State Machines and Statecharts
• Nozbe/WatermelonDB: High-performance reactive database
• Monorepo

Charles Max Wood:

• https://www.twitch.tv/
• OBS: Open Broadcaster Software

Sponsors

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

Panel

• Charles Max Wood

Joined by Special Guest: Colby Tresness

Episode Summary

Coming to you live from the podcast booth at Microsoft BUILD is Charles Max Wood with Colby Tresness. Colby is a Program Manager on Azure Functions at Microsoft. Azure functions are the serverless functions on Azure. Colby explains what the Azure functions premium plan entails, then talks about KEDA – Kubernetes-based event-driven autoscaling, a Microsoft and Red Hat partnered open source component to provide event-driven capabilities for any Kubernetes workload. One of the other cool features of serverless functions they talk about is the Azure serverless community library.

Colby and Charles discuss the best way to get started with Azure functions, as well as the non-JavaScript languages it supports.

Links

• Colby’s GitHub
• Colby’s Twitter
• Colby’s LinkedIn
• Colby’s Blog
• Microsoft Build 2019
• KEDA
• Red Hat
• Azure Serverless Community Library
• Follow Adventures in Angular on tv, Facebook and Twitter.

Picks

Colby Tresness:

• Barry (TV Series 2018– ) – IMDb 

Charles Max Wood:

• The Legend of Zelda: Breath of the Wild
• The MFCEO Project Podcast – Andy Frisella 
• Downtown Seattle

Sponsors

• Triplebyte offers a $1000 signing bonus

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

• CacheFly

Panel

Charles Max Wood

Joined by Special Guest: Jeff Hollan

Episode Summary

Coming to you live from the podcast booth at Microsoft BUILD is Charles Max Wood with Jeff Hollan. Jeff is a Sr. Program Manager for the Azure Functions cloud service. Continuing from where Colby Tresness left off in Adventures in Angular 241: Azure Functions with Colby Tresness LIVE at Microsoft BUILD, Jeff defines what “serverless” really means in developer world. Jeff also talks about various scenarios where Azure functions are extremely useful and explains what Durable Functions are.

Jeff and Charles discuss creating and running an Azure function inside a container and the upcoming capabilities of Azure functions they are currently working on.

Links

• JavaScript Jabber 369: Azure Functions with Colby Tresness LIVE at Microsoft BUILD

• Durable Functions

• Jeff’s GitHub

• Jeff’s Twitter

• Jeff’s LinkedIn

• Jeff’s Website

• Jeff’s Medium

• Microsoft Build 2019

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

Picks

Jeff Hollan:

• Calm App

• Game of Thrones TV Series

Charles Max Wood:

• Family Tree App

Sponsors

• Triplebyte $1000 signing bonus

• Sentry use code “devchat” for 2 months free

• Linode

Panel

• Charles Max Wood

• Aimee Knight

• Chris Ferdinandi

• AJ O’Neal

• Joe Eames

Episode Summary

Today the panel discusses what is necessary to get a website up and how complicated or simple it needs to be. They mention different tools they like for static sites and ways to manage their builds and websites. They talk about why some people choose to host their websites and at what point the heavier tools become a concern. They discuss whan it is necessary to use those heavy tools. 

They caution listeners to beware of premature optimization, because sometimes businesses will take advantage of newer developers and make them think they need all these shiny bells and whistles, when there is a cheaper way to do it. It is important to keep the tools you work with simple and to learn them so that if you encounter a problem, you have some context and scope. The option of serverless website hosting is also discussed, as well as important things to know about servers.

The panel discusses what drives up the price of a website and if it is worth it to switch to a cheaper alternative. They discuss the pros and cons of learning the platform yourself versus hiring a developer. The importance of recording the things that you do on your website is mentioned. Several of the panelists choose to do this by blogging so that if you search for a problem you can find ones you’ve solved in the past.

Links

• Heroku

• Github Pages

• Netlify

• Eleventy

• DigitalOcean

• Lightsale

• Ubuntu

• Git clone

• Node static server

• Systemd script

• NGinx

• Cloud66

• Thinkster

• Gatsby

• Docker

• Gentoo

• How to schedule posts with a static website

• How to set up automatic deployment with Git with a vps

• Automating the deployment of your static site with Github and Hugo

Follow DevChat on Facebook and Twitter

Picks

Charles Max Wood:

• Microsoft build

Aimee Knight:

• Systems Thinking is as Important as Ever for New Coders

Chris Ferdinandi:

• Adrian Holivadi framework video

• Server Pilot

AJ O’Neal:

• Jeff Atwood tweet

• More on Stackflow Architecture

• Minio

Joe Eames:

• Miniature painting

Sponsors

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

Panel

Charles Max Wood

Joined by Special Guest: Steve Faulkner

Episode Summary

Coming to you live from the podcast booth at Microsoft BUILD is Charles Max Wood with Steve Faulkner. Steve is a Senior Software Developer for Azure Cosmos DB at Microsoft. Cosmos DB is a global distributed, multi-model noSQL database. Steve explains the Cosmos DB service and scenarios it can be used in. They discuss how Cosmos DB interacts with Azure functions and how partition keys work in Cosmos DB.

Listen to the show for more Cosmos DB updates and to find out how Steve he got his twitter handle @southpolesteve.

Links

• Steve’s GitHub
• Steve’s Twitter
• Steve’s LinkedIn
• Steve Dev.to
• Microsoft Build 2019  
• Introduction to Azure Cosmos DB
• AiA 241: Azure Functions with Colby Tresness LIVE at Microsoft BUILD
• AiA 242- Azure Functions Part II with Jeff Hollan LIVE at Microsoft BUILD
• Microsoft Learn Resource
• Partitioning in Azure Cosmos DB

Picks

Steve Faulkner:

• FINAL FANTASY X/X-2 HD Remaster for Nintendo Switch
• Overcooked on Steam
• Fastly

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

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

Host: Charles Max Wood

Episode Summary

Charles talks about his journey as a podcaster and his mission with Devchat.tv. Devchat.tv  is designed to home podcasts that speak to all developer communities. Charles also plans Devchat.tv to host shows for technologies that are on the verge of a breakthrough and will be a lot more widely available in the near future such as Artificial Intelligence (AI), Internet of Things (IoT), Virtual Reality (VR) and Augmented Reality (AR). There are new shows being added continuously to reach out to new communities, some examples of which are: a Data Science show, a DevOps show and an Open Source show. As a kid, Charles would record his own shows on a tape recorder. He was always interested in technology. While studying Computer Engineering at Brigham Young University, he worked in the University's Operations Center. Upon graduation, he started working for Mozy where he was introduced to podcasts. Listen to the show to find out the rest of Charles' story, some of the lessons and tips he learned throughout his journey and the evolution of the shows on Devchat.tv. If there isn't a show for your community and you would like there one to be, reach out to Charles. Also if there was a podcast about a programming related subject that ended abruptly and you would like it to continue, reach out to Charles. Devchat.tv would like to host these podcasts.

Links

• Charles' Twitter
• EverywhereJS JavaScript Community
• EverywhereRB Ruby and Rails Community
• Find Your Dream Job As A Developer
• Devchat.tv on Facebook
• Devchat.tv

Picks

• EverywhereJS JavaScript Community
• EverywhereRB Ruby and Rails Community
• Netlify
• Eleventy
• https://github.com/cmaxw/devchat-eleventy