Baylis, Daniel, author

Montgomery, Scott L., author

Dewey Library - QH543.B76 2019

Hayden Library - SB112.5.W35x 2019

Online Resource

Dewey Library - JC330.3.M29 2020

Rodríguez Eugenio, Natalie, author

Brandt, Daniel A

The panelists talk to Daniel Tao, maintainer of Lazy.js.

02:35 - John-Daniel Trask Introduction and Background

• Twitter
• GitHub
• Blog
• Mindscape
  • @MindscapeHQ

04:57 - Raygun.io

• @raygunio

06:23 - Crash Reporting The Right Way

• Error Grouping
• Suppress Notifications

10:06 - Most Common Errors

12:05 - Source Maps

19:16 - Managing Error Reporting in Gross Environments

22:17 - Determining Where The Issue Is

24:45 - Do People Write Their Own Errors?

26:23 - Frameworks Support

28:28 - Collecting Data: Privacy and Security

30:01 - Does working in error reporting make you judgemental of others’ code?

• “DDOSing Yourself”

32:42 - Planning for Rare Exceptions

33:36 - Tactics to Cut Down on Messages

35:53 - Gathering Basic Debugging Information

37:58 - Getting the BEST Information

• Promises
• Stockholm Syndrome

42:24 - The Backend: Node.js

• The raygun4node provider

43:24 - “Creating an Application”

Picks

LDS Connect (AJ)
LDS I/O (AJ)
TED Talk About Nothing (Dave)
OlliOlli 2 Soundtrack (Jamison)
Jurassic Park (Joe)
 ng-vegas (Joe)
WASD CODE 87-Key Illuminated Mechanical Keyboard with White LED Backlighting - Cherry MX Clear (Chuck)
Grifiti Fat Wrist Pad (Chuck)
Thank You Rails Clips Kickstarter Backers! (Chuck)
Mastery by Robert Greene (Chuck)
Ready Player One by Ernest Cline (Chuck)
The Pirates of Silicon Valley (John-Daniel)
littleBits (John-Daniel)

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!

This episode features Moving from Node.js to .NET and Raygun.io with John-Daniel Trask. John-Daniel is the Co-founder and CEO of Raygun, a software intelligence platform for web and mobile. He's been programming for many years, and is originally from New Zealand. Tune in and learn what prompted them to move to the .NET framework!

JSJ 275: Zones in Node with Austin McDaniel

The panel for this week on JavaScript Jabber is Cory House, Aimee Knight, and Charles Max Wood. They speak with special guest Austin McDaniel about Zones in Node. Tune in to learn more about this topic!

[00:01:11] Introduction to Austin

Austin has worked in JavaScript for the past ten years. He currently works in Angular development and is a panelist on Angular Air. He has spent most of his career doing work in front-end development but has recently begun working with back-end development. With his move to back-end work he has incorporated front-end ideas with Angular into a back-end concept.

[00:02:00] The Way it Works

NodeJS is an event loop. There is no way to scope the context of a call stack. So for example, Austin makes a Node request to a server and wants to track the life cycle of that Node request. Once deep in the scope, or deep in the code, it is not easy to get the unique id. Maybe he wants to get the user from Passport JS. Other languages – Python, Java – have a concept called thread local storage. They can associate context with the thread and throughout the life cycle of that request, he can retrieve that context.

There is a TC39 proposal for zones. A zone allows you to do what was just described. They can create new zones and associate data with them. Zones can also associate unique ids for requests and can associate the user so they can see who requested later in the stack. Zones also allow to scope and create a context. And then it allows scoping requests and capturing contacts all the way down.

[00:05:40] Zone Uses

One way Zone is being used is to capture stack traces, and associating unique ids with the requests. If there is an error, then Zone can capture a stack request and associate that back to the request that happened. Otherwise, the error would be vague.

Zones are a TC39 proposal. Because it is still a proposal people are unsure how they can use it. Zones are not a new concept. Austin first saw Zones being used back when Angular 2 was first conceived. If an event happened and they wanted to isolate a component and create a scope for it, they used Zones to do so. Not a huge fan of how it worked out (quirky). He used the same library that Angular uses in his backend. It is a specific implementation for Node. Monkey patches all of the functions and creates a scope and passes it down to your functions, which does a good job capturing the information.

[00:08:40] Is installing the library all you need to get this started?

Yes, go to npminstallzone.js and install the library. There is a middler function for kla. To fork the zone, typing zone.current. This takes the Zone you are in and creates a new isolated Zone for that fork. A name can then be created for the Zone so it can be associated back with a call stack and assigned properties. Later, any properties can be retrieved no matter what level you are at.

[00:09:50] So did you create the Zone library or did Google?

The Google team created the Zone library. It was introduced in 2014 with Angular 2. It is currently used in front-end development.

[00:10:12] Is the TC39 proposal based on the Zone library?

While Austin has a feeling that the TC39 proposal came out of the Zone library, he cannot say for sure.

[00:10:39] What stage is the proposal in right now?

Zone is in Stage Zero right now. Zone JS is the most popular version because of its forced adoption to Angular. He recommends people use the Angular version because it is the most tested as it has a high number of people using it for front-end development.

[00:11:50] Is there an easy way to copy the information from one thread to another?

Yes. The best way would probably be to manually copy the information. Forking it may also work.

[00:14:18] Is Stage Zero where someone is still looking to put it in or is it imminent?

Austin believes that since it is actually in a stage, it means it is going to happen eventually but could be wrong. He assumes that it is going to be similar to the version that is out now. Aimee read that Stage Zero is the implementation stage where developers are gathering input about the product. Austin says that this basically means, “Implementation may vary. Enter at your own risk.”

[00:16:21] If I’m using New Relic, is it using Zone JS under the hood?

Austin is unsure but there something like that has to be done if profiling is being used. There has to be a way that you insert yourself in between calls. Zone is doing that while providing context, but probably not using Zone JS. There is a similar implementation to tracing and inserting logging in between all calls and timeouts.

[00:17:22] What are the nuances? Why isn’t everybody doing this?

Zone is still new in the JavaScript world, meaning everyone has a ton of ideas about what should be done. It can be frustrating to work with Zone in front-end development because it has to be manually learned. But in terms of implementation, only trying to create a context. Austin recommends Zone if people want to create direct contacts. The exception would be 100 lines of Zone traces because they can get difficult.

Another issue Austin has is Node’s native basic weight. Weight hooks are still up in the air. The team is currently waiting on the Node JS community to provide additional information so that they can finish. Context can get lost sometimes if the wrong language is used. He is using Typescript and doesn’t have that problem because it is straightforward.

[00:21:44:] Does this affect your ability to test your software at all?

No, there have not been any issues with testing. One thing to accommodate for is if you are expecting certain contexts to be present you have to mock for those in the tests. After that happens, the tests should have no problems.

Picks

Cory:

• Apple AirPods

Aimee:​

• Blackmill
• Understanding Zones

Charles:

• Classical Reading Playlist on Amazon
• Building stairs for his dad
• Angular Dev Summit 

Austin:

• NGRX Library Redux 

Links

• Twitter
• GitHub

Tweet this Episode

John-Daniel Trask is the CEO and developer at Raygun.io.

JD and Chuck talk in this episode about learning to program as a kid, the arc of JD's career, and entrepreneurship.

Links:

• 154 JSJ Raygun.io Error Reporting and Workflow with John-Daniel Trask
• JSJ 263 Moving from Node.js to .NET and Raygun.io with John-Daniel Trask
• C
• C++
• Delphi
• NetScape Navigator
• VBScript
• JQuery
• Mindscape
• Raygun.io
• CoffeeScript
• Visual Studio
• Scott Hanselman on Dark Matter Developers
• Tensorflow
• Stripe
• @traskjd

Picks:

JD:

• Keygen.sh
• Octopus Deploy
• JavaScript x86

Chuck:

• The Miracle Morning
• Meditations App
• Vision Board App
• LootCrate
• Game of Thrones Journal
• Zelda Theme Journal

Panel: 

Charles Max Wood

Guest: Austin McDaniel

This week on My JavaScript Story/My Angular Story, Charles speaks with Austin McDaniel. Austin is a return guest and was previously featured on JavaScript Jabber episode 275 . Austin talks about his journey getting into programming as an 11year old, to recently, as a web developer with more complex technologies. Austin talks about building widgets, working in Angular, JavaScript, and more in-depth web development on many different platforms. Lastly, Austin talks about his contributions to NGX Charts and speaking at a variety of developer conferences.

In particular, we dive pretty deep on: 

• How did you get into programming? 11 years old
• Cue Basic
• Web developer
• College jobs was in web developing
• IE6
• Building Widgets
• Components
• jquery 
• Web is the future
• How did you get into Angular? 2013, v1.2
• Backbone
• Angular 1 & 2
• NG X Charts
• Speaking at Conferences
• Augmented Reality and VR
• Web AR
• Angular Air Podcast
• Working as a contractor with Google
• and much, much more!

Links: 

• JavaScript Jabber episode 275
• jquery
• http://amcdnl.com
• Angular Air Podcast
• @amcdnl
• github.com/amcdnl
•  

Picks

Austin

• Todd Motto 

Charles

• NG Conf
• Angular Dev Summit
• Angular Air Podcast

This episode of My JavaScript Story is coming to you live from OSCON. Joining Charles Max Wood is Daniel Gruesso from GitLab to talk about developing in the Open Source and the Developer Report.

GitLab works with an open core model, Daniel talks about the trade - offs of having code open to public, the first of which is having everything up-to-date so any contributions made will work with the latest version. Daniel calls this the "bus-factor" where if one of the team members gets hit by a bus, the rest of the team will have everything to work with.

They then talk about the GitLab 2019 Global Developer Report results. One of the most interesting results of this survey with over 4,000 respondents, was that remote teams outperformed on site teams. This ties into the current Twitter discussion about "10x Performing Engineers". Remote teams are able to work on their own most productive hours and are not disturbed by their teammates when they are doing dedicated work on a deadline. Also remote teams by nature have to be more conscious of 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 Guest: Daniel Gruesso

Links

• Daniel's LinkedIn

• GitLab

• Open Source & Software Development| O'Reilly OSCON

• GitLab 2019 Global Developer Report | GitLab

• 10x Engineer Twitter

Daniel Caldas is calling from Singapore. He currently works as a software engineer for Zendesk and has also worked in Portugal and Germany. He has worked primarily on the frontend with Node and JavaScript. He talks about his experience testing JavaScript, how he got started with Jest, and why he likes it. Daniel finds Jest very easy to use and straightforward. He likes that  Jest has a single reference page for documentation. He feels that Jest is largely complete out of the box and has only made a small add on to get rid of Boilerplate in some tests.

Daniel explains what a snapshot, how they work, and why he prefers fixtures over factories. He gives tips on how to set up your tests so that they are easy to follow. He finds it helps to structure your scenarios in the fixture description. He talks about gotchas in Jest. While Jest is largely easy to use, Jest has been around for a while and breaking changes do happen. It’s important to check what version your code base is using. While there are a lot of free sources around Jest online, he advises listeners to stick as close to the official documentation as possible, or to people associated with Jest, and to read recent stuff. As for conventions, Jest has pretty much everything out of the box and the built in conventions make it easy to navigate any project that uses Jest.

Daniel talks about some of the features available in Jest, converting observables into promises, and tricks he has used to make tests easier to put together. He talks about his method for keeping his mocks and stubs straight. He advises listeners to have some organizational rules, such as starting the imports alphabetically, and to always follow those rules. He talks about how he runs tests and what environments he uses. While Jest is normally used for unit testing, Daniel has also used it for end to end tests, and he talks about his experience with an open source project doing both types in Jest. Daniel concludes the show by advising listeners starting with JavaScript and frontend, don’t think too much about the library you’re going to use because you’ll probably end up using Jest. It’s more important to have unit tests and a proper testing framework at the beginning than anything else. He also invites listeners to check out his open source work on Github.

Panelists

• Aimee Knight

• 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"**

Guest

• Danile Caldas

Sponsors

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

Links

• Zendesk

• Jest

• React

• Babel

• ESLint

• Async/Await

• Cypress

• React-d3-graph

• Unrevealed tips for unit testing with Jest

Picks

Aimee Knight:

• The Difference Between Fault Tolerance, High Availability, and Disaster Recovery

AJ O’Neal:

• Rubin Report with Lindsay Shepherd

Charles Max Wood:

• White Christmas

• Holiday Inn

Daniel Caldas:

• Home Alone

Daniel Caldas is a Portuguese developer working and living in Singapore. He learned to code in high school programming in Pascal. He moved up to the university and that's where he encountered JavaScript. He wound up doing a bunch of design work, static websites, and jQuery. He explains his journey and learning methods leading to a job working for Zendesk on their CRM.

Host: Charles Max Wood

Joined By Special Guest: Daniel Caldas

Sponsors

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

• CacheFly

______________________________________

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

______________________________________

Links

• JSJ 411: Unit Testing Jest with Daniel Caldas

• goodguydaniel.com

Picks

Daniel Caldas:

• tweak

Charles Max Wood:

• Shift

• Bose SoundLink Around Ear Wireless Headphones II

Sculptor and artist. Correspondence, writings, financial records, scrapbooks, newspaper clippings, photographs, and other papers of French, his daughter, Margaret French Cresson, and other members of the French family relating primarily to French's career as a sculptor and artist and to the French family.

Allhoff, Fritz

Hayden Library - TP155.5.C76 2019

Adewuya, J. Ayodeji, 1951- author

Korschun, Daniel

Wildermuth, Daniel

Rotch Library - KF3050.A78 2018

Dewey Library - KF3775.Z9 F56 2019

Dewey Library - KF3775.F36 2019

Online Resource

The John W. Kluge Center invites you to an Author Salon with Danielle Allen

Get your free tickets here.

Please join us for an event in which Danielle Allen will discuss the meaning of the text of the Declaration of Independence. She is the author of Our Declaration (2015), which makes the case that the Declaration of Independence was intended to ensure equality as much as it was intended to secure freedom.

The event will be held at noon on November 12, in Room LJ-119 of the Library’s Thomas Jefferson Building.

Allen is the Director of the Edmond J. Safra Center for Ethics at Harvard University as well as the author of several books, including Education and Equality (2016) and Cuz: The Life and Times of Michael A. (2017).

Tickets are recommended, but not required, and are free.

Register for a ticket here.

Seating is on a first-come, first-served basis. Request ADA accommodations five days in advance at (202) 707-6362 or ada@loc.gov.

Questions? Please contact (202) 707-9219 or scholarly@loc.gov

Barker Library - QC173.55.K35 2019

Cambridge, Mass. : National Bureau of Economic Research, 2020

Cambridge, Mass. : National Bureau of Economic Research, 2020

Online Resource

Rotch Library - HT384.E8 M35 2019

Rotch Library - HT221.S34 2019

Online Resource

Hayden Library - LB1060.B768 2014

Online Resource

Although famously reclusive and fitful in his creative output, Daniel Day-Lewis's decision to hang up his boots feels both untimely and unexpected.

'He has given us a history, a heritage that we can share with generations to come,' says Aseem Chhabra.

Interview with ambassador of Israel to India

Hillel, Daniel, author