diff --git a/gen-weeknote.md b/gen-weeknote.sh similarity index 100% rename from gen-weeknote.md rename to gen-weeknote.sh diff --git a/productivity/anki.md b/productivity/anki.md new file mode 100644 index 0000000..d8b58b9 --- /dev/null +++ b/productivity/anki.md @@ -0,0 +1,27 @@ +Note: this page is not meant to be documentation for me as much as information to share with others. +--- + +SRS is an incredibly useful tool for learning and remembering things. +I highly recommend reading [Gwern's writing](https://gwern.net/spaced-repetition) if you want the full story. +I'll only highlight the most important parts: + +- One of the best ways to "train" your memory is to try to actively recall something. +- This is easy with flashcards. +- You can end up spending a lot of time reviewing flashcards that you already know the answers to. +- SRS aims to fix this by showing you cards at the optimal time. +- Anki is an SRS flashcard program. + - It's open source. + - It's free on all platforms except iOS (because that is the *only* way the developer the dev has chosen to make money, but it's only a one-time fee). +- You can share card decks with others. This makes it easy to get decks for things like languages that would have potentially thousands of cards. +- You can customize the scheduling to fit your needs. + +Now, Anki is a *very* versitile program and can be modified a lot to fit your needs and preferences. +However, I'd recommend that you start off with the defaults and use a deck that you make yourself. +Go find a Wikipedia article on a topic that interests you and collect various facts from it. +If you need some inspiration: [the Wardian case](https://en.wikipedia.org/wiki/Wardian_case), [Eustace Tilley](https://en.wikipedia.org/wiki/Eustace_Tilley), or [Nightwish](https://en.wikipedia.org/wiki/Nightwish) +(My first deck was trivia from *Index, A history of the* by Dennis Duncan.) +Why do I recommend this? + +- The defaults will prevent you from overloading on reviews early on. +- A deck that you make yourself will always be better than a pre-made for everything except the time taken to make it. You have to understand the content before you can make questions about it. + diff --git a/productivity/kanban.md b/productivity/kanban.md new file mode 100644 index 0000000..d4e64e4 --- /dev/null +++ b/productivity/kanban.md @@ -0,0 +1,23 @@ +notes from Kanban in Action + +- three core principles: + - visualize + - limit work-in-progress + - manage flow + +# Visualize +- transparency between team members +- easy-to-understand visuals +- only give *necessary* and *useful* information + - anything else is a waste to both read and to update + +## Kanban board +- should match *actual* process rather than *ideal* process +- queue columns: columns before and after the board with no limit on the number of items +- entry/edit criteria: criteria for items entering/exiting a column of the board + +### Work Items +- cards should facilitate decision making +- use color coding to show type of work +- visually identify work that is blocked +- optionally, link the cards to extra documentation using IDs (mostly useful for physical cards) diff --git a/study_plan.md b/study_plan.md new file mode 100644 index 0000000..eb6f10e --- /dev/null +++ b/study_plan.md @@ -0,0 +1,15 @@ +# Study Plan - Career +Modified: 2024-01-10 + +## General Plan +- 2 career topics + 1-2 non-career topics / mo +- Tested on one topic / quarter + +## Q1 +- How AI Works +- *Systems Engineering* +- Art + +## Future Topics +- Understanding Cryptography with OpenSSL 3.0 +- *VMware or RH cert* diff --git a/sysadmin/podman.md b/sysadmin/podman.md index ab8dbfd..15887b7 100644 --- a/sysadmin/podman.md +++ b/sysadmin/podman.md @@ -140,6 +140,7 @@ exit - describing and documenting image use ### Containerfile directives + ``` # FROM specifies the container to base the image off of # FROM scratch # start with no content at all @@ -193,10 +194,11 @@ RUN yum -y clean all - flags can be combined with commas - `-v ./html:/var/www/html:ro,z` - `:ro` - mount as read-only -- `:z` - relabel content for use by SELinux, allows multi-container access -- `:Z` - relabel content for use by SELinux, disallows multi-container access +- `:z` - recursively relabel content for use by SELinux, allows multi-container access +- `:Z` - recursively relabel content for use by SELinux, disallows multi-container access - `--security-opt label=disable` can be used to run containers with an "unconfined" label, if needed (but not recommended) - `:U` - change ownership of volume to match UID in container +- `:O` - mount as temporary storage, destroyed when finished executing ### Named Volumes @@ -205,4 +207,24 @@ RUN yum -y clean all - creates a directory for named volumes - can be used by multiple containers at once +## Pods +- comes from the Kubernetes project +- allows one or more containers to share namespaces and cgroups +- ensured shared SELinux labels +- all pods ahve a container called the *infra* or *pause* container to hold open namespaces/cgroups +- pods can optionally have *init* containers that run before the primary containers are executed + - can run either once on pod creation, or every time the pod is started +- "sidecar containers" are just other containers in the pod + + +### conmon +- container monitoring process +- added to every container that is in a pod +- lightweight C executable that monitors pod until exit +- executes OCI runtime +- responsible for reporting error code back to Podman +- provides socket for STDOUT and STDERR + + +fdsafdsa diff --git a/weeknotes/2023-49.md b/weeknotes/2023-49.md new file mode 100644 index 0000000..174035e --- /dev/null +++ b/weeknotes/2023-49.md @@ -0,0 +1,2 @@ +# 2023-49 +