I started the Intro to Cybersecurity Nanodegree some weeks ago and finished it today.

Just enrolled because of the flash sale back then, so ended up paying 270€.

The amount of content wa big, but the projects were often times ambigious in their tasks. Sometimes the downloads were messed up, e.g. wrong links.

In the original course, we had to create an account for Microsoft Azure to work with VMs. Microsoft Azure is a pain in the ass (duplicate subscriptions, wrong receipts, broken web UI etc.). Although the support people were nice and able to solve the wrong receipts, I will never use it again.

The automatically created course VMs were very slow (Windows 10 with 1GB RAM...) and horrible to work with.

One week ago, Udacity added cloud VMs, so we were able to connect to disposable VMs without an Azure account. This improved the experience a lot, although I already finished the VM-intensive projects.

All in all, I'm "okay" with the content and the projects. But I would never ever again pay 270€ for this course. (already subtracted discount of 75%)

Next time, I will search on coursera and pay after some looks into course.

I love to pay for online teaching. If it's worth the money.

miku86.com/finished-nanodegree…

Learnings

General

• default options are strong: I always ask myself, why people don't use my cool, sophisticated software, but Windows 10 / Edge / Chrome / Google Search / whatever

Project Management

• we mostly use the tools we know, e.g. we default to Trello, Excel, Google Docs etc.
• these tools shape how we think, e.g. "everything is a tablesheet, kanban etc."
• most use of this software is fragile, because it is owned by for-profit companies and closed source -> moral dilemma: buyer's need is not seller's need
• idea: use gitea/gitlab/github issues
• pros: everything in one place, no sending of files (excel etc), no additional accounts (only on the git platform), connection between management and code, removes complexity through using markdown
• cons: everyone needs an account, everyone has to learn simple markdown
• use labels for categorical information (e.g. bug, feature), use milestones for time-bound chunks of work; do not use milestones for categorical information

Commandline

• signals: sigint, sigterm, sigkill
• terminal multiplexer:
  • session (e.g. "work" or "personal") ->
  • window (e.g. "work/rust" or "work/nodejs") ->
  • panel (e.g. "work/rust/main.rs" or "work/rust/lib.rs")
• why multiplexer instead of multiple window manager windows: not always access to window manager (e.g. on server), also increases complexity (more software)

Reading

• blog.placemark.io/2021/07/19/i…

miku86.com/project-management/

Concepts: multiple notes or single summary?

I love to write down stuff. I am better at thinking than at memorizing, that's why I have a big amount of notes on my local drive.

In the last few months and years, I had this habit of blogging nearly daily.

The last few months, there was something going on: complexity and my love for good organization.

I love to have a user-friendly, well-organized summaries of a topic, let's call it "All I know about X".

In my daily notes, I also want to write about small stuff, let's say a newly learned shortcut for X.

Where should this new information live?

• in the daily note: Sure, because I learned it today. But I learn everything on a specific day, so I would not be able to add anything to a summary.
• in the summary: There are topics I'm heavily invested, e.g. Rust, Linux, nutrition, thinking, philosophy etc. There are also topics a "cheatsheet" is great, e.g. Vim. But I would always keep track which topics already have a summary, if/when I can start a new summary etc.

Alright, probably a mixed approach makes sense: writing daily notes and if a topic is big enough, copying it into a summary.

Implementation: blog or wiki?

The website I read the most: wikipedia.

I simply love it:

• clean, simple design
• internal linking
• free to use, free to share (en.wikipedia.org/wiki/Wikipedi…)
• access to the data's history

miku86.com/blog-or-wiki/

Ideas

• this is just my mental model, build your own
• life can be thought about in different environments, let's call them sessions; example: work environment, private environment, gym environment
• an environment can be divided into different projects, let's call them windows; example: work/client A, work/client B, private/hobby A
• a project can be divided into different tasks, let's call them panes; example: work/client A/add feature A, work/client B/add feature Z, private/hobby A/do workout D
• so I have different sessions, e.g. working on a tool, writing my blog
• when I want to work on my tool, I hit mod + s to show my sessions and then change to my "work on my tool" session, with all the tools set up
• when I want to switch to writing my blog, I hit mod + s again and go to my "write my blog" session, with all the tools set up

Shortcuts

• mod stands for modifier key; the default modifier key is ctrl + b, I changed mine to ctrl + a for ergonomics
• example: when I write mod + x, then hit your modifier key (defaults to ctrl + b) and x
• all shortcuts: mod + ?
• show all sessions: mod + s
• new window: mod + c
• kill window: mod + x
• go to next pane: mod + n
• go to previous pane: mod + p
• scroll up/down: mod, pageup/pagedown, quit: q

Links

• tmux faq
• github SetupNotes

miku86.com/tmux/

Ideas

Shortcuts

:help help
:q quit
:w write
:o open
esc escape mode
i insert mode
c - change mode
v - visual mode to select chars
V - visual line mode to select lines
vim tutor to learn
hjkl - left, down, up, right
u - undo
w - next start of word
b - last start of word
e - next end of word
f - find
x - delete char
dd - delete line
yy - copy line
yw - copy word
p - paste at cursor
P - paste before cursor
ctrl + r, 0 - paste in insert mode
r - replace with
3l - 3 times l key
di( - delete inside next (
da( - delete around next (
. - repeat last action
gg - go to start of file
G - go to end of file
dw: delete next (word)
ddp: swap lines
:% s/foo/bar/g: in all lines (`%`), `s`ubstitute (= search & replace) `foo` with `bar`
:% s/foo/bar/gc: in all lines (`%`), `s`ubstitute (= search & replace) `foo` with `bar`, ask for `c`onfirmation on each occurency
:1,$ s/foo/bar/g: from line `1` to the end (`$`), `s`ubstitute (= search & replace) `foo` with `bar`
:.,$ s/foo/bar/g: from the current line to the end (`$`), `s`ubstitute (= search & replace) `foo` with `bar`
:s/foo/bar/g: in the current line, `s`ubstitute (= search & replace) `foo` with `bar`

Links

• vimawesome.com/
• vim-adventures.com/
• vimgolf.com/
• vim.fandom.com/wiki/Search_and…

miku86.com/vim/