I’ve Cracked the Code, Please Call Tech Support- Episode 22, Knights of the Old Repository

Two weeks out of class, and we’re back at it again with React. This is an interesting…framework? Framework. I’m looking forward to learning more about it in our 411 course!

  1. Tell me about a project that you’re particularly proud of. What did you do that worked out so well?

Way back in 101, we had to make a barbershop website based on a template. I could knock that out incredibly quickly now, but back then I barely had a grasp on anything that we were doing.

But I kept at it. And kept at it. I learned how to effectively inspect and implement, how to make the page react properly, and even how to incorporate some basic JavaScript (when we hadn’t been taught that language) in order to make a drop down navigation menu. I’m honestly pretty proud of that.

2. How do you do testing, and what do you think about it? How would you improve QA?

Since it’s just me here, I test every way that I know how. Let’s say that I’m building a Pig Latin translator. I would type every weird word that I could think of and see if the results match expectations.

Ideally, I would improve it by having a wide variety of people try to break it. They are going to approach this in many ways that I had not considered, and I could make it rock solid as a result.

3. What tools do you use to find a performance bug?

VS Code is great for finding faults in your code as you write it. In addition, the Google inspect console is great for seeing if an action fails. It tells you what line of code had the problem, so you can inspect it.

4. What is the preferred method of resolving unhandled exceptions in Node.js?

There is a listener function in Node.js called Process. This function, as the listener adjective implies, listens for events. These include exits, disconnects, rejectionHandled, and unhandledException. This catches the exception as it occurs.

5. How does Node.js support multi-processor platforms, and does it fully utilize all processor resources?

Node.js is a single thread app, running on a single processor core. So, by default, it doesn’t use all processor resources.

However, it does support multi-core systems using a module called Cluster. This allows for the running of multiple Node.js processes using separate, single cores to accomplish one task.

6. What is typically the first argument passed to a Node.js callback handler?

For convenience in handling, the first argument passed to a Node.js callback handler is an error object, if one exists. If it doesn’t, then null or undefined is returned.