learn-co-curriculum / javascript-logging Goto Github PK

The lab mentions having used console.log but up to this point in curriculum, we haven't.

"We've already made use of perhaps the most popular of these methods, console.log(); but there are a few more tricks up console's sleeve. Let's dive in!"

Really like that this is pared down more --

A couple of comments. When you first talk about 'console' you write "What methods does console expose? " Students do not know what methods yet mean.

I get a good grasp of console.log because it's just printing out stuff to the screen.

I understand less well console.warn and console.error -- I think my biggest questions are why/when will they happen. I know the mechanics of typing them to the console but I'm not sure how this actually works. Is there a little bit of context that you can provide? Or maybe an example. For example, having a scenario where this would appear would be helpful "console.error() prints an error and usually includes a stack trace. "Stack traces" is a report of code that was executed at a certain time (in this case, starting from when the error occurred and working backwards). Enter the following in your console:"

Otherwise, this is pretty good.

@jmburges

Not sure if it's just me, but I was working in one console through multiple lessons before realizing I should reopen a fresh one. A reminder maybe to close out of the console and open before the new lesson might be nice!

1. "takes any number of arguments". Students don't know what arguments are.

2. String Substitution is actually pretty hard for students to understand, you need to go much deeper into this and make sure they are coding along.

I completed everything and passed the tests. How do I submit pull to move to the next lesson?

I think the primary issue here for me is that this lesson focuses on methods but we haven't yet defined for them. And in the individual methods that are covered, things like variables and objects and errors and libraries and stack trace and arguments and object properties are mentioned but the student will have no idea what they are.

I think this lesson is good, but might be misplaced in the track.

WHY LOG? Think of logging like journaling. Journaling gives us a way to record things that happened over the course of a day; logging gives our programs a way to record what happened while they were running.

This section seems unnecessary since it's covered in the first section of this lesson under Javascript Logging.

1. What's a library?

2. What's a function. Also function vs. method?

3. What's deprecation? Most students won't know that word

The image for the console.warn() example isn't displayed:

1. Using object creation and variable assignment and they've never seen that before

2. Show them what a stack trace looks like.

3. You do string substitution, but they've never seen that before. Is this the best place to introduce it? Also shouldnt' there be a lot more information around that?