-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
Feedback
by Matthew Alicea
Overall pretty good, just some grammatical issues and maybe some sentences to reword. Use of figures and tables is good!
Intro / Problem, Objective, Users
- Some grammatical errors, might be a few missing words
Design, Development, Test / Design
- Might be a good idea to use the
codestyle for all filenames in the text. Completely optional, but I like doing that for all file & directory names, and typically for code references like class names. You do this relatively consistently in the Logic Flow explanation with files. - The Logic Flow figure is very nice! Definitely going to do something like this for my report too.
- I wonder if Chris is looking for as detailed of a "this-then-that" description of the logic flow. I would ask, and if he doesn't want it as detailed I think talking about it in more of a summary form (higher-level) would be easier to read.
Design, Development, Test / Development
-
Second sentence starts kinda wonky, maybe change to: "This was largely due to the fact that I did not have a solid project idea…" or something like that.
-
Might help to elaborate on the issues you faced with the MEAN stack approach; you mentioned it was a pain and you could not figure it out but didn't mention specifically what about it was difficult.
Results / Findings
- I think overall just make sure you're balancing describing the charts enough but not too much, and summarizing what they mean.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels