On today's JavaScript Jabber Show, Charles Max Wood, AJ O'neal, Aimee Knight, Joe Eames, and Cory House discuss Docker for Developers with Derick Bailey. Derick is currently into Docker and has been doing a series on it at WatchMeCode. He is also writing an ebook titled Docker Recipes for Node.js Development which aims to provide solutions for things that concern Node.js. Stay tuned to learn more about Docker and the ebook which Derick is working on!

On today's JavaScript Jabber Show, Charles, Aimee, Joe, and Cory discuss Wordpress and Wordpress API for JavaScript Developers with Roy Sivan. Roy is a WordPress (WP) developer at Disney Interactive. He has long been a fan of JavaScript and WP. During a WordCamp, the WP Founder announced the need for WP developers to learn JavaScript. But, what's in WP that developers should be interested about? Tune in to learn!

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

Join AJ, Aimee, and Joe as they discuss Mozilla Firefox Developer Tools with Jason Laster. Jason just started working at Mozilla since March. But even before that, he has been working on Chrome's dev tool extension called Marionette. That's when he discovered that the browser is an open source that anyone can play with. Now, he is working on a new debugger in Firefox. Tune in!

This episode features Moving from Node.js to .NET and Raygun.io with John-Daniel Trask. John-Daniel is the Co-founder and CEO of Raygun, a software intelligence platform for web and mobile. He's been programming for many years, and is originally from New Zealand. Tune in and learn what prompted them to move to the .NET framework!

On this week's episode of My JS Story, Charles Max Wood interviews Alex Russell. Alex is a software engineer on the Chrome team. He focuses on designing new features and running their standards work. He appeared as a guest on episode 87, where he talked about TC39. Tune in to his story!

MJS 025: Helen V. Holmes

This episode features a My JavaScript story with Helen V. Holmes. Helen has never before been a guest on the show. She is both a designer and front-end programmer who previously worked for Mozilla. In January, she started her own freelancing business. Listen to Charles Max Wood and Helen discuss how she got into programming, what made her decide to open a freelance business, and more!

How did you get into programming?

Helen started by making themes for herself and friends in LiveJournal using other people's CSS themes. Once she got to college she realized that although this wasn't a career, it was an aspect of a career. She then majored in graphic design, going on to do internships in both front-end development and design. Since college, she has gone back and forth between front-end development and design work.

How long ago was that?

Helen graduated college in 2013.

Did you graduate in computer science?

Helen did not even minor in computer science. At the time, she was focused on making stuff. The computer science major was too heavily focused on theory. She did take a couple of classes in it, but the graphic design major was more focused on building prototypes. Her graphic design major didn't teach her how to do anything - she said that you're on your own, and you have to figure out how to show off your ideas. The major appealed to her at the time because of that reason. Now Helen thinks majoring in computer science would have been really helpful for her career.

Charles points out that you don't have to have a computer science degree to do this work. Helen agrees; it can be wasted on you if you don't have the right enthusiasm to learn everything. Both say that you can get the education you want through self-education. Helen explains that so much of successful programming is good communication - this can be learned in college, while the specifics of how to code can be learned later.

How do you get from a graphic design major to "serious programming?"

Helen doesn't know how serious the programming she does is now. Her first real job was at Capital One as a front-end developer on their design team. She was doing prototypes and communicating between the design and production/engineering teams. She realized that nobody knew how to write JavaScript when trying to communicate between the two teams, so she decided that she should learn. A lot of the engineers came to the same realization at the same time. She started to write React as she was leaving Capital One. Everyone was trying to improve his or her JavaScript chops at the same time.

Did you get into Angular or React at Capital One?

When she first started at Capital One everyone was writing Angular. She wrote a lot of Angular in the beginning of her work. Most of the prototypes could be solved with React. Near the end of her time, she started using a lot of React.

What do you see is the difference between Angular and React?

Angular solves a lot more problems than React. It brings logic to the client side. React is only about solving visual problems. That's why it appealed to Helen. The design team she worked with was all about solving visual problems.

Why did you choose the front end?

Helen mainly chose it because she was a graphic design major. She believes that because the web is so accessible that it is the easiest thing. She also thinks the front end is fun.

How'd you wind up at Mozilla?

She met James Long through a mutual friend. Once they met, he thought she'd be a good addition to their team. He told her why it'd be a good switch for her - they were doing React work and they were looking for someone to understand problems that engineers go through.

What do they use React on?

She was on the browser team. The front-end of the developer tools was a JavaScript application that wasn't Angular. They were working on moving it to become a more documented framework. They wanted to use Redux and React. The team was converting it panel by panel.

What made you decide you were going to go freelance?

Helen had been missing things that she had done in college such as branding and illustration work. She had done some illustration work while at Firefox. She ultimately wanted to do a variety of different things instead of just product work. What gave her courage to go into freelance work was that James Long was also going freelance at the same time, so she thought that she was in good company. She also is related to a lawyer, so it wasn't as scary filing the paperwork because she had someone to ask for help during the process.

What contributions do you feel like you've made to the JavaScript community?

Helen believes that the highest impact work she has done has been on the Firefox browser. She didn't write a lot of code, but feels like what she did write is being used by a lot of people. She is most proud of the CSS grid because she says that it is exciting for people who do layout stuff on the web.

What are you working on now?

Helen started her own business at the beginning of the year. She is figuring out how she wants her skills to grow and with what kind of clients she wants to work. She has a lot of side projects, one being what she calls an art project. She is translating JPEG to Pixel art. She is taking NeoPixels, which are little programmable LEDs, and taking a matrix of values and displaying them on a sight board.

With everything that's out there in JavaScript, how do you keep current?

Helen answers that she doesn't. She tries to stay current with the tools she is using, which is React. She doesn’t try to be good at everything because she is also a designer, so she says that she has to pick and choose what she stays current on. Charles says that is what he tells people to do. There is so much out there that there is no way that anyone is going to stay current on everything. He says to keep current on what you are doing specifically.

Picks         

Helen:

• Wonder Woman http://wonderwomanfilm.com
• Debt: The First 5,000 Years https://www.amazon.com/Debt-First-5-000-Years/dp/1612191290

Charles:

• JavaScript Jabber Slack Room https://devchat.tv/javascript-jabber-slack
• Monthly Webinars  https://devchat.tv/webinars
• Angular Remote Conf https://devchat.tv/conferences/angular-remote-conf-2017

Links

• Helen V Holmes Twitter https://twitter.com/helenvholmes

JSJ 270 The Complete Software Developers Career Guide with John Sonmez

This episode features a panel of Joe Eames, AJ O’Neal, as well as host Charles Maxwell. Special guest John Sonmez runs the website SimpleProgrammer.com that is focused on personal development for software developers. He works on career development and improving the non-technical life aspects of software developers. Today’s episode focuses on John’s new book The Complete Software Developers Career Guide.

Did the book start out being 700 pages?

No. My goal was 200,000 words. During the editing process a lot of questions came up, so pages were added. There were side sections called “Hey John” to answer questions that added 150 pages.

Is this book aimed at beginners?

It should be valuable for three types of software developers: beginner, intermediate, and senior developers looking to advance their career. The book is broken up into five sections, which build upon each other. These sections are: - How to get started as a software developer - How to get a job and negotiate salary - The technical skills needed to know to be a software developer - How to work as a software developer - How to advance in career

Is it more a reference book, not intended to read front to back?

The book could be read either way. It is written in small chapters. Most people will read it start to finish, but it is written so that you can pick what you’re interested in and each chapter still makes sense by itself.

Where did you come up with the idea for the book?

It was a combination of things. At the time I wanted new blog posts, a new product, and a new book. So I thought, “What if I wrote a book that could release chapters as blog posts and could be a product later on?” I also wanted to capture everything I learned about software development and put it on paper so that didn’t lose it.

What did people feel like they were missing (from Soft Skills) that you made sure went into this book?

All the questions that people would ask were about career advice. People would ask things regarding: - How do I learn programming? - What programming language should I learn? - Problems with co-workers and boss - Dress code

What do you think is the most practical advice from the book for someone just getting started?

John thinks that the most important thing to tell people is to come up with a plan on how you’re going to become educated in software development. And then to decide what you’re going to pursue. People need to define what they want to be. After that is done, go backwards and come up with a plan in order to get there. If you set a plan, you’ll learn faster and become a valuable asset to a team. Charles agrees that this is how to stay current in the job force.

What skills do you actually need to have as a developer?

Section 3 of the book answers this question. There was some frustration when beginning as a software developer, so put this list together in the book. - Programming language that you know - Source control understanding - Basic testing - Continuous integration and build systems - What kinds of development (web, mobile, back end) - Databases - Sequel

Were any of those surprises to you?

Maybe DevOps because today’s software developers need to, but I didn’t need to starting out. We weren’t involved in production. Today’s software developers need to understand it because they will be involved in those steps.

What do you think is the importance of learning build tools and frameworks, etc. verses learning the basics?

Build tools and frameworks need to be understood in order to understand how your piece fits into the bigger picture. It is important to understand as much as you can of what’s out there. The basics aren’t going to change so you should have an in depth knowledge of them. Problems will always be solved the same way. John wants people to have as few “unknown unknowns” as possible. That way they won’t be lost and can focus on more timeless things.

What do you think about the virtues of self-taught verses boot camp verses University?

This is the first question many developers have so it is addressed it in the book. If you can find a good coding boot camp, John personally thinks that’s the best way. He would spend money on boot camp because it is a full immersion. But while there, you need to work as hard as possible to soak up knowledge. After a boot camp, then you can go back and fill in your computer science knowledge. This could be through part time college classes or even by self-teaching.

Is the classic computer science stuff important?

John was mostly self-taught; he only went to college for a year. He realized that he needed to go back and learn computer science stuff. Doesn’t think that there is a need to have background in computer science, but that it can be a time saver.

A lot of people get into web development and learn React or Angular but don’t learn fundamentals of JavaScript. Is that a big mistake?

John believes that it is a mistake to not fully understand what you’re doing. Knowing the function first, knowing React, is a good approach. Then you can go back and learn JavaScript and understand more. He states that if you don’t learn the basics, you will be stunted and possibly solve things wrong. Joe agrees with JavaScript, but not so much with things algorithms. He states that it never helped him once he went back and learned it. John suggests the book Algorithms to Live By – teaches how to apply algorithms to real life.

Is there one question you get asked more than anything else you have the answer to in the book?

The most interesting question is regarding contract verses salary employment and how to compare them. It should all be evaluated based on monetary value. Salary jobs look good because of benefits. But when looking at pay divided by the hours of work, usually a salary job is lower paid. This is because people usually work longer hours at salary jobs without being paid for it.

What’s the best place for people to pick up the book?

simpleprogrammer.com/careerguide and it will be sold on Amazon. The book will be 99 cents on kindle – want it to be the best selling software development book ever.

Picks

Joe

Wonder Woman

AJ

The Alchemist

Charles

Artificial Intelligence with Python

John

Algorithms to Live by: The Computer Science of Human Decisions Apple Airpods

Links

Simple Programmer Youtube

JSJ 275: Zones in Node with Austin McDaniel

The panel for this week on JavaScript Jabber is Cory House, Aimee Knight, and Charles Max Wood. They speak with special guest Austin McDaniel about Zones in Node. Tune in to learn more about this topic!

[00:01:11] Introduction to Austin

Austin has worked in JavaScript for the past ten years. He currently works in Angular development and is a panelist on Angular Air. He has spent most of his career doing work in front-end development but has recently begun working with back-end development. With his move to back-end work he has incorporated front-end ideas with Angular into a back-end concept.

[00:02:00] The Way it Works

NodeJS is an event loop. There is no way to scope the context of a call stack. So for example, Austin makes a Node request to a server and wants to track the life cycle of that Node request. Once deep in the scope, or deep in the code, it is not easy to get the unique id. Maybe he wants to get the user from Passport JS. Other languages – Python, Java – have a concept called thread local storage. They can associate context with the thread and throughout the life cycle of that request, he can retrieve that context.

There is a TC39 proposal for zones. A zone allows you to do what was just described. They can create new zones and associate data with them. Zones can also associate unique ids for requests and can associate the user so they can see who requested later in the stack. Zones also allow to scope and create a context. And then it allows scoping requests and capturing contacts all the way down.

[00:05:40] Zone Uses

One way Zone is being used is to capture stack traces, and associating unique ids with the requests. If there is an error, then Zone can capture a stack request and associate that back to the request that happened. Otherwise, the error would be vague.

Zones are a TC39 proposal. Because it is still a proposal people are unsure how they can use it. Zones are not a new concept. Austin first saw Zones being used back when Angular 2 was first conceived. If an event happened and they wanted to isolate a component and create a scope for it, they used Zones to do so. Not a huge fan of how it worked out (quirky). He used the same library that Angular uses in his backend. It is a specific implementation for Node. Monkey patches all of the functions and creates a scope and passes it down to your functions, which does a good job capturing the information.

[00:08:40] Is installing the library all you need to get this started?

Yes, go to npminstallzone.js and install the library. There is a middler function for kla. To fork the zone, typing zone.current. This takes the Zone you are in and creates a new isolated Zone for that fork. A name can then be created for the Zone so it can be associated back with a call stack and assigned properties. Later, any properties can be retrieved no matter what level you are at.

[00:09:50] So did you create the Zone library or did Google?

The Google team created the Zone library. It was introduced in 2014 with Angular 2. It is currently used in front-end development.

[00:10:12] Is the TC39 proposal based on the Zone library?

While Austin has a feeling that the TC39 proposal came out of the Zone library, he cannot say for sure.

[00:10:39] What stage is the proposal in right now?

Zone is in Stage Zero right now. Zone JS is the most popular version because of its forced adoption to Angular. He recommends people use the Angular version because it is the most tested as it has a high number of people using it for front-end development.

[00:11:50] Is there an easy way to copy the information from one thread to another?

Yes. The best way would probably be to manually copy the information. Forking it may also work.

[00:14:18] Is Stage Zero where someone is still looking to put it in or is it imminent?

Austin believes that since it is actually in a stage, it means it is going to happen eventually but could be wrong. He assumes that it is going to be similar to the version that is out now. Aimee read that Stage Zero is the implementation stage where developers are gathering input about the product. Austin says that this basically means, “Implementation may vary. Enter at your own risk.”

[00:16:21] If I’m using New Relic, is it using Zone JS under the hood?

Austin is unsure but there something like that has to be done if profiling is being used. There has to be a way that you insert yourself in between calls. Zone is doing that while providing context, but probably not using Zone JS. There is a similar implementation to tracing and inserting logging in between all calls and timeouts.

[00:17:22] What are the nuances? Why isn’t everybody doing this?

Zone is still new in the JavaScript world, meaning everyone has a ton of ideas about what should be done. It can be frustrating to work with Zone in front-end development because it has to be manually learned. But in terms of implementation, only trying to create a context. Austin recommends Zone if people want to create direct contacts. The exception would be 100 lines of Zone traces because they can get difficult.

Another issue Austin has is Node’s native basic weight. Weight hooks are still up in the air. The team is currently waiting on the Node JS community to provide additional information so that they can finish. Context can get lost sometimes if the wrong language is used. He is using Typescript and doesn’t have that problem because it is straightforward.

[00:21:44:] Does this affect your ability to test your software at all?

No, there have not been any issues with testing. One thing to accommodate for is if you are expecting certain contexts to be present you have to mock for those in the tests. After that happens, the tests should have no problems.

Picks

Cory:

• Apple AirPods

Aimee:​

• Blackmill
• Understanding Zones

Charles:

• Classical Reading Playlist on Amazon
• Building stairs for his dad
• Angular Dev Summit 

Austin:

• NGRX Library Redux 

Links

• Twitter
• GitHub

JSJ 277: Dojo 2 with Dylan Schiemann and Kitson Kelly

This episode of JavaScript Jabber features panelists Aimee Knight, Cory House, and Charles Max Wood. They talk with Dylan Schiemann and Kitson Kelly about Dojo 2.

[00:02:03] Introduction to Dylan Schiemann

Dylan is the CEO at Sitepen and co-founder of the Dojo Toolkit.

[00:02:22] Introduction to Kitson 

Kitson is the CTO at Sitepen and project lead for Dojo 2.

[00:02:43] Elevator Pitch for Dojo

Dojo 1 has been around forever. Started back in 2004 as a way to solve the challenge of "I want to build something cool in a browser." Promises and web components were inspired by or created by Dojo. It's been a huge influence on the web development community.

Dojo 2 is a ground up re-write with ES 2015, TypeScript and modern API's. It's a modernized framework for Enterprise applications.

[00:04:29] How is Dojo different from other frameworks?

There's a spectrum: small libraries like React with an ecosystem and community of things you add to it to Angular which is closer to the MV* framework with bi-directional data binding. Vue lands somewhere in the middle. Dojo 2 is also somewhere in the middle as well. It's written in TypeScript and has embraced the TypeScript experience.

[00:06:00] Did the Angular 2 move influence the Dojo 2 development and vice-versa?

Dojo 2 had moved to TypeScript and 2 days later Angular announced that they were going to TypeScript. Angular also moved very quickly through their BETA phase, which caused some challenges for the Angular community.

With Dojo 2, they didn't start the public discussion and BETA until they knew much better what was and wasn't going to change. They've also been talking about Dojo 2 for 6 or 7 years.

The update was held up by adoption of ES6 and other technologies.

Dojo 1 was also responsible for a lot of the low-level underpinning that Angular didn't have to innovate on. Dojo 2 was built around a mature understanding of how web applications are built now.

People doing Enterprise need a little more help and assistance from their framework. Dojo provides a much more feature rich set of capabilities.

Angular could have pushed much more of TypeScript's power through to the developer experience. Dojo much more fully adopts it.

It's also easier if all of your packages have the same version number.

Call out to Angular 4 vs Angular 2.

[00:12:44] AMD Modules

Why use AMD instead of ES6 modules?

You can use both. Dojo 2 was involved in the creation of UMD. James Burke created UMD while working on Dojo.

ES6 modules and module loading systems weren't entirely baked when Dojo 2 started to reach maturity, so they went with UMD. It's only been a few months since Safari implemented the ES6 module system. Firefox and friends are still playing catchup.

The Dojo CLI build tool uses webpack, so it's mostly invisible at this point.

So, at this point, should I be using UMD modules? or ES6? Is there an advantage to using AMD?

With TypeScript you'd use ES6 modules, but UMD modules can be loaded on the fly.

[00:16:00] Are you using Grunt?

Internally, for tasks we use Grunt. But for users, we have a CLI tool that wraps around Webpack.

For package builds and CI, Grunt is used.

[00:18:30] What is the focus on Enterprise all about?

There are a lot of different challenges and complexities to building Enterprise apps. Dojo was the first framework with internationalization, large data grids, SVG charts, etc. Dojo has spend a long time getting this right. Many other systems don't handle all the edge cases.

Internationalization in Angular 2 or 4 seems unfinished.

Most Dojo users are building for enterprises like banks and using the features that handle large amounts of data and handle those use cases better.

[00:21:05] If most application frameworks have the features you listed, is there a set of problems it excels at?

The Dojo team had a hard look at whether there was a need for their framework since many frameworks allow you to build great applications. Do we want to invest into something like this?

React has internationalization libraries. But you'll spend a lot of time deciding which library to use and how well it'll integrate with everything else. A tradeoff in decision fatigue.

In the Enterprise, development isn't sexy. It's necessary and wants to use boring but reliable technology. They like to throw bodies at a problem and that requires reliable frameworks with easily understood decision points.

Producing code right is a strong case for TypeScript and they pull that through to the end user.

Many frameworks start solving a small set of problems, become popular, and then bolt on what they need to solve everything else...

Dojo tried to make sure it had the entire package in a clear, easy to use way.

You can build great apps with most of the big frameworks out there. Dojo has been doing this for long enough that they know where to optimize for maintainability and performance.

[00:29:00] Where is Dojo's sweet spot? 

The Sitepen Blog series on picking a framework

The biggest reason for using Dojo over the years is the data grid component.

They also claim to have the best TypeScript web development experience.

You may also want a component based system with the composition hassles of React.

The composability of components where one team may write components that another uses is a big thing in Dojo where one person doesn't know the entire app you're working on.

Theming systems is another selling point for Dojo.

[00:34:10] Ending the framework wars

Try Dojo out and try out the grid component and then export it to your Angular or React app.

There are a lot of frameworks out there that do a great job for the people who use them. The focus is on how to build applications better, rather than beating out the competition.

Sitepen has build apps with Dojo 2, Angular, React, Dojo + Redux, etc.

[00:39:01] The Virtual DOM used by Dojo

2 years ago or so they were looking for a Virtual DOM library that was small and written in TypeScript. They settled on Maquette.

The more you deal with the DOM directly, the more complex your components and libraries become.

Makes things simpler for cases like server side rendering getting fleshed out in BETA 3.

It also allows you to move toward something like React Native and WebVR components that aren't coupled to the DOM.

They moved away from RxJS because they only wanted observables and shimmed in (or polyfilled) the ES-Next implementation instead of getting the rest of the RxJS  that they're not using.

[00:46:40] What's coming next?

They're finishing Dojo 2. They're polishing the system for build UI components and architecture and structuring the app. They plan to release before the end of the year.

They're also wrapping up development on the Data Grid, which only renders what shows on the screen plus a little instead of millions of rows.

[00:49:08] Testing

They've got intern.

It pulls together unit testing, functional testing, continuous integration hooks, accessibility testing, etc.

It's rewritten in TypeScript to take advantage of modern JavaScript.

The Dojo CLI uses intern as the default test framework.

Kitson build the test-extras library to help with Dojo testing with intern.

Dojo Links

• dojo.io
• github.com/dojo/meta
• sitepen.com/blog
• gitter channel
• github.com/dylans
• twitter.com/dylans
• twitter.com/sitepen
• twitter.com/dojo
• github.com/kitsonk
• twitter.com/kitsonk

Picks

Cory

• Amateur vs Professional

Aimee

• DevFest Florida (use code 'jsjabber')

Chuck

• Taking some time off
• AudioTechnica ATR2100
• How to define your life purpose in 5 minutes

Dylan

• zenhub
• HalfStack Conference
• How to choose a framework series on the Sitepen Blog

Kitson

• Dunbar Number

Tweet this episode

JSJ BONUS: Web Apps on Linux with Jeremy Likness and Michael Crump

In this episode Aimee Knight and Charles Max Wood discuss Microsoft's Web Apps on Linux offering with Jeremy Likness and Michael Crump.

[00:37] Michael Crump Introduction

Michael is on the developer experience team for Azure.

[00:52] Jeremy Likness Introduction

Jeremy is on the cloud developer advocacy team. Their mission is to remove friction and support developers and work with teams to build a positive experience.

The NodeJS team is headed up by John Papa. They have teams around the world and involved in many open source communities.

They're focused on building documentation and creating great experiences

[02:54] What is it about Azure that people should be getting excited about?

Azure is a huge platform. It can be overwhelming. They're trying to help you start with your problem and then see the solution as it exists on Azure.

Azure is growing to embrace the needs of developers as they solve these problems.

The experience is intended to be open and easy to use for any developer in any language on any platform. It allows you to work in whatever environment you want.

Standing up applications in production is tough. Azure provides services and facilities (and interfaces) that make it easy to manage infrastructure.

You don't have to be an operations expert.

Chuck mentions this messaging as he heard it at Microsoft Connect() last year.

It's not about bringing you to .NET. It's about making it easy where you're at.

Aimee adds that as a new-ish person in the community and Azure excites her because the portal and tutorials are easy to follow for many new programmers.

A lot of these features are available across command lines, tools, and much more.

The documentation is great. See our interview with Dan Fernandez on the Microsoft Docs.

[12:04] Web Apps on Linux

Web application as a service offering from Microsoft. I don't need to worry about the platform, just what's different about my application.

Web Apps has traditionally been on Windows. Web Apps on Linux is in preview.

You can choose the size of your infrastructure. You only get billed for what you use and can scale up.

Setting up multiple servers, managing synchronization and load balancing is a pain. Web Apps gives you a clean interface that makes this management easy.

You can also scale across multiple datacenters around the world.

[15:06] Why Linux? What's hard about Windows?

Node was originally created on Linux and many tools run nicely on Linux. It was later ported to Windows.

The toolchains and IDE's and build processes is in an ecosystem that is targeted more toward Linux than Windows.

This allows people to work in an environment that operates how they expect instead of trying to map to an underlying Windows kernel.

Aimee gives the example of trying to set up ImageMagick on Windows.

Web Apps on Linux also allows you to build integrations with your tools that let you build, test, and deploy your application automatically.

[19:12] Supported Runtimes

Web Apps on Linux supports Node, PHP, Ruby, and .NET Core.

You can run a docker container with Node up to 6.x. If you want Node 7.x and 8.x you can create your own Docker container.

Web Apps on Linux is build on Docker.

The containers also have SSH, so developers can log into the docker container and troubleshoot problems on the container.

If you can build a container, you can also run it on this service.

At certain levels, there's automatic scaling.

[22:06] Consistency between containers? Shared ownership of state or assets

It depends on how you build your app. The Docker containers have a shared storage where all the containers have access to the same data and state.

There's a system called kudu that makes this really simple.

You can also pull logs across all systems.

You can also use SSH in the browser

[25:23] What's painful about Linux and containers?

How is the application built and how does it manage state so that you can isolate issues.

If you have 20 containers, can you connect to the right one.

It's up to you to manage correlation between containers so you can find the information you need.

Knowing your traffic and understanding what to do to prepare for it with scaling and automation is sometimes more art than science.

[28:28] How should you manage state?

A lot of these systems lend themselves to running stateless, but you don't want to run mongodb on each container versus running one mongodb instance that everything attaches. You want a common place to store data for the entire app for shared state.

[30:34] CosmosDB (was DocumentDB)

It's an API equivalent to MongoDB. It's a database as a service and you can connect your containers to the CosmosDB in Azure using your portal to make it super easy.

You may need to open up some firewall rules, but it should be pretty straightforward.

[34:14] Third Party Logging Management Apps

Azure has a service that provides metrics (Application Insights) and a logging service. Many other companies use elasticsearch based solutions that solve some of these problems as well.

[36:06] How do people use Web Apps on Linux?

Companies building new applications many times want to run without managing any infrastructure. So, they use Azure Functions, and other services on Azure.

Lift and shift: Take a virtual machine and change it into a web app container that they can run in the cloud. They also move from SQL Server on a server to SQL Server on the cloud. Moving from hosted MongoDB to CosmosDB.

You can also use any images on DockerHub.

[40:06] Continuous Integration and Continuous Deployment

Whether you're using a private registry or cloud registry. When you publish a new image, it'll use a webhook to pull the custom image and deploy it. Or to run it through Continuous Integration and then deploy it without any human interaction.

Chuck mentions the case when you haven't logged into a server for a while, there's a huge backlog of system updates. Updating your container definitions makes upkeep automatic.

[42:02] Process files and workers with PM2 format

You can set up instances to run across cores with the PM2 definitions. You can also make it run various types of workers on different containers.

Why did you use PM2? What other uses are there for this kind of setup?

You can tell it which processes to start up on boot. You can also have it restart processes when a file is changed, for example, with a config file you can have it restart the processes that run off that config file.

[45:38] How to get started

Getting started with Node

docs.microsoft.com

Trial account with a few hundred dollars in Azure credit.

Michael's Links

• michaelcrump.net
• @mbcrump
• github.com/mbcrump

Jeremy's Links

• bit.ly/coderblog
• @jeremylikness
• github/jeremylikness

Picks

Aimee

• Having a little bit of mindfulness while waiting on code and tests to run.

Joe

• Ozark on Netflix
• Star Wars: Rogue One

Chuck

• Travelers on Netflix

Jeremy

• Ozark filming in Woodstock, GA
• Autonomous Smart Desk
• LED light strips

Michael

• Conference Call Bingo
• Life (Movie)
• Get Out (Movie)

Tweet this Episode

Tyler Renelle is a contractor and developer who has worked in various web technologies like Node, Angular, Rails, and much more. He's also build machine learning backends in Python (Flask), Tensorflow, and Neural Networks.

The JavaScript Jabber panel dives into Machine Learning with Tyler Renelle. Specifically, they go into what is emerging in machine learning and artificial intelligence and what that means for programmers and programming jobs.

This episode dives into:

• Whether machine learning will replace programming jobs
• Economic automation
• Which platforms and languages to use to get into machine learning
• and much, much more...

Links:

• Raspberry Pi
• Arduino
• Hacker News
• Neural Networks (wikipedia)
• Deep Mind
• Shallow Algorithms
• Genetic Algorithms
• Crisper gene editing
• Wix
• thegrid.io
• Codeschool
• Codecademy
• Tensorflow
• Keras
• Machine Learning Guide
• Andrew Ng Coursera Course
• Python
• R
• Java
• Torch
• PyTorch
• Caffe
• Scikit learn
• Tensorfire
• DeepLearn.js
• The Singularity is Near by Ray Kurzweil
• Tensorforce
• Super Intelligence by Nick Bostrom

Picks:

Aimee

• Include media
• Nodevember
• Phone cases

AJ

• Data Skeptic
• Ready Player One

Joe

• Everybody Lies

Tyler

• Ex Machina
• Philosophy of Mind: Brains, Consciousness, and Thinking Machines

Tweet this Episode

John-Daniel Trask is the CEO and developer at Raygun.io.

JD and Chuck talk in this episode about learning to program as a kid, the arc of JD's career, and entrepreneurship.

Links:

• 154 JSJ Raygun.io Error Reporting and Workflow with John-Daniel Trask
• JSJ 263 Moving from Node.js to .NET and Raygun.io with John-Daniel Trask
• C
• C++
• Delphi
• NetScape Navigator
• VBScript
• JQuery
• Mindscape
• Raygun.io
• CoffeeScript
• Visual Studio
• Scott Hanselman on Dark Matter Developers
• Tensorflow
• Stripe
• @traskjd

Picks:

JD:

• Keygen.sh
• Octopus Deploy
• JavaScript x86

Chuck:

• The Miracle Morning
• Meditations App
• Vision Board App
• LootCrate
• Game of Thrones Journal
• Zelda Theme Journal

Panel:

Amiee Knight

Charles Max Wood

Special Guests: 

JC Hiatt

In this episode, JavaScript Jabbers speak with JC Hiatt. JC is a software consultant, and working a starting a company called DevLifts. DevLifts is a company that helps developers learn to live healthier lives. JC mentions this business was base on this health journey.

JC and the panel discuss output and mental clarity to get work done in a healthy fashion. Also, the benefits of eating a healthy diet, rather it is the Keto Diet or others types of healthy clean eating, there is a physical and mental benefit. JC and the panel talk about count macros, healthy food intake, and a basic outline of getting into ketosis. Also, the panel discusses finding the motivation to get into a healthy lifestyle to benefit work and your lifestyle.

In particular, we dive pretty deep on:

• Mental Clarity
• Keto Diet
• Cutting out processed foods
• Counting Macros
• Getting into Ketosis
• Supporting brain function
• Motivation for a healthy lifestyle
• Gaining energy
• Getting started  - Walking, Eat Whole. Etc.
• Pack your own lunch
• Mindset change -  you are responsible for anyone else’s healthy choices
• Drink Water
• You can find a healthy balance and practice moderation
• Cheat day?
• Sugar
• Sitting to0 long at work
• Sleep - brain wave activity, caffeine, and light
• Naps
• And much more!

Links:

@jchiatt

@devlifts

devlifts.io

Picks:

Amiee

• https://www.womenwhotech.com/panelist-bios
• https://github.com/AllThingsSmitty/css-protips

Charles

• Gunnar blue blockers 
• Flux
• ReactDevSummit.com
• JSDevSummit.com
•  

JC

• American Vandal
• Confession Tapes 
• Qalo
• https://lodash.com

Panel:

Charles Max Wood

In this episode of JavaScript Jabber, Charles does a solo episode talking about entrepreneurship and the topic/course on “How to Get a Job.” This is an informative episode for those looking for a job as a developer and how to prepare your resume for your career search. Charles covers the core pieces of the course and specific areas of tailoring your credentials for the job you want to acquire.

In particular, we dive pretty deep on:

• How do I get a great job? Companies are only hiring Senior Devs.
• Your selling point as a Jr. Dev.
• Framing your experience for the companies to better see your experience.
• I don’t want a ( this kind of boss)
• Feeling like you are making a difference in your job.
• Who do you want to work for, with, where, and how, etc?
• Working in a facility or remotely. What do you want?
• Check out the meet-up places or workplaces (WeWork), Glassdoor
• Check out the people who work that these companies, LinkedIn.
• Check out company’s Slack rooms, forum, etc. to make connections
• Visit the companies personally
• Look into contacting the Meetup Organizers
• Building rapport
• Resume mistakes - how to properly format it so it is skim-able
• Top 3 bullet points and tailor you resume for each job
• Unnecessary material in your resume - again tailor to the company
• Important material to include on your resume, contributions on projects
• The cover letter - How to do this correctly with a personal touch
• What to do when you get the interview - the offer!
• And much more!

Links:

• devchat.tv/get-a-coder-job-full-accessfull-access
• WeWork
• Expert Salary Negotiation

Panel:

Charles Max Wood

Aimee Knight

Corey House

Joe Eames

Special Guests: 

In this episode, JavaScript Jabber speaks with Dirk Hohndel about Open Source Software. Dirk is the Chief Open Source Officer at VMWare and has been working with open source for over 20 years. Dirk duties as the Chief Open Source Officer is to engage with the open source community and help promote the development between the community, companies, and customers.

Dirk provides historical facts about open sources to current processes. The discussion covers vision and technological advances with languages, security, and worries of using open source software, view/consumption and burnout on maintaining a project. This is a great episode to learn about more different avenues of Open Source.

In particular, we dive pretty deep on:

• What does the Chief Open Source Officer do?
• What is really different and has stayed the same in open source?
• Technological advances
• Good engineering and looking ahead or forward
• 100 million lines of code running a car…
• This is in everything..
• Production environments
• Security
• Bugs in the software and the security issues
• Scaling and paying attention
• Where should we be worried about open source
• Notation and data sets
• Write maintainable software
• How does VMWare think about open source?
• View and Consumption of open source
• The burnout of open source projects - how to resolve this abandonment
• To much work to maintain open source  - not a money issue
• Scaling the team workload not the money
• Contribution and giving back
• Companies who do and don’t welcome open source
• What to do to make a project open source?
• Adopting an API
• And much more!

Links:

• @_drikhh
• VMWare
• Drikhh - everywhere!
• https://github.com/dirkhh

Picks:

Aimee

• De Contact 
• Dodow 

Dirk

• Track This Critical Thinking

Charles

• Nicholas Zakas - Books 

Corey

• Fun Fun Function Show

Joe

• Dice Forge
• Concept of empathy

Panel: 

Charles Max Wood

Guest: Tyler Renelle

This week on My JavaScript Story, Charles speaks with Tyler Renelle. Tyler is a contractor and developer who has worked in many web technologies like Angular, Rails, React and much more! Tyler is a return guest, previously on Adventure in Angular and JavaScript Jabber talking Ionic and Machine learning.

Tyler has recently expanded his work beyond JavaScript and is on the show to talk his interest in AI or Artificial intelligence and Machine Learning. Furthermore, Tyler talks about his early journey as a game developer, web developer, and work with some content management systems, and more recently, his development in various technologies.

In particular, we dive pretty deep on:

• Writing games out of college
• Studies computer science in college
• Did web development to pay for college working with PHP and ASP
• Content management
• Working with various technologies
• Working with React, is this it?
• Problems React has solved with web apps
• What is the next big innovation?
• View
• Creating Podcasts
• Machine Learning
• Specialized application of AI
• NLP
• Never use his computer science degree as a web developer
• You don’t study code to be a developer
• AI and machine learn is based on Computer Science
• Tensor Flow
• Data Skeptic - podcast
• Performance
• Graphics cards
• Philosophy of Consciousness
• The subjective experience
• Job displacement phenomenon
• and much, much more!

Links: 

• http://ocdevel.com
• http://ocdevel.com/podcasts/machine-learning
• Tensor Flow
• Data Skeptic - podcast
• https://devchat.tv/js-jabber/jsj-278-machine-learning-tyler-renelle
• https://www.linkedin.com/in/lefnire

Picks

Tyler

• The Great Courses 

Charles

• CES
• Email beforehand and set up an appointment
• VRBO.com
• Autonomous.ai

Panel: 

Charles Max Wood

Guest: Kitson Kelly

This week on My JavaScript Story, Charles speaks with Kitson Kelly. Kitson is a return guest, previously on JavaScript Jabber 277. Kitson is the CTO at SitePen, and has been working and maintaining Dojo 2 for the last couple years.

Kitson talks about his journey as a developer. First, sparking his interest with old Atari games and getting his first computer in his early years.  Kitson talks about his education background and introduction to computers in high school and hang out with other in the same programming niche. Kitson talks about his challenges not having a degree in computer science, but still very successful as a developer after climbing the corporate latter.

In particular, we dive pretty deep on:

• Atari Games and old first computer
• Hangout with the computer nerds
• Community college
• No actual formal computer science degree
• Tech Support and Self Taught
• Challenges with not degree
• Climbing the latter
• Troubles even with a degree
• Is a degree in computer science really needed?
• Experience verses degree
• Working with other people is important
• Getting into JavaScript and Dojo
• What kept you working in JavaScript
• How do you get to being CTO and SitePen?
• What are you most proud of with the work on Dojo
• Contributions
• Side Projects  - Dojo 2
• and much, much more!

Links: 

• https://github.com/kitsonk
• Kistson Kelly
• https://www.sitepen.com
• https://dojo.io

Picks:

Kitson

• SVG 
• Noun Project

Charles

• adminlte.io
• Ruby on Rails, Jquery
• podwrench.com

Panel: 

Charles Max Wood

Guest: Austin McDaniel

This week on My JavaScript Story/My Angular Story, Charles speaks with Austin McDaniel. Austin is a return guest and was previously featured on JavaScript Jabber episode 275 . Austin talks about his journey getting into programming as an 11year old, to recently, as a web developer with more complex technologies. Austin talks about building widgets, working in Angular, JavaScript, and more in-depth web development on many different platforms. Lastly, Austin talks about his contributions to NGX Charts and speaking at a variety of developer conferences.

In particular, we dive pretty deep on: 

• How did you get into programming? 11 years old
• Cue Basic
• Web developer
• College jobs was in web developing
• IE6
• Building Widgets
• Components
• jquery 
• Web is the future
• How did you get into Angular? 2013, v1.2
• Backbone
• Angular 1 & 2
• NG X Charts
• Speaking at Conferences
• Augmented Reality and VR
• Web AR
• Angular Air Podcast
• Working as a contractor with Google
• and much, much more!

Links: 

• JavaScript Jabber episode 275
• jquery
• http://amcdnl.com
• Angular Air Podcast
• @amcdnl
• github.com/amcdnl
•  

Picks

Austin

• Todd Motto 

Charles

• NG Conf
• Angular Dev Summit
• Angular Air Podcast

Panel: 

Charles Max Wood 

Cory House

Joe Eames

Aimee Knight  

Special Guests: Ryan Glover

In this episode, JavaScript Jabber panelist speak with Ryan Glover. Ryan is on JavaScript Jabber to talks about Entrepreneurship as a developer.  Ryan runs Clever Beagle in Chicago Illinois. Clever Beagle is a mentorship company that helps people build their first software Product. Ryan and the panel discuss the many roads of entrepreneurship, startup business ideas, servicing and teaching the community, how to’s, and psychological challenges, hiring, seeing your ideas through to the end, and privilege. 

In particular, we dive pretty deep on:

• How do you get started as an entrepreneur? 
• Clever Beagle
• The Meteor Chef
• Where are people getting stuck on the builds? 
• Fear, unknowns
• Simple, but not easy 
• Drive and ability to step into the unknown
• Survival of the fittest
• Hire before you are already 
• Losing your marbles
• Starting on a smaller scale
• How do I know my idea is going to work? 
• Book - Brick by Brick
• Multiple lines of business
• Managing a portfolio of business 
• Revenue streams 
• Marketing 
• Quitter
• When do I quit? 
• 6-12 months of cash before you quit
• Making mistakes in entrepreneurship?
• Be a reader and study
• Go out a read books! 
• Experiential not taught 
• Luck and Privilege
• Video - Life of Privilege Explained in a $100 Race
• Procrastinate on Purpose
• And much more! 

Links:

• Clever Beagle 
• The Meteor Chef
• https://www.linkedin.com/in/ryangglover
• http://www.ryanglover.net
• Brick by Brick
• Quitter
• Procrastinate on Purpose
• Do Thing That Don’t Scale
• @rglover

Picks:

Cory

• The Power of Moments
• The 50th Law

Charles

• ReactDevSummit.com
• Indiegogo for Dev Chat
• .NetRocks

Aimee

• Life of Privilege Explained in a $100 Race

Joe

• Everybody Lies
• Murder on the Orient Express
•  

Ryan

• Turning Pro - Steven Pressfield series
• The Power of Beliefs in Business

Panel: 

Charles Max Wood

Joe Eames

Aimee Knight

Special Guests: Russell Goldenberg and Adam Pearce

In this episode, JavaScript Jabber panelist speak with Russell Goldenberg and Adam Pearce Russell creates visualizations, interactive graphics, and documentaries for the web. Currently an editor at The Pudding.  Adam is a graphics editor at The New York Times and a journalist engineers/developer  Russell and Adam are on the show to talk about what Scrollytelling is, as well as Scrollama. Scrollama is a modern and lightweight JavaScript library for scrollytelling using IntersectionObserver in favor of scroll events. This is a great episode to understand another technology/tool created with JavaScript.

In particular, we dive pretty deep on:

• What is Scrollytelling!
• Graph Scroll library
• What is the intersection Observerable?
• How long does it take to build an interactive graphic…?
• How do you test something like this?
• Test on a lot of different devices
• Can you do automated testing?
• Do you have to understand the use cases or can you implement quickly?
• Recommendation for getting started?
• Is this a skill set people have to have before that some on board?
• How do design these interactions?
• Scroll jacking
• What JS developers should know about this technology.
• Position sticky
• What are other uses cases?
• What can devs use it for?
• Tax calculator
• And much more!

Links:

•  
• https://github.com/russellgoldenberg/scrollama
• https://pudding.cool/process/introducing-scrollama/
• @codenberg
• @adamrpearce
• https://pudding.cool/
• http://russellgoldenberg.github.io
• https://github.com/1wheel?direction=desc&sort=created&tab=stars
• https://roadtolarissa.com

Picks:

Adam

• Dominion - Broad Game

Charles

• Smoker
• Tiny Epic Galaxies
• Indiegogo Dev Chat TV

Aimee

• Deadlines
• Quest Protein Powder

Joe

• Giving!
• Board Game - Azul

Russel

• Crokinole
• Bust Out

Panel: 

AJ O’Neal

Joe Eames

Aimee Knight

Special Guests: Chris Ferdinandi

In this episode, JavaScript Jabber panelist speak with Chris Ferdinandi. Chris teaches vanilla JavaScript to beginners and those coming from a design background. Chris mentions his background in Web design and Web Develop that led him JavaScript development. Chris and the JSJ panelist discuss the best ways to learn JavaScript, as well as resources for learning JavaScript. Also, some discussion of technologies that work in conjunction with vanilla JavaScript.

In particular, we dive pretty deep on:

• Teaching JavaScript - Beginners and Design patrons
• Web Design and Web Development
• CSS Tricks 
• Todd Motto
• How to do jQuery Things without jQuery
• Doing things like mentors (Todd)
• When JavaScript makes sense.
• CSS is easier to learn then JS?
• Being good at CSS and JS at the same time?
• How about Node developers?
• jRuby, DOM
• Documentation
• And much more!

Links:

• https://github.com/cferdinandi
• https://gomakethings.com
• @ChrisFerdinandi
• https://www.linkedin.com/in/cferdinandi
•  

Picks:

AJ

• Discover Card
• Mistborn 

Aimee

• Your Smart Phone is Making You Stupid…
• Crypto Currency

Joe

• Mystic Vale
• Kedi

Chris

• https://gomakethings.com
• Teva Mush

Panel: Charles Max Wood

Guest: Tim Caswell

This week on My JavaScript Story, Charles speaks with Tim Caswell. Tim got into programming when he was a kid and would mess around on a Commodore 64 he had found. He next moved onto writing games in Cue Basic, and once the internet came into play in the mid to late 90’s, his programming really took off, especially after he got Windows. Tim has since written his own language based on Lua, called Luvit, worked on browser-based IDE systems, like Cloud 9, and so much more. After working on many projects and programs over the years, he is now focusing on building his startup. His advice is to always balance your needs with what you can do and make sure that you are always moving forward.

In particular, we dive pretty deep on:

• How did you get into programming?
• Commodore 64
• 386SX
• Games in Cue Basic
• CompuServe
• SweetSharks.com startup
• JavaScript and HTML
• Learning about CPUs in college
• Studied at Central Arkansas originally
• C++
• Software engineering at UT Dallas
• Connect Framework
• NVM in Bash
• Luvit computer language
• Polyglot startup
• New product, SDK, coming soon
• Daplie
• Balance and moving forward
• Getting paid for value
• His mission
• The power to create and to inspire
• And much, much more!

Links: 

• Fresh Books
• Linode
• @CreationIX
•  

Picks

Tim

• Daplie
• Upcoming SDK
• Beaker Browser
• Secure Scuttle Butt

Charles

• CES
• Upside.com (CODE: VGCU7O)

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

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

Special Guests: Evan Hahn

In this episode, the JavaScript Jabber panelists discuss securing Express apps with Helmet.js with Evan Hahn. Evan is a developer at Airtable, which is a company that builds spreadsheet applications that are powerful enough that you can make applications with. He has also worked at Braintree, which does payment processing for companies. They talk about what Helmet.js is, when you would want to use it, and why it can help secure your Express apps. They also touch on when you wouldn’t want to use Helmet and the biggest thing that it saves you from in your code.

In particular, we dive pretty deep on:

• Evan intro
• JavaScript
• What is Helmet.js?
• Node and Express
• Why would you use the approach of Middleware?
• Helmet is not the only solution
• Http headers
• Current maintainer of Helmet.js
• npm
• Has added a lot to the project, but is not the original creator
• Outbound HTTP response headers
• Helmet doesn’t fully secure your app but it does help secure it
• How does using Helmet work?
• Are there instances when you wouldn’t want to use Helmet?
• No cash middleware
• Where do you set the configuration options?
• Top level Helmet module
• 12 modules
• What is the biggest thing that Helmet saves you from?
• Content security policy code
• And much, much more!

Links:

• Airtable
• Braintree
• JavaScript
• Helmet.js
• Node
• Express
• npm
• Evan’s Website
• @EvanHahn
• Evan’s GitHub

Picks:

Charles

• Camera
• Zoom H6
• Shure SM58
• DevChat.tv Youtube
• React Round Up

Evan

• Clojure
• Fortune
• Kantaro: The Sweet Tooth Salaryman

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
• AJ ONeal
• Aimee Knight
• Joe Eames

Special Guests: Jordan Eldredge

In this episode, the JavaScript Jabber panelists discuss Winamp2-js with Jordan Eldredge. Jordan is the creator of Winamp2-js and was inspired to create this media player from the old Winamp media player that he used back in the day. They talk about the importance of limitations, the value of having fun side projects, and pushing the boundaries. They also touch on skin parsing, making Webamp an electron app, and more!

In particular, we dive pretty deep on:

• What is Winamp2-js?
• The history and future of Winamp
• WACUP
• Winamp was the first big mp3 player that you could style
• Webamp’s features and the technical challenges associated with them
• Why JavaScript?
• Creative solutions
• Limitations of browser and creating something that previously existed
• The importance of limitations
• Hadn’t done very much JavaScript prior to this project
• Originally created with jQuery
• Led him into a career in JavaScript
• Pushing the boundaries
• Skin parsing
• “Bitrot” and making Winamp skins accessible again
• The value of side projects, even stupid ones
• Architecture docs
• What made you choose React and Redux?
• Spotiamp (Soptify’s canceled Winamp client)
• Making Webamp an Electron app
• Winamp visualizers being ported to the web
• The domain name webamp.org
• And much, much more!

Links:

• Winamp2-js
• Webamp
• JavaScript
• jQuery
• Architecture docs
• React
• Redux
• jordaneldredge.com
• Jordan’s GitHub
• @captbaritone

Sponsors

• Kendo UI
• FreshBooks
• Loot Crate

Picks:

Charles

• JAM XT Speaker
• Trello

AJ

• Samson GoMic
• Greenlock for Web Servers
• Greenlock for Node.js

Aimee

• KA Engineering Principles

Joe

• 2ality.com
• What if JavaScript wins? Medium post

Jordan

• JavaScript Garden
• Rust
• @winampskins

Panel:

• Charles Max Wood
• Aimee Knight
• AJ ONeal
• Joe Eames

Special Guests: Henry Zhu

In this episode, the JavaScript Jabber panel talks to Henry Zhu about Babel and open source software. Henry is one of the maintainers on Babel, which is a JavaScript compiler, and recently left this job to work on doing open source full time as well as working on Babel. They talk about where Babel is today, what it actually is, and his focus on his open source career. They also touch on how he got started in open source, his first PR, and more!

In particular, we dive pretty deep on:

• Henry intro
• Babel update
• Sebastian McKenzie was the original creator of Babel
• Has learned a lot about being a maintainer
• What is Babel?
• JavaScript compiler
• You never know who your user is
• Has much changed with Babel since Sebastian left?
• Working on open source
• How did you get started in pen source?
• The ability to learn a lot from open source
• Atrocities of globalization
• More decentralization from GitHub
• Gitea and GitLab
• Gitea installer
• Open source is more closed now
• His first PR
• JSCS
• Auto-fixing
• Prettier
• Learning more about linting
• You don’t have to have formal training to be successful
• Codefund.io
• Sustainability of open source
• And much, much more!

Links:

• Babel
• JavaScript
• Gitea
• GitLab
• Gitea installer
• Prettier
• Codefund.io
• @left_pad
• Henry’s GitHub
• henryzoo.com
• Henry’s Patreon

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:

Charles

• Orphan Black
• Crucial Accountability by Kerry Patterson

Aimee

• Desk with cubby holes for cats
• The Key to Good Luck Is an Open Mind blog post

AJ

• Gitea
• Gitea installer
• Greenlock

Joe

• Solo
• Justified

Henry

• Celeste
• Zeit Day talks

Panel:

• Aimee Knight
• Joe Eames
• AJ ONeal

Special Guests: Jeremy Fairbank

In this episode, the JavaScript Jabber panel talks to Jeremy Fairbank about his talk Practical Functional Programming. Jeremy is a remote software developer and consultant for Test Double. They talk about what Test Double is and what they do there and the 6 things he touched on in his talk, such as hard to follow code, function composition, and mutable vs immutable data. They also touch on the theory of unit testing, if functional programming is the solution, and more!

In particular, we dive pretty deep on:

• Jeremy intro
• Works for Test Double
• What he means by “remote”
• What is Test Double?
• They believe software is broken and they are there to fix it
• His talk - Practical Functional Programming
• The 6 things he talked about in his talk
• Practical aspects that any software engineer is going to deal with
• Purity and the side effects of programming in general
• Hard to follow code
• Imperative VS declarative code
• Code breaking unexpectedly
• Mutable data VS immutable data
• The idea of too much code
• Combining multiple functions together to make more complex functions
• Function composition
• Elm, Elixir, and F#
• Pipe operator
• Scary to refactor code
• Static types
• The idea of null
• The theory of unit testing
• Is functional programming the solution?
• His approach from the talk
• And much, much more!

Links:

• Test Double
• His talk - Practical Functional Programming
• Elm
• Elixir
• F#
• @elpapapollo
• jeremyfairbank.com
• Jeremy’s GitHub
• Jeremy’s YouTube

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:

Aimee

• American Dollar
• Force with lease

AJ

• Superfight

Joe

• The 2018 Web Developer Roadmap by Brandon Morelli
• Svelte

Jeremy

• Programming Elm
• The Secrets of Consulting by Gerald M. Weinberg
• Connect.Tech

Panel: Charles Max Wood

Guest: Michael Garrigan

This week on My JavaScript Story, Charles speaks with http://michaelgarrigan.com who is one of the podcast’s listeners. He is changing careers midway and has had many exciting careers in the past, such as being a professional chef, carpenter, repairman, and so on. Listen to today’s episode to hear Michael’s unique experience with programming and JavaScript.

In particular, we dive pretty deep on:

1:18 – Chuck: I started this show but interviewing guests and then opened up to listeners. Michael scheduled an interview and here we go! I find that his experience will be different than mine than others. We will be getting guests on here, but wanted this to be a well-rounded view within the community.

2:25 – Michael’s background! His experience is a mid-career change. To see the things that are intimidating and exciting.

3:16 – How did you get into programming?

3:23 – Michael: How do people talk to machines? What are the different computer languages out there? What do people prefer to use? The C programming language, I saw as the “grandfather” program. That’s the first thing I looked at. Then I was like, “what is going on?” I got a copy of the original K&R book and worked through that.

4:58 – Chuck: I did the C language in college. The Java that I was learning then was less complicated. How did you end up with JavaScript then?

5:26 – Guest: It was easy and you can just open up a console and it works. You want to see things happen visually when you program is great. It’s a great entry point. We started building things in React and how fun that is. I enjoy JavaScript in general.

6:11 – Chuck: What is your career transition?

6:18 – Guest: I have always been a craftsman and building things. I had a portion time I was a professional chef, which is the cold side like sausages and meats and cheeses, etc. I used to do a lot of ice carvings, too. Stopped that and opened a small business and repaired antique furniture for people. Wicker restoration. It was super cool because it was 100+ years old. To see what people did very well was enjoyable. Every few years I wanted to see how something worked, and that’s how I got into it. That was the gateway to something that was scary to something that made programs.

8:24 – Chuck: I was working in IT and wrote a system that managed updates across multiple servers. There is some automation I can do here, and it grew to something else. What made you switch? Were you were looking for something more lucrative?

9:01 – Michael: Main motivation I appreciate the logic behind it. I always build physical items. To build items that are non-physical is kind of different. Using logic to essentially put out a giant instruction sheet is fun.

9:52 – Chuck: At what point do you say I want to do a boot camp?

10:04 – Michael: I might to this as a career. Hobby level and going to work is definitely different. I could see myself getting up every day and going to meetings and talking about these topics and different issues. Coding day to day.

10:51 – Chuck: Who did you talk to who got you started?

10:57 – Guest: Things I read online and friends. They said get the basics behind programming. Languages come and go. Be able to learn quickly and learn the basics.

12:13 – Chuck: In NY city? It’s pricy to live there.

12:33 – Guest: Cost of living is much greater.

12:42 – Chuck: What was it like to go to a boot camp?

12:50 – Guest answers question.

14:30 – Advertisement – Get a Coder Job

15:11 – Chuck: What different projects have you worked on?

15:19 – Guest talks about his many different projects. Like senses.gov.

18:11 – Michael: Working on getting a job. I put together a portfolio and just graduated this past week.

19:38 – Charles: Anything that has been a huge challenge for you?

19:47 – Not really just one. I’ve done big projects in the past. Seeing that I can do them and sheer amount of work that I have put in. Not really too concerned. Only concern is that mid-30s any bias that is out there. I don’t think that will really affect me.

20:25 – Chuck: Yeah, it’s rally not age-bias.

20:55 – Michael: “Making your bones” is an expression in culinary school. That means that you put in the hours in the beginning to become a professional at it. So I have had transitioned several times and each time I had to make my bones and put in the time, so I am not looking forward to that for me right now, but...

21:43 – Chuck: Anything else?

21:51 – Guest: Meetups.

22:40 – Chuck: I have been putting time into making this book.

22:53 – Guest puts in his last comments.

24:00 – Chuck: Thinking about what I want DevChat TV to be. I have been thinking and writing the mission statement for DevChat TV.

25:14 – Chuck: It’s a big deal to get out of debt. My wife and I will be at the end of the year.

25:37 – Guest: Discipline not to spend money, and peer pressure.

25:48 – Picks!

25:57 – Advertisement for Digital Ocean!

Links:

• Book
• Dave Ramsey: Introducing Our Brand-New Book!
• Hack Reactor
• JavaScript
• Meetup
• Michaelgarrigan.com – website

Sponsors:

• Code Badge
• Digital Ocean
• Cache Fly
• Get A Coder Job

Picks:

Charles

• TNT – The Last Ship
• Board game – Pandemic Legacy
• Kickstarter – Code Badges

Michael Garrigan

• Brad’s YouTube channel - ½ million subscribers
• Michaelgarrigan.com – website

Panel: Charles Max Wood

Guest: Ely Lucas

This week on My JavaScirpt Story, Charles speaks with Ely Lucas who is a software developer. He loves technologies and mobile technologies among other things. Let’s listen to today’s episode where Chuck and Ely talk about Ionic, Angular, React and many other topics! Check it out!

In particular, we dive pretty deep on:

1:33 – Hello!

1:40 Chuck: Give us a background on who you are, and tell us how famous you are!

2:31 – Chuck: What do you do with Ionic?

2:40 – Ely answers the question.

3:51 – Chuck: How did you get into your field?

3:55 – Ely: When I was a kid and played with video games. Later on I got into web development, like my website. Then I got into a professional-level of developing.

Ely goes into detail about how his passion for developing began and developed.

6:30 – Chuck: Yeah, I’ve talked with people who have gotten into video games, then got into software development.

7:01 – Ely: Someday I would like to develop games.

7:12 – Chuck: Yes, web developing is awesome.

Chuck asks Ely another question.

7:25 – Ely answers the question and mentions web controls.

9:17 – Ely: I thought Ajax was easier.

9:38 – Chuck: When I got into web development jQuery was sort of new. It made things a lot easier.

9:58 – Ely: A lot of people like to sneer at jQuery now, but back in the day it was IT.

10:28 – Chuck: How did you get into Ionic?

10:43 – Ely: I got a fulltime gig working on Ionic; I like the framework. I saw a job application and sent in my résumé. Two days later I got a callback and was amazed. They were hiring remotely. The team liked me and started over a year ago.

11:46 – Chuck asks a question.

11:54 – Ely answers the question.

13:20 – Chuck: Why Ionic?

13:35 – Ely: It was based off of Angular.

15:17 – Chuck: You mentioned...what has the transition been like?

15:32 – Ely talks about past programs he has worked with. He taught React in the early React days.

16:37 – Ely: I have a deep appreciation on React now.

17:09 – Chuck: I like seeing the process that people go through.

17:24 – Ely continues the conversation.

Ely: It is interesting to see the learning process that people go through to arrive in the same place.

18:18 – Chuck: Redux is a good example of this. Anyway, this is near the end of our time.

18:39 – Chuck: Anything else you want to talk about?

18:48 – Ely: Yes, I have been involved in the Denver community. Check us out.

Links:

• Ionic
• jQuery
• JavaScript
• React
• Ely Lucas’ Twitter
• Ely Lucas’ LinkedIn
• Ely Lucas
• Ely Lucas’ GitHub

Sponsors:

• Get A Coder Job
• Code Badges
• Digital Ocean

Picks:

Charles

• Audible
• Book: Seven Proven Principles...
• Tony Robbins’ Book: Unshakeable

Ely

• Fantasy Novel: Shadow of what was lost.
• Ionic

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:

• Aimee Knight
• AJ O’Neal
• Aaron Frost
• Christopher Ferdinandi

Special Guests: Christopher Buecheler

In this episode, the panel talks with Christopher Buecheler who is an author, blogger, web developer, and founder of CloseBrace. The panel and Christopher talk about stepping outside of your comfort zone. With a technological world that is ever changing, it is important to always be learning within your field. Check out today’s episode to learn more!

Show Topics:

0:00 – Advertisement: KENDO UI

1:08 – Aimee: Our guest is Christopher Buecheler – tell us about yourself and what you do.

1:22 – Guest: I run a site and help mid-career developers. I put out a weekly newsletter, too.

2:01 – Aimee: It says that you are a fan of “getting comfortable being uncomfortable”?

2:15 – Guest: I am a self-taught developer, so that means I am scrambling to learn new things all the time. You are often faced with learning new things. When I learned React I was dumped into it. The pain and the difficulty are necessary in order to improve. If you aren’t having that experience then you aren’t learning as much as you could be.

3:26 – Aimee: I borrow lessons that I learned from ice-skating to programming.

3:49 – Guest: I started running a few years ago for better health. It was exhausting and miserable at the start and wondered why I was doing it. Now I run 5 times a week, and there is always a level of being uncomfortable, but now it’s apart of the run. It’s an interesting comparison to coding. It’s this idea of pushing through.

5:01 – Aimee: If you are comfortable you probably aren’t growing that much. In our industry you always have to be learning because things change so much!

5:25 – Guest: Yes, exactly. If you are not careful you can miss opportunities.

6:33 – Panel: You have some ideas about frameworks and libraries – one thing that I am always anxious about is being able to make sense of “what are some new trends that I should pay attention to?” I remember interviewing with someone saying: this mobile thing is just a fad. I remember thinking that she is going to miss this opportunity. I am worried that I am going to be THAT guy. How do you figure out what sort of things you should / shouldn’t pay attention to?

7:47 – Guest: It is a super exhausting thing to keep up with – I agree. For me, a lot of what I pay attention to is the technology that has the backing of a multi-million dollar company then that shows that technology isn’t going anywhere, anytime soon. The other thing I would look at is how ACTIVE is the community around it?

9:15 – Panel: Is there a strategic way to approach this? There is so many different directions that you can grow and push yourself within your career? Do you have any kinds of thoughts/tips on how you want your career to evolve?

10:00 – Guest: I am trying to always communicate better to my newsletter audience. Also, a good approach, too, is what are people hiring for? 

11:06 – Aimee: Again, I would say: focus on learning.

11:30 – Panel: And I agree with Aimee – “learn it and learn it well!”

12:01 – Panel: I want to ask Chris – what is CloseBrace?

12:17 – Guest: I founded it in November 2016, and started work on it back in 2013.

14:20 – Panel: It was filled with a bunch of buzz worthy words/title.

14:32 – Guest continues his thoughts/comments on CloseBrace.

16:54 – Panel: How is the growth going?

17:00 – Guest: It is growing very well. I put out a massive, massive tutorial course – I wouldn’t necessarily advice that people do this b/c it can be overwhelming. However, growth this year I have focused on marketing. I haven’t shared numbers or anything but it’s increased 500%, and I am happy about it.

18:05 – Panel: Are you keeping in-house?

18:13 – Guest: I think it would be cool to expand, but now it is in-house. I don’t want to borrow Egg Head’s setup. I would love to cover MORE topics, though.

19:05 – Panel: You are only one person.

19:08 – Guest: If I can get the site creating more revenue than I can hire someone to do video editing, etc.

19:35 – Panel: I think you are overthinking it.

19:45 – Guest.

19:47 – Advertisement – Sentry.io

20:47 – Guest.

21:30 – Aimee: There are SO many resources out there right now. Where do you think you fit into this landscape?

21:44 – The landscape is cluttered, but I feel that I am different b/c of my thoroughness. I don’t always explain line by line, but I do say how and why things work. I think also is my VOICE. Not my radio voice, but the tone and the approach you take with it.

23:25 – Panel: I was trying to copy folks in the beginning of my career. And at some point I realized that I needed to find my own style. It always came down to the reasons WHY I am different rather than the similarities. Like, Chris, you have these quick hits on CloseBrace, but some people might feel like they don’t have the time to get through ALL of your content, because it’s a lot. For me, that’s what I love about your content.

24:46 – Christopher: Yeah, it was intentional.

25:36 – Panel: Good for you.

25:49 – Guest: I am super device agnostic: Android, Mac, PC, etc. I have a lot of people from India that are more Microsoft-base.

26:28 – Aimee: I think Egghead is pretty good about this...do you cover testing at all with these things that you are doing? It’s good to do a “Hello World” but most of these sites don’t get into MORE complex pieces. I think that’s where you can get into trouble. It’s nice to have some boiler point testing, too.

27:18 – Guest answers Aimee’s question.

28:43 – Aimee: We work with a consultancy and I asked them to write tests for the things that we work with. That’s the value of the testing. It’s the code that comes out.

29:10 – Panel: Can you explain this to me. Why do I need to write tests? It’s always working (my code) so why do I have to write a test?

29:39 – Guest: When working with AWS I was writing...

31:01 – Aimee: My biggest thing is that I have seen enough that the people don’t value testing are in a very bad place, and the people that value testing are in a good place. It even comes back to the customers, because the code gets so hard that you end up repeatedly releasing bugs. Customers will stop paying their bills if this happens too often for them.

33:00 – Panel: Aimee / Chris do you have a preferred tool? I have done testing before, but not as much as I should be doing.

33:25 – Aimee: I like JEST and PUPPETEER.

33:58 – Guest: I like JEST, too.

34:20 – Aimee: Let’s go to PICKS!

34:35 – Advertisement – eBook: Get a coder job!

Links:

• JavaScript
• jQuery
• React
• Elixir
• Elm
• Vue
• JEST
• Puppeteer
• Podflix
• Autojump
• Brutalist Web Design
• YouTube: Mac Miller
• Balloon Fiesta
• DocZ
• CloseBrace
• Christopher Buecheler’s Website
• Christopher Buecheler’s LinkedIn
• Christopher Buecheler’s GitHub
• Go Learn Things – Chris Ferdinandi

Sponsors:

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

Picks:

Aimee

• Podflix

Chris F.

• AutoJump 
• Brutalist Web Design
• Mac Miller Tiny Desk Concert

AJ

• Canada Dry with Lemonade

Aaron

• ABQ Ballon Festival
• Joe Eames DND Recording Channel

Christopher

• Docz
• South Reach Trilogy
• Jeff Vandermeer

Panel:

• AJ O’Neal
• Joe Eames
• Jesse Sanders

Special Guest: Sean Hunter

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

Show Topics:

0:00 – Advertisement: KENDO UI

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

1:45 – Guest talks about Vegemite!

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

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

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

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

4:30 – Guest goes into detail about Aurelia.

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

6:42 – Guest: Yes that is correct.

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

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

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

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

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

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

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

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

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

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

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

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

20:02 – Panel: Your book?

20:10 – Guest: Yep.

20:13 – Panel.

20:20 – Guest. 

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

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

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

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

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

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

26:36 – Advertisement – Sentry.io

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

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

28:40 – Panel.

28:45 – Panel.

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

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

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

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

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

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

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

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

33:39 – Guest answers the question.

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

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

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

What are your thoughts of having multiple SPAs?

37:17 – Guest.

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

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

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

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

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

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

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

43:05 – Panel.

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

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

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

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

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

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

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

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

47:35 – Guest answers question.

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

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

50:45 – Guest mentions that Aurelia website!

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

51:17 – Picks!

51:20 – Advertisement: Get A Coder Job!

END – Advertisement: CacheFly!

Links:

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

Sponsors:

• Kendo UI
• Sentry
• CacheFly

Picks:

Joe

• React Conf.
• Endless Quest

AJ

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

Jesse Sanders

• The Miracle Morning
• React Hooks
• Apple Products

Sean

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

Panel:

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

Special Guest: Andy Bell

In this episode, the panel talks with Andy Bell who is an independent designer and developer who uses React, Vue, and Node. Today, the panelists and the guest talk about the power of progressive enhancements. Check it out!

Show Topics:

0:00 – Advertisement: KENDO UI

0:34 – Chuck: Hi! Our panel is AJ, Aimee, Chris, myself and my new show is coming out in a few weeks, which is called the DevRev! It helps you with developer’s freedom! I am super excited. Our guest is Andy Bell. Introduce yourself, please.

2:00 – Guest: I am an independent designer and developer out in the U.K.

2:17 – Chuck: You wrote things about Vanilla.js. I am foreshadowing a few things and let’s talk about the power and progressive enhancement.

2:43 – The guest gives us definitions of power and progressive enhancements. He describes how it works.

3:10 – Chuck: I’ve heard that people would turn off JavaScript b/c it was security concern and then your progressive enhancement would make it work w/o JavaScript. I am sure there’s more than that?

3:28 – The guest talks about JavaScript, dependencies, among other things.

4:40 – Chuck: Your post did make that very clear I think. I am thinking I don’t even know where to start with this. Are people using the 6^th version? How far back or what are we talking about here?

5:09 – Guest: You can go really far back and make it work w/o CSS.

5:49 – Chris: I am a big advocate of progressive enhancement – the pushback I get these days is that there is a divide; between the broadband era and AOL dialup. Are there compelling reasons why progressive enhancements even matter?

6:48 – Guest.

8:05 – Panel: My family lives out in the boonies. I am aware of 50% of American don’t have fast Internet. People don’t have access to fast browsers but I don’t think they are key metric users.

8:47 – Guest: It totally depends on what you need it for. It doesn’t matter if these people are paying or not.

9:31 – Chris: Assuming I have a commute on the trail and it goes through a spotty section. In a scenario that it’s dependent on the JS...are we talking about 2 different things here?

10:14 – Panelist chimes-in.

10:36 – Chris: I can take advantage of it even if I cannot afford a new machine.

10:55 – Panel: Where would this really matter to you?

11:05 – Chris: I do have a nice new laptop.

11:12 – Chuck: I had to hike up to the hill (near the house) to make a call and the connection was really poor (in OK). It’s not the norm but it can happen.

11:37 – Chris: Or how about the All Trails app when I am on the trail.

11:52 – Guest.

12:40 – Chris: I can remember at the time that the desktop sites it was popular to have...

Chris: Most of those sites were inaccessible to me.

13:17 – Guest.

13:51 – Chuck: First-world countries will have a good connection and it’s not a big deal. If you are thinking though about your customers and where they live? Is that fair? I am thinking that my customers need to be able to access the podcast – what would you suggest? What are the things that you’d make sure is accessible to them.

14:31 – Guest: I like to pick on the minimum viable experience? I think to read the transcript is important than the audio (MP3).

15:47 – Chuck.

15:52 – Guest: It’s a lot easier with Vue b/c you don’t’ have to set aside rendering.

17:13 – AJ: I am thinking: that there is a way to start developing progressively and probably cheaper and easier to the person who is developing. If it saves us a buck and helps then we take action.

17:49 – Guest: It’s much easier if you start that way and if you enhance the feature itself.

18:38 – AJ: Let me ask: what are the situations where I wouldn’t / shouldn’t worry about progressive enhancements?

18:57 – Guest answers the question.

19:42 – AJ: I want people to feel motivated in a place WHERE to start. Something like a blog needs Java for comments.

Hamburger menu is mentioned, too.

20:20 – Guest.

21:05 – Chris: Can we talk about code?

21:16 – Aimee: This is the direction I wanted to go. What do you mean by that – building your applications progressively?

Aimee refers to his blog.

21:44 – Guest.

22:13 – Chuck: I use stock overflow!

22:20 – Guest.

22:24 – Chuck: I mean that’s what Chris uses!

22:33 – Guest (continues).

23:42 – Aimee.

23:54 – Chris.

24:09 – Chris

24:16 – Chris: Andy what do you think about that?

24:22 – Guest: Yes, that’s good.

24:35 – Chris: Where it falls apart is the resistance to progressive enhancements that it means that your approach has to be boring?

25:03 – Guest answers the question.

The guest mentions modern CSS and modern JavaScript are mentioned along with tooling.

25:50 – Chuck: My issue is that when we talk about this (progressive enhancement) lowest common denominator and some user at some level (slow network) and then they can access it. Then the next level (better access) can access it. I start at the bottom and then go up. Then when they say progressive enhancement I get lost. Should I scrap it and then start over or what?

26:57 – Guest: If it’s feasible do it and then set a timeline up.

27:42 – Chuck: You are saying yes do it a layer at a time – but my question is HOW? What parts can I pair back? Are there guidelines to say: do this first and then how to test?

28:18 – Advertisement – Sentry.io

29:20 – Guest: Think about the user flow. What does the user want to do at THIS point? Do you need to work out the actual dependencies?

30:31 – Chuck: Is there a list of those capabilities somewhere? So these users can use it this way and these users can use it that way?

30:50 – Guest answers the question.

31:03 – Guest: You can pick out the big things.

31:30 – Chuck: I am using this feature in the browser...

31:41 – Guest.

31:46 – Chris: I think this differently than you Andy – I’ve stopped caring if a browser supports something new. I am fine using CSS grid and if your browser doesn’t support it then I don’t have a problem with that. I get hung up on, though if this fails can they still get the content? If they have no access to these – what should they be able to do?

Note: “Cutting the Mustard Test” is mentioned.

33:37 – Guest.

33:44 – Chuck: Knowing your users and if it becomes a problem then I will figure it out.

34:00 – Chris: I couldn’t spare the time to make it happen right now b/c I am a one-man shop.

34:20 – Chuck and Chris go back-and-forth.

34:36 –Chris: Check out links below for my product.

34:54 – AJ: A lot of these things are in the name: progressive.

36:20 – Guest.

38:51 – Chris: Say that they haven’t looked at it all before. Do you mind talking about these things and what the heck is a web component?

39:14 – The guest gives us his definition of what a web component is.

40:02 – Chuck: Most recent episode in Angular about web components, but that was a few years ago. See links below for that episode.

40:25 – Aimee.

40:31 – Guest: Yes, it’s a lot like working in Vue and web components. The concepts are very similar.

41:22 – Chris: Can someone please give us an example? A literal slideshow example?

41:45 – Guest answers the question.

45:07 – Chris.

45:12 – Guest: It’s a framework that just happens to use web components and stuff to help.

45:54 – Chuck: Yeah they make it easier (Palmer). Yeah there is a crossover with Palmer team and other teams. I can say that b/c I have talked with people from both teams. Anything else?

46:39 – Chuck: Where do they go to learn more?

46:49 – Guest: Check out the Club! And my Twitter! (See links below.)

47:33 – Chuck: I want to shout-out about DevLifts that has $19 a month to help you with physical goals. Or you can get the premium slot! It’s terrific stuff. Sign-up with DEVCHAT code but there is a limited number of slots and there is a deadline, too. Just try it! They have a podcast, too!

49:16 – Aimee: Yeah, I’m on their podcast soon!

49:30 – Chuck: Picks!

END – Advertisement: CacheFly!

Links:

• JavaScript
• React
• Elixir
• Ember.js
• Vue
• GO
• jQuery
• Node.js
• Puppeteer
• Cypress
• Past episode: AiA 115
• Past episode: JSJ 120
• Vue.js – Slots
• Using templates and slots – Article
• Web Components Club
• GitHub: Pwa – Starter – Kit
• Progressively Enhanced Toggle Panel
• Time Ago in under 50 lines of JavaScript
• GitHub: ebook-boilerplate
• Chris Ferdinandi’s Go Make Things Site
• Game Chops
• CNBC – Trump Article
• New in Node v10.12
• Quotes Archive
• My Amazon Interview Horror Story
• DevPal.io
• Honest Work
• Relative Paths
• DevLifts
• Andy Bell’s Twitter
• Andy’s Website

Sponsors:

• DevLifts
• Kendo UI
• Sentry
• CacheFly

Picks:

Aimee

• Hacker News  -  Programming Quotes
• My Amazon Interview Horror Story

Chris

• Time Ago in Under 50 Lines of JavaScript
• E-Book Boiler Plate
• JSJABBER at gomakethings.com

AJ

• Experimental Drugs Bill
• My Browers FYI
• New In Node,10.12
• Arcade Attack

Charles

• Getacoderjob.com
• Self-Publishing School
• MF CEO podcast

Andy

• Devpay.io
• Honest.work
• Relativepath.uk

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

• KendoUI

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

• Clubhouse

Panel

• AJ O’Neal

• Aimee Knight

• Joe Eames

• Charles Max Wood

Special Guest: James Shore

Episode Summary

James Shore is a developer who specializing in extreme programming, an Agile method. He also used to host a screencast called Let’s Code Test-Driven JavaScript. They begin by discussing the core of Agile development, which James believes is being responsive to customers and business partners in a way that’s sustainable and humane for the programmers involved. It prioritizes individuals and interactions over processes and tools. More can be found in The Agile Manifesto.

James delves into the historical context of the immersion of Agile and how things have changed from the 90’s. Now, the name Agile is everywhere, but the ideals of agile are not as common. There is a tendency to either take Agile buzzwords and apply them to the way it was done long ago, or it’s absolute chaos. James talks about ways to implement Agile in the workplace. He believes that the best way to learn Agile is work with someone who knows Agile, or read a book on it and then apply it. James recommends his book The Art of Agile Development: Pragmatic Guide to Agile Software Development for people who want to started with Agile development. The panelists talk about where people often get stuck with implementing Agile. The hosts talk about their own processes in their company.

They discuss how people involved in the early days of Agile are disappointed in how commercial it has become.They agree that what’s really the most important is the results. If you can respond to a request to change direction in less than two weeks and you don’t have to spend months and months preparing something, and you do that in a way where the people on the team feel like their contributing, then you’re doing Agile. James thinks that the true genius of Agile is in the way the actual work is done rather than in the way your organize the work.

Links

• Agile

• Scrum

• Waterfall

• Feature Driven Development

• Extreme Programming (XP)

• Jira

• Bamboo

• Confluence

• Atlassian stack

• Cowboy

• Mock objects

• Grows Method by Andy Hunt

Picks

AJ O’Neal:

• Origin by Dan Brown

• Searching

Aimee Knight:

• Hacker News Interview Questions Thread.

Joe Eames:

• The Ballad of Buster Scruggs on Netflix

Charles Max Wood:

• Getting up early

• John Sonmez Kanbanflow video

• Drip

James Shore:

• Lost in Space on Netflix

• Star Citizen PC game

• Jame’s Agile book online

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

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

Panel

• Joe Eames
• Aimee Knight

Joined by special guest: Richard Feldman

Episode Summary

In this episode of JavaScript Jabber, Richard Feldman, primarily known for his work in Elm, the author of “Elm in Action” and Head of Technology at NoRedInk, talks about Elm 0.19 and the new features introduced in it. He explains how the development work is distributed between the Elm creator – Evan Czaplicki and the other members of the community and discusses the challenges on the way to Elm 1.0.

Richard also shares some educational materials for listeners interested in learning Elm and gives details on Elm conferences around the world touching on the topic of having diversity among the speakers. He finally discusses some exciting things about Elm which would encourage developers to work with it.

Links

• Elm in Action
• Frontend Masters – Introduction to Elm
• Frontend Masters – Advanced Elm
• Small Assets without the Headache
• Elm Guide
• ElmBridge San Francisco
• Renee Balmert

Picks

Aimee Knight:

• Most lives are lived by default

Joe Eames:

• Thinkster

Richard Feldman:

• Framework Summit 2018 – Keynote speech
• Nix Package Manager
• A Philosophy of Software Design

Sponsors

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

Host: Charles Max Wood

Special Guest:  Charles Lowell

Episode Summary

In this episode of My Ruby Story, Charles hosts Charles Lowell, founder and  developer at The Frontside Software based in Austin, TX.

Listen to Charles on the podcast JavaScript Jabber on this episode.

Links

• JavaScript Jabber 337: Microstates.js – Composable State Primitives for JavaScript with Charles Lowell & Taras Mankovski
• Charles Lowell’s Twitter
• Charles Lowell’s GitHub
• Charles Lowell’s Frontside Bio
• https://devchat.tv/my-javascript-story/
• https://www.facebook.com/DevChattv

Picks

Charles Lowell:

• Yousician App

Charles Max Wood:

• Parade of Homes - St. George, Utah
• Vrbo.com

Sponsors

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

Panel

• Chris Ferdinandi
• Aimee Knight
• Aaron Frost
• AJ O’Neal

Joined by special guest: Keith Cirkel

Episode Summary

In this episode of JavaScript Jabber, Keith Cirkel, Senior Application Engineer at GitHub, briefly explains the projects he is working with and moves on to the recent changes done by GitHub to their website, including the decision to remove jQuery, and not choosing a popular framework such as React or Vue. He talks about some problems in using Internet Explorer 11, how these GitHub changes can help with certain browser compatibility issues, and a few challenges the team had to face during the redesigning process.

The panelists then discuss event delegation, performance considerations, Polyfill.io and web components. Keith gives some insight into accessibility and they talk about related user concerns.

Links

• Keith’s website
• Keith’s GitHub
• Keith’s Twitter
• GitHub Engineering blog
• Financial Times – Polyfill service
• Include fragment - element

Picks

Aaron Frost:

• Bag Man
• What It’s Like to Be A Woman on the Internet

Aimee Knight:

• Smooth Sailing with Kubernetes

Joe Eames:

• GitHub Free users get free unlimited private repositories
• Swig
• Things I don’t know as of 2018

AJ O’Neal:

• Isopropyl alcohol
• Bang good electronics
• Soldering Iron – Hakko, X-Tronic

Keith Cirkel:

• GitHub careers
• Heston’s Pod & Chips
• Brexit

Chris Ferdinandi:

• 52 things I learned in 2018
• Learn Vanilla JS

Sponsors

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

Host: Charles Max Wood

Guest: Christopher Buecheler

Episode Summary

In this episode of My JavaScript Story, Charles hosts Christopher Buecheler, novelist, web developer and founder of CloseBrace, a JavaScript tutorial and resource site.

Christopher is a self-taught full-stack web developer with extensive experience in programming with JavaScript, jQuery, React.js, Angular.js, and much more. Listen to Christopher on the  JavaScript Jabber podcast.

Christopher started CloseBrace because he really enjoys helping people and giving back to the community. In his spare time, he writes science fiction novels and is also working on a web application for knitting called Stitchly with a friend.

Links

• https://devchat.tv/js-jabber/jsj-338-its-supposed-to-hurt-get-outside-of-your-comfort-zone-to-master-your-craft-with-christopher-buecheler/
• CloseBrace
• React.js
• https://twitter.com/closebracejs
• Christopher Buecheler’s Twitter
• Christopher Buecheler’s Website
• Christopher Buecheler’s LinkedIn
• Christopher Buecheler’s GitHub
• https://closebrace.com/categories/five-minute-react
• contact@closebrace.com
• http://stitchly.io/
• Christopher Buecheler's Amazon link
• Elixir by Christopher Buecheler
• https://devchat.tv/my-javascript-story/
• https://www.facebook.com/DevChattv
• https://www.facebook.com/javascriptjabber
• https://devchat.tv/my-javascript-story/

Picks

Christopher Buecheler:

• Bracket Pair Colorizer
• Highlight Matching Tag
• https://gitlens.amod.io/
• Fifth Season by N. K. Jemisin

Charles Max Wood:

• Language Server Extension Guide
• RRU 015: Visual Studio Code with Rachel MacFarlane and Matt Bierner LIVE at Microsoft Build
• VoV 015: Visual Studio Code with Rachel MacFarlane and Matt Bierner LIVE at Microsoft Build

Sponsors

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

Panel

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

Joined by special guests: Hillel Wayne and Richard Feldman

Episode Summary

In this episode of JavaScript Jabber, Hillel Wayne kicks off the podcast by giving a short background about his work, explains the concepts of formal methods and the popular npm package - event-stream, in brief. The panelists then dive into the recent event-stream attack and discuss it at length, focusing on different package managers and their vulnerabilities, as well as the security issues associated with them. They debate on whether paying open source developers for their work, thereby leading to an increase in contribution, would eventually help in improving security or not. They finally talk about what can be done to fix certain dependencies and susceptibilities to prevent further attacks and if there are any solutions that can make things both convenient and secure for users.

Links

• STAMP model in accident investigation
• Hillel’s Twitter
• Hillel’s website
• Richard’s Twitter
• Stamping on Event-Stream

Picks

Joe Eames:

• Stuffed Fables

Aimee Knight:

• SRE book - Google
• Lululemon leggings
• DVSR - Band

Aaron Frost:

• JSConf US

Chris Ferdinandi:

• Paws New England
• Vanilla JS Guides

Charles Max Wood:

• Sony Noise Cancelling Headphones
• KSL Classifieds
• Upwork

Richard Feldman:

• Elm in Action
• Sentinels of the Multiverse

Hillel Wayne:

• Elm in the Spring
• Practical TLA+
• Nina Chicago - Knitting
• Tomb Trader

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

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

Panel

• AJ O’Neal

Joined by special guest: Sam Selikoff

Episode Summary

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

Links

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

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

Picks

AJ O’Neal:

• Good Mythical Morning - YouTube

Sam Selikoff:

• The Man In the High Castle  
• Tailwind CSS

Sponsors

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

Panel

• Charles Max Wood

• AJ O’Neal

• Joe Eames

• Aimee Knight

With Special Guest: Evan Weaver

Episode Summary

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

Links

• FaunaDB

• GraphQL

• Netlify

• AWS Lambda

• Apollo.io

• SQL

• Jamstack 

• Akkeris

• Graphile

Follow DevChat on Facebook and Twitter

Picks

Charles Max Wood:

• Captain Sonar

• Canny

• JSJ Reccomendations

Aimee Knight:

• Falling in Reverse

Joe Eames:

• Battlestations

Evan Weaver

• Forza Motorsport

• Follow Evan on Twitter and Github @evan