Ascii Art Colors Questions

subjects/ascii-art/ascii-color.audit.en.md

@@ -0,0 +1,54 @@
+#### Ascii-Color
+
+##### Try passing as arguments "hello world" --color=red.
+###### Does it displays the expected result?
+##### Try passing as arguments "1 + 1 = 2" --color=green.
+###### Does it display the expected result?
+##### Try passing as arguments "(%&) ??" --color=yellow.
+###### Does it display the expected result?
+##### Try specifying a set of letters to be colored (the second until the last letter).
+###### Does it displays the expected result (the corresponding set of letters with that color)?
+##### Try specifying letter to be colored(the second letter).
+###### Does it displays the expected result (the corresponding letter with that color)?
+##### Try specifying letter to be colored(just two letter).
+###### Does it displays the expected result (the corresponding letters with that color)?
+##### Try passing as arguments "HeY GuYs" --color=orange, in order to color "GuYs".
+###### Does it display the expected result?
+##### Try passing as arguments "RGB()" --color=blue, in order to color just the B.
+###### Does it display the expected result?
+
+#### General Requirements
+
+##### *Is it easy/intuitive to specify letter(s) to be coloured?
+##### *Can you use more than one color in the same string?
+
+#### 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?