summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorOskar <[email protected]>2024-04-07 19:45:50 +0200
committerOskar <[email protected]>2024-04-07 19:45:50 +0200
commit5d9aa978796cd7290c4c7ece59a75da532fd839c (patch)
treed7b224836951d7a4aee253972fb6c556fce27634 /TODO
parent28bcb44c3690c5f58f25358341739a81e6535edc (diff)
N is completely done, will start on X maybe?
Diffstat (limited to 'TODO')
-rw-r--r--TODO6
1 files changed, 2 insertions, 4 deletions
diff --git a/TODO b/TODO
index 5443165..c7716d0 100644
--- a/TODO
+++ b/TODO
@@ -1,8 +1,6 @@
TODO list. This is mostly so i can plan more granularly and remember small stuff i was working on last time and what i should prioritise first.
This is not my overall big planning board. (1 highest prio, 10 lowest)
-1 - Think about how i want N to actually work
-1 - Implement N functionality.
-1 - Do tests on N
-2 - All L functionality is done. Did some testing and made some fixes. I will keep this here for now in case i find anything more.
+1 -
+2 - All L and N functionality is done. Did some testing and made some fixes. I will keep this here for now in case i find anything more.
2 - Not really a TODO point but more of an observation and a realisation i have made. I could have just used regex to do the validation of my commands. How about that... Well im too far in (sunk cost fallacy or whatever its called).