ALTA Gold Conference (3rd : 2012 : Perth, W.A)

Louis, Catherine Dr

Chappell, Marianne Diane, author

Woodward, Travis M., author

Cocks, Robert J., author

ALTA Gold-PM Conference (7th : 2016 : Perth, W.A.)

The Government of India has taken a $500 million loan from the Asian Infrastructure Investment Bank to support its emergency response to the COVID-19

Retail investors continued to enter markets via systematic investment plans

TVS Srichakra Ltd. has enabled its retail partners either to place or track orders through its app ‘TVS Eurogrip Bandhan’ as part of its move to aid s

Revision necessitated due to pandemic

‘Reasons for the accident yet to be ascertained’

‘It may take up to 48 hours to neutralise styrene vapours’

The panelists have Igor Minar back on the show to discuss AngularJS in detail.

The panelists talk to Rob Dodson and Eric Bidelman about the Google Polymer project and Google I/O.

JS Remote Conf 2016 will be from January 14th-16th from noon-4:30PM ET! Get your early bird tickets or submit a CFP now thru December 14th!

02:46 - Panel Consensus and Experience and Career Paths

16:00 - The School Doesn’t Matter

• David and Goliath: Underdogs, Misfits, and the Art of Battling Giants by Malcolm Gladwell

19:59 - Panel Experience and Career Paths (Cont’d)

38:36 - Practically Helpful Knowledge and Disciplines; Interviewing and Hiring

46:38 - Privilege and Navigating Without Opportunity

49:54 - Why get a degree if it’s not necessary?

• Support Structure

01:02:13 - Consensus Part 2

Picks

The More Things Change (Jamison)
Allison Kaptur: Effective Learning Strategies for Programmers (Jamison)
@Aimee_Knight (Joe)
Star Wars Battlefront (Joe)
Amazing Grass (Aimee)
Daniel Brain: Sane, scalable Angular apps are tricky, but not impossible. Lessons learned from PayPal Checkout. (Aimee)
xkcd: Correlation (Dave)
Lviv, Ukraine (Dave)
CharlesMaxWood.com (Chuck)
Every Time Zone (Chuck)
The Positioning Manual for Technical Firms by Philip Morgan (Chuck)
JS Remote Conf (Chuck)

02:54 - John A. De Goes Introduction

• Twitter
• GitHub
• Blog
• SlamData

06:34 - Phil Freeman Introduction

• Twitter
• GitHub
• Blog

07:38 - What is PureScript?

09:11 - Features

• Extensible Effects

12:24 - Overcoming the Vocabulary Problem in Functional Programming

• Gang of Four Book (Design Patterns)
• purescript-halogen

20:07 - Prerequisites to PureScript

26:14 - PureScript vs Elm

• JavaScript Jabber Episode #175: Elm with Evan Czaplicki and Richard Feldman
• No Runtime
• General Purpose vs UI-Focused
• Generic Containers

40:37 - Similar Languages to PureScript

44:07 - PureScript Background

• Roy

47:48 - The WebAssembly Effect

51:01 - Readability

53:42 - PureScript Learning Resources

• PureScript by Example by Phil Freeman
• PureScript Conf 2015/6

55:43 - Working with Abstractions

• purescript-aff
• Audrey Popp: Fighting Node Callback Hell with PureScript

Picks

Philip Robects: What the heck is the event loop anyways? @ JS Conf EU 2014 (Aimee)
loupe (Aimee)
The Man in the High Castle (Jamison)
Nickolas Means: How to Crash an Airplane @ RubyConf 2015 (Jamison)  
Lambda Lounge Utah (Jamison)
Michael Trotter: Intro to PureScript @ Utah Haskell Meetup (Jamison)
Utah Elm Users (Jamison)
Screeps (Joe)
Most Likely to Succeed: Preparing Our Kids for the Innovation Era by Tony Wagner (Joe)
Dark Matter (Joe)
LambdaConf (John)
@lambda_conf (John)
ramda (John)
Proper beef, ale & mushroom pie (John)
Tidal (Phil)
purescript-flare (Phil)
The Forward JS Conference (Phil)

03:08 - John A. De Goes Introduction

• Twitter
• GitHub
• Blog
• SlamData

04:07 - PureScript

JavaScript Jabber Episode #189: PureScript with John A. De Goes and Phil Freeman

04:58 - “Purely Functional”

09:18 - Weaknesses With Functional Programming

• Object-oriented Programming
• Procedural Programming

14:36 - Organizing a FP Codebase

• John A. De Goes: A Modern Architecture for FP

17:54 - Beginners and Functional Programming; Getting Started

• Learning About the History of Functional Programming
• Hiring Junior Devs to do FP

28:20 - The Rise of Functional Programming in JavaScript-land

32:08 - Handling Existing Applications

36:03 - Complexity Argument

41:53 - Weighing Language Tradeoffs; Alt.js

Picks

• Nadia Odunayo: The Guest: A Guide To Code Hospitality @ RailsConf 2016 (Aimee)
• React Rally (Jamison)
• Cleanup Algorithm (Jamison)
• PostgreSQL Exercises (Jamison)
• iPad Pro (Chuck)
• Smart Keyboard for iPad Pro (Chuck)
• Apple Pencil (Chuck)
• GoodNotes (Chuck)
• John A. De Goes: Halogen: Past, Present, and Future (John)
• slamdata (John)

02:50 The definition of a plug-in

03:31 The definition of an extension

05:09 The way to determine the plug-ins and extensions you are running

08:22 How to create an extension file

11:02 The appeal of creating extensions

13:26 How John got into creating extensions

15:48 Ways to organize extensions

19:38 Aspects of chrome that will affect extensions

23:23 Packaging for the Chrome store

26:22 Using dev tools

29:42 Conflicting plug-ins/extensions and how to deal with them

31:30 Open source extensions

32:32 A quick way to create an extension

QUOTES:

“I teach software developers how to be cool.” –John Sonmez

“There wasn’t an ability to extend the dev tools, but now there is.” –John Sonmez

“One quick way to create an extension is just to take one of these sample apps…and then just start modifying it…” –John Sonmez

PICKS:

“Django Unchained” Website

“Using Angular 2 Patterns in Angular 1.x” Apps Egghead Course

Girls’ Life vs. Boys’ Life on Refinery29

Webinar Jam Software

“Five Mistakes That are Keeping You From Getting Hired” Webinar

Screencastify Chrome Extension

How to Fail at Almost Everything and Still Win Big Book on Amazon

The Complete Software Developers Career Guide Book in Progress

Simple Programmer Website

Simple Programmer on Youtube

On today's episode, Charles Max Wood and Aimee Knight discuss GraphQL and Apollo with Uri Goldshtein. Uri is a core developer at Meteor Development Group, and is an expert with GraphQL and Apollo.

On today's JavaScript Jabber Show, Aimee Knight, Cory House, and Charles Max Wood discuss Gomix with Daniel X Moore. Daniel is a Software Developer at Fog Creek Software, and has been in the industry for 10 years. Their company currently offers an amazingly convenient way to build apps. Tune in to learn about it!

On today's episode, Charles, Joe, and Cory discuss Practical JavaScript with Gordon Zhu. Gordon is the founder of Watch and Code, and teaches the Practical JavaScript online course. His mission is to help beginners become developers through tutorials. Tune in!

Panel: 

Charles Max Wood

Joe Eames

Aimee Knight

Special Guests: Russell Goldenberg and Adam Pearce

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

In particular, we dive pretty deep on:

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

Links:

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

Picks:

Adam

• Dominion - Broad Game

Charles

• Smoker
• Tiny Epic Galaxies
• Indiegogo Dev Chat TV

Aimee

• Deadlines
• Quest Protein Powder

Joe

• Giving!
• Board Game - Azul

Russel

• Crokinole
• Bust Out

Panel: Charles Max Wood

Guest: Gordon Zhu

This week on My JavaScript Story, Charles speaks with Gordon Zhu. Gordon is the founder of Watch and Code. The mission of the company is to take total beginners and turn them into amazing developers. He first got into programming by trying to avoid programming. He studied business in college and was really interested in the internet, leading him to have to learn coding. He talks about the importance of being focused, especially in the beginning, and the ability to figure things out.

In particular, we dive pretty deep on:

• Watch and Code
• How did you first get into programming?
• Studied business in college
• Peak
• Two different eras of programmers
• There is more than one way to get into programming
• Culture is promoting a new way of thinking about technology
• Black Mirror
• How did you get into JavaScript?
• Marketing, product management, and engineering
• Angular
• Tried to avoid JS and focused on Python
• Importance of focus
• The ability to figure things out
• How to spend your time in the beginning
• Current focus
• Focus gives you freedom
• Reading a lot of code
• What are you proud of?
• And much, much more!

Links:

• JavaScript
• Watch and Code
• Peak
• Black Mirror
• Angular
• Python
• @Gordon_Zhu
• Practical JavaScript

Picks

Charles

• 4k Camcorder
• 25 ft XLR Cables
• Zoom H6
• Roland R-09
• USB-C Dongle Docking Station
• ScreenFlow
• PB Works

Gordon

• How I Built This podcast
• Stay Tuned with Preet podcast

Panel:

• Charles Max Wood

Special Guests: Ori Zohar and Gopinath Chigakkagari

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

In particular, we dive pretty deep on:

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

Links:

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

Sponsors

• Kendo UI
• Linode
• FreshBooks

Picks:

Charles

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

Ori

• Fitbit
• Pacific Northwest Hiking

Gopinath

• Seattle, WA

Sponsors

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

Panel

• Joe Eames

• AJ O’Neal

Episode Summary

In this episode of JavaScript Jabber, Joe Eames and AJ O’Neal talk about what TypeScript is, and their background and experiences with it. They discuss the different kinds of typed languages such as dynamic vs static, strong vs weak, implicit vs explicit casting and the reasons for selecting one type over the other. AJ shares his opinion on not preferring TypeScript in general, while Joe offers a counter perspective on liking it, and both give a number of reasons to support each argument. They talk about some final good and bad points about TypeScript and move on to picks.

Links

• TypeScript
• CoffeeScript

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

Picks

Joe Eames:

• Cypress
• What if your dev environment was a PWA? ???? | Eric Simons
• Angular 8 Intergalactic
• Star Wars Tantive IV Lego set

AJ O’Neal:

• Measure What Matters
• @root on npm
• @bluecrypt on npm

Episode Summary

Rachel Roumeliotis and Roger Magoulas from O'Reilly Media join Charles Max Wood at OSCON to talk about the process of content development for OSCON. Rachel is the Vice President of Content Strategy at O'Reilly and Roger is Vice President of Radar at O'Reilly.

Rachel and Roger talk about the history of OSCON Conference as well as the key technologies they wanted to cover this year such as Artificial Intelligence, Machine Learning and Cloud-Native applications.

They then talk about the future of OSCON and the highlights they wat to cover next year such as security.

Sponsors

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

• Adventures in DevOps

• Adventures in Blockchain

• CacheFly

Host: Charles Max Wood

Joined by Special Guests: Rachel Roumeliotis and Roger Magoulas

Links

• Rachel's LinkedIn

• Roger's LinkedIn

• Open Source & Software Development| O'Reilly OSCON

• O'Reilly Radar

• O'Reilly Media - Technology and Business Training

   

Tanmai is one of the founders at Hasura. Hasura gives you instant graphQL APIs on top of a Postgres database. The eventual idea is to make data access secure and easy. Tanmai explains the challenges of doing this in the cloud. He talks about some of the difficulties with the tooling around using GraphQL and its bias towards working well with a monolith. Since GraphQL is basically a shared type system that describes your API, that means all your types need to be in the same code base. This is at odds with the folks who want to do microservices and serverless functions, because since their API is split across multiple services they have different types, and forcing these types to work together defeats the purpose of using microservices. Also, storing state across requests doesn’t work well with serverless and cloud native stuff. In short, learning to live without state is one of the general challenges with going serverless. 

This is where Hasura comes into play, and Tanmai explains how it works. Hasura is metadata driven, and each instance of the server can leverage multiple calls and exhibit a high amount of concurrency. It’s designed to be a little more CPU bound than memory bound, which means that configuring auto scaling on it is very easy and allows you to utilize the elasticity of cloud native applications. Tanmai clarifies his usage of the word ‘cloud native’, by which he means microservices. He explains that when you have a metadata based engine, this metadata has a language that allows you to bring to bring in types from multiple upstream microservices, and create a coherent graphQL API on top of that. Hasura is a middle man between the microservices and the consumer that converts multiple types into a single coherent graphQL API.

Next, Tanmai explains how Hasura handles data fetching and a high volume of requests. They also invented PostgresQL, RLS-like semantics within Hasura. He explains the process for merging your microservices into a single graphQL interface. Back on data fetching, Tanmai explains that when the product is an app, preventing an overabundance of queries becomes easier because during one of the staging processes that they have, they extract all of the queries that the app is actually making, and in the production version it only allows the queries that it has seen before. Hasura is focused on both the public interface and private use cases, though private is slightly better supported. 

Tanmai talks about the customizations available with Hasura. Hasura supports two layers. One is an aliasing layer that lets you rename tables, columns, etc as exposed by PostgresQL. The other is a computer column, so that you can add computer columns so you can extend the type that you get from a data model, and then you can point that to something that you derive. 

The panelist discusses the common conception of why it is a bad idea to expose the data models to the frontend folks directly. They discuss the trend of ‘dumbing down’ available tooling to appeal to junior developers, at the cost of making the backend more complicated. They talk about some of the issues that come from this, and the importance of tooling to solve this concern. 

Finally, Tanmai talks about the reasons to use Hasura over other products. There are 2 technologies that help with integrating arbitrary data sources. First is authorization grammar, their version of RLS that can extend to any system of types and relationships, The second is the data wrapper, part of the compiler that compiles from the graphQL metadata AST to the actual SQL AST. That is a generic interface, so anyone can come in and plug in a Haskell module that has that interface and implement a backend compiler for a native query language. This allows us to plug in other sources and stitch microservices together. The show concludes with Tanmai talking about their choice to use Haskell to make Hasura. 

Panelists

• AJ O’Neal

• Dan Shapir

• Steve Edwards

• Charles Max Wood

With special guest: Tanmai Gopal

Sponsors

• Adventures in DevOps

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

• The Dev Ed Podcast

Links

• Hasura

• Haskell

• Node.js

• Cloud Native

• Microservices 

• PostGraphile 

• Postgres 

• PostgresQL RLS

• Swagger

• JAMstack

• Soap

• Rest

Follow DevChatTV on Facebook and Twitter

Picks

AJ O’Neal:

• The Economic Singularity

• Capital Cities

• GameCube Homebrew

Dan Shapir:

• Romania

• JSCamp

Steve Edwards:

• Cold Blooded: The Clutter Family Murders

Charles Max Wood:

• Maxcoders.io

• TripIt

• St. George Marathon

• VO2 Max app

Tanmai Gopal: 

• Follow Tanmai on Twitter @tanmaigo

• Broken Earth Trilogy

• The Three-Body Problem

• graphQL Asia

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!

____________________________________________________________

Links

• G Suite

• AppScript

• Clasp

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

Betts, Dion E. (Dion Emile), 1963-

Mass, Jeffrey P

Kennedy, Theodore R., 1936-

Drake, Chris

Florescu, Liviu C

Teixeira, Joe

Filmer, Deon, author

Chase, Michael

Crnobrnja, Mihailo

Krupnik, Igor

González, Roberto J. (Roberto Jesús), 1969-

McKinney, Gordon B., 1943-

Rotenstreich, Nathan, 1914-1993

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.