ALTA Uranium Conference (4th : 2008 : Perth, W.A)

ALTA Copper Conference (12th : 2008 : Perth, W.A)

ALTA Nickel/Cobalt conference (13th : 2008 : Perth, Australia)

ALTA Gold Ore Processing Symposium (1st : 2010 : Perth, W. A.)

ALTA Uranium Conference (6th : 2010 : Perth, W.A.)

ALTA Nickel/Cobalt/Copper Conference (1st : 2010 : Perth, W. A.)

Gupta, A. (Ashok), author

Qi, Dezhi, author

‘Reasons for the accident yet to be ascertained’

Panel Scott Hanselman (twitter github blog) Joe Eames (twitter github blog) Aaron Frost (twitter github blog) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 01:14 - Scott Hanselman Introduction Community Program Manager for Web Tools at Microsoft Azure and Web Tools ASP.NET Runtime 03:17 - Microsoft and JavaScript Microsoft Build Developer Conference Scott Hanselman: Angle Brackets, Curly Braces, One ASP.NET and the Cloud Json.NET 13:40 - The Cost of Web Development Tooling Sublime Text Visual Studio 18:17 - Libraries and Frameworks Knockout 24:14 - Innovation in Software Befunge 29:48 - Apps Supporting JavaScript Create your first Windows Store app using JavaScript (Windows) Visual Studio Express 34:14 - Windows and Internet Explorer Chakra 40:42 - Microsoft’s Attitude Towards JavaScript Scott Hanselman: Azure for the non-Microsoft Person - How and Why? 45:58 - Open Source 49:12 - asm.js 52:05 - Angle Brackets Conference Picks The Wolverine (Joe) ng-conf (Joe) Cancún (Aaron) @ngconf (Aaron) Wistia (Chuck) Mumford And Sons 'Hopeless Wanderer' Music Video (Scott) Beyoncé Joins the Short Hair Club (Scott) Next Week Screencasting: Sharing What You Know Through Video Transcript [Hosting and bandwidth provided by the Blue Box Group. Check them out at BlueBox.net.]  [This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.]  [This podcast is sponsored by JetBrains, makers of WebStorm. Whether you’re working with Node.js or building the front end of your web application, WebStorm is the tool for you. It has great code quality and code exploration tools and works with HTML5, Node, TypeScript, CoffeeScript, Harmony, LESS, Sass, Jade, JSLint, JSHint, and the Google Closure Compiler. Check it out at JetBrains.com/WebStorm.] CHUCK:  Hey everybody and welcome to Episode 71 the JavaScript Jabber show. This week on our panel, we have Joe Eames. JOE:  Hey. CHUCK:  Aaron Frost. AARON:  Hello. CHUCK:  I’m Charles Max Wood from DevChat.TV. And we have a special guest that is Scott Hanselman. SCOTT:  Hello. CHUCK:  Since you’re new to the show, do you want to introduce yourself really quickly? SCOTT:  My name is Scott Hanselman. You can learn more about me on the internet by googling for Scott. I’m in an epic battle right now with the Scott toilet paper people. You’ll find me just below Scott toilet tissue. I’ve been blogging for ten years. More than ten years, 13 years. I work at Microsoft right now. Before that I worked in finance at a company called Corillian that is now Fiserv. I’ve been building big systems on the web for as long as the web’s been around. CHUCK:  Wow. What do you do at Microsoft? SCOTT:  I work in Azure and Web Tools. I’m a program manager. I’m in charge of the experience from file new project until deployment. I call myself the PM of miscellaneous. I spend time going through that experience making sure that it doesn’t suck. My focus is on web tools but also ASP.NET Runtime and what the experience is when you deploy something into Azure. That might be everything from what’s it like editing JavaScript in Visual Studio and I’ll find some issue and go and work with the guys that own that, or it might be someone’s trying to do something in Node on Azure and that experience is not good. I’m like an ombudsman or a customer liaison. But the simplest way would be to say I’m the community PM, community program manager, for web tools at Microsoft. CHUCK:  Okay. AARON:  Cool. CHUCK:  So, is JavaScript your primary focus? SCOTT:  I would say that my primary focus is just anything that makes the web better and moves the web forward. While I work for ASP.NET and most of my work is in C#,

The panelists celebrate their 100th episode!

The Panelists talk to the creator of the Smallest Federated Wiki, Ward Cunningham.

Check out React Remote Conf

01:56 - Valeri Karpov Introduction

• Twitter
• GitHub
• Blog
• JavaScript Jabber Episode #92: The MEAN Stack with Ward Bell and Valeri Karpov

02:17 - Booster Fuels

03:06 - ES2015 Generators

• The 80/20 Guide to ES2015 Generators by Valeri Karpov
• co

05:47 - try-catch

07:49 - Generator Function vs Object

• The Fibonacci Sequence

10:39 - Generator Use Cases

12:02 - Why in ES6 would they come out with both native promises and generators?

• Koa

14:04 - yield star and async await

17:06 - Wrapping a Generator in a Promise

19:51 - Testing

20:56 - Use on the Front-end

22:14 - The 80/20 Guide to ES2015 Generators by Valeri Karpov and Tech Writing

• nightmare
• Professional AngularJS

Picks

Why and How Testing Can Make You Happier (Aimee)
Pitango Gelato (Aimee)
The Primal Blueprint by Mark Sisson (Chuck)
The Primal Blueprint 21-Day Total Body Transformation (Chuck)
acquit (Valeri)
nightmare (Valeri)
now (Valeri)
The 80/20 Guide to ES2015 Generators by Valeri Karpov (Valeri)

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

Panel:

Amiee Knight

Charles Max Wood

Special Guests: 

Kye Hohenberger

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

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

In particular, we dive pretty deep on:

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

Links:

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

Picks:

Amiee

• Article on Medium
• Antibiotics and Steroids
• RX Bars 

Charles

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

Kye

• Styled System
• Face Paint
• Aussie Bites 

Panel: 

Charles Max Wood

Aimee Knight

Cory House

AJ O'Neal

Joe Eames

Special Guests: None

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

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

In particular, we dive pretty deep on:

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

Links:

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

Picks:

Charles

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

Aimee

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

Cory

• JavaScript Tip Tweet
•  

AJ

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

Joe

• WebFlow.com

Panel:

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

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

In particular, we dive pretty deep on:

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

Links:

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

Picks:

Charles

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

Aimee

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

Joe

• SaltCON
• Stuffed Fables Board Game

AJ

• UniFi AC Lite
• Fullmetal Alchemist

Orta

• The Wire
• Worm Web Serial

Sponsors

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

Panel:

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

Notes:

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

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

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

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

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

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

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

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

Picks:

Charles Max Wood

• Villainous Board Game

Joe Eames

• Azul Stained Glass Board Game

AJ O’Neal

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

Aimee Knight

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

Aaron Frost

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

Chris Ferdinandi

• https://learnvanillajs.com/

Tim Caswell

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

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

Today the panel is discussing iterating on open source projects. Aimee and AJ recall a conversation they had in the past on this subject and AJ talks about some of his experience iterating with open source. AJ believes that we have an obligation to capture the value of what you create so that we can reinvest and create more value, though he admits that making money in open source is a unique challenge because donations only really work if you have a project that gets billions of downloads a month. As your project grows, it has to change in order to survive, and eventually you will need to get financial support from your project. The panel agrees that some of the main issues with iterating in open source are maintaining the code and getting feedback from users, financial backing, and roadmapping and integrations.

The panel discusses their methods for getting feedback from their users. This feedback is valuable because it can show you things that you missed. They acknowledge that there can be conflicts of interest between those who only use the project and those who financially support it, and you have to make a choice. Unfortunately, someone is probably going to be inconvenienced no matter what choice you make. When making these decisions, you have to consider who it helps, who it frustrates, and who it may cause problems for. The panelists talk about different ways they’ve handled making these decisions in the past. The JavaScript experts talk about the importance of having data on your user base in order to make good choices for your users. They talk about different methods for notifying your users of upcoming changes and how it will affect compatibility, and some of the challenges with communicating with your users. AJ talks about an iteration he thought was a good idea but that a lot of people hated and how he noticed that the new users liked it but the old users did not. They panel agrees that people in general don’t like change. AJ talks about what he learned from this experience. 

Another common issue is integrating with other services. Integrating with cloud services, or at least giving people the option to integrate gives you an opportunity to reach more people and maintain the project long term. AJ gives some final thoughts to close the show, namely that most projects never go anywhere, and that’s ok. If you’ve got something that starts going somewhere, think early on about how you can better serve the community and remember that these people are mostly grateful and semi-willing to support you. He believes that if you are helping people create value, you deserve to see the fruits of your labor. He advises listeners to stay true to your open source ideals, think about your users perspective, and that the earlier you can think about this and make these choices, the better it is for your project

Panelists

• Aimee Knight

• Steve Edwards

• AJ O’Neal

• Charles Max Wood

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

Sponsors

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

Links

• How-npm-am-i

• React

• Vue.js

• Let’s Encrypt

• Async/await

• Node

Picks

Aimee Knight:

• Debug Like a Ninja

Steve Edwards:

• Jack Ryan 

AJ O’Neal:

• Why I, as a black man, attend KKK meetings

Charles Max Wood:

• It’s a Wonderful Life

• Mr. Kreuger’s Christmas

Konicek-Moran, Richard

Vinitzky-Seroussi, Vered

Chesterman, Simon

Watkins, S. Craig (Samuel Craig)

Levy, Jared, 1976-

Lakes, Richard D

Chase, Michael

Anglin, Douglas George

Cousineau, Robert Henri

Mruk, Christopher J

Rotenstreich, Nathan, 1914-1993

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.

Increased attention has focused on shared decision-making (SDM) and use of decision aids for treatment decisions in cardiology. In this issue of JAMA Cardiology, Coylewright et al report the results of a rigorously performed pilot study on the use of a decision aid to facilitate SDM for patients with symptomatic severe aortic stenosis (AS) at high or prohibitive risk for surgery considered for transcatheter aortic valve replacement vs medical therapy. Comparisons were made between encounters before clinicians were trained to use a decision aid and the first and fifth encounters after a decision aid was used. The patient-clinician interactions were audio recorded and later coded by independent reviewers using a validated measure to assess SDM. This mixed-methods study found that SDM significantly improved in a stepwise manner from the initial usual care encounter (before use of a decision aid) to the first and then fifth encounters after implementation of the decision aid. Along with this improvement in SDM, patients (n = 35) demonstrated increased knowledge about their treatment choices and reported increased satisfaction in their care with no increase in decisional conflict. In contrast, clinicians (n = 6) reported that they believed they already engaged in SDM prior to use of the decision aid and, after multiple uses of the decision aid, believed patients did not understand or benefit from this tool. The disconnect between clinician and patient perspectives was sobering and has implications for the adoption of decision aids or other tools to facilitate SDM in the clinical setting. Notable limitations of the study, which are acknowledged by the authors, include (1) small sample size (of clinicians and patients); (2) the decision aid is most useful for the relatively smaller number of patients at high or prohibitive risk for surgery for whom transcatheter aortic valve replacement and medical therapy may both be reasonable options; and (3) the lack of diversity in the clinicians (all male), which reflects the current demographics of interventional cardiology and cardiac surgery.

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.

Dewey Library - PQ7070.C65 2018

Dewey Library - PQ7082.P7 W45 2018

With the arrest of Tehsin Akhtar, thought to be Indian Mujahideen (IM) commander of India operations, security agencies have netted another big fish in the fight against terror.