Pahalgam was the coldest place in Kashmir valley with minimum temperature of minus 4 degree Celsius.

In reverence to the emperor, people don't talk to him directly or touch him.

Berlin ; New York : Springer, [2007]

Scheberle, Denise, author

Manners, Ron (Ron B.)

International Symposium on Iron Control in Hydrometallurgy (3rd : 2006 : Montréal, Québec)

D'Aloya de Pinilla, Anna, author

Support our Teespring campaign! Get your JavaScript Jabber unisex t-shirts, hoodies, ladies’-sized, and long-sleeve tees!

02:01 - Feross Aboukhadijeh Introduction

• Twitter
• GitHub
• Blog

02:39 - Peer-to-Peer Background, Content Delivery Networks (CDNs)

• WebRTC
• PeerCDN
• BitTorrent

09:43 - The BitTorrent Protocol and Hypertext Transfer Protocol (HTTP)

• [YouTube] Feross Aboukhadijeh: WebTorrent (JSConf.Asia 2014)
  • Distributed Hash Table (DHT)

13:08 - WebTorrent = BitTorrent over WebRTC

• Transmission Control Protocol (TCP)
• The User Datagram Protocol (UDP)
• Session Traversal Utilities for NAT (STUN)

17:22 - Where Do Original Files Come From?

• Tracker Servers
• BitTorrent Enhancement Proposal (BEP)

21:23 - Opposition

27:26 - Where is WebTorrent Going? (Use Cases)

• Instant.io
  • [GitHub] instant.io

29:52 - Live Broadcasts

31:12 - Progression of BitTorrent Over Time

• Technical Decentralization

35:03 - Same-Origin Policy

36:33 - Firefox Hello

Picks

January 12th, 2016: Goodbye IE8 and IE9! (Dave)
js-must-watch (Aimee)
Headspace (Aimee)
Popcorn Time (AJ)
Steelheart (The Reckoners) by Brandon Sanderson (Chuck)
Teespring (Chuck)
Loop Drop by Matt McKegg (Feross)
SceneVR by Ben Nolan (Feross)
WebTorrent (Feross)
node-nat-upnp (AJ)
node-nat-pmp (AJ)
simple-peer (Feross)

00:55 - Introducing Jerome Hardaway

• Vets Who Code
• Ruby Rogues Podcast
• Facebook
• Twitter
• Instagram

02:10 - Spouses and dependants of Vets Who Code

06:55 - Accepting and rejecting applicants

10:10 - The GI Bill

• Operation Code
• Dreamforce

15:45 - Military language and coding

18:20 - PTSD, trauma, and coding

21:10 - Moving past the veteran stigma

25:45 - Military backgrounds as an asset for jobs

30:45 - The future of Vets Who Code

32:35 - How much does it cost to be part of the program?

• General Assembly

36:15 - Is it easier or harder for Vets to get hired?

39:15 - Stories and memories

42:30 - Contributing to Vets Who Code

• Contact hello@vetswhocode.io to become a mentor
• Donate: https://vetswhocode.kindful.com/
• SwearJar
• Hiring managers please contact Jerome@vetswhocode.io

Picks:

Soft Skills Engineering Podcast (Dave)

Soft Skills Engineering Twitter (Dave)

Awesome Algorithms Github list (Aimee)

“The Churn” blog post by Bob Martin (Aimee)

The 12 Week Year by Brian P. Moran and Michael Lennington (Charles)

Vets Who Code (Jerome)

Practical Javascript (Jerome)

MJS 032: Feross Aboukhadijeh

Today's episode is a My JavaScript Story with Feross Aboukhadijeh. Feross talked about his contributions to the JavaScript community to the decentralized web. Listen to learn more about Mike!

[01:00] – Introduction to Feross Aboukhadijeh

Feross was on episode 155 and he talked about Webtorrent. It was 2 years ago.

[01:35] – How did you get into programming?

Toddler

Feross has always been interested in computers and technology. His mom told him a story about how when he was a toddler, he was always watching people whenever they’re using technology – the television, the microwave, or the VCR. She said that he’s trying to imitate what he saw.

HTML and Web proxies

According to Feross, he became seriously interested when he was in middle school when he learned about HTML and wanted to make a personal site. In high school, there was this class that you could take. It’s a tech team where they went around and fixed teachers’ computers because they were understaffed. Some of the computers have administrator privileges turned on for the student accounts as well because some of the software that was required for certain classes needed it. The computers always had viruses on them because people would install first-person shooters and play during class time. They actually have school-wide filtering system so students can’t access certain sites. One of the categories they blocked was downloading sites. In order to even do their job, they have to figure out web proxies to get around the filters. He ended up setting up one of those on his own server.

First website

Feross’ real programming experience was PHP. It was in his junior year of high school. He bought a book in Barnes & Noble about PHP and MySQL. He wanted to build a site to host his favorite flash animations. That project was a database-driven website where people can segment their flash animations and soundboards, prank phone calls, and other internet humor. The site was called freetoflash. That was the first website that he built.

[07:10] – How did you get into JavaScript?

Feross thinks JavaScript is one of those languages that you don’t actually really bother to sit down and learn. There weren’t any good resources. According to him, He really didn’t know JavaScript until he started a company right after he graduated from college. He started taking JavaScript seriously because he was learning Node.js and realized that you can build real things from it. The start-up is called PeerCDN. They’re trying to make a content delivery network that would work in the browser using WebRTC. The idea is you would add a script tag to your website and then we would try to find other people visiting your site that already has the content that you want, you’ll fetch it from them over a peer-to-peer connection to save on your hosting build to reduce your CDN bill. That was a big Node application. It also has intense front-end component. He started learning about NPM, how you build things with microservices, and how do you deploy a JavaScript application. That was in 2013.

[09:35] – Webtorrent

Feross has been trying to transition Webtorrent into a distributed contribution model. It’s always been something that he would give out commit rights. If someone makes a good contribution, he’ll just add them to the Github for it. He recently made it into an organization on Github. He’s hoping to make it something that’s not completely dependent on him in order for it to continue existing. He’s going to be involved with it for the foreseeable future but he’s also trying to do new projects as well besides that. The good news is Webtorrent is mostly done in some sense. It works well. There are bugs. But if you use Webtorrent, especially if you use the desktop application to torrent things, it’s really polished and works nicely.

Picks

Feross Aboukhadijeh

• Decentralized web
• Dat Project
• Beaker Project
• IPFS
• Secure Scuttlebutt
• Patchwork
• Brave
• Twitter: @WebTorrentApp
• Twitter: @feross

Charles Max Wood

• Let’s Encrypt
• Digital Ocean

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

Panel: Charles Max Wood

Guest: Jerome Hardaway

This week on My JavaScript Story, Charles speaks with Jerome Hardaway. Jerome used to be a panelist on Ruby Rogues and loved the ability to share his knowledge and interact with so many people from the community. He first got into programming by accident when he couldn’t find a job after becoming a veteran. He saw a commercial about job opportunities in coding, ended up finding a book on SQL and taught himself how to program. They talk about where he ran across Ruby on Rails, what he has worked on that he is particularly proud of, what he is doing currently, and more!

In particular, we dive pretty deep on:

• Jerome’s experience being a panelist on Ruby Rogues
• Loves being able to reach his goals in a speedy manner
• Ruby Rogues Episode 279
• JavaScript Jabber Episode 239
• How did you first get into programming?
• In the military during the recession and had trouble finding a job
• Saw a commercial about coding
• Taught himself SQL
• Wordpress
• Focusing on making Vets Who Code better
• People would go for products over projects any day
• Chose Ruby on Rails 
• Setting himself apart by picking to focus on Ruby on Rails
• Where did you come across Ruby on Rails?
• From PHP to Ruby on Rails
• Ruby
• Have you found the learning curve has gotten steeper for Rails?
• Keeping up with the JavaScript community
• What have you done on Ruby in Rails that you are proud of?
• Being the right person for the job when you don’t look like it on paper
• What are you working on now?
• And much, much more!

Links: 

• Ruby Rogues Episode 279
• JavaScript Jabber Episode 239
• Vets Who Code
• Ruby Rogues
• Wordpress
• Ruby on Rails
• Ruby
• JavaScript
• @JeromeHardaway
• Vets Who Code blog
• Jerome’s GitHub

Sponsors: 

• Loot Crate
• FreshBooks

Picks

Charles 

• Take some time with the people you care about
• Mattermost

Jerome

• Brian Holt Frontend Masters
• Pragmatic Studio

Panel: Charles Max Wood

Guest: Orta Therox

This week on My JavaScript Story, Charles speaks with Orta Therox. Orta is a native engineer that believes that the right way to build systems is to understand as many systems as possible. He works predominately on iOS programming at a company called Artsy, where they make it easy to buy and sell art on the internet. He first got into programming because he loved playing video games as a child, loved creating his own video games, and worked his way up from there. They talk about his work at Artsy, how he used open source to learn himself how program, how he got into Ruby and then React and React Native, and more!

In particular, we dive pretty deep on:

• JavaScript Jabber Episode 305
• Orta intro
• Artsy
• iOS programming
• Hates lack of documentation
• CocoaPods
• Trouble with building native apps
• His move to React and React Native
• Used to run iOS team at Artsy
• How did you get into programming?
• Played video games as a kid
• Taught himself with books
• Using open source to learn
• Open source by default idea
• Loves giving back through blogging and open source
• How did you get into Ruby?
• MacRuby
• Boundaries are very obvious in React Native
• How did you get into React and React Native?
• Native developers building stuff in JavaScript
• Culture conflicts
• How they dealt with dependencies in their apps
• And much, much more!

Links:

• JavaScript Jabber Episode 305
• Artsy
• CocoaPods
• React
• React Native
• MacRuby
• JavaScript
• @orta
• orta.io
• Orta’s GitHub
• Artsy Engineering

Sponsors:

• Loot Crate
• FreshBooks

Picks

Charles

• South Pacific
• Get a Coder Job course
• Framework Summit

Orta

• Prettier

Sponsors

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

Panel:

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

Special Guest - Sarah Dayan

In this episode of JavaScript Jabber, the panelists talk to Sarah Dayan, who is a Frontend Software Engineer working for Algolia in Paris. They about the complications in handling money in software development and ask Sarah about the journey that led to the creation of Dinero.js, it’s implementation details, importance of maintaining good documentation, dealing with issues faced along the way, various features of Dinero and working with open source projects in general. Check it out!

Show Topics:

0.40 - Advertisement : Netlify

1:44 - Sarah introduces herself and Chris talks about his interest in learning more about Dinero and compliments Sarah on its great documentation.

3.10 - Sarah gives some background saying that she created and published Dinero around a year ago. She goes on to explain that the Dinero library helps in handling monetary values. It comes with several methods to parse, manipulate and format these values. The reason behind creating it is that there is no consensus on representing money in software development currently. She shares the story from her previous job where her work was to maintain legacy accounting software, and along the way they realized, that since JavaScript did not have a way to natively represent decimal values, it led to adding large numbers of rounded up numbers continuously, eventually leading to wrong computations.

6:50 - Aimee asks about ways to handle different currencies in Dinero. Sarah answers that she has followed Martin Fowler’s money pattern where two different currencies were not allowed to be worked on directly, conversion was mandatory, just like in real life.

7:50 - Charles talks about his old freelance work where he was overwhelmed while handling and representing money in software.

8:25 - Aimee enquires if Dinero can be used for both frontend and backend. Sarah replies that it can be used anywhere and explains that there is no such thing as just a number when it comes to money, there must be a currency associated with it.

9:30 - Charles asks how to figure out the direction to go to when dealing with money and to make sure that all use-cases are covered. Sarah answers that in cases such as floating-point math where the computations don’t end up being accurate as handling is not supported, numbers can be used if treated as subunits (for e.g. 100cents = 1$). However, even then, there are issues in dividing money. She then explains the procedure of “allocation” from the Fowler pattern and she says that Dinero helps in doing the same in such scenarios.

12:54 - They discuss how they did not realize how difficult it was dealing with monetary values in development. Sarah talks about the fact that there are numerous aspects involved in it, giving the example of rounding off and stating that there are even factors such as different laws in different countries that need to be considered.

16:00 - AJ asks details about crafting the library, maintaining the centralized code and covering of edge cases and using inheritance. Sarah explains the concept of domain driven development and the importance of being an expert in the respective domains. She talks about the library structure briefly, describing that is kept very simple with a module pattern and it has allowed her to manage visibility, make it immutable, include currency converters, formatters and so on.

19:34 - AJ asks about the internal complexity of the implementation. Sarah answers that code wise it is extremely simple and easy, anyone with a limited JavaScript experience can understand it.

20:50 - AJ asks if it’s open source to which Sarah answers in affirmative and says that she would like external help with implementing some features too.

22:10 - Chris asks about Sarah’s excellent documentation approach, how has she managed to do it in a very detailed manner and how important it is in an open source project. Sarah says that she believes that documentation is extremely important, and not having good docs is a big hindrance to developers and to anyone who is trying to learn in general. She talks about her love for writing which explains the presence of annotations and examples in the source code.

27:50 - Charles discusses how autogenerated documentation gives an explanation about the methods and functions in the code but there is no guidance as such, so it is important to have guides. Sarah agrees by saying that searching for exact solutions is much simpler with it, leading to saving time as well.

29:43 - Chris speaks about Vue also being quite good at having guides and links and thanks Sarah for her work on Dinero.

30:15 - Advertisement - Sentry - Use code “devchat” to get two months free on Sentry’s small plan.

31:23 - Chris asks what the process is, for creating and running Dinero in different places. Sarah explains that she uses rollup.js which is a bundler suited for libraries, it takes in the ES module library and gives the output in any format. She states that the reason for using the ES module library is that she wanted to provide several builds for several environments with a clean and simple source and goes on to explain that these modules are native, have a terse syntax, easy to read and can be statically analyzed. She also gives the disadvantages in choosing webpack over rollup.

36:05 - Charles asks if anyone else is using Dinero. Sarah replies that around two or three people are using it, not much, but she is happy that it is out there to help people and she enjoyed working on it.

37:50 - Joe asks if there are any interesting stories about issues such as involving weird currency. Sarah answers in affirmative and gives the example of the method “hasCents”. She explains that she had to deprecate it because the unit “cents” does not have any value in non-Western currencies, and has created “hasSubUnits” method instead. She explains some problems like dealing with currencies that don’t support the ISO 4217 standard.

42:30 - Joe asks if social and political upheavals that affect the currencies have any effect on the library too. Sarah gives the example of Chinese and Japanese currencies where there are no sub-units and states that it is important to be flexible in developing stuff in an ever-changing domain like money. She also says that she does not include any third-party dependency in the library.

46:00 - AJ says that BigInts have arrived in JavaScript but there is no way to convert between typed arrays, hexadecimal or other storage formats. But later (1:10:55), he corrects that statement saying that BigInts in fact, does have support for hexadecimals. Sarah talks about wanting to keep the code simple and keep developer experience great.

49:08 - Charles asks about the features in Dinero. Sarah elaborates on wanting to work more on detecting currencies, improve the way it is built, provide better support for type libraries and get much better at documentation.

52:32 - Charles says that it is good that Sarah is thinking about adopting Dinero to fit people’s needs and requirements and asks about different forms of outreach. Sarah says that she blogs a lot, is active on Twitter and attends conferences as well. Her goal is not popularity per se but to help people and keep on improving the product.

55:47 - Chris talks about the flip side that as the product grows and becomes popular, the number of support requests increases too. Sarah agrees that open source projects tend to eat up a lot of time and that doing such projects comes with a lot of responsibility but can also help in getting jobs.

59:47 - Sarah says that she is available online on her blog - frontstuff, on Twitter as Sarah Dayan and on GitHub as sarahdayan.

1:00:06 - Advertisement - Clubhouse

1:01:01 - Picks!

1:11:42  - END - Advertisement - CacheFly!

Picks:

Sarah

• DocSearch - Algolia

AJ O’Neal

• The Legendary Profile by Modern Jazz Quartet
• Webcam Cover by Dcreate
• How Music Works - David Byrne

Chris

• Tommy Hodgins Code Series
• Tom Scott - YouTube
• Future Man

Joe

• Timeless
• A Christmas Carol narrated by Patrick Stewart

Aimee

• Hacker News thread on working with Legacy Codebases

Charles

• George Marathon
• Garmin Forerunner 235

Vinitzky-Seroussi, Vered

Ewumbue-Monono, Churchill, 1961-

McLeod, Doug

Akgul, Faruk

Amit-Cohen, Irit

This cohort study uses the UK Biobank cohort data to compare the association of monogenic vs polygenic hypercholesterolemia with the risk of atherosclerotic cardiovascular disease among individuals with comparable levels of low-density lipoprotein cholesterol.

Yeo, Sue-Yee Sharon, author