diff options
author | Jasper Ras <jras@hostnet.nl> | 2024-11-23 11:30:28 +0100 |
---|---|---|
committer | Jasper Ras <jras@hostnet.nl> | 2024-11-23 11:30:28 +0100 |
commit | 1f1423fdb8d4e2928768ffa33a6ad2b59c75e82e (patch) | |
tree | 67d94f0d821a053aca0e7c8a7ffb6c369047aa14 /daily/2024-08-21.md | |
parent | 93d36010a9d54bca1fdcaf1f4c99e6981aaf41bc (diff) |
lowercase dirs
Diffstat (limited to 'daily/2024-08-21.md')
-rw-r--r-- | daily/2024-08-21.md | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/daily/2024-08-21.md b/daily/2024-08-21.md new file mode 100644 index 0000000..7408220 --- /dev/null +++ b/daily/2024-08-21.md @@ -0,0 +1,27 @@ +Need to start learning to take notes consistently. My idea now, to kick-off this process, is to open a daily note in obsidian every day at the start of the day in which I will keep crude, quick notes. +Then at the end of the day I shall take some time to go over the notes and refine them. Not yet sure if that refinement will already be the end result or if i should go over refined notes again at maybe the end of each week to see if they really stick. +I should commit notes to git to save them. + +Use taskwarrior to keep track of todo's. +`task <filter> <command> [ <mods> | <args> ]` +commands can be abbreviated as long as they dont become ambigious. +Tasks can be recurring. +See `man task`, specially the CONTEXT section, because i'm always confused about the context, `task context none` to unset the damn thing. +Annotate tasks that are critical with the critical tag, `task <ID> annotate +critical` or `task add +critical blaat` +Upgraded to taskwarrior3. Should set-up a task server to synchronize tasks to so I don't lose all of them if my laptop dies. + +Don't forget to always read man pages. Maybe I should create a detailed note about how to use man pages. + +I will start going to the office full-time from now on. +I should make sure my Obsidian notes and taskwarrior tasks are kept safely in a git repo in case i lose my laptop.l + +Today I learned that we can influence the output of `rabbitmqctl list_queues` , we can append it with keywords of columns that it should show, this also allows us to reorder them to set those pesky names on the end to have nicer formatting. +`rabbitmqctl list_queues messages consumers name` shows messages accumulated in Q and the number of consumers it has and then ends with the name. Of course this is explained in the manpage which I should read more often as noted before. + +I should ask for a diagram of the current systems and take note of it, e.g what is OneCRM / OneHOP / OneHome and all that. + +To upgrade a single package using apt we can use `apt-get install --only-upgrade <packagename>`. + +Need to "relearn" to design stuff and document it. + +Designing structures and a mechanism to return and store info about individual disk backups, we can send that as parent when making incremental backups. Currently we fetch parent reference from checkpoint, which in case of volume's doesn't work of course. It also breaks if, on the testpod, we reset all backups etc but dont do so with all checkpoints.
\ No newline at end of file |