Blog 307 — JS311

  1. Tell me about a project you’re particularly proud of. What did you do that worked out well?
  • I proud of the check point 1 I did a month ago. This is the first server I build with express. What I am did that is working well is that I am taking my time with it and I am allowing myself to change my ideas on it as I work along.
  1. How do you do testing, and what do you think about it? How would you improve QA?
  • I do a lot of my testing as a user. I know the functions that I created so once I have them working I try to find a loophole around it and fix the vulnerabilities. I can improve on this by conducting better debugging sessions and also by allowing others to be my beta users.
  • Testing, Quality Assurance,and Quality Control QA includes activities that ensure the implementation of processes, procedures and standards in context to verification of developed software and intended requirements. … It includes activities that ensure the identification of bugs/error/defects in a software.
  1. What tools do you use to find a performance bug?
  • I typically use the built-in debugger on google chrome to check the loading speeds and general efficiency of my project and I use this along with the built-in vscode debugger to improve the performance of my project.
  1. What is the preferred method of resolving unhandled exceptions in Node.js?
  • I mostly find myself using try-catch blocks; however, I am looking to start to use the process.on() method which listens to events and throws errors if one is encountered.
  1. How does Node.js support multi-processor platforms, and does it fully utilize all processor resources?
  • Node.js is a single-threaded language and because of this, it does not make full use of multi-processor platforms. Regardless, separate instances of Node work processes can be run on different processors and can be used to communicate with each other thanks to Node’s cluster module.
  1. What is typically the first argument passed to a Node.js callback handler?
  • The first argument passed to a Node callback handler is an optional error argument. If there is an error, this allows the developer to handle it some way, otherwise, it can simply be ignored.