Browse Source

renaming files and replacing * -> +

content-update
lee 5 years ago
parent
commit
d74e5d1b07
  1. 53
      subjects/ascii-art/ascii-art-justify.audit.en.md
  2. 32
      subjects/ascii-art/ascii-fs.audit.en.md
  3. 35
      subjects/ascii-art/ascii-justify.audit.en.md
  4. 32
      subjects/ascii-art/ascii-output.audit.en.md

53
subjects/ascii-art/ascii-art-justify.audit.en.md

@ -1,53 +0,0 @@
#### Functional Project Questions
##### Try passing as arguments `"left" --align=right`
###### Does it displays the correct result at the right side?
##### Try passing as arguments `"right" --align=left`
###### Does it displays the correct result at the left side?
##### Try passing as arguments `"hello" --align=center`
###### Does it displays the correct result at the center?
##### Try passing as arguments `"1 Two 4" --align=justify`
###### Does it displays the correct result justified?
##### Try passing as arguments `"23/32" --align=right`
###### Does it displays the correct result at the right side?
##### Try passing as arguments `"ABCabc123" --align=right`
###### Does it displays the correct result at the right side?
##### Try passing as arguments `"!#$%&" --align=center`
###### Does it displays the correct result at the center?
##### Try passing as arguments `"23Hello World!" --align=left`
###### Does it displays the correct result at the left side?
##### Try passing as arguments `"HELLO there HOW are YOU?!" --align=justify`
###### Does it displays the correct result justified?
##### Try passing as arguments `"a -> A b -> B c -> C" --align=right`
###### Does it displays the correct result at the right side?
#### Basic
###### *Has the code passed the formatting? (gofmt, goimports)
###### *Does the project runs quickly and effectively? (Favoring recursive, no unnecessary data requests, etc)
###### *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 Are not 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://github.com/01-edu/public/blob/master/subjects/good-practices.en.md)
###### *Is the error handled, is it error free?
###### *Is there a test file for this code?
###### *Are the tests checking each case possible?
###### *Is the output of the program well structured? Does any letter seems to be out of line?
#### Social
###### *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?

32
subjects/ascii-art/ascii-art-fs.audit.en.md → subjects/ascii-art/ascii-fs.audit.en.md

@ -113,31 +113,13 @@ o-O-o o o-o o o o-o o o o | o o o--O
#### Basic
###### *Has the code passed the formatting? (gofmt, goimports)
###### *Does the project runs quickly and effectively? (Favoring recursive, no unnecessary data requests, etc)
###### *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 Are not 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://github.com/01-edu/public/blob/master/subjects/good-practices.en.md)
###### *Is the error handled, is it error free?
###### *Is there a test file for this code?
###### *Are the tests checking each case possible?
###### *Is the output of the program well structured? Does any letter seems to be out of line?
###### +Does the project runs quickly and effectively (Favoring of recursive, no unnecessary data requests, etc.)?
###### +Is the output of the program well structured? Does any letter seems to be out of line?
###### +Is there a test file for this code?
###### +Are the tests checking each possible case?
###### +Does the code obey the [good practices](https://github.com/01-edu/public/blob/master/subjects/good-practices.en.md)?
#### Social
###### *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?
###### +Did you learn anything from this project?
###### +Would you recommend/nominate this program as an example for the rest of the school?

35
subjects/ascii-art/ascii-justify.audit.en.md

@ -0,0 +1,35 @@
#### Functional Project Questions
##### Try passing as arguments `"left" --align=right`
###### Does it displays the correct result at the right side?
##### Try passing as arguments `"right" --align=left`
###### Does it displays the correct result at the left side?
##### Try passing as arguments `"hello" --align=center`
###### Does it displays the correct result at the center?
##### Try passing as arguments `"1 Two 4" --align=justify`
###### Does it displays the correct result justified?
##### Try passing as arguments `"23/32" --align=right`
###### Does it displays the correct result at the right side?
##### Try passing as arguments `"ABCabc123" --align=right`
###### Does it displays the correct result at the right side?
##### Try passing as arguments `"!#$%&" --align=center`
###### Does it displays the correct result at the center?
##### Try passing as arguments `"23Hello World!" --align=left`
###### Does it displays the correct result at the left side?
##### Try passing as arguments `"HELLO there HOW are YOU?!" --align=justify`
###### Does it displays the correct result justified?
##### Try passing as arguments `"a -> A b -> B c -> C" --align=right`
###### Does it displays the correct result at the right side?
#### Basic
###### +Does the project runs quickly and effectively (Favoring of recursive, no unnecessary data requests, etc.)?
###### +Is the output of the program well structured? Does any letter seems to be out of line?
###### +Is there a test file for this code?
###### +Are the tests checking each possible case?
###### +Does the code obey the [good practices](https://github.com/01-edu/public/blob/master/subjects/good-practices.en.md)?
#### Social
###### +Did you learn anything from this project?
###### +Would you recommend/nominate this program as an example for the rest of the school?

32
subjects/ascii-art/ascii-art-output.audit.en.md → subjects/ascii-art/ascii-output.audit.en.md

@ -126,31 +126,13 @@ student$ cat test07.txt
#### Basic
###### *Has the code passed the formatting? (gofmt, goimports)
###### *Does the project runs quickly and effectively? (Favoring recursive, no unnecessary data requests, etc)
###### *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 Are not 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://github.com/01-edu/public/blob/master/subjects/good-practices.en.md)
###### *Is the error handled, is it error free?
###### *Is there a test file for this code?
###### *Are the tests checking each case possible?
###### *Is the output of the program well structured? Does any letter seems to be out of line?
###### +Does the project runs quickly and effectively (Favoring of recursive, no unnecessary data requests, etc.)?
###### +Is the output of the program well structured? Does any letter seems to be out of line?
###### +Is there a test file for this code?
###### +Are the tests checking each possible case?
###### +Does the code obey the [good practices](https://github.com/01-edu/public/blob/master/subjects/good-practices.en.md)?
#### Social
###### *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?
###### +Did you learn anything from this project?
###### +Would you recommend/nominate this program as an example for the rest of the school?
Loading…
Cancel
Save