Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript JavaScript Basics (Retired) Introducing JavaScript The JavaScript Console

Brian Bartlett
Brian Bartlett
20,278 Points
Posted by Brian Bartlett
Brian Bartlett
20,278 Points

There is another bug that was not discussed: "No" instead of "Now" in the .write output.

This could have led to a discussion about errors the interpreter cannot catch.

1 Answer

Marcus Parsons
Marcus Parsons
15,719 Points
Marcus Parsons
Marcus Parsons
15,719 Points

Hey Brian Bartlett,

That's not an error with the interpreter; that is user error. The interpreter doesn't look at human language, only at JavaScript, so it can't see that the author meant "Now it works!" instead of "No it works!". In fact, "No it works!" is still a valid sentence, albeit not the sentence that Dave had in mind, I'm sure. Perhaps with some advanced artificial intelligence a computer system would recognize that Dave meant "Now" instead of "No", but we're not there yet! lol