All right, so just to recap then, three tools to have in the proverbial toolbox now are help50 anytime you see an error message that you don't understand, whether it's with make or Clang or, perhaps, something else, printf--when you've got a logical program--a bug in your program, and it's just not working the way it's supposed to or the way the problem set tells you it should, and then style50 when you want to make sure that, does my code look right in terms of style, and is it as readable as possible?
It's looking at my code, it's getting ready for submission, it's now uploading it to GitHub.com, and once it's on the servers, then it's going to tell CS50 server, here is so-and-so's submission, go ahead and run a few automated tests on it, checking therefore its correctness, and hopefully we're about to see some green, happy smiley faces, and voila, yes, it looks like this check50 command for this problem--or slug, so to speak--checked that hello.c exists, because if I forgot to write the file or if I misnamed it, nothing's going to work.
