JavaScript Jabber

Panel:

• Charles Max Wood
• Joe Eames

Special Guests: AJ O'NealIn this episode, the JavaScript Jabber panel talks to AJ O'Neal about Greenlock and LetsEncrypt. LetsEncrypt is a brand name and is the first of its kind in automated SSL and Greenlock does what Certbot does in a more simplified form. They talk about what led him to create Greenlock, compare Greenlock to Certbot, and what it’s like to use Greenlock. They also touch on Greenlock-express, how they make Greenlock better, and more!In particular, we dive pretty deep on:

• Greenlock and LetsEncrypt overview
• LetsEncrypt is free to get your certificate
• Why Charles uses LetsEncrypt
• Wildcard domains
• Certbot
• Why he originally created Greenlock
• Working towards home servers
• Wanted to get HTTP on small devices
• Manages a certificate directory
• Greenlock VS Certbot
• Greenlock can work stand alone
• The best use case for Greenlock
• Excited about how people are using his tool
• What is it like to use Greenlock?
• Working on a desktop client
• Greenlock-express
• Acme servers
• CAA record
• Making Greenlock better by knowing how people are using it
• Using Greenlock-express
• Let's Encrypt v2 Step by Step by AJ
• And much, much more!

Links:

• LetsEncrypt
• Greenlock
• Certbot
• Greenlock-express
• Acme servers
• Let's Encrypt v2 Step by Step by AJ
• @coolaj86
• coolaj86.com
• AJ’s Git
• Greenlock.js Screencast Series
• Greenlock.js Patreon

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:Charles

• Take some time off

AJ

• OverClocked Records

Support this podcast at — https://redcircle.com/javascript-jabber/donations

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: 

• Joe Eames
• Aimee Knight
• AJ ONeal

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

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

Links:

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

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:Joe

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

Aimee

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

AJ

• James Veitch

Tom

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

Support this podcast at — https://redcircle.com/javascript-jabber/donations

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: 

• Aimee Knight
• Joe Eames
• AJ ONeal

Special Guests: Jeremy FairbankIn 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

Support this podcast at — https://redcircle.com/javascript-jabber/donations

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: 

• Charles Max Wood
• Joe Eames
• Aimee Knight

Special Guests: Kent BeckIn this episode, the JavaScript Jabber panel talks to Kent Beck. Kent left Facebook 4 months ago after working for them for 7 years and is now self-unemployed so that he can decompress from the stressful environment that he was a part of for so long. He now travels, writes, creates art, thinks up crazy programming ideas, and is taking a breather.  They talk about what he did at Facebook, what his coaching engagement sessions consisted of, and the importance of taking time for yourself sometimes. They also touch on what he has learned from his experience coaching, how to create a healthy environment within the workplace, and more!In particular, we dive pretty deep on:

• Kent intro/update
• Ruby Rogues Episode 23
• Worked at Facebook for 7 years
• What were you doing at Facebook?
• Unique culture at Facebook
• His strengths as a developer didn’t match with the organization’s
• Coaching developers
• TDD and Patterns
• Advantages as an old engineer
• What did coaching engagement consist of?
• Takes time to build trust
• Discharging shame
• Need permission to take care of what you need to
• Being at your best so you can do your best work
• Vacation in place
• What have you learned in your time working with people?
• The nice thing about coaching
• Everyone is different
• How do we create a healthy environment within the workplace?
• Mentor in Ward Cunningham
• What is it costing us?
• Why did you decide to leave?
• And much, much more!

Links:

• Ruby Rogues Episode 23
• @KentBeck
• kentbeck.com
• Kent’s GitHub

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:Charles

• The Five Dysfunctions of a Team by Patrick Lencioni
• Crucial Accountability by Kerry Patterson

Aimee

• n-back

Joe

• Test Driven Development: By Example by Kent Beck

Kent

• The Field Guide to Understanding 'Human Error' by Sidney Dekker
• Conspiracy: Peter Thiel, Hulk Hogan, Gawker, and the Anatomy of Intrigue by Ryan Holiday

Support this podcast at — https://redcircle.com/javascript-jabber/donations

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: 

• Charles Max Wood
• AJ ONeal

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

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

Links:

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

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:Charles

• GitLab

AJ

• Gitea
• Black Panther

Kurt

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

Support this podcast at — https://redcircle.com/javascript-jabber/donations

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

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

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

Links:

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

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:Charles

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

Vesa

• Armada by Ernest Cline

Support this podcast at — https://redcircle.com/javascript-jabber/donations

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: 

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

Special Guests: Henry ZhuIn 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

Support this podcast at — https://redcircle.com/javascript-jabber/donations

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: 

• Charles Max Wood
• Alyssa Nicholl
• Ward Bell

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

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

Links:

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

Sponsors

• Kendo UI
• FreshBooks
• Loot Crate

Picks:Charles

• Socks as Swag

David

• VS Code
• Kubernetes

Support this podcast at — https://redcircle.com/javascript-jabber/donations

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: 

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

Special Guests: Jordan EldredgeIn 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

Support this podcast at — https://redcircle.com/javascript-jabber/donations

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Panel: 

• Charles Max Wood

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

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

Links:

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

Sponsors

• Kendo UI
• Linode
• FreshBooks

Picks:Charles

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

Ori

• Fitbit
• Pacific Northwest Hiking

Gopinath

• Seattle, WA

Support this podcast at — https://redcircle.com/javascript-jabber/donations

Privacy & Opt-Out: https://redcircle.com/privacy

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.