mirror of https://github.com/01-edu/public.git
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
50 lines
3.0 KiB
50 lines
3.0 KiB
5 years ago
|
#### Functional Project Questions
|
||
|
|
|
||
|
|
##### Try passing as arguments `"hello" standard --output=test1.txt`
|
||
|
|
###### Does it save the right output in the right file?
|
||
|
|
##### Try passing as arguments `"123 -> !#$&%" standard --output=test2.txt`
|
||
|
|
###### Does it save the right output in the right file?
|
||
|
|
##### Try passing as arguments `"432 -> !#$%&@" shadow --output=test3.txt`
|
||
|
|
###### Does it save the right output in the right file?
|
||
|
|
##### Try passing as arguments `"There" shadow --output=test4.txt`
|
||
|
|
###### Does it save the right output in the right file?
|
||
|
|
##### Try passing as arguments `"123 -> !"#$%@" thinkertoy --output=test5.txt`
|
||
|
|
###### Does it save the right output in the right file?
|
||
|
|
##### Try passing as arguments `"2 you" thinkertoy --output=test6.txt`
|
||
|
|
###### Does it save the right output in the right file?
|
||
|
|
##### Try passing as arguments `"Testing long output!" standard --output=test7.txt`
|
||
|
|
###### Does it save the right output in the right file?
|
||
|
|
##### Try passing as arguments `"this is a long string for testing purposes!" standard --output=test8.txt`
|
||
|
|
###### Does it save the right output in the right file?
|
||
|
|
##### Are all the test files saved?
|
||
|
|
|
||
|
|
#### Basic
|
||
|
|
|
||
|
|
###### *Does the code present commenting ? (https://github.com/01-edu/public/blob/master/subjects/good-practices.en.md)
|
||
|
|
###### *Does the code present documentation ?
|
||
|
|
###### *Does it present consistent indentation ?
|
||
|
|
###### *Does the code avoid obvious comments ? (no over information)
|
||
|
|
###### *Does the code avoid code grouping ?
|
||
|
|
###### *Does the code have a consistent naming scheme (camelCase, under_scores) ?
|
||
|
|
###### *Does the code obey the principles "DRY" (Don't Repeat Yourself) or "DIE" (Duplication is Evil) ?
|
||
|
|
###### *Does the code obey the principal "KISS" (keep it simple, stupid) ?
|
||
|
|
###### *Does the code obey the principle YAGNI (You Aren’t Gonna Need It) ?
|
||
|
|
###### *Does the code obey the principle SOC (Separation of Concerns)
|
||
|
|
###### *Does the code avoid deep nesting (if in ifs, forest of ifs) ?
|
||
|
|
###### *Does the code present a good file and folder organization ?
|
||
|
|
###### *Does it present a good separation of Code and Data ?
|
||
|
|
###### *Does the go code follow the go recommendation ? ((https://golang.org/doc/effective_go.html), (https://golang.org/cmd/gofmt/), (https://godoc.org/golang.org/x/tools/cmd/goimports), (https://goinbigdata.com/goimports-vs-gofmt/))"
|
||
|
|
|
||
|
|
###### *Has the code passed the formatting ? (gofmt, goimports)
|
||
|
|
###### *Did the program runned without crashing at anytime ?
|
||
|
|
###### *Does the project runs quickly and effectively ? (Favoring of recursive, no unnecessary data requests, etc)
|
||
|
|
|
||
|
|
###### *Is the error handled, is it error free ?
|
||
|
|
###### *Is there a test file for this code ?
|
||
|
|
###### *Are the tests checking each case ?
|
||
|
|
###### *Is the output of the program well structured? Does any letter seems to be out of scoop ?
|
||
|
|
|
||
|
|
###### *Can the project be used for a common good ?
|
||
|
|
###### *Did you learn anything from this project ?
|
||
|
|
###### *Can it be open-sourced / be used for other sources ?
|
||
|
|
###### *Would you recommend/nominate this program as an example for the rest of the school ?
|