Skip to content

read_class6.md

Latest commit

 

History

History
33 lines (30 loc) · 2.4 KB

read_class6.md

File metadata and controls

33 lines (30 loc) · 2.4 KB

NODE.JS

An Introduction to Node.js on sitepoint.com

  • What is node.js?

is an open-source, cross-platform, back-end JavaScript runtime environment that runs on the V8 engine and executes JavaScript code outside a web browser. Node.js lets developers use JavaScript to write command line tools and for server-side scripting—running scripts server-side to produce dynamic web page content before the page is sent to the user's web browser.

  • In your own words, what is Chrome’s V8 JavaScript Engine?

is the open-source JavaScript engine that runs in Google Chrome and other Chromium-based web browsers.

  • What does it mean that node is a JavaScript runtime?

This means that Node.js is a program we can use to execute JavaScript on our computers.

  • What is npm?

npm (node package manager)is the world's largest Software Registry ,The registry contains over 800,000 code packages,Open-source developers use npm to share software.

  • What version of node are you running on your machine?

v12.22.1

  • What version of npm are you running on your machine?

6.14.12

  • What command would you type to install a library/package called ‘jshint’?

npm install -g jshint

  • What is node used for?

Embedded systems,Browser games, Command-line applications ,Streaming applications ,Chat applications.

6 Reasons for Pair Programming

  • What are the 6 reasons for pair programming?
  • Greater efficiency
  • Engaged collaboration
  • Learning from fellow students
  • Social skills
  • Job interview readiness
  • Work environment readiness
  • In your experience, which of these reasons have you found most beneficial?

I think the greater efficiency and learning from fellow student .

  • How does pair programming work?

pair programming commonly involves two roles: the Driver and the Navigator. The Driver is the programmer who is typing and the only one whose hands are on the keyboard. Handling the “mechanics” of coding, the Driver manages the text editor, switching files, version control, and—of course writing—code. The Navigator uses their words to guide the Driver but does not provide any direct input to the computer. The Navigator thinks about the big picture, what comes next, how an algorithm might be converted in to code, while scanning for typos or bugs. The Navigator might also utilize their computer as a second screen to look up solutions and documentation, but should not be writing any code.