Follow your code: Best Practices for Node.js Problem determination
Submitted by Gireesh Punathil (@gireeshpunam) on Friday, 3 August 2018
While learning a language and its APIs can be easy for a programmer, Problem determination requires deeper insights into the inner working of the execution environment, not just the language semantics
Any production scale application would require problem determination applied to as an essential ingredient, in at least one milestone of its development lifecycle.
The presentation aims to educate the audience with the powerful tracing option that is intrinsic to Node.js, and that caters to a number of real world production issues.
Focus on issues that are experienced in the field - insight gathered from the support experience. So directly consumable.
Gireesh Punathil is an Architect and Software developer with IBM India Software Labs, predominantly working in Java and Node.js. In 15 years of his career, he has been porting, developing and debugging web servers, virtual machines and compilers. His expertise is in problem isolation and determination of large and complex software modules. He has spoken at several Node.js and Java conferences.