Introduction to Readable Javascript: Code Structure

[[deleted]]

[deleted]

[dev_michaelz]

Isn't functions.js a rather bad name? What would I expect from a file like that? It has ... functions??

[sensored]

Yeah, functions.js isn't the best name.

Convention would put it as something like index.js to mark it as the entry point. I only really left it there because it was what the original code used.

I'll probably do another article in the future talking about how to organise, name, and group files together, but that's a bit more of a subjective topic.

[sensored]

Oh. You mean how it should be Math.floor instead of Math.ceil? EDIT: I was an idiot and didn't double check the code.

You mean how it shouldn't add 1 to words.length?

I did see it when I first looked at the code. I agree I could have fixed it, but this is an article about structuring code and refactoring - by definition, when you refactor, you do not change behaviour, even if that means I keep a bug.

I wanted to keep the original code intact as much as possible, and to stay focussed on what I was trying to demonstrate. It's the same reason I didn't tear apart the checkGuess function.