Updated on : added Michael Bryzek's talk
Here lies most of the stuff I consider worthy to remember from the videos I stumbled upon on the web.
Alexander Fridman: My Dad, the Plasma Physicist | AI Podcast #100 with Lex Fridman [archived link]
- In Soviet Russia they used to make pupils write 12 pages of text without writing or grammar mistakes... in 2 languages: Russian AND Ukranian.
- Quality means perfection for Alexander. He takes the "hero" perspective of pushing quality to its most extreme limit (because quality is usually seen as a spectrum tending towards lack of flaws).
- Alexander used to know at least 1000 poems by heart.
Sisyphus 55 - The Modern Shaman: A Guide to Carl Jung [archived link]
- Jung talked to ghosts and believed those to be undeveloped personalities(?).
Jung - Sea of Faith - BBC documentary (Part 2 of 2) [archived link]
- For Jung, all religious ideas ale equally valid as expressions of human psychic life. Also, all religious "truths" and objects are simply psychological.
- Maybe this is connected with Nietzsche's claim that all philosophers do is articulate their being through their writing, not discovering absolute truths.
- For Jung, the knowledge of God is self-knowledge. Kinda like for Jesus:
the kingdom of God is within you.
Jordan Peterson - 45 minutes on a single paragraph of Nietzsche's Beyond Good & Evil [archived link]
- The living being vs. the rational being: The living being does things to continue living as its top priority, the rational being does not keep the same top priority. Nietzsche believed that people are not rational (philosophers included).
- Nietzsche thought that every philosopher is articulating their being through their writing, not discovering absolute truths — not thinking, but revealing (like a story).
- The nascent form of the Will to Power:
For every impulse is imperious, and as such, attempts to philosophize.
- Nietzsche says that these impulses/instincts are alive and are trying to live (expand, climb the dominance/competence hierarchy), ergo dominate.
- There might be no distinction between climbing the social ladder and the Will to Power. But, Peterson asks,
power in relationship to what?
Kurzgesagt - Optimistic Nihilism [archived link]
- We are small, we do not really matter. But, we are also miraculous and have been gifted with the power to make stuff matter. Life is really short.
So, we are free and pressed by time to make things nice and nice things:
There are so many dawns which have not yet shed their light.
Chris Lattner: The Future of Computing and Programming Languages | Lex Fridman Podcast #131 [archived link]
- Chris does not really bother with the meaning of life, but
the universe has a lot of value.
Archetype, Reality, Friendship and Literature: Peterson/Hurwitz [archived link]
- Intimacy nails you down to the ground, it makes you sane. It detracts from the perfection one can attain while being alone, but it offers you something more.
- You need a goal that is noble and meaningful enough to make the petty worries of daily life meaningless.
Parisa Tabriz - Black Hat USA 2018 Keynote [archived link]
- An argument for in-house software: you can't fix Windows' problems, you must pressure Windows to fix it, which takes more time.
Michael Bryzek - Design Microservice Architectures the Right Way [archived link]
- Code generation can be used to set strict standards across systems.
One programming language for every 4000 engineers.
- Starting with the API definition — which is seen as the backbone of the entire software system (excluding infrastructure) that a company provides and/or uses — allows for major system modifications (e.g. incorporating GDPR regulation) with a few language-neutral JSON/YAML/etc. line changes.
- If you start with the entire system being defined as an API you can store that API definition in Git (so you can revert back changes that would otherwise take more time to fix, collaborate, etc.) and do CI tasks on it: run linters, test the API, etc. For sure there are more pros and cons on this, like being able to understand how your system works without needing to look at MBs of code written in different programming languages (that you might not know). Cons? Not really a con, but: you still need to enforce code to only use defined interfaces to communicate with other services.
- The scenario described above defines the API specification as the (single?) source of truth for the system design. If, then, the system specification passes your tests (e.g. querying for a random user returns an error), you can also be sure that the system code passes those tests.
- It's language studies 101: the language you learn shapes how you think. In this case: the communication protocol you implement (the API definition) shapes your code.
How To Speak by Patrick Winston [archived link]
- Start with a promise, cycle around the subject, build a fence (distinguish from similar ideas), ask a question to keep people engaged, and use verbal punctuation to allow people to get back on the train of ideas (e.g. enumerate, use seven-second breaks, and stress some words).
- Get rid of title slides.
- End elegantly.
Your ideas are like your children, and you don't want them to go into the world in rags.