Boom, Rob

Polmear, I. J., author

Dutta, Sujay Kumar, author

Gilligan, Rorie Alexander, author

Lavakumar, A., author

Global Conference on Extractive Metallurgy (1st : 2018 : Ottawa, Ont.)

Qi, Dezhi, author

Ndlovu, Sehliselo, author

Raghavan, V., author

The panelists talk to Eric Schoffstall, the creator of Gulp.js.

02:43 - Dave Rupert Introduction

• Twitter
• GitHub
• Blog
• Paravel

03:42 - Chris Coyier Introduction

• Twitter
• GitHub
• Blog
• CSS-Tricks
• CodePen

06:24 - The ShopTalk Show and Podcasting

• @shoptalkshow
• “What do I learn next?” => “Just Build Websites!”
• Question & Answers Aspect

23:19 - Tech Is A Niche

• Paul Ford: What is Code?

29:51 - Balancing Technical Content for All Levels of Listeners

• Community Opinion

38:42 - Learning New CSS Tricks (Writing Blog Posts)

• Code Golf

41:54 - The Accessibility Project

• Adventures in Angular Episode #027: Accessibility with Marcy Sutton
• Anne Gibson: An Alphabet of Accessibility Issues

56:02 - Favorite & Cool Episodes

• ShowTalk Show Episode #091: with Jamison Dance and Merrick Christensen
• ShopTalk Show Episode #101: with John Resig
• ShopTalk Show Episode #157: with Alex Russell  
• ShopTalk Show Episode #147: with Tom Dale
• ShopTalk Show Episode #123: Special Archive Episode from 2004
• ShopTalk Show Episode #166: with Lisa Irish
• ShopTalk Show Episode #161: with Eric Meyer

Picks

FIFA Women's World Cup (Joe)
Winnipeg (Joe)
The Martian by Andy Weir (Joe)
Zapier (Aimee)
SparkPost (Aimee)
dev.modern.ie/tools/vms (AJ)
remote.modern.ie (AJ)
Microsoft Edge (AJ)
StarFox Zero for Wii U (AJ)
Hot Plate (AJ)
untrusted (AJ)
Skiplagged (Dave)
Judge John Hodgman (Dave)
Wayward Pines (Chris)
Sturgill Simpson (Chris)
The Economic Value of Rapid Response Time (Dave)
The Adventure Zone (Dave)
React Rally (Jamison)
Matsuoka Shuzo: NEVER GIVE UP (Jamison)
DESTROY WITH SCIENCE - Quantum Loop (Jamison)
Serial Podcast (Chuck)
Ruby Remote Conf (Chuck)

02:28 - Eric Schoffstall Introduction

• Twitter
• GitHub
• Blog
• Instagram

02:59 - shasta

• Dan Abramov
• tahoe

07:20 - Getting Started

• github.com/shastajs/boilerplate

08:20 - Solidifying on Best Practices

10:37 - Made to Work Together vs Made to be Neatly Modular

11:19 - shasta and redux

12:01 - shasta Ideals

• Opinions
  • Immutable.js

15:07 - Making Choices

17:35 - redux-thunk, redux-saga

19:01 - Lessons Learned from gulp.js

• Open Source Marketing

23:55 - redux-router

25:20 - React-Specific vs Agnostic

• Lazer Team

27:35 - Experimentation with shasta

29:50 - Relay and GraphQL Conflict

31:31 - Swapability

35:30 - The Future of front-end development in JavaScript; Where shasta fits in

• mercury
  • Victor Savkin: Managing State in Angular 2 Applications

Picks

Victor Savkin: Managing State in Angular 2 Applications (Joe)
Lazer Team (Joe)
Big Black Delta (Jamison)
Learning to Use Google Analytics More Effectively at CodePen (Jamison)
Thing Explainer: Complicated Stuff in Simple Words by Randall Munroe (Dave)
Soft Skills Engineering Podcast (Dave)
RevolutionConf 2016 (Aimee)
[Frontend Masters] Functional-Lite JavaScript (Aimee)
Lush Cosmetics (Aimee)
horizon (Eric)
Shannon and the Clams - Rip Van Winkle (Eric)
shasta (Eric)

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

04:40 An explanation of Capital One and its operations

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

10:30 Process of approval for app/website development

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

18:25 Using Javascript libraries to manage different currencies

19:40 Venmo and its influence on banking

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

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

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

44:00 Upgrading via open source codes

45:40 The process for hiring developers

51:35 Typescript vs. non-typescript

PICKS:

“Nerve” Movie

Brave Browser

“Stranger Things” on Netflix

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

“Strategy for Healthier Dev” blog post

Health-Ade Beet Kombucha

“The Adventure Zone” podcast

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

“The Freelancer Show” podcast

“48 Days” podcast

Node.university

Azat Mardan’s Website

Azat Mardan on Twitter

CETUSA – Foreign exchange program

Panel:

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

Special Guests: Vitali Zaidman

In this episode, the panel talks with programmer, Vitali Zaidman, who is working with Software Solutions Company. He researches technologies and starts new projects all the time, and looks at these new technologies within the market. The panel talks about testing JavaScript in 2018 and Jest.

Show Topics:

1:32 – Chuck: Let’s talk about testing JavaScript in 2018.

1:53 – Vitali talks about solving problems in JavaScript.

2:46 – Chuck asks Vitali a question.

3:03 – Vitali’s answer.

3:30 – Why Jest? Why not Mocha or these other programs?

3:49 – Jest is the best interruption of what testing should look like and the best practice nowadays. There are different options, they can be better, but Jest has this great support from their community. There are great new features.

4:31 – Chuck to Joe: What are you using for testing nowadays?

4:43 – Joe: I use Angular, primarily.

6:01 – Like life, it’s sometimes easier to use things that make things very valuable.

7:55 – Aimee: I have heard great things about Cypress, but at work we are using another program.

8:22 – Vitali: Check out my article.

8:51 – Aimee: There are too many problems with the program that we use at work.

9:39 – Panelist to Vitali: I read your article, and I am a fan. Why do you pick Test Café over Cypress, and how familiar are you with Cypress? What about Selenium and other programs?

10:12 – Vitali: “Test Café and Cypress are competing head-to-head.”

Listen to Vitali’s suggestions and comments per the panelists’ question at this timestamp.

11:25 – Chuck: I see that you use sign-on...

12:29 – Aimee: Can you talk about Puppeteer? It seems promising.

12:45 – Vitali: Yes, Puppeteer is promising. It’s developed by Google and by Chrome. You don’t want to use all of your tests in Puppeteer, because it will be really hard to do in other browsers.

13:26: Panelist: “...5, 6, 7, years ago it was important of any kind of JavaScript testing you had no idea if it worked in one browser and it not necessarily works in another browser. That was 10 years ago. Is multiple browsers testing as important then as it is now?

14:51: Vitali answers the above question.

15:30 – Aimee: If it is more JavaScript heavy then it could possibly cause more problems.

15:56 – Panelist: I agree with this.

16:02 – Vitali continues this conversation with additional comments.

16:17 – Aimee: “I see that Safari is the new Internet Explorer.”

16:23: Chuck: “Yes, you have to know your audience. Are they using older browsers? What is the compatibility?”

17:01 – Vitali: There are issues with the security. Firefox has a feature of tracking protection; something like that.

17:33 – Question to Vitali by Panelist.

17:55 – Vitali answers the question.

18:30 – Panelist makes additional comments.

18:43 – If you use Safari, you reap what you sow.

18:49 – Chuck: I use Chrome on my iPhone. (Aimee does, too.) Sometimes I wind up in Safari by accident.

19:38 – Panelist makes comments.

19:52 – Vitali tells a funny story that relates to this topic.

20:45 – There are too many standards out there.

21:05 – Aimee makes comments.

21:08 – Brutalist Web Design. Some guy has this site – Brutalist Web Design – where he says use basic stuff and stop being so custom. Stop using the web as some crazy platform, and if your site is a website that can be scrolled through, that’s great. It needs to be just enough for people to see your content.

22:16 – Aimee makes additional comments about this topic of Brutalist Web Design.

22:35 – Panelist: I like it when people go out and say things like that.

22:45 – Here is the point, though. There is a difference between a website and a web application. Really the purpose is to read an article.

23:37 – Vitali chimes in.

24:01 – Back to the topic of content on websites.

25:17 – Panelist: Medium is very minimal. Medium doesn’t feel like an application.

26:10 – Is the website easy enough for the user to scroll through and get the content like they want to?

26:19 – Advertisement.

27:22 – See how far off the topic we got?

27:31 – These are my favorite conversations to have.

27:39 – Vitali: Let’s talk about how my article got so popular. It’s an interesting thing, I started researching “testing” for my company. We wanted to implement one of the testing tools. Instead of creating a presentation, I would write first about it in Medium to get feedback from the community as well. It was a great decision, because I got a lot of comments back. I enjoyed the experience, too. Just write about your problem in Medium to see what people say.

28:48 – Panelist: You put a ton of time and energy in this article. There are tons of links. Did you really go through all of those articles?

29:10 – Yes, what are the most permanent tools? I was just reading through a lot of comments and feedback from people. I tested the tools myself, too!

29:37 – Panelist: You broke down the article, and it’s a 22-minute read.

30:09 – Vitali: I wrote the article for my company, and they ad to read it.

30:24 – Panelist: Spending so much time – you probably felt like it was apart of your job.

30:39 – Vitali: I really like creating and writing. It was rally amazing for me and a great experience. I feel like I am talented in this area because I write well and fast. I wanted to express myself.

31:17 – Did you edit and review?

31:23 – Vitali: I wrote it by myself and some friends read it. There were serious mistakes, and that’s okay I am not afraid of mistakes. This way you get feedback.

32:10 – Chuck: “Some people see testing in JavaScript, and people look at this and say there are so much here. Is there a place where people can start, so that way they don’t’ get too overwhelmed? Is there a way to ease into this and take a bite-size at a time?”

32:52 – Vitali: “Find something that works for them. Read the article and start writing code.”

He continues this conversation from here on out.

34:03 – Chuck continues to ask questions and add other comments.

34:16 – Vitali chimes-in. 

34:38 – Chuck. 

34:46 – Vitali piggybacks off of Chuck’s comments.

36:14 – Panelist: Let’s go back to Jest. There is a very common occurrence where we see lots of turn and we see ideas like this has become the dominant or the standard, a lot of people talk about stuff within this community. Then we get this idea that ‘this is the only thing that is happening.’ Transition to jQuery to React to... With that context do you feel like Jest will be a dominant program? Are we going to see Jest used just as common as Mocha and other popular programs?

38:15 – Vitali comments on the panelist’s question.

38:50 – Panelist: New features. Are the features in Jest (over Jasmine, Mocha, etc.) so important that it will drive people to it by itself?

40:30 – Vitali comments on this great question.

40:58 – Panelist asks questions about features about Jest.

41:29 – Vitali talks about this topic.

42:14 – Let’s go to picks!

42:14 – Advertisement.

Links:

• Vitali Zaidman’s Facebook
• Vitali Zaidman’s Medium
• Vitali Zaidman’s GitHub
• Vitali Zaidman’s NPM
• Vitali Zaidman’s LinkedIn
• Vitali Zaidman’s Medium Article
• JavaScript
• Brutalist Web Design
• Jasmine
• Cypress
• React
• jQuery
• Jest
• Protractor – end to end testing for Angular
• Test Café
• Intern
• Sinon
• XKCD

Sponsors:

• Kendo UI
• Sentry
• Digital Ocean
• Cache Fly

Picks:

AJ O’Neal

• Continuous from last week’s episode: Crossing the Chasm – New Technologies from Niche to General Adaptation.
• Go Lang

Joe Eames

• Board Game: Rajas of the Ganges
• Framework Summit Conference in Utah
• React Conference

Aimee Knight

• Hacker News – “Does Software Understand Complexity” via Michael Feathers
• Cream City Code

Chuck

• E-Book: How do I get a job?
• Express VPN

Vitali

• Book: The Square and The Tower: Networks and Power, from the Freemasons to Facebook by Niall Ferguson
• My article!

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

Links

• JSJ 331: An Overview of JavaScript Testing in 2018 with Vitali Zaidman
• https://www.facebook.com/vzaidman
• https://twitter.com/vzaidman
• https://github.com/vzaidman
• https://medium.com/@vzaidman
• https://bitsrc.io/vzaidman
• https://www.welldone-software.com/
• https://www.powtoon.com/home/?

Picks

Vitali Zaidman:

• https://www.testim.io/
• https://applitools.com/
• An Overview of JavaScript Testing in 2019 by Vitali Zaidman
• https://github.com/welldone-software/why-did-you-render

Charles Max Wood:

• https://www.vrbo.com/
• https://paradehomes.com/web/
• https://www.tripit.com/web
• Player's Handbook Dungeons & Dragons Core Rule Book

Sponsors

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

Panel

• Charles Max Wood

With Special Guest: Anatoliy Zaslavskiy

Episode Summary

Anatoliy Zaslavsky works for Hover, made framework called Pickle.js, and has been on JavaScript Jabber before. Today Chuck and Anatloliy are talking about the importance of mental health. Anatoliy has Bipolar Disorder, and he talks about what it is and his experience with it and how his manic and depressive episodes have affected him. Thankfully, his employers at Hover have been extremely supportive. Chuck and Anatoliy talk about what people should do when they are suffering from a mental illness so that they can do the things they love again. Some of the best ways of coping with mental health issues are to keep a lifeline out to friends and family, go to a professional therapist, stay on a consistent exercise and sleep pattern, and stay away from substances. They talk about how to support someone that is suffering from a mental illness. 

Anatoliy talks about some of the symptoms and behavioral changes he has during both manic and depressive episodes and how it has affected him in the workplace. Mental health issues are almost always accompanied by changes in behavior, and Chuck and Anatoliy talk about ways to approach a person about their behavior. Anatoliy gives advice on how to work with your employer while you are suffering from a mental illness. For mental illnesses that aren’t as dramatic as Bipolar Disorder, Anatoliy talks about coping mechanisms such as staying away from triggers, knowing what motivates you and communicating it to your employer, and other practices that have helped him. He talks about some of his triggers and how it has affected his work, both for the better and worse.

 Finding out what helps you cope and what triggers you is often trial and error, but it can help to talk to other people in your field who struggle with the same mental health issues. Anatoliy talks about the pros and cons of working from home or in an office when you have a mental illness. They finish by talking about a few other points on mental health and resources for those suffering from a mental illness to get the help they need. 

Links

• Bipolar disorder

• Pickle.js 

• Ketamine therapy

• Ruby Rogues ep. 142: Depression and Mental Illness with Greg Bauges

• JSJ 358: Pickle.js Tooling and Developer Happiness with Anatoliy Zaslavskiy

• NAMI

• DBS Alliance

Follow DevChat on Facebook and Twitter

Picks

Charles Max Wood:

• ExpressVPN

Anatoliy Zaslavskiy:

• Contact Anatoliy at toli@toliycodes.com

• Visit his website tolicodes.com

• Misu app (in beta)

Vitali Zaidman is a full stack developer who works for WellDone Software Solutions and is currently working on a SEO project. Today’s show is about SEO for developers. SEO stands for search engine optimization, which helps your website appear higher on search engines.

 SEO has changed a lot in the past 10 years. It has become much more regulated, and the “dirty tricks” of the past will actually penalize you, so it is important to do it properly. Today the best way to promote yourself on Google besides making good content is for developers to optimize the content, make it small, operational, secure, accessible, and operate on mobile. Much of it goes back to using semantic HTML since Google looks at it before looking at the structure of your website, how valuable it is, and how users interact with it. Having good semantics helps Google determine how valuable it is, so semantic HTML should be a top priority. Semantic HTML can also make your site more accessible to users, which will in turn give you a larger audience. 

The panel talks about some of the challenges of SEO faced by companies. While bigger companies have the privilege of dedicated SEO teams, small companies often lack these specialists. Thankfully, Google has made their guidelines for SEO very accessible and gives you a lot of tools to track your optimization. The panel talks about different methods of SEO, such as including FAQ at the bottom of the web page, optimizing page speed, and image optimization. Structured data like questions and answers enriches the data that is shown for users on the search results page. To score your website’s SEO, Google released the tool PageSpeed Insights, which will assign your website a performance score. 

Google uses two main tools to track a website’s SEO. First, they use real field data. If you opt in to ‘help improve Chrome’s features and performance’ when you install Chrome, it tracks how fast websites load on your Chrome, and they collect this information to understand how webpages load. It is required that your website has a certain amount of visitors to be tracked and added to the database. Second, Google has their own devices that will check your website. Currently, they are using a Moto G4 to test for mobile access, and a slow internet connection. Because of this, it is pretty easy to get a good score on desktop, but difficult to get a good score on mobile. The technology that drives all this is called Lighthouse. 

Overall, performance is the main thing users look for, so aim for good performance and fast websites. The panel discusses the correlation between performance and SEO. For example, Fox News and CNN are two of the top search results for ‘news’, but they have a dismal Google PSI score. They conclude that performance shouldn’t be ignored, but be careful about directly correlating performance and SEO. They also caution against getting obsessed over certain aspects of SEO by themselves. 

Panelists

• Dan Shapir

• Aimee Knight

• Charles Max Wood

With special guest: Vitali Zaidman

Sponsors

• Tidelift

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

• Elixir Mix

Links

• SEO

• JSON

• Google Webmaster guidelines

• Google PageSpeed Insights

• Chrome CrUX

• Lighthouse

• Here's How the Google Speed Update Will Impact Your Site

• SEO for Developers - A Quick Overview

• Google Quality Guidelines

Follow DevChatTV on Facebook and Twitter

Picks

Aimee Knight:

• Spotify CLI

Dan Shapir:

• Chrome Dev Summit 2019

• Dan Shapir on Twitter

• The Anubis Gates

Charles Max Wood:

• St. George Marathon

Vitali Zaidman: 

• Vitali’s website

• Arzamas Academy

• Follow Vitali on Medium and Twitter

Park, Jane Chi Hyun

Stadler, Nurit

Sachdev, Perminder

Watkins, S. Craig (Samuel Craig)

Helman, Anat

Mansfield, Natalie

Vitale, Joe, 1953-

Spencer, Scott, 1975-

This study develops and validates a quantitative method to predict the pulmonary to systemic flow ratio in patients with congenital heart disease from chest radiographs using deep learning.

This cohort study assesses whether long-term variability and rate of change of blood pressure from young adulthood to midlife are associated with cardiovascular disease and all-cause mortality by middle age.

This study developed and validated a prognostic prediction model for patients with heart failure.

To the Editor We read the recent article by Klauser et al with great interest. While the potential implications of the findings are exciting, we have several concerns. First, the authors do not explicitly state whether electrocardiogram gating was used in their study. This is an important detail because cardiac motion artifact is a source of artifactual coloration with dual-energy computed tomography (DECT), particularly with dual-source scanners given the approximately 80-millisecond temporal difference between the 2 radiography beams. Furthermore, beam hardening artifact from calcified atheromas and partial volume effect, known sources of artifacts in the 2-material decomposition algorithm of DECT, may largely explain the findings. While patients with gout had higher prevalence of coronary calcification (55 of 59 patients [93%]) and cardiovascular monosodium urate (MSU) deposition (51 of 59 patients [86%]) than controls, the authors do not report whether the 4 patients with gout without coronary calcifications exhibited MSU deposition nor the number of controls or cadaveric hearts with coronary calcification. The images from the article show areas of green pixelization occurring adjacent to calcified plaques on grayscale computed tomography images (eg, Figure 2A and D, left anterior descending artery [yellow arrowhead]), which would favor this artifact hypothesis without additional data.

In Reply We appreciate the valuable comments of Becce et al on our article. We applied prospective electrocardiography gating using a thin-slice cardiac protocol to ensure highest spatial resolution with minimal motion artifact. A noncontrast electrocardiography-gated computed tomography (CT) examination with standardized scan parameters was performed using a 128-slice dual-source CT (SOMATOM Definition Flash; Siemens) with a detector collimation of 2 × 64 × 0.6 mm, rotation time of 0.28 seconds, and prospective electrocardiography triggering for heart rates less than 65 beats per minute (diastolic padding, 70% of RR interval) and more than 65 beats per minute (systolic padding, 40% of RR interval). Axial images were reconstructed with 0.75-mm slice width, increment of 0.5, and a medium-smooth convolution kernel (B26f). When motion artifact was present, it was distinguished by visual analysis of an experienced observer and colorized pixels related to motion were excluded.