Tropicana Joint Venture

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.)

ALTA Gold Conference (2nd : 2011 : Perth, W.A)

ALTA Uranium Conference (7th : 2011 : Perth, W.A)

ALTA Nickel/Cobalt/Copper Conference (2nd : 2011 : Perth, W.A)

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

ALTA Uranium Conference (8th : 2012 : Perth, W.A)

ALTA Nickel/Cobalt/Copper Conference (3rd : 2012 : Perth, W.A)

Cocks, Robert J., author

Garrett, Donald E., author

The government has geared up to roll out the delivery of quality rice at the door steps of beneficiaries from September 1. It already launched a pilo

The panelists talk about SVG and data visualization with Chris Bannon.

Panel Tom Dale (twitter github blog Tilde Inc.) James Halliday (twitter github substack.net) AJ O’Neal (twitter github blog) Jamison Dance (twitter github blog) Merrick Christensen (twitter github) Joe Eames (twitter github blog) Tim Caswell (twitter github howtonode.org) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 01:52 - James Halliday Introduction browserify 02:37 - Tom Dale Introduction iCloud Ember.js Big Data & Hadoop 04:47 - Specialized vs Monolithic github.com/tildeio Idiology Micro Libraries 14:13 - Learning Frameworks 18:04 - Making things modular 25:23 - Picking the right tool for the job 27:44 - voxel.js & emberjs emberjs / packages BPM - Browser Package Manager NPM - Node Packaged Modules testling-ci Backbone.js 38:19 - Module Systems CommonJS 41:14 - Cloud9 Use Case 43:54 - Bugs jQuery Source Code Picks jQuery 2.0 (Merrick) ECMAScript 6 Module Definition (Merrick) AMD (Merrick) Yiruma (Joe) Elementary (Joe) Miracle Berry Tablets (AJ) The Ubuntu You Deserve (AJ) Bravemule (Jamison) RealtimeConf Europe (Tim) visionmedia / cpm (Tim) Why I Love Being A Programmer in Louisville (or, Why I Won’t Relocate to Work for Your Startup: Ernie Miller (Chuck) Is Audio The Next Big Thing In Digital Marketing? [Infographic] (Chuck) testling-ci (James) voxel.js (James) CAMPJS (James) Discourse (Tom) Williams-Sonoma 10-Piece Glass Bowl Set (Tom) The Best Simple Recipes by America’s Test Kitchen (Tom) Next Week Why Javascript is Hard Transcript JAMISON:  You can curse but we will just edit it out and replace it with fart noises. TOM:  I’ll be providing plenty of my own. [Laughter] JAMISON:  Okay, good. [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.] CHUCK:  Hey everybody and welcome to Episode 47 of the JavaScript Jabber show. This week on our panel, we have AJ O’Neal. AJ:  Yo! Yo! Yo! Coming at you not even live! CHUCK:  [Laughs] Alright, Jamison Dance. JAMISON:  Hi guys, it’s tough to follow that. CHUCK:  Merrick Christensen. MERRICK:  Hey. CHUCK:  Joe Eames. JOE:  Howdy! CHUCK:  Tim Caswell. TIM:  Hello. CHUCK:  I’m Charles Max Wood from DevChat.tv. And this week, we have two guests. The first one is Tom Dale. TOM:  Hey, thanks for having me. CHUCK:  The other is James Halliday. JAMES:  Yep. Hello. CHUCK:  Welcome to the show, guys. We were having a conversation a while back, I don’t remember if it was during another episode or after another episode. But we were having a discussion over code complexity and having like small simple libraries or small simple sets of functionality versus large monolithic sets of functionality, and how to approach those and when they’re appropriate. So, we brought you guys on to help us explore this because you're experts, right? TOM:  I don’t think that’s a fair analysis of the situation, but we can certainly fumble our way through something. [Laughter] CHUCK:  Alright. So, why don’t you guys, real quick, just kind of introduce yourselves? Give us a little background on what your experience is so that we know which questions to ask you guys. James, why don’t you start? I know you’ve been on the show before. JAMES:  Hello. I suppose I wrote Browserify which is relevant here. It’s a common JS style, bundler packager thing that just uses NPM. And I have a bunch of other libraries. And I really like doing data development as just a bunch of little modules put together. They are all published completely independently on NPM. I think I’m up to like 230-ish some odd modules on NPM now. So, I’ve been doing that and I really like that style.

The panelists talk to Matt DeBergalis about Meteor.js.

02:43 - Oren Rubin Introduction

• Twitter
• GitHub
• LinkedIn
• TESTIM.IO

05:43 - Testing

• Unit Testing
• End-to-end Testing
• Acceptance Testing
• Functional Testing
• Performance Testing

18:18 - Page Object(s)

• Locators

27:10 - Protractor & Selenium

• Zombie

32:06 - Checking UI (Screenshots)

37:04 - End-to-end > Full Coverage?

40:03 - When should you start testing?

42:21 - Cucumber

45:39 - Debugging

Picks

Paul Ford: 10 Timeframes (Jamison)
Kishi Bashi - “In Fantasia” (Jamison)
Matt Zabriskie (Jamison)
http-backend-proxy (Aimee)
repl.it (Aimee)
React.js Training with Michael Jackson and Ryan Florence (Joe)
React Rally (Joe)
AngularConnect (Joe)
ng-conf (Joe)
Ruby Remote Conf Videos (Chuck)
Angular Remote Conf (Chuck)
15 Minute Podcast Listener chat with Charles Wood (Chuck)
Dave Haeffner: Elemental Selenium (Oren)
CSS Secrets by Lea Verou (Oren)
Cloudinary (Oren)

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

•  Datadog

• Sentry use code “devchat” for 2 months free

Panel

• Aimee Knight

• Chris Ferdinandi

• Christopher Beucheler

• AJ O’Neal

With Special Guest: Javan Makhmali

Episode Summary

Today’s guest is Javan Makhmali, who works for Basecamp and helped develop Trix. Trix is a rich text editor for the web, made purposefully simple for everyday use instead of a full layout tool. Trix is not the same as Tiny MCE, and Javan discusses some of the differences. He talks about the benefits of using Trix over other native browser features for text editing. He talks about how Trix has simplified the work at Basecamp, especially when it came to crossing platforms. Javan talks more about how Trix differs from other text editors like Google Docs and contenteditable, how to tell if Trix is functioning correctly, and how it works with Markdown.

The panel discusses more specific aspects of Trix, such as Exec command. One of the features of Trix is it is able to output consistently in all browsers and uses semantic, clean HTML instead of classnames. Javan talks about how Trix handles getting rid of the extraneous cruft of formatting when things are copy and pasted, the different layers of code, and the undo feature. He talks about whether or not there will be more features added to Trix. The panel discusses who could benefit from using Trix. The show finishes with Javan talking about Basecamp’s decision to make Trix open source and why they code in CoffeeScript. 

Links

• Trix

• Tiny MCE

• Contenteditable

• Markdown

• SVG

• HTML

• CoffeeScript

Follow DevChat on Facebook and Twitter

Picks

Javan Makhmali:

• API for form submissions

Chris Ferdinandi:

• CSS Grid

• Alex Russel Twitter thread

• How To Live a Vibrant Life with Early Stage Dementia

AJ O’Neal:

• Mario and Chill

• Chip Tunes 4 Autism: Catharsis

• Toilet Auger

Christopher Beucheler: 

• Medium to Own blog

Aimee Knight:

• Absolute Truth Unlearned as Junior Developer

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

This week, My Javascript Story welcomes Javan Makhmali,a Programmer at Basecamp from Ann Arbor, Michigan. Javan attended Community College to study Computer Science but then decided to work as a Freelancer developer. Javan and Charles debate whether having a 4-year college degree is better to become a developer and conclude that it depends on the person. Some people prefer a structured 4 year degree to feel ready for a full time jo and some people do better with bootcamps. Javan mentions he knows several people that switched careers after completing an 8 week bootcamp and that the industry was really flexible to accomodate both options.

Charles and Javan then continue talking about Javan's journey as a developer and particularly his journey with Basecamp. Javan started out working with Ruby on Rails and after a couple of years applied for a job at Basecamp (then known as 37 Signals). Javan then started working with CoffeeScript which helped him understand working with JavaScript.

Charles and Javan talk about the projects Javan is working on currently at Basecamp. Outside of work Javan, is a new parent and enjoys spending time with his daughter. He feels ever since he has become a parent, his work life balance has been better.

Host: Charles Max Wood

Joined by Special Guest:  Javan Makhmali

Links

• JSJ 376: Trix: A Rich Text Editor for Everyday Writing with Javan Makhmali

• Javan's Twitter

Sponsors

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

• Dev Ed Podcast

• Adventures in Blockchain

• CacheFly

Picks

Charles Max Wood:

• https://maxcoders.io/

Sasson, Diane, 1946-

Bell, Vereen M., 1934-

Stadler, Nurit

ʻAmr, Sāmī, 1924-1998

Chelpi-den Hamer, Magali

Mansfield, Natalie

Aliber, Robert Z

Lahire, Nathalie

Straker, Jay, 1967-

Chrétien, de Troyes, active 12th century

Chrétien, de Troyes, active 12th century

Mentinis, Mihalis

Barsky, Robert F

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.

Economist, government official, and director of the Congressional Budget Office. Correspondence, memoranda, reports, speeches and other writings, congressional testimony, printed materials, newspaper clippings, and photographs pertaining to Rivlin's career as an economist and government official.

O'Toole, Peter Martin, author

Australia. Parliament. Senate. Environment and Communications References Committee, author

Kondo, Manabu, author

Weyler, Rex, 1947-