Closed Vages closed 2 years ago
I have a few candidates:
I would also suggest that this issue includes updating the paths in the markdown files after a name has been chosen:
For example in TASKS.md:
I would also suggest that this issue includes updating the paths in the markdown files after a name has been chosen:
For example in TASKS.md:
Done.
Two more suggestions:
Problem and solution seem like a good pair. They are antonyms.
Closed by b21c81431dd7f42ef25fc9d14851ee83393671df
Working with #12, I grew dissatisfied with my task naming convention:
begin
andend
. The expressions require too much explanation. And they simply sound bad.I settled for
working-area
andsolution
. These expressions are the best-fitting I have yet thought of. Solution is self-explanatory.working-area
conveys that this is where you should work.There are two weaknesses with these names:
solution
is where he/she is to program his/her solution in the solution (not so important)working-area
comes later thansolution
in the alphabet. Because the tasks themselves are sorted chronologically in the downward direction, the sub-parts of the task should be sorted chronologically in the same direction.To avoid problem two, I have prefixed the folders with 0 and 1, so that their chronology flows in the same direction as the tasks themselves.
That brings us to the title of this issue: Find self-explanatory names for finished and "unfinished" tasks where the finished variant is later in the alphabet. Any suggestions?