From dbe655fca3cf4fc5bc882015006f006764eace52 Mon Sep 17 00:00:00 2001 From: Jasper Ras Date: Sat, 23 Nov 2024 17:15:20 +0100 Subject: organise most stuff into para dirs --- 0 inbox/2024-08-21.md | 27 ++++ 0 inbox/2024-08-22.md | 25 +++ 0 inbox/2024-08-23.md | 6 + 0 inbox/2024-08-26.md | 1 + 0 inbox/2024-08-27.md | 11 ++ 0 inbox/2024-08-28.md | 1 + 0 inbox/2024-08-29.md | 0 0 inbox/2024-09-03.md | 1 + 0 inbox/2024-09-10.md | 1 + 0 inbox/2024-09-30.md | 1 + 0 inbox/2024-10-02.md | 6 + 0 inbox/2024-10-04.md | 26 ++++ 0 inbox/2024-10-15.md | 3 + 0 inbox/2024-11-11.md | 3 + 0 inbox/2024-11-12.md | 3 + 0 inbox/antagonist_migratie.md | 27 ++++ 3 resources/Group.ONE Infrastructure.md | 1 + 3 resources/Man pages.md | 3 + 3 resources/Note taking.md | 7 + 3 resources/RabbitMQ.md | 2 + 3 resources/TaskWarrior (ToDo).md | 3 + 3 resources/programming/Elixir - modules.md | 0 3 resources/programming/Elixir.md | 228 ++++++++++++++++++++++++++++ 3 resources/programming/Nix.md | 16 ++ 3 resources/sollicitatie-vragenlijst.md | 7 + Elixir - modules.md | 0 Elixir.md | 228 ---------------------------- Nix.md | 16 -- antagonist_migratie.md | 27 ---- daily/2024-08-21.md | 27 ---- daily/2024-08-22.md | 25 --- daily/2024-08-23.md | 6 - daily/2024-08-26.md | 1 - daily/2024-08-27.md | 11 -- daily/2024-08-28.md | 1 - daily/2024-08-29.md | 0 daily/2024-09-03.md | 1 - daily/2024-09-10.md | 1 - daily/2024-09-30.md | 1 - daily/2024-10-02.md | 6 - daily/2024-10-04.md | 26 ---- daily/2024-10-15.md | 3 - daily/2024-11-11.md | 3 - daily/2024-11-12.md | 3 - interviews/Interview Mohammed Al-Mahdawi.md | 7 - interviews/Interview Patrick Spek.md | 21 --- interviews/Vragenlijst.md | 7 - refined/Group.ONE Infrastructure.md | 1 - refined/Man pages.md | 3 - refined/Note taking.md | 7 - refined/RabbitMQ.md | 2 - refined/TaskWarrior (ToDo).md | 3 - 52 files changed, 409 insertions(+), 437 deletions(-) create mode 100644 0 inbox/2024-08-21.md create mode 100644 0 inbox/2024-08-22.md create mode 100644 0 inbox/2024-08-23.md create mode 100644 0 inbox/2024-08-26.md create mode 100644 0 inbox/2024-08-27.md create mode 100644 0 inbox/2024-08-28.md create mode 100644 0 inbox/2024-08-29.md create mode 100644 0 inbox/2024-09-03.md create mode 100644 0 inbox/2024-09-10.md create mode 100644 0 inbox/2024-09-30.md create mode 100644 0 inbox/2024-10-02.md create mode 100644 0 inbox/2024-10-04.md create mode 100644 0 inbox/2024-10-15.md create mode 100644 0 inbox/2024-11-11.md create mode 100644 0 inbox/2024-11-12.md create mode 100644 0 inbox/antagonist_migratie.md create mode 100644 3 resources/Group.ONE Infrastructure.md create mode 100644 3 resources/Man pages.md create mode 100644 3 resources/Note taking.md create mode 100644 3 resources/RabbitMQ.md create mode 100644 3 resources/TaskWarrior (ToDo).md create mode 100644 3 resources/programming/Elixir - modules.md create mode 100644 3 resources/programming/Elixir.md create mode 100644 3 resources/programming/Nix.md create mode 100644 3 resources/sollicitatie-vragenlijst.md delete mode 100644 Elixir - modules.md delete mode 100644 Elixir.md delete mode 100644 Nix.md delete mode 100644 antagonist_migratie.md delete mode 100644 daily/2024-08-21.md delete mode 100644 daily/2024-08-22.md delete mode 100644 daily/2024-08-23.md delete mode 100644 daily/2024-08-26.md delete mode 100644 daily/2024-08-27.md delete mode 100644 daily/2024-08-28.md delete mode 100644 daily/2024-08-29.md delete mode 100644 daily/2024-09-03.md delete mode 100644 daily/2024-09-10.md delete mode 100644 daily/2024-09-30.md delete mode 100644 daily/2024-10-02.md delete mode 100644 daily/2024-10-04.md delete mode 100644 daily/2024-10-15.md delete mode 100644 daily/2024-11-11.md delete mode 100644 daily/2024-11-12.md delete mode 100644 interviews/Interview Mohammed Al-Mahdawi.md delete mode 100644 interviews/Interview Patrick Spek.md delete mode 100644 interviews/Vragenlijst.md delete mode 100644 refined/Group.ONE Infrastructure.md delete mode 100644 refined/Man pages.md delete mode 100644 refined/Note taking.md delete mode 100644 refined/RabbitMQ.md delete mode 100644 refined/TaskWarrior (ToDo).md diff --git a/0 inbox/2024-08-21.md b/0 inbox/2024-08-21.md new file mode 100644 index 0000000..7408220 --- /dev/null +++ b/0 inbox/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 [ | ]` +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 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 `. + +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 diff --git a/0 inbox/2024-08-22.md b/0 inbox/2024-08-22.md new file mode 100644 index 0000000..fd1531c --- /dev/null +++ b/0 inbox/2024-08-22.md @@ -0,0 +1,25 @@ +Woke up full of motivation to go to the office. Asked my honey if it's okay to join her by train "is there enough time left?", "yeah" she replied. Then when I come downstairs and she asks me if I can be fast, I tell her maybe it's better you go then bc i worry I will not be able to. Right away she storms off mad and angry... My motivation gone, so I'll work from home.. + +Went to the office anyway by motorcycle, cannot feel like I'm waking up when staying at home anymore. + +**MermaidJS ZenUML** +Optional **Title** +**Participants** can be declared when used or at the start. +**Annotators** give **participants** a special icon, defined at the doc site. +**Aliases** give a short **participant** name a more descriptive name when rendered, e.g: A as Alice <- Alice will be rendered, but the code can use A. +**Messages** between **participants** can be **sync, async, creation or reply**. +**Sync** use A.\ have a block {} for nested messages +**Async** use an arrow A->B: How are you? +**Creation** new keyword new A(optional params) +**Reply** three ways to define: +* Assign var from **Sync** message, e.g: OptionalType a = A.SyncMessage() +* Return A.SyncMessage { return blaat } +* @return or @reply on an **async** message +**Nesting** can be done on both creation and sync messages using blocks {}. +**Comments** can be added using `// comment` and support markdown. +**Loops** can be defined using keywords: **while, for, foreach and loop**. +**Alternative** paths can be sequenced using **if, else** statements. if(blaat) { A.syncMessage(B) } +**Opt** fragments rendered via `opt { ... }`. This can be useful for optional responses or paths. +**Parallel** paths can be defined using `par { ... }`. +**Try/catch/finally** statements are supported as well. +**@Starter(participant)** to make the line start from a **participant** \ No newline at end of file diff --git a/0 inbox/2024-08-23.md b/0 inbox/2024-08-23.md new file mode 100644 index 0000000..6f41ca2 --- /dev/null +++ b/0 inbox/2024-08-23.md @@ -0,0 +1,6 @@ +Discussed about Automatic Evac (HA). We were unsure about what to do when a local storage goes down. Do we restore the instances from backups to a new node? In that case a DB server might lose important transtactions. So we could also wait until it is fixed. + +Would like Rutger to explain the Freenet BGP load balancing setup in more detail. How do the routers work, what are all those interfaces attached to them? + +A local storage disk backup is stored as a QCOW2 image. An incremental has a relationship to its parent, because they neged to be rebased onto each other. +A volume disk backup is stored as raw data and is accompanied by a file of checksums per block. The extra file is used both to track dirtied blocks for incremental backup. \ No newline at end of file diff --git a/0 inbox/2024-08-26.md b/0 inbox/2024-08-26.md new file mode 100644 index 0000000..a91a1c9 --- /dev/null +++ b/0 inbox/2024-08-26.md @@ -0,0 +1 @@ +Nothing of note \ No newline at end of file diff --git a/0 inbox/2024-08-27.md b/0 inbox/2024-08-27.md new file mode 100644 index 0000000..eb75d3f --- /dev/null +++ b/0 inbox/2024-08-27.md @@ -0,0 +1,11 @@ +Changed a few things in the backup service: +* No longer delete all checkpoints when we make a full backup + * TODO: make sure we delete the checkpoint corresponding to a backup when the backup is deleted. + * TODO: Gracefully handle all checkpoints being deleted by openstack +* No longer explicitly specify "incremental" bool, just make it a best effort attempt. + * Still need to work out restores + + +When can we reboot n01.compute vps1-cph8. Its uptime is already 300 days. + +Short call with Jakub. Their priorities have shifted again, the focus on backup will be moved to improving performance of OneHome. They plan to synchronize data from OpenStack to OneHome so they can serve it faster. He asked me whether the customer can influence OpenStack state from within their VM. I told him that probably the only thing they can do to influence OpenStack is shutdown their VM. \ No newline at end of file diff --git a/0 inbox/2024-08-28.md b/0 inbox/2024-08-28.md new file mode 100644 index 0000000..ac0cac1 --- /dev/null +++ b/0 inbox/2024-08-28.md @@ -0,0 +1 @@ +Had a meeting about onehome performance, they query everything in existence for a customer because of their graphQL workflow. they want to now sync everything in existence to a table so their gQL is fast again. \ No newline at end of file diff --git a/0 inbox/2024-08-29.md b/0 inbox/2024-08-29.md new file mode 100644 index 0000000..e69de29 diff --git a/0 inbox/2024-09-03.md b/0 inbox/2024-09-03.md new file mode 100644 index 0000000..1d8a68e --- /dev/null +++ b/0 inbox/2024-09-03.md @@ -0,0 +1 @@ +one on one Rutger; diff --git a/0 inbox/2024-09-10.md b/0 inbox/2024-09-10.md new file mode 100644 index 0000000..07ff5ba --- /dev/null +++ b/0 inbox/2024-09-10.md @@ -0,0 +1 @@ +EYQBGNF95VORXXVVJ6NKFZF expressVPN \ No newline at end of file diff --git a/0 inbox/2024-09-30.md b/0 inbox/2024-09-30.md new file mode 100644 index 0000000..fef578b --- /dev/null +++ b/0 inbox/2024-09-30.md @@ -0,0 +1 @@ +- Check freenetvps gobs \ No newline at end of file diff --git a/0 inbox/2024-10-02.md b/0 inbox/2024-10-02.md new file mode 100644 index 0000000..64c611f --- /dev/null +++ b/0 inbox/2024-10-02.md @@ -0,0 +1,6 @@ +* Fixed n06 testpod, due to installing stuff via pip we had some conflicting packages being used. Pip has been purged and stuff seems to work normally now. +* Investigated DNS issues on testpod lb with Erik. +* Fixed some small issues in the backup service + * Deleted servers couldn't be removed from the periodic backup, that is now fixed. + * Less noisy logging by moving some stuff to debug level. +* Deployed image_id change to prod \ No newline at end of file diff --git a/0 inbox/2024-10-04.md b/0 inbox/2024-10-04.md new file mode 100644 index 0000000..9c77b37 --- /dev/null +++ b/0 inbox/2024-10-04.md @@ -0,0 +1,26 @@ +What is needed to recreate a deleted server: +* name +* description +* block device mapping +* image properties + * while restoring we need to somehow schedule according to image properties, e.g os_type, or is this already resolved by selecting the correct AZ? + * volumes need to clone volume_image_properties +* port mapping +* availability zone +* flavor +* propertieskjk + + + +port +* name +* description +* allowed_address_pairs +* dns_domain +* dns_name +* extra_dhcp_opts +* fixed_ips +* is_port_security_enabled +* security_group_ids +* qos_policy_id +* network_id \ No newline at end of file diff --git a/0 inbox/2024-10-15.md b/0 inbox/2024-10-15.md new file mode 100644 index 0000000..8887a01 --- /dev/null +++ b/0 inbox/2024-10-15.md @@ -0,0 +1,3 @@ +Reminder: +* write SOP for fix_allocation +* write SOP for fixing duplicate connector \ No newline at end of file diff --git a/0 inbox/2024-11-11.md b/0 inbox/2024-11-11.md new file mode 100644 index 0000000..5f3eedb --- /dev/null +++ b/0 inbox/2024-11-11.md @@ -0,0 +1,3 @@ +Sqlalchemy/mysql connections lijken een timeout te hitten +zie: +`https://kibana.one.com/s/openstack/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:now-7d%2Fd,to:now))&_a=(columns:!(),dataSource:(dataViewId:d80a7401-b1fd-43b2-bdfc-79dffb0e8b15,type:dataView),filters:!(),hideChart:!f,interval:auto,query:(language:kuery,query:%22cb3204fa-208f-4b90-95a0-846a9e13852b%22),sort:!(!('@timestamp',desc)))` diff --git a/0 inbox/2024-11-12.md b/0 inbox/2024-11-12.md new file mode 100644 index 0000000..e48d53f --- /dev/null +++ b/0 inbox/2024-11-12.md @@ -0,0 +1,3 @@ +Prometheus: +- scrape config: `roles/prometheus/onecom-prometheus-scrape-config-*.json` +- \ No newline at end of file diff --git a/0 inbox/antagonist_migratie.md b/0 inbox/antagonist_migratie.md new file mode 100644 index 0000000..c04a00b --- /dev/null +++ b/0 inbox/antagonist_migratie.md @@ -0,0 +1,27 @@ +Migrate VMs + +Not managed by customers, only Antagonist managed +Most of it is backoffice, only few are front facing + +Ovirt (KVM) + + +Possible to change IPs? + +Difficulty: private networking between hosts + databases only ones in the private network + + Should be possible to switch IPs + + +Outsourced routers to DC provider, more difficult to integrate networks + +Most of the things can be redeployed, Rutger notes that maybe all they need is access + +We can use their left-over IP space + +Features +- requires internal network, so want to create networks/routers +- HA/automatic failover? -> Not yet +- Anti-affinity rules? Dont want all the LBs on the same (failing) node + diff --git a/3 resources/Group.ONE Infrastructure.md b/3 resources/Group.ONE Infrastructure.md new file mode 100644 index 0000000..1d9ba33 --- /dev/null +++ b/3 resources/Group.ONE Infrastructure.md @@ -0,0 +1 @@ +I want to have an overview of systems and what they are responsible for. Example, what is OneHOP or OneHome and what do they do. I plan to write that down in this document. \ No newline at end of file diff --git a/3 resources/Man pages.md b/3 resources/Man pages.md new file mode 100644 index 0000000..901be15 --- /dev/null +++ b/3 resources/Man pages.md @@ -0,0 +1,3 @@ +**2024-08-21 18:07:20** +I need to more consistently read man pages. Example is `man task` to see how taskwarrior works, after reading it today I found that it is actually quite easy. +They often contain good information on how to use a certain tool. \ No newline at end of file diff --git a/3 resources/Note taking.md b/3 resources/Note taking.md new file mode 100644 index 0000000..2a47666 --- /dev/null +++ b/3 resources/Note taking.md @@ -0,0 +1,7 @@ +**2024-08-21 17:59:00** +I want to become better at taking notes consistently in the hope that I forget less important things and become better overall at managing knowledge. +To try and create the habit I will open a new daily note in Obsidian at the start of the day and sit down at the end of the day to refine anything written down into a more permanent form like this one. I'm hoping that by doing this consistently I will more often write down ideas, information, etc. during the day, rather than forget about it. + +After refining the daily notes, I should commit and push changes to a remote git repo that is also regularly backed up so I keep all this knowledge safe. + +I'm not yet sure if and how I incorporate this into a "zettelkast", something I did start before but never really stuck. I will need to do more research into this, and note taking overall. \ No newline at end of file diff --git a/3 resources/RabbitMQ.md b/3 resources/RabbitMQ.md new file mode 100644 index 0000000..e9c94c5 --- /dev/null +++ b/3 resources/RabbitMQ.md @@ -0,0 +1,2 @@ +**2024-08-21 18:09** +With `rabbitmqctl list_queues` we can add columns to show. So instead of the default layout which shows messages in the Q after the name and is horrible we can specify stuff like: `rabbitmqctl list_queues messages consumers name`. There are more options to be found in `man rabbitmqctl`. diff --git a/3 resources/TaskWarrior (ToDo).md b/3 resources/TaskWarrior (ToDo).md new file mode 100644 index 0000000..6002fde --- /dev/null +++ b/3 resources/TaskWarrior (ToDo).md @@ -0,0 +1,3 @@ +**2024-08-21 18:03:00** +I want to better keep track of what i'm doing, for that purpose I will use taskwarrior. For usage see `man task`. +Adding a task is done by `task add`, to modify it `task modify` . I use priorities, they can be set on a new or existing task with `priority:H/M/L`. diff --git a/3 resources/programming/Elixir - modules.md b/3 resources/programming/Elixir - modules.md new file mode 100644 index 0000000..e69de29 diff --git a/3 resources/programming/Elixir.md b/3 resources/programming/Elixir.md new file mode 100644 index 0000000..b106ae4 --- /dev/null +++ b/3 resources/programming/Elixir.md @@ -0,0 +1,228 @@ +Elixir supports "macro's", which is Elixir code that runs at compile time. They receive the AST of the source code as input and can apply transformations to it. This is how Elixir is written itself, using Elixir macro's. + +Elixir functions can be organized into [[Elixir - modules]]. +``` +defmodule MyModule do + # Comment + @moduledoc "Documentation for the module" + import IO + alias IO, as MyIO # Alias import + + @pi 3.14 # Module attribute + + @doc "Describe what the function does" + def hello do + MyIO.puts("blaat") + 3*@pi # Module attribute reference + done + + @spec hello_private(string) # typespec, can be used by dialyzer, very useful + defp hello_private(hello) do + puts(hello) + done +done +``` + +The [[Elixir - Kernel]] module is always imported, so functions we use without prefix come from Kernel. + +Elixir introduces a concept called [[Elixir - Atoms]]. They are named constants, like enumerations in C. +``` +:blaat +:"Bla at" +Blaat == :"Elixir.Blaat" # Alias + +var = :blaat # var contains only a reference to the atom, thus is small and fast. +``` + +[[Elixir - Aliases]] are internally represented as "Elixir.RealThing", in the case of the module alias above `MyIO == Elixir.IO`. + +[[Elixir - Tuples]] group a, usually small, fixed number of elements together. Kernel.elem/2 for access, Kernel.put_elem/3 for updating. + +[[Elixir - Lists]] are a recursive structure with a head of any type and a tail which is another list. They are notated as regular arrays in other languages, but can be written as `[head | tail]`. Therefore it's easy and efficient to push a new item to the top, we can use the head | tail notation -> +https://hexdocs.pm/elixir/List.html +https://hexdocs.pm/elixir/Enum.html +``` +list = [1, 2, 3] +list = [4 | list] +list +[4, 1, 2, 3] +``` + +[[Elixir - Immutable functions]] give a form of atomicity, because operations (other functions) they call do not mutate data if anything fails we can just return the original data without having changed anything. + +[[Elixir - Maps]] %{}, can also be created with Map.new([{1, 2}, {3, 4}]) (2-tuples). +https://hexdocs.pm/elixir/Map.html +``` +a = %{1 => 1} +a[1] +1 +``` +Maps can also be used to define structures, +``` +person = %{name: "Jasper"} +``` + +[[Elixir - Binaries]] are consecutive sequences of bytes. +``` +<<1, 1>> is a two-byte binary where each byte has value of, thus +0000 0001 0000 0001 +<<1>> <> <<2>> concatenate two binaries +0000 0001 0000 0010 +``` + +[[Elixir - Strings]] +``` +"This is a stringt" +" +Multiline +string +" +a = 1337 +"Print number #{a}" # #{} allows evaluation of values strings + +~s(This is a sigil which is also a string) +~s(Is useful to "use" quotes) +str = "INTERPOLATION!" +~S(Capital-S sigil allows prevention of string #{str} and \nescaping) +"Capital-S sigil allows prevention of string \#{str} and \\nescaping" + +"Blaat" <> " henk" # Concatenation works like binaries, because strings are binaries +``` + +[[Elixir - Lambda]] +``` +square = fn x -> # lambda's use fn + x*x +end + +square.(5) # lambda is called with name period arguments enclosed by parens. The dot is to make it known that we are calling a lambda and not a regular function. +``` + +For cases where the lambda just forwards its arguments to another function there is a special syntax, example: +[[Elixir - capture operator]] +``` +Enum.each([1, 2, 3], fn x -> IO.puts(x) end) +Enum.each([1, 2, 3], &IO.puts/1) # The & is called the "capture operator" and can also be used to shorten a lambda definition: +lambda = fn x, y, z -> x * y + z end +lambda = &(&1 * &2 + &3) # Like bash arguments ${1} ${2} etc +``` + +[[Elixir - Closure]] +A lambda can reference variables from the outside scope. If we rebind the variable in the parent scope, the lambda will still reference the old one. +``` +outside = "Abc" +lambda = &IO.puts/1 +outside = "cdef" +lambda.() +"Abc" +``` + +Range +0..1, internally represented as a map with bounds set, therefore small no matter how "big" the range. Is also an enumeration so can use the Enum module. + +Keyword list +List of 2-tuple where the 1st element is an atom. E.g. `[{:monday, 1}, {:tuesday, 2}]` can be written more elegant as `[monday: 1, tuesday: 2]` +https://hexdocs.pm/elixir/Keyword.html +Can be used as kwargs like in python. + +MapSet +https://hexdocs.pm/elixir/MapSet.html +Also an enumeration. +Initialize with MapSet.new + +Times and Dates +Have modules: Date, Time, DateTime, NaiveDateTime +Created with sigil ~D for dates, and ~T for time +``` +dt = ~D[2023-01-01] +dt.year +2023 + +tm = ~T[19:03:32] +tm.second +32 +``` + +IO lists +Are lists that can consist of one of three types: +- Int in range 0..255 +- Binaries +- Another IO list +It is thus a tree. Input operations are O(1) + + +Pattern matching +The '=' operator is not an assignment operator, but a match operator. +pattern = expression +Pattern can be list, map, tuple, variable, binaries, binary strings +constants, atom can be matched to discriminate results of expressions. +{:ok, result} = expr, fails is expr returns for example {:error, result} +Patterns can be nested: `{_, {hour, _, }, _} = :calendar.local_time()` + +Maps can partial match, to extract a property from a complex map. +Lists can abuse their recursive naturs: `[head | tail] = [1, 2, 3] head = 1, tail = [2,3]` +Pin-operator `^` is used to match against the value of a variable: +``` +a = "Bob" +{^a, _} = {"Bob", 25} <- Matches because the value of a is "Bob" +{^a, _} = {"Alice", 25} <- Doesn't match +``` + +Pattern matching using strings it's possible to match the beginning of a string and assign the rest to a var: +``` +command = "ping www.hostnet.nl" +"ping " <> url = command +url = "www.hostnet.nl" +``` + +Pattern matching can be done in function arguments and enabled "multiclause functions", which is a sort of function overloading. It's multiple definitions of the same function, with the same arity, but with different argument patterns. They are treated as a single function, so with the capture operator you can use all "variants". +``` +defmodule Geo do + def area({:square, a, b}), do a * b end + def area({:circle, r}), do r * r * pi end + def area(unknown), do {:error, {:unknown_shape, unknown}} end + # ^ do mind that the arity has to match for this catch-all error, also + # ordering is important. The runtime matches from top to bottom. +end + +fn = &Geo.area/1 + +fn.({:square, 1, 2}) +2 +fn.({:circle, 23}) +whatever this is +``` + +Conditionals can be implemented using multiclause functions, but also with the regular if..else statements, cond do .. end and case expression do ... end. + +A with-clause can be used to match multiple patterns in order and halt if a pattern doesn't match. +``` +defp extract_login(%{"login" => login}%) do, %{:ok, login} end +defp extract_login(_) do, {:error, "login missing"} end + +defp extract_email(%{"email" => email}) do, %{:ok, email} end +defp extract_email(_) do, %{:error, "email missing"} end + +def extract_user(user) do + case extract_login(user) do + {:error, reason} -> {:error, reason} + {:ok, login} -> + case extract_email(user) do + {:error, reason} -> {:error, reason} + {ok, email} -> %{login: login, email: email} + end + end +end + +# can be written as + +def extract_user(user) do + with {:ok, login} <- extract_login(user), + {:ok, email} <- extract_email(user) do + {:ok, %{login: login, email: email}} + end +end +``` + +Looping is mainly implemented via recursion. The break condition is implemented via a multiclause function matching the condition that you want to break at. +Recursion can be expensive, unless the recursive call is at the end of a function, which is called a tail-call. Tail-calls are optimized to not require any additional memory, because their result is also the result of the caller, so we don't need to come back to the caller. \ No newline at end of file diff --git a/3 resources/programming/Nix.md b/3 resources/programming/Nix.md new file mode 100644 index 0000000..fca31a8 --- /dev/null +++ b/3 resources/programming/Nix.md @@ -0,0 +1,16 @@ + `nix repl` to interactively evaluate Nix expressions. `:p` if output is not full. + `nix-instantiate --eval .nix` to evaluate a Nix expression from a file. `--strict`. + +Nix is like JSON, but with functions. +Recursive attribute sets can reference values declared earlier in the same set. +```nix +rec { + one = 1; + two = one + 1; +} +``` + +A `let` binding is used to assign names to values just as attribute sets, they can then be used in expressions. Let bindings have a local scope. + +A `with` allows referencing attributes of attribute sets without referencing the set. + diff --git a/3 resources/sollicitatie-vragenlijst.md b/3 resources/sollicitatie-vragenlijst.md new file mode 100644 index 0000000..08e2f89 --- /dev/null +++ b/3 resources/sollicitatie-vragenlijst.md @@ -0,0 +1,7 @@ +- Ben je bekend met scrum, agile, kanban, jira etc? + + +Technische vragen: +threading, race conditions, deadlocks +message queue +- Kun je uitleggen hoe een binary search werkt \ No newline at end of file diff --git a/Elixir - modules.md b/Elixir - modules.md deleted file mode 100644 index e69de29..0000000 diff --git a/Elixir.md b/Elixir.md deleted file mode 100644 index b106ae4..0000000 --- a/Elixir.md +++ /dev/null @@ -1,228 +0,0 @@ -Elixir supports "macro's", which is Elixir code that runs at compile time. They receive the AST of the source code as input and can apply transformations to it. This is how Elixir is written itself, using Elixir macro's. - -Elixir functions can be organized into [[Elixir - modules]]. -``` -defmodule MyModule do - # Comment - @moduledoc "Documentation for the module" - import IO - alias IO, as MyIO # Alias import - - @pi 3.14 # Module attribute - - @doc "Describe what the function does" - def hello do - MyIO.puts("blaat") - 3*@pi # Module attribute reference - done - - @spec hello_private(string) # typespec, can be used by dialyzer, very useful - defp hello_private(hello) do - puts(hello) - done -done -``` - -The [[Elixir - Kernel]] module is always imported, so functions we use without prefix come from Kernel. - -Elixir introduces a concept called [[Elixir - Atoms]]. They are named constants, like enumerations in C. -``` -:blaat -:"Bla at" -Blaat == :"Elixir.Blaat" # Alias - -var = :blaat # var contains only a reference to the atom, thus is small and fast. -``` - -[[Elixir - Aliases]] are internally represented as "Elixir.RealThing", in the case of the module alias above `MyIO == Elixir.IO`. - -[[Elixir - Tuples]] group a, usually small, fixed number of elements together. Kernel.elem/2 for access, Kernel.put_elem/3 for updating. - -[[Elixir - Lists]] are a recursive structure with a head of any type and a tail which is another list. They are notated as regular arrays in other languages, but can be written as `[head | tail]`. Therefore it's easy and efficient to push a new item to the top, we can use the head | tail notation -> -https://hexdocs.pm/elixir/List.html -https://hexdocs.pm/elixir/Enum.html -``` -list = [1, 2, 3] -list = [4 | list] -list -[4, 1, 2, 3] -``` - -[[Elixir - Immutable functions]] give a form of atomicity, because operations (other functions) they call do not mutate data if anything fails we can just return the original data without having changed anything. - -[[Elixir - Maps]] %{}, can also be created with Map.new([{1, 2}, {3, 4}]) (2-tuples). -https://hexdocs.pm/elixir/Map.html -``` -a = %{1 => 1} -a[1] -1 -``` -Maps can also be used to define structures, -``` -person = %{name: "Jasper"} -``` - -[[Elixir - Binaries]] are consecutive sequences of bytes. -``` -<<1, 1>> is a two-byte binary where each byte has value of, thus -0000 0001 0000 0001 -<<1>> <> <<2>> concatenate two binaries -0000 0001 0000 0010 -``` - -[[Elixir - Strings]] -``` -"This is a stringt" -" -Multiline -string -" -a = 1337 -"Print number #{a}" # #{} allows evaluation of values strings - -~s(This is a sigil which is also a string) -~s(Is useful to "use" quotes) -str = "INTERPOLATION!" -~S(Capital-S sigil allows prevention of string #{str} and \nescaping) -"Capital-S sigil allows prevention of string \#{str} and \\nescaping" - -"Blaat" <> " henk" # Concatenation works like binaries, because strings are binaries -``` - -[[Elixir - Lambda]] -``` -square = fn x -> # lambda's use fn - x*x -end - -square.(5) # lambda is called with name period arguments enclosed by parens. The dot is to make it known that we are calling a lambda and not a regular function. -``` - -For cases where the lambda just forwards its arguments to another function there is a special syntax, example: -[[Elixir - capture operator]] -``` -Enum.each([1, 2, 3], fn x -> IO.puts(x) end) -Enum.each([1, 2, 3], &IO.puts/1) # The & is called the "capture operator" and can also be used to shorten a lambda definition: -lambda = fn x, y, z -> x * y + z end -lambda = &(&1 * &2 + &3) # Like bash arguments ${1} ${2} etc -``` - -[[Elixir - Closure]] -A lambda can reference variables from the outside scope. If we rebind the variable in the parent scope, the lambda will still reference the old one. -``` -outside = "Abc" -lambda = &IO.puts/1 -outside = "cdef" -lambda.() -"Abc" -``` - -Range -0..1, internally represented as a map with bounds set, therefore small no matter how "big" the range. Is also an enumeration so can use the Enum module. - -Keyword list -List of 2-tuple where the 1st element is an atom. E.g. `[{:monday, 1}, {:tuesday, 2}]` can be written more elegant as `[monday: 1, tuesday: 2]` -https://hexdocs.pm/elixir/Keyword.html -Can be used as kwargs like in python. - -MapSet -https://hexdocs.pm/elixir/MapSet.html -Also an enumeration. -Initialize with MapSet.new - -Times and Dates -Have modules: Date, Time, DateTime, NaiveDateTime -Created with sigil ~D for dates, and ~T for time -``` -dt = ~D[2023-01-01] -dt.year -2023 - -tm = ~T[19:03:32] -tm.second -32 -``` - -IO lists -Are lists that can consist of one of three types: -- Int in range 0..255 -- Binaries -- Another IO list -It is thus a tree. Input operations are O(1) - - -Pattern matching -The '=' operator is not an assignment operator, but a match operator. -pattern = expression -Pattern can be list, map, tuple, variable, binaries, binary strings -constants, atom can be matched to discriminate results of expressions. -{:ok, result} = expr, fails is expr returns for example {:error, result} -Patterns can be nested: `{_, {hour, _, }, _} = :calendar.local_time()` - -Maps can partial match, to extract a property from a complex map. -Lists can abuse their recursive naturs: `[head | tail] = [1, 2, 3] head = 1, tail = [2,3]` -Pin-operator `^` is used to match against the value of a variable: -``` -a = "Bob" -{^a, _} = {"Bob", 25} <- Matches because the value of a is "Bob" -{^a, _} = {"Alice", 25} <- Doesn't match -``` - -Pattern matching using strings it's possible to match the beginning of a string and assign the rest to a var: -``` -command = "ping www.hostnet.nl" -"ping " <> url = command -url = "www.hostnet.nl" -``` - -Pattern matching can be done in function arguments and enabled "multiclause functions", which is a sort of function overloading. It's multiple definitions of the same function, with the same arity, but with different argument patterns. They are treated as a single function, so with the capture operator you can use all "variants". -``` -defmodule Geo do - def area({:square, a, b}), do a * b end - def area({:circle, r}), do r * r * pi end - def area(unknown), do {:error, {:unknown_shape, unknown}} end - # ^ do mind that the arity has to match for this catch-all error, also - # ordering is important. The runtime matches from top to bottom. -end - -fn = &Geo.area/1 - -fn.({:square, 1, 2}) -2 -fn.({:circle, 23}) -whatever this is -``` - -Conditionals can be implemented using multiclause functions, but also with the regular if..else statements, cond do .. end and case expression do ... end. - -A with-clause can be used to match multiple patterns in order and halt if a pattern doesn't match. -``` -defp extract_login(%{"login" => login}%) do, %{:ok, login} end -defp extract_login(_) do, {:error, "login missing"} end - -defp extract_email(%{"email" => email}) do, %{:ok, email} end -defp extract_email(_) do, %{:error, "email missing"} end - -def extract_user(user) do - case extract_login(user) do - {:error, reason} -> {:error, reason} - {:ok, login} -> - case extract_email(user) do - {:error, reason} -> {:error, reason} - {ok, email} -> %{login: login, email: email} - end - end -end - -# can be written as - -def extract_user(user) do - with {:ok, login} <- extract_login(user), - {:ok, email} <- extract_email(user) do - {:ok, %{login: login, email: email}} - end -end -``` - -Looping is mainly implemented via recursion. The break condition is implemented via a multiclause function matching the condition that you want to break at. -Recursion can be expensive, unless the recursive call is at the end of a function, which is called a tail-call. Tail-calls are optimized to not require any additional memory, because their result is also the result of the caller, so we don't need to come back to the caller. \ No newline at end of file diff --git a/Nix.md b/Nix.md deleted file mode 100644 index fca31a8..0000000 --- a/Nix.md +++ /dev/null @@ -1,16 +0,0 @@ - `nix repl` to interactively evaluate Nix expressions. `:p` if output is not full. - `nix-instantiate --eval .nix` to evaluate a Nix expression from a file. `--strict`. - -Nix is like JSON, but with functions. -Recursive attribute sets can reference values declared earlier in the same set. -```nix -rec { - one = 1; - two = one + 1; -} -``` - -A `let` binding is used to assign names to values just as attribute sets, they can then be used in expressions. Let bindings have a local scope. - -A `with` allows referencing attributes of attribute sets without referencing the set. - diff --git a/antagonist_migratie.md b/antagonist_migratie.md deleted file mode 100644 index c04a00b..0000000 --- a/antagonist_migratie.md +++ /dev/null @@ -1,27 +0,0 @@ -Migrate VMs - -Not managed by customers, only Antagonist managed -Most of it is backoffice, only few are front facing - -Ovirt (KVM) - - -Possible to change IPs? - -Difficulty: private networking between hosts - databases only ones in the private network - - Should be possible to switch IPs - - -Outsourced routers to DC provider, more difficult to integrate networks - -Most of the things can be redeployed, Rutger notes that maybe all they need is access - -We can use their left-over IP space - -Features -- requires internal network, so want to create networks/routers -- HA/automatic failover? -> Not yet -- Anti-affinity rules? Dont want all the LBs on the same (failing) node - diff --git a/daily/2024-08-21.md b/daily/2024-08-21.md deleted file mode 100644 index 7408220..0000000 --- a/daily/2024-08-21.md +++ /dev/null @@ -1,27 +0,0 @@ -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 [ | ]` -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 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 `. - -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 diff --git a/daily/2024-08-22.md b/daily/2024-08-22.md deleted file mode 100644 index fd1531c..0000000 --- a/daily/2024-08-22.md +++ /dev/null @@ -1,25 +0,0 @@ -Woke up full of motivation to go to the office. Asked my honey if it's okay to join her by train "is there enough time left?", "yeah" she replied. Then when I come downstairs and she asks me if I can be fast, I tell her maybe it's better you go then bc i worry I will not be able to. Right away she storms off mad and angry... My motivation gone, so I'll work from home.. - -Went to the office anyway by motorcycle, cannot feel like I'm waking up when staying at home anymore. - -**MermaidJS ZenUML** -Optional **Title** -**Participants** can be declared when used or at the start. -**Annotators** give **participants** a special icon, defined at the doc site. -**Aliases** give a short **participant** name a more descriptive name when rendered, e.g: A as Alice <- Alice will be rendered, but the code can use A. -**Messages** between **participants** can be **sync, async, creation or reply**. -**Sync** use A.\ have a block {} for nested messages -**Async** use an arrow A->B: How are you? -**Creation** new keyword new A(optional params) -**Reply** three ways to define: -* Assign var from **Sync** message, e.g: OptionalType a = A.SyncMessage() -* Return A.SyncMessage { return blaat } -* @return or @reply on an **async** message -**Nesting** can be done on both creation and sync messages using blocks {}. -**Comments** can be added using `// comment` and support markdown. -**Loops** can be defined using keywords: **while, for, foreach and loop**. -**Alternative** paths can be sequenced using **if, else** statements. if(blaat) { A.syncMessage(B) } -**Opt** fragments rendered via `opt { ... }`. This can be useful for optional responses or paths. -**Parallel** paths can be defined using `par { ... }`. -**Try/catch/finally** statements are supported as well. -**@Starter(participant)** to make the line start from a **participant** \ No newline at end of file diff --git a/daily/2024-08-23.md b/daily/2024-08-23.md deleted file mode 100644 index 6f41ca2..0000000 --- a/daily/2024-08-23.md +++ /dev/null @@ -1,6 +0,0 @@ -Discussed about Automatic Evac (HA). We were unsure about what to do when a local storage goes down. Do we restore the instances from backups to a new node? In that case a DB server might lose important transtactions. So we could also wait until it is fixed. - -Would like Rutger to explain the Freenet BGP load balancing setup in more detail. How do the routers work, what are all those interfaces attached to them? - -A local storage disk backup is stored as a QCOW2 image. An incremental has a relationship to its parent, because they neged to be rebased onto each other. -A volume disk backup is stored as raw data and is accompanied by a file of checksums per block. The extra file is used both to track dirtied blocks for incremental backup. \ No newline at end of file diff --git a/daily/2024-08-26.md b/daily/2024-08-26.md deleted file mode 100644 index a91a1c9..0000000 --- a/daily/2024-08-26.md +++ /dev/null @@ -1 +0,0 @@ -Nothing of note \ No newline at end of file diff --git a/daily/2024-08-27.md b/daily/2024-08-27.md deleted file mode 100644 index eb75d3f..0000000 --- a/daily/2024-08-27.md +++ /dev/null @@ -1,11 +0,0 @@ -Changed a few things in the backup service: -* No longer delete all checkpoints when we make a full backup - * TODO: make sure we delete the checkpoint corresponding to a backup when the backup is deleted. - * TODO: Gracefully handle all checkpoints being deleted by openstack -* No longer explicitly specify "incremental" bool, just make it a best effort attempt. - * Still need to work out restores - - -When can we reboot n01.compute vps1-cph8. Its uptime is already 300 days. - -Short call with Jakub. Their priorities have shifted again, the focus on backup will be moved to improving performance of OneHome. They plan to synchronize data from OpenStack to OneHome so they can serve it faster. He asked me whether the customer can influence OpenStack state from within their VM. I told him that probably the only thing they can do to influence OpenStack is shutdown their VM. \ No newline at end of file diff --git a/daily/2024-08-28.md b/daily/2024-08-28.md deleted file mode 100644 index ac0cac1..0000000 --- a/daily/2024-08-28.md +++ /dev/null @@ -1 +0,0 @@ -Had a meeting about onehome performance, they query everything in existence for a customer because of their graphQL workflow. they want to now sync everything in existence to a table so their gQL is fast again. \ No newline at end of file diff --git a/daily/2024-08-29.md b/daily/2024-08-29.md deleted file mode 100644 index e69de29..0000000 diff --git a/daily/2024-09-03.md b/daily/2024-09-03.md deleted file mode 100644 index 1d8a68e..0000000 --- a/daily/2024-09-03.md +++ /dev/null @@ -1 +0,0 @@ -one on one Rutger; diff --git a/daily/2024-09-10.md b/daily/2024-09-10.md deleted file mode 100644 index 07ff5ba..0000000 --- a/daily/2024-09-10.md +++ /dev/null @@ -1 +0,0 @@ -EYQBGNF95VORXXVVJ6NKFZF expressVPN \ No newline at end of file diff --git a/daily/2024-09-30.md b/daily/2024-09-30.md deleted file mode 100644 index fef578b..0000000 --- a/daily/2024-09-30.md +++ /dev/null @@ -1 +0,0 @@ -- Check freenetvps gobs \ No newline at end of file diff --git a/daily/2024-10-02.md b/daily/2024-10-02.md deleted file mode 100644 index 64c611f..0000000 --- a/daily/2024-10-02.md +++ /dev/null @@ -1,6 +0,0 @@ -* Fixed n06 testpod, due to installing stuff via pip we had some conflicting packages being used. Pip has been purged and stuff seems to work normally now. -* Investigated DNS issues on testpod lb with Erik. -* Fixed some small issues in the backup service - * Deleted servers couldn't be removed from the periodic backup, that is now fixed. - * Less noisy logging by moving some stuff to debug level. -* Deployed image_id change to prod \ No newline at end of file diff --git a/daily/2024-10-04.md b/daily/2024-10-04.md deleted file mode 100644 index 9c77b37..0000000 --- a/daily/2024-10-04.md +++ /dev/null @@ -1,26 +0,0 @@ -What is needed to recreate a deleted server: -* name -* description -* block device mapping -* image properties - * while restoring we need to somehow schedule according to image properties, e.g os_type, or is this already resolved by selecting the correct AZ? - * volumes need to clone volume_image_properties -* port mapping -* availability zone -* flavor -* propertieskjk - - - -port -* name -* description -* allowed_address_pairs -* dns_domain -* dns_name -* extra_dhcp_opts -* fixed_ips -* is_port_security_enabled -* security_group_ids -* qos_policy_id -* network_id \ No newline at end of file diff --git a/daily/2024-10-15.md b/daily/2024-10-15.md deleted file mode 100644 index 8887a01..0000000 --- a/daily/2024-10-15.md +++ /dev/null @@ -1,3 +0,0 @@ -Reminder: -* write SOP for fix_allocation -* write SOP for fixing duplicate connector \ No newline at end of file diff --git a/daily/2024-11-11.md b/daily/2024-11-11.md deleted file mode 100644 index 5f3eedb..0000000 --- a/daily/2024-11-11.md +++ /dev/null @@ -1,3 +0,0 @@ -Sqlalchemy/mysql connections lijken een timeout te hitten -zie: -`https://kibana.one.com/s/openstack/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:now-7d%2Fd,to:now))&_a=(columns:!(),dataSource:(dataViewId:d80a7401-b1fd-43b2-bdfc-79dffb0e8b15,type:dataView),filters:!(),hideChart:!f,interval:auto,query:(language:kuery,query:%22cb3204fa-208f-4b90-95a0-846a9e13852b%22),sort:!(!('@timestamp',desc)))` diff --git a/daily/2024-11-12.md b/daily/2024-11-12.md deleted file mode 100644 index e48d53f..0000000 --- a/daily/2024-11-12.md +++ /dev/null @@ -1,3 +0,0 @@ -Prometheus: -- scrape config: `roles/prometheus/onecom-prometheus-scrape-config-*.json` -- \ No newline at end of file diff --git a/interviews/Interview Mohammed Al-Mahdawi.md b/interviews/Interview Mohammed Al-Mahdawi.md deleted file mode 100644 index 7c0ab8c..0000000 --- a/interviews/Interview Mohammed Al-Mahdawi.md +++ /dev/null @@ -1,7 +0,0 @@ -Bekendheid met virtualisatie? Libvirt? QEMU? -Puppet, Ansible, chef? -Heeft Erlang geprogrammeerd? BEAM tunen/beheren? RabbitMQ? -Gezien vooral functioneel programmeren op CV: Bekendheid met OOP concepten? Ken je bijv. het repository pattern? -Weet je wat een test piramide is? - - Wat is het verschil tussen unit tests en integratie tests? - diff --git a/interviews/Interview Patrick Spek.md b/interviews/Interview Patrick Spek.md deleted file mode 100644 index 6f86ea9..0000000 --- a/interviews/Interview Patrick Spek.md +++ /dev/null @@ -1,21 +0,0 @@ -Wat wil ik weten? -* Wat zijn ze z'n hobbies? Is hij in zijn vrije tijd ook bezig met zelfontwikkeling? -* Is hij gepassioneerd over software ontwikkeling of is het iemand die dit doet omdat het goed verdiend? - -"They wanted better insights into how the mail service of their platform was used, so I set up some systems to keep better details. I also configured DMARC and made sure those reports were properly analyzed." - - -Wat gaan we doen? -Ff praten, wie ben je, waar kom je vandaan? -Daarna, CV erbij, vragen over stellen? - -Wat is de reden dat je weg wilt? -Waar ben je het meest trots op? - -openstack ciso, aws, aws nieuwe aws - -geen webcam.. meh - -is nu lead, word dat niet meer, wat vind je ervan? - -veel ervaring perl, is nu golang aan het leren \ No newline at end of file diff --git a/interviews/Vragenlijst.md b/interviews/Vragenlijst.md deleted file mode 100644 index 08e2f89..0000000 --- a/interviews/Vragenlijst.md +++ /dev/null @@ -1,7 +0,0 @@ -- Ben je bekend met scrum, agile, kanban, jira etc? - - -Technische vragen: -threading, race conditions, deadlocks -message queue -- Kun je uitleggen hoe een binary search werkt \ No newline at end of file diff --git a/refined/Group.ONE Infrastructure.md b/refined/Group.ONE Infrastructure.md deleted file mode 100644 index 1d9ba33..0000000 --- a/refined/Group.ONE Infrastructure.md +++ /dev/null @@ -1 +0,0 @@ -I want to have an overview of systems and what they are responsible for. Example, what is OneHOP or OneHome and what do they do. I plan to write that down in this document. \ No newline at end of file diff --git a/refined/Man pages.md b/refined/Man pages.md deleted file mode 100644 index 901be15..0000000 --- a/refined/Man pages.md +++ /dev/null @@ -1,3 +0,0 @@ -**2024-08-21 18:07:20** -I need to more consistently read man pages. Example is `man task` to see how taskwarrior works, after reading it today I found that it is actually quite easy. -They often contain good information on how to use a certain tool. \ No newline at end of file diff --git a/refined/Note taking.md b/refined/Note taking.md deleted file mode 100644 index 2a47666..0000000 --- a/refined/Note taking.md +++ /dev/null @@ -1,7 +0,0 @@ -**2024-08-21 17:59:00** -I want to become better at taking notes consistently in the hope that I forget less important things and become better overall at managing knowledge. -To try and create the habit I will open a new daily note in Obsidian at the start of the day and sit down at the end of the day to refine anything written down into a more permanent form like this one. I'm hoping that by doing this consistently I will more often write down ideas, information, etc. during the day, rather than forget about it. - -After refining the daily notes, I should commit and push changes to a remote git repo that is also regularly backed up so I keep all this knowledge safe. - -I'm not yet sure if and how I incorporate this into a "zettelkast", something I did start before but never really stuck. I will need to do more research into this, and note taking overall. \ No newline at end of file diff --git a/refined/RabbitMQ.md b/refined/RabbitMQ.md deleted file mode 100644 index e9c94c5..0000000 --- a/refined/RabbitMQ.md +++ /dev/null @@ -1,2 +0,0 @@ -**2024-08-21 18:09** -With `rabbitmqctl list_queues` we can add columns to show. So instead of the default layout which shows messages in the Q after the name and is horrible we can specify stuff like: `rabbitmqctl list_queues messages consumers name`. There are more options to be found in `man rabbitmqctl`. diff --git a/refined/TaskWarrior (ToDo).md b/refined/TaskWarrior (ToDo).md deleted file mode 100644 index 6002fde..0000000 --- a/refined/TaskWarrior (ToDo).md +++ /dev/null @@ -1,3 +0,0 @@ -**2024-08-21 18:03:00** -I want to better keep track of what i'm doing, for that purpose I will use taskwarrior. For usage see `man task`. -Adding a task is done by `task add`, to modify it `task modify` . I use priorities, they can be set on a new or existing task with `priority:H/M/L`. -- cgit v1.2.3