#### Functional Project Questions

##### Try passing to the reverse flag (--reverse=example00.txt) the example 00 (github.com/public/subject/ascii-art/ascii-reverse-example.md).
`Hello World`
###### Does it display the value above?
##### Try passing to the reverse flag (--reverse=example01.txt) the example 01 (github.com/public/subject/ascii-art/ascii-reverse-example.md).
`123`
###### Does it display the value above?
##### Try passing to the reverse flag (--reverse=example02.txt) the example 02 (github.com/public/subject/ascii-art/ascii-reverse-example.md).
`#=\[`
###### Does it display the value above?
##### Try passing to the reverse flag (--reverse=example03.txt) the example 03 (github.com/public/subject/ascii-art/ascii-reverse-example.md).
`(somthing&234)`
###### Does it display the value above?
##### Try passing to the reverse flag (--reverse=example04.txt) the example 04 (github.com/public/subject/ascii-art/ascii-reverse-example.md).
`abcdefghijklmnopqrstuvwxyz`
###### Does it display the value above?
##### Try passing to the reverse flag (--reverse=example05.txt) the example 05 (github.com/public/subject/ascii-art/ascii-reverse-example.md).
`\!" #$%&'()*+,-./`
###### Does it display the value above?
##### Try passing to the reverse flag (--reverse=example06.txt) the example 06 (github.com/public/subject/ascii-art/ascii-reverse-example.md).
`:;<=>?@`
###### Does it display the value above?
##### Try passing to the reverse flag (--reverse=example07.txt) the example 07 (github.com/public/subject/ascii-art/ascii-reverse-example.md).
`ABCDEFGHIJKLMNOPQRSTUVWXYZ`
###### Does it display the value above?

#### 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?