Summary

[jmcrey]

Rubric Score

Criteria 1: Valid Python Code

• Score Level: 4 (Exceeds Expectations)
• Comment(s): The code included in the Jupyter notebook runs without any errors.

Criteria 2: Implementation of Project Requirements

• Score Level: 4 (Exceeds Expectations)
• Comment(s): Code produces the suite of functions and classes required of it and calls them in an appropriate order. Also, the code is well written and organized such that it is easy to read and follows many of Python's best practices (my favorite being the percent_difference and find_text_similarity functions). Great job!

Criteria 3: Software Architecture

• Score Level: 3 (Meets Expectations)
• Comment(s): Classes and functions are defined, and the majority of classes and functions are invoked for their own purposes; but, the build_frequency_table could have been significantly simplified if it expected the output of the prepared_text function (covered more here). Otherwise, each function was very well done and used for its own purpose. Nice job!

Criteria 4: Uses Python Language Features

• Score Level: 4 (Exceeds Expectations)
• Comment(s): Okay, this is where this project shined. It did a great job at using Python's built-in functions to accomplish each of its desired tasks (my personal favorite is the use of the zip function in the build_frequency_table). Great job!

Criteria 5: Produces Accurate Output

• Score Level: 4 (Exceeds Expectations)
• Comment(s): The output of the code was accurate.

Overall Score: 19/20

Honestly, this project did a great job! It produced accurate output; it included helpful comments in the code; it followed Python's best practices; and it utilized Python's built-in functionality very well.

One thing it could have done better is simplification -- many of the functions did not require the length of code produced. Often, this specific correction gets better with experience; but, to quicken the pace on simplifying functions, simply answer two questions for every function produced: "How do I combine functionality? and "Is every line of code necessary?". For the get_average_sentence_length function, not every line of code was necessary (covered here). Two for loops could have been removed. For the build_frequency_table function, we could have combined functionality by ensuring it accepted input from the prepared_text function (covered here). In both of the cases, it was possible to simplify the functionality by answering those questions.

Nevertheless, this project was very well done. Best of all, the project was accurate. Great job!

[yalqaoud]

@jmcrey Awesome! I thank you for your evaluation. To be honest, I thought I that after submission, I was going to be able to go back on forth with the project (amendments wise), and so I have done it as soon as I could (4-5 hours) and submitted right away. I am pretty happy with the score I got with that being said!

Again, thanks for your efforts, and I wish you all the best as well!