MJS 097: Charles Lowell

By devchat.tv
Published On :: Wed, 06 Mar 2019 05:00:00 -0500

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.

Picks

Charles Lowell:

Yousician App

Charles Max Wood:

Full Article

MJS 098: Vitali Zaidman

By devchat.tv
Published On :: Wed, 13 Mar 2019 06:00:00 -0400

Sponsors

Sentry use the code “devchat” for 2 months free on Sentry small plan
Triplebyte offers a $1000 signing bonus
Clubhouse
CacheFly

Host: Charles Max Wood

Guest: Vitali Zaidman

Episode Summary

In this episode of My JavaScript Story, Charles hosts Vitali Zaidman, Technical Lead at WellDone Software Solutions. He is also the author of the popular blog piece: “An Overview of JavaScript Testing in 2019”.

Vitali has been writing code since he was 13 years old. After completing his military service, he attended The Open University of Israel where he took computer science courses. He picked JavaScript not knowing that it was going to be so popular.

He has been working for WellDone Software Solutions since he was a student where he has had the chance to work in many different projects. Vitali feels in order to keep up with technology it is important to work in different projects.

Vitali talks about projects he has worked on that he is proud of, one of which is his library at https://github.com/welldone-software/why-did-you-render

Picks

Vitali Zaidman:

Charles Max Wood:

Full Article

JSJ 356: Build Websites Like It's 2005 with Keith Cirkel

By devchat.tv
Published On :: Tue, 19 Mar 2019 06:00:00 -0400

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.

Picks

Aaron Frost:

Aimee Knight:

Smooth Sailing with Kubernetes

Joe Eames:

AJ O’Neal:

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

Keith Cirkel:

Chris Ferdinandi:

Full Article

MJS 099: Christopher Buecheler

By devchat.tv
Published On :: Wed, 20 Mar 2019 06:00:00 -0400

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

Picks

Christopher Buecheler:

Charles Max Wood:

Full Article

JSJ 359: Productivity with Mani Vaya

By devchat.tv
Published On :: Tue, 09 Apr 2019 06:00:00 -0400

Get Mani's 2x Productivity Course

Sponsors

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

Panel

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

Joined by special guest: Mani Vaya

Episode Summary

Mani is the founder of a book summary business called www.2000books.com

At 2000 Books, Mani studies the world’s greatest business and personal development books.

Then he takes the most important ideas from each book and presents them in tight, 9- to 15-minute video summaries.

You get the 4-7 most important ideas in a condensed format that's easy to absorb, easy to review, and easy to put into action immediately.

To help people with productivity, Mani created an awesome course called “10x Productivity"

His “10x Productivity" video course contains summaries of the 50 greatest books ever written on time management, productivity, goal setting, systems, execution, strategy and leverage.

"10x Productivity" pack includes summaries of all the NY Times Best Sellers on Productivity & Time Management, such as:

The 7 Habits of Highly Effective People by Stephen Covey
Getting Things Done by David Allen
Deep Work by Cal Newport
The Power of Habit by Charles Duhigg
The One Thing by Gary Keller
Essentialism by Greg McKeown

All together, this collection includes more than 250 strategies, tips, tools & techniques for:

- Becoming more productive

- Getting results rather than being busy, stressed out & frustrated

- Time Management

- Defeating procrastination

- Achieving big goals

- Hacking your brain for high performance

- Identifying the highest leverage points that lead to much faster results

- Creating powerful habits

- Installing execution systems that make goal achievement inevitable

10x Productivity Package contains:

Summaries of the 50 greatest books ever written on Productivity & Time Management
250+ greatest ideas, tips and strategies on Time Management & Productivity
10+ Hours of no-fluff solid Video Content
PDF Summaries of all 50 books

Since Mani is my friend and fellow mastermind member, I worked with him to get you guys an amazing discount (using discount code “DEVCHAT”) on the 10x Productivity Book Summary Pack which you can find here

Make sure to use the Coupon code “DEVCHAT” to get the discount.

Links

Mani’s 2x Productivity Course use the code “devchat” for a discount

Picks

AJ O’Neal:

M. Night Shyamalan’s The Village
colophony/pine sap/rosin/flux for electronics work

Aimee Knight:

Interested In Becoming A Site Reliability Engineer? blog post

Charles Max Wood:

Entreprogrammers episode 248
Kanbonflow
Physical Pomodoro timer

Mani Vaya:

Full Article

MJS 109: James Shore

By
Published On :: Tue, 28 May 2019 06:00:00 -0400

Sponsors

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

Host: Charles Max Wood

Joined By Special Guest: James Shore

Episode Summary

James Shore, the author of the book, “The Art of Agile Development” and a thought leader in the Agile software development community, talks about his journey in Agile development. James and Charles discuss how Agile has transformed software development process and the traits that a good software developer should have. James talks about his contributions to the developer community, his CSS testing tool quixote and the Agile Fluency Project.

Picks

James Shore:

Charles Max Wood:

Full Article

JSJ 369: Azure Functions with Colby Tresness LIVE at MIcrosoft BUILD

By
Published On :: Tue, 18 Jun 2019 06:00:00 -0400

Sponsors

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

Panel

Charles Max Wood

Joined by Special Guest: Colby Tresness

Episode Summary

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

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

Picks

Colby Tresness:

Barry (TV Series 2018– ) – IMDb

Charles Max Wood:

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

Full Article

JSJ 379: FindCollabs and Podcasting with Jeff Meyerson

By devchat.tv
Published On :: Thu, 01 Aug 2019 06:00:00 -0400

Sponsors

Netlify
RxJS Live

Panel

Aimee Knight
AJ O’Neal
Charles Max Wood

With Special Guest: Jeff Meyerson

Episode Summary

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

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

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

Links

Follow DevChat on Facebook and Twitter

Picks

Aimee Knight:

Burnout and the Brain

AJ O’Neal:

Saber’s Edge from Final Fantasy by Distant Worlds

Greenlock on FindCollabs
Telebit on FindCollabs

Charles Max Wood:

Adventures in Machine Learning on FindCollabs
Adventures in Virtual Reality on FindCollabs
Adventures in Python on FindCollabs
Adventures in Java on FindCollabs
Air conditioning
MFCEO Project

Jeff Meyerson:

Follow Jeff @the_prion
Listen Notes
Linbin’s Podcast Playlist
Hidden Forces Podcast

Full Article

MJS 119: Jeffrey Meyerson

By devchat.tv
Published On :: Tue, 20 Aug 2019 06:00:00 -0400

Sponsors

Sentry use the code “devchat” for 2 months free on Sentry small plan
Ruby Rogues
React Native Radio
CacheFly

Host: Charles Max Wood

Joined by Special Guest: Jeffrey Meyerson

Episode Summary

Jeffrey Meyerson, founder of FindCollabs and host at Software Engineering Daily joins Charles Max Wood for a discussion about latest trends in developer world, ways of monetizing podcasts and finding ads for podcasts.Jeffrey shares how he started hosts podcasts and how he became a developer.

Jeffrey's journey as a developer started out with his interest through music and poker. They compare advertising through sponsoring a booth in a conference versus advertising through a podcast. Tune in for a fun chat that covers everything from Keto dieting to software buzz words.

Picks

Charles Max Wood

#75Hard

Jeffrey Meyerson

Owning a Rice Cooker

Full Article

JSJ 389: What Makes a 10x Engineer?

By devchat.tv
Published On :: Thu, 05 Sep 2019 06:00:00 -0400

Sponsors

Sustain Our Software
Sentry– use the code “devchat” for $100 credit
Adventures in Blockchain

Panel

Charles Max Wood

Episode Summary

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

Links

10x engineer twitter thread

Follow DevChat on Facebook and Twitter

Picks

Charles Max Wood:

Full Article

JSJ 390: Transposit with Adam Leventhal

By devchat.tv
Published On :: Tue, 10 Sep 2019 06:00:00 -0400

Episode Summary

Adam Leventhal is the CEO and cofounder of Transposit. Transposit was born from the desire to build a way for developers to work with lots of different APIs, take authentication and pagination off the table, and let developers focus on the problems they’re trying to solve. Transposit is a serverless platform that’s free and gives you a combination of SQL or JavaScript to start playing with your API.

Since interacting with API data securely can be difficult, the panel discusses how Transposit might replace the personally built tools and how does it compare to JAMstack. They talk about some common things that people do wrong with security.

Transposit is often used as the full backend, and Adam shares how that works. There is a list of APIs that Transposit can talk to, and you can build your own connector. You can also work with JavaScript and SQL simultaneously.

Chris Ferdinandi asks some more specific questions about how Transposit can work with email lists. Adam clarifies the difference between connectors and apps in Transposit. He delves into more detail on what makes it work under the hood.

There are some 450,000 Stack applications but the majority have one user because they built it to communicate specifically with their API. The panel discusses how Transposit can help with this. Since Transposit is still in startup mode, it is free for now, and can connect to any public facing API. Adam talks about their decision not to make it open source and gives more details on where the authentications occur. The show wraps up with the panel talking about the pros of going serverless

Panelists

Chris Ferdinandi
Christopher Buecheler

With special guest: Adam Leventhal

Sponsors

Adventures in .NET
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
Elixer Mix

Links

Transposit
SQL
JAMstack
OpenAPI
Swagger
YAML
MailChimp
React Redux
Converting a string into Markup with Vanilla JS
How to create a map of DOM nodes with Vanilla JS
Custom events in Internet Explorer with Vanilla JS
DOM diffing with Vanilla JS part 1
DOM diffing with Vanilla JS part 2

Follow DevChat on Facebook and Twitter

Picks

Christopher Buecheler:

Manchester Orchestra

Chris Ferdinandi:

Reef
Elizabeth Warren

Adam Leventhal:

Hamilton the biography
Antler
Follow Adam on Twitter @ahl

Full Article

JSJ 391: Debugging with Todd Gardner

By devchat.tv
Published On :: Thu, 12 Sep 2019 06:00:00 -0400

Episode Summary

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

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

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

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

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

Panelists

Chris Ferdinandi
Christopher Buecheler
Aimee Knight
Charles Max Wood
Steve Emmrich

With special guest: Todd Gardner

Sponsors

Adventures in Blockchain
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
React Round Up

Links

Follow DevChat on Facebook and Twitter

Picks

Christopher Buecheler:

React/TypeScript cheat sheet

Chris Ferdinandi:

Aimee Knight:

TechLead Youtube channel

Charles Max Wood:

Atomic Habits
Getting up at 4 am

Steve Emmrich:

Trello
Babushkas and grandmas to help you with your newborn

Todd Gardner:

PubConf
Follow Todd @toddhgardner or todd.mn

Full Article

JSJ 392: The Murky Past and Misty Future of JavaScript with Douglas Crockford

By devchat.tv
Published On :: Tue, 17 Sep 2019 06:00:00 -0400

Episode Summary

Douglas is a language architect and helped with the development of JavaScript. He started working with JavaScript in 2000. He talks about his journey with the language, including his initial confusion and struggles, which led him to write his book JavaScript: The Good Parts.

Douglas’ take on JavaScript is unique because he not only talks about what he likes, but what he doesn’t like. Charles and Douglas discuss some of the bad parts of JavaScript, many of which were mistakes because the language was designed and released in too little time. Other mistakes were copied intentionally from other languages because people are emotionally attached to the way things “have always been done”, even if there is a better way.

Doug takes a minimalist approach to programming. They talk about his opinions on pairing back the standard library and bringing in what’s needed. Douglas believes that using every feature of the language in everything you make is going to get you into trouble. Charles and Douglas talk about how to identify what parts are useful and what parts are not.

Douglas delves into some of the issues with the ‘this’ variable. He has experimented with getting rid of ‘this’ and found that it made things easier and programs smaller. More pointers on how to do functional programming can be found in his book How JavaScript Works

Charles and Douglas talk about how he decided which parts were good and bad. Douglas talks about how automatic semicolon insertion and ++ programming are terrible, and his experiments with getting rid of them. He explains the origin of JS Lint. After all, most of our time is not spent coding, it’s spent debugging and maintaining, so there’s no point in optimizing keystrokes.

Douglas talks about his experience on the ECMAScript development committee and developing JavaScript. He believes that the most important features in ES6 were modules and proper tail calls. They discuss whether or not progression or digression is occurring within JavaScript. Douglas disagrees with all the ‘clutter’ that is being added and the prevalent logical fallacy that if more complexity is added in the language then the program will be simpler.

Charles asks Douglas about his plans for the future. His current priority is the next language. He talks about the things that JavaScript got right, but does not believe that it should not be the last language. He shares how he thinks that languages should progress. There should be a focus on security, and security should be factored into the language.

Douglas is working on an implementation for a new language he calls Misty. He talks about where he sees Misty being implemented. He talks about his Frontend Masters course on functional programming and other projects he’s working on. The show concludes with Douglas talking about the importance of teaching history in programming.

Panelists

Charles Max Wood

With special guest: Douglas Crockford

Sponsors

Sustain Our Software
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
Views on Vue

Links

JavaScript: The Good Parts
How JavaSript Works
“This” variable
ECMAScript
C++
JS Lint
ECMA TC39
Dojo
Promise
RxJS
Drses
Misty
Tail call
Frontend Masters course JavaScript the Good Parts

Follow DevChatTV on Facebook and Twitter

Picks

Charles Max Wood:

Superfans by Pat Flynn
SEO course Agency Unlocked by Neil Patel

Douglas Crockford:

The Art of Computer Programming by Donald Knuth
Game of Thrones
Follow Douglas at crockford.com

Full Article

JSJ 393: Why You Should Be Using Web Workers with Surma

By devchat.tv
Published On :: Thu, 19 Sep 2019 06:00:00 -0400

Episode Summary

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

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

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

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

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

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

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

Panelists

Charles Max Wood
Christopher Buecheler
Aimee Knight
AJ O’Neal

With special guest: Surma

Sponsors

Adventures in DevOps
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
Adventures in Angular

Links

Follow DevChatTV on Facebook and Twitter

Picks

Charles Max Wood:

For Love of Mother-Not

Surma:

Follow Surma @DasSurma on Twitter and at dassur.ma
WebAssembly Spec

AJ O’Neal:

Christopher Buecheler

CinemaSins Sincast podcast

Full Article

JSJ 394: SMS Integration with Dominik Kundel

By devchat.tv
Published On :: Tue, 24 Sep 2019 06:00:00 -0400

Episode Summary

Dominik Kundel works as developer evangelist at Twilio. Dominik talks about the history of Twilio, which actually started with integrating phone calls into apps and then moved to SMS integration.

Today Charles and Dominik are talking about how the SMS message approach can augment your user experience. Since many people are not familiar with implementing SMS, Dominik talks about how Twilio can help. Twilio created was a supernetwork where they work with carriers and gateways around the world to ensure that they provide reliable services. They also focus heavily on making sure that the developer experience is great.

Uber and Lyft are two of the companies that use Twilio, and Dominik shares some of the interesting things that they’ve accomplished. He is particularly excited about phone number masking to support privacy. Uber and Lyft use phone number masking so that your driver doesn’t see your real number and you don’t see theirs. Instead, each of you sees a Twilio number. This use case is becoming more common.

Twilio recently introduced Flex, which Dominik explains is their contact center solution. Flex is designed to keep with their philosophy of everything should be programmable and configurable, and take it on to a software shipment. This is their first time shipping software instead of just APIs. Flex is highly customizable and flexible, allows you to build React plugins that let you change anything you want.

Charles asks Dominik about some of the gotchas in telephony. One major issues is spam calls, which Twilio is trying to work with some providers on a ‘verified by Twilio’ list. This list lets companies get verified, and they’re working on ways to let you know the reason why they’re calling without having to answer your phone. This can be difficult because each country has different regulations.

Dominik talks about what it would take for someone who wanted to build an SMS gateway themselves. They would have to work with carriers and learn SMS protocols. It’s important to note that SMS and phone calls have different protocols

Dominik talks about some of the unique use cases they’ve seen their system. Some examples are contextual communications, account verifications, and codex creation. There are other fun examples, such as a drone controlled via text message, a fake boyfriend app, and a dog that was taught to take selfies that are sent to his owner.

Charles asks about ways to get started with Twilio. If you want to explore this and don’t know where to get started, try Twilio Quest, a game to teach you how to use Twilio. There is also documentation, which is good if you know exactly what you want to achieve, or if you just want to explore possibilities then download Twilio Quest.

They delve into a more specific use case for Twilio to send text to subscibers of DevChatTV. Dominik talks about ways of dealing with sending notifications to people outside of the US. You can send with a US number to any country code, or you can personalize it, so that people in the UK receive it from a UK number and so on through automatic geocode matching. They talk about Twilio’s billing.

Finally, they talk about security within telephony in light of recent hacks. They discuss the security of two factor authentication.Two factor authentication and security, especially in light of recent hacks. Dominik talks about the API called Authy, where you can implement different ways of doing two factor authentication, such as push notifications, time based one time password, sms, and phone calls. For most people in the world two factor authentication is very safe, unless you’re a very important person, then you’re more at risk for targeted attacks. They conclude by talking about Twilio’s acquisition of Sendgrid.

Panelists

Charles Max Wood

With special guest: Dominik Kundel

Sponsors

iPhreaks Show
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
Ruby Rogues

Links

Twilio
Flex
React
Rust
Twilio Quest
Twilio docs
Twilio Completes Acquisition of Sendgrid
Authy

Follow DevChatTV on Facebook and Twitter

Picks

Charles Max Wood:

Superfans by Pat Flynn
Neilpatel.com

Dominik Kundel:

Enable a setting called javascript.implicit
Follow him @dkundel

Full Article

JSJ 395: The New Ember with Mike North

By devchat.tv
Published On :: Thu, 26 Sep 2019 06:00:00 -0400

Mike North is the Ember guy at Frontend Masters and LinkedIn’s web developer trainer. Today the panel is talking about the upcoming Ember update, which Mike calls a total reinvention of the way you build with Ember. Finally, they are letting go of the cruft and stuff they had to hold on to in order to support IE8 and using modern interface

The panel talks about some of the issues with IE8, and agree that the reason Ember felt its age because it was built for IE8. Ember 314 is moving from the past into the present, a sleek modern way to build apps. Mike talks about how easy the new Ember is to use.

Mike talks about the excitement in the Ember community because the new build is focused on stability and seamlessness. Charles talks about his less seamless experience with the Angular community. For context, Mike North’s first frontend masters course was recorded in 2014, and he’s only had to change two lines of code. Ember is the only framework that has managed to go all the way from IE7/IE8 to today without a major gap,breaks, or rewrites.

They transition to talking about what keeps Ember going. There is an effort to make sure things are decentralized and not tied to any specific company, although Apple, Netflix, Nasa, and PlaysStation all use it. LinkedIn has also been hiring Ember core member to continue working on it, and sponsoring open source work.

Next, they talk about how Ember works with TypeScript. You can install an Ember add on with one terminal command that will enable TypeScript in an Ember app.There are some issues that could cause misalignment with JavaScript and TypeScript, but Ember has designed things around it. MIke talks about the major change in the learning curve with using Ember and how far Vanilla JS will take you. Overall, it is a lot more approachable than it used to be.

They move on to talk about the availability of third party solutions with Ember. Mike assures them that Ember has add-ons, and parts of the framework are opening up to allow experimentation with components. There are lots of ways to make Ember your own without running the risk of diverging, giving more flexibility than ever while maintaining the happy path. Testing within Ember is also a priority, and they want the code to be as readable as possible.

The last topic discussed in this show is the importance of developer education. LinkedIn looks at employment numbers and the rate at which new jobs open, and software engineering is growing like crazy and will likely continue to grow.The rate at which new people are graduating with computer science and programming degrees, as well as those from unconventional backgrounds, is not keeping up with the number of jobs. This means that there will be fewer senior people spread across bigger groups of developers with less experience. The panel agrees that it is the responsibility of people who have been around or learned something period to pass on the knowledge because the more knowledge is passed on, the more stable things will remain as seniors become more scarce. It is also important for companies to level up junior developers. They conclude by talking about tools available for people who want to learn more about Ember Octane, and Mike makes an open request to the JS community.

Panelists

Charles Max Wood
Steve Emmerich
Chris Ferdinandi
Aimee Knight
AJ O’Neal
Christopher Buecheler

With special guest: Mike North

Sponsors

React Native Radio
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
Dev Ed Podcast

Links

Ember
Frontend Masters
IE8
Ember Octane
Sprout Core
TypeScript
ES6
Lodash
Mocha
Backstop.js
Semver
https://twitter.com/thefalken/status/1177483501777473537

Follow DevChatTV on Facebook and Twitter

Picks

Chris Ferdinandi:

Vanilla JS Academy, get 30% off with code ‘jsjabber’
leanweb.dev

Steve Emmerich:

123 Magic
RGDK

Aimee Knight:

Recursion blog post
Wholesome Provisions Protein Cereal

AJ O’Neal:

Carby V2 by Insurrection Industries
GameCube Mods

Charles Max Wood:

Christopher Buecheler:

Tool’s Fear Inoculum on Apple Music, Spotify, and Google Play

Mike North:

Github Universe
Github Tracer Bench
Follow Mike @mike-north on Github, @northm on LinkedIn, and @michaellnorth on Twitter

Full Article

JSJ 396: Publishing Your Book with Jonathan Lee Martin

By devchat.tv
Published On :: Tue, 01 Oct 2019 06:00:00 -0400

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

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

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

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

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

Panelists

Charles Max Wood
Christopher Buecheler
J.C. Hyatt

With special guest: Jonathan Lee Martin

Sponsors

Adventures in Blockchain
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
The Freelancers’ Show

Links

Big Nerd Ranch
Digital Crafts
JSJ 070: Book Club JavaScript Allonge with Reginald Braithwaite
JavaScript Allonge by Reginald Braithwaite
Functional Design Patterns for Express JS by Jonathan Lee Martin
Node.js
Express.js
Koa
Minjs
Sinatra
Http.createserver
Monads
Middleware
Markdown
Pandoc
Diff-match-path library
Epub
MOBI
LaTeX
Stripe Checkout
Fstoppers
Softcover
Bookseller API

Follow DevChatTV on Facebook and Twitter

Picks

Christopher Buecheler:

Cluisbrace.com newsletter

J.C. Hyatt:

Corsair wireless charging mouse pad

Charles Max Wood:

Magnetic whiteboard baskets
Mrs. Piggle-Wiggle books

Jonathan Lee Martin:

Eric Elliot JS
YellowScale
Follow Jonathan and find his book at jonathanleemartin.com

Full Article

JSJ 397: Design Systems with Kaelig Deloumeau-Prigent

By devchat.tv
Published On :: Thu, 03 Oct 2019 06:00:00 -0400

Kaelig Deloumeau-Prigent is a self taught web developer from west France. He has worked for BBC, The Guardian, and The Financial Times in the UK. He has also worked in the US for SalesForce and currently works for Shopify on their Polaris design system. Shopify has multiple design systems, and Polaris is open source. Today the panel is talking about design systems and developer tooling around design systems.

To begin, Kaelig explains what a design system is. A design system is all of the cultural practices around design and shipping a product. It includes things like the words, colors, spacing grid system, and typography, plus guidance on how to achieve that in code. The panelists discuss what has made design systems so popular. Design systems have been around for a while, but became popular due to the shift to components, which has been accelerated by the popularity of React. The term design system is also misused by a lot of people, for it is much more than having a Sketch file.

Next, they talk about whether design systems fall under the jurisdiction of a frontend developer or web designers. Kaelig has found that a successful design system involves a little bit of everyone and shouldn’t be isolated to one team. They talk about what the developer workflow looks like in a design system. It begins with thinking of a few common rules, a language, and putting it into code. As you scale, design systems can become quite large and it’s impossible for one person to know everything. You either give into the chaos, or you start a devops practice where people start to think about how we build, release, and the path from designer’s brain to production.

The panelists then talk about how to introduce a design system into a company where there are cultural conflicts. Kaelig shares his experience working with SalesForce and introducing a design system there. They discuss what aspects of a design system that would make people want to use it over what the team is currently doing. Usually teams are thankful for the design system. It’s important to build a system that’s complete, flexible, and extensible so that you can adapt it to your team. A good design system incorporates ‘subatomic’ parts like the grid system, color palette, and typography, referred to as design tokens. Design systems enable people to take just the bits of the design system that are interesting to them and build the components that are missing more easily.

The conversation turns to the installation and upgrade process of a design system. Upgrading is left up to the customer to do on their own time in most cases, unless it’s one of the big customers. They talk about the role of components in upgrading a design system. Kaelig talks about the possibility of Shopify transitioning to web components. Kaelig shares some of his favorite tools for making a design system and how to get started making one. A lot of design teams start by taking a ton of screen shots and looking at all the inconsistencies.Giving them that visibility is a good thing because it helps get everyone get on the same page. The panelists talk about the role of upper management in developing components and how to prioritize feature development. Kaelig talks about what drives the decision to take a feature out. The two main reasons a feature would be removed is because the company wants to change the way things are done and there’s a different need that has arisen. The show concludes by discussing the possibility of a design system getting bloated over time. Kaelig says that Design systems takes some of the burden off your team, help prevent things from getting bloated, allow you to ship less code.

Panelists

Chris Ferdinandi
Aimee Knight
Steve Emmerich

With special guest: Kaelig Deloumeau-Prigent

Sponsors

Sustain Our Software
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
Adventures in Blockchain

Links

Shopify Polaris
Bootstrap
React
Sketch.ui
Figma.ui
CSS
StoryBook
ESLint
Jest
Ensign
Webpacker

Follow DevChatTV on Facebook and Twitter

Picks

Steve Emmerich:

CedarWorks play beds
Azure’s container instances

Aimee Knight:

Awesome Actions for Github

Chris Ferdinandi:

Kaelig Deloumeau-Prigent:

Dependabot
Ink by Vadim Demedez
Follow Kaelig on Twitter @kaelig

Full Article

JSJ 398: Node 12 with Paige Niedringhaus

By devchat.tv
Published On :: Tue, 08 Oct 2019 06:00:00 -0400

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

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

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

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

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

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

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

GCC minimum 6
GLIVC minimum 2.17 on platforms other than Mac and Windows (Linux)
Mac users need at least 8 and Mac OS 10.10
If you’ve been running node 11 builds in Windows, you’re up to speed
Linux binaries supported are Enterprise Linux 7, Debian 8, and Ubuntu 14.04
If you have different requirements, go to the Node website

Panelists

J.C. Hyatt
Steve Edwards
AJ O’Neal

With special guest: Paige Niedringhaus

Sponsors

Tidelift
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
Sustain Our Software

Links

Follow DevChatTV on Facebook and Twitter

Picks

J.C. Hyatt:

AWS Amplify framework
12 Rules for Life: An Antidote to Chaos by Jordan Petersen
React and Gatsby workshops

Steve Edwards:

The Farside comic coming back?

AJ O’Neal:

Paige Niedringhaus:

Follow Paige on Twitter, Medium, and Github

Full Article

JSJ 399: Debugging with Async/Await with Valeri Karpov

By devchat.tv
Published On :: Thu, 10 Oct 2019 06:00:00 -0400

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

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

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

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

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

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

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

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

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

Panelists

Christopher Buecheler
AJ O’Neal
Charles Max Wood

With special guest: Valeri Karpov

Sponsors

The DevEd Podcast
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
Adventures in DevOps

Links

Follow DevChatTV on Facebook and Twitter

Picks

AJ O’Neal:

Ethan Garofolo YouTube

Christopher Buecheler:

Functional Design Patterns for Express.js

Charles Max Wood:

Microsoft Ignite
Maxcoders.io

Valeri Karpov:

Follow Valeri on Twitter @code_barbarian and Github @vkarpov15
Masteringjs.io
Jurassic Park: A Novel

Full Article

MJS 129: Filipa Lacerda

By devchat.tv
Published On :: Tue, 29 Oct 2019 06:22:00 -0400

Charles Max Wood talks to Filipa Lacerda in this week's My JavaScript Story. Filipa has been working as a front end engineer since 2011 and she currently works at GitLab.

Filipa originally wanted to study Economy but when she got to university she decided to major in Communications thinking it would be a lot more about communication and not as much about coding. At first she really didn't like the coding aspect of it but then as time went by she actually started to enjoy coding.

When she first started working she started out on the User Experience side, but then she wanted to switch to building stuff with code because she wanted to see results really fast and enjoyed that aspect of coding.

Charles asks why she stuck with that degree instead of switching it and Filipa explains that at first because she didn't want to go back and re - take the exams and also decided that this degree offered many job opportunities in many different industries and now she can't imagine herself doing anything else.

Filipa then talks about why she is working with Vue and all the different kind of projects she has done using Vue as well as what working for GitLab looks like on a day to day basis.

Host: Charles Max Wood

Joined by Special Guest: Filipa Lacerda

Sponsors

Sentry use the code “devchat” for 2 months free on Sentry small plan
Adventures in .NET
Elixir Mix
CacheFly

Picks

Filipa Lacerda:

Why We Sleep by Walker PhD, Matthew

Charles Max Wood:

Full Article

JSJ 409: Swagger and Open API with Josh Ponelat

By devchat.tv
Published On :: Tue, 26 Nov 2019 06:00:00 -0500

Today the panel discusses the difference between Swagger and Open API with Josh Ponelat. Josh details the difference between the two. Swagger is a set of protocols around describing restful APIs. Swagger was taken over by a company called SmartBear, who donated the donated the specification to the Open Linux Foundation, and that became the Open API. Swagger is the tooling surrounding these specifications. Open API is a standardized way to describe a restful API in a YAML file. Once you’ve got a YAML file to describe your API, you can use tooling like Swagger to leverage that and take it to the next level. Using the Open API process is useful for situations where you already have an API in place, but want to codify and document it so that it’s controlled. Then going forward, you won’t introduce contradictions and it remains consistent because it’s documented in a YAML file. The process leaves room for enhancement in the future as well.

Josh talks about some of the benefits of standardizing your API and some of the use cases besides tooling. A standardized API can help show developers how to use your API, SDKs, and service stubs by knowing your API is consistent in style. This makes it easier to find breaking changes and more. Josh talks more about Swagger, a finite set of tooling around Open API, most of which are open source. He talks about other tools that test APIs and do linting on YAML files. Some of the companies that use Open API include Google, Amazon, and Microsoft. Josh talks about how Amazon implements Open API.

Josh talks about the book he’s writing, Designing APIs with Swagger and Open API. The book goes over describing APIs today, how to design APIs without writing code first, and how to get the most out of the system. The show concludes with Josh talking about the power of consistency and writing things down on paper. He discusses where implications that the standardization of APIs has on the text industry.

Panelists

Dan Shapir
Charles Max Wood

Guest

Josh Ponelat

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

Sponsors

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

Picks

Dan Shapir

Saga of Pliocene Exile

Charles Max Wood

DevChat.tv Merchandise
BusyCal

Josh Ponelat

AsciiDoc
FASD tool

Full Article

JSJ 419: Google App Script with Ben Collins

By devchat.tv
Published On :: Tue, 04 Feb 2020 06:00:00 -0500

Today’s guest is Ben Collins, who creates online courses, writes tutorials, and teaches workshops around G Suite and App Script. Apps Script is a scripting platform developed by Google for light-weight application development in the G Suite platform. It is an implementation of JavaScript with the express purpose of extending Google apps. App Script was started 10 years ago as a side project, and it eventually took on its own life. Ben talks about some of the different things that App Script can do and where things are stored. They discuss different ways you can get into the script and how to import external scripts from a CDN. Ben gives two examples, one simple and one sophisticated, that you might build from App Script. He talks about event triggers and how authentication is handled. He goes over the three deployment options, namely web app, app executable, sheets add-on, and deploying from the manifest. Ben talks about how triggers are managed in App Script and options for debugging. There is also the option to develop locally as well as in the browser. The show ends with him talking about how to build using HTML in App Script.

Panelists

Aimee Knight
Steve Edwards
Dan Shapir

Guest

Ben Collins

Sponsors

G2i
Split

____________________________

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

____________________________________________________________

Picks

Steve Edwards:

King Kong Apparel

Aimee Knight:

Developers Mentoring Other Developers

Dan Shapir:

The Web Almanac

AJ O’Neal:

Photography
Magic Lantern

Bem Collins:

Cold Turkey app
Follow Ben at Benlcollins.com and Twitter

Full Article

MJS 139: Radoslav Stankov

By devchat.tv
Published On :: Tue, 03 Mar 2020 06:00:00 -0500

Rado Stankov is the Head of Engineering at Product Hunt. He's based in Sofia Bulgaria. He walks us through learning Pascal and PHP and Flash. We then dive into Ruby and JavaScript and what he's working on now at Product Hunt.

Host: Charles Max Wood

Joined By Special Guest: Radoslav Stankov

Sponsors

______________________________________

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

______________________________________

Picks

Radoslav Stankov:

Charles Max Wood:

Full Article

JSJ 429: Learning about Postman with Joyce Lin

By devchat.tv
Published On :: Tue, 14 Apr 2020 06:04:00 -0400

JavaScript Remote Conf 2020

May 13th to 15th - register now!

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

Panel

Aimee Knight
Steve Edwards

Guest

Joyce Lin

Sponsors

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

____________________________________________________________

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

____________________________________________________________

Picks

Steve Edwards:

The Big Red NO! Button Desktop Sound Toy

Joyce Lin:

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

Follow JavaScript Jabber on Twitter > @JSJabber

Full Article

MJS 146: Håkon Krogh

By devchat.tv
Published On :: Tue, 28 Apr 2020 06:00:00 -0400

JavaScript Remote Conf 2020

May 13th to 15th - register now!

Håkon Krogh is a Norweigan developer who focuses on web performance. We start out discussing working from home in the current pandemic. His current company works in Product Information Management. It's a headless ecommerce system. We dive into his experience learning learning to build applications and learning JavaScript and leading a team.

Host: Charles Max Wood

Joined By Special Guest: Håkon Krogh

Sponsors

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

Picks

Håkon Krogh:

Charles Max Wood:

Full Article