zaine/vault
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

13
Some checks failed
Build Quartz Notes / build (push) Failing after 20s
Details

Browse Source
This commit is contained in:
Zaine
2026-07-13 09:16:09 +01:00
parent 9645ee23b0
commit 129ce1442b
336 changed files with 3812 additions and 579 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
Articles/Notes/20 Software Engineering Laws.md Executable file
View File

@@ -0,0 +1,18 @@
---
pdf:
- "[[20-laws-software-engineering.pdf]]"
date started: 2026-06-03
date finished:
type: pdf-notes
done:
note type:
- dev-articles
---
# Link: <https://substack.com/inbox/post/194605697>
# 20 Software Engineering Laws: Notes
> [!PDF|yellow] [[20-laws-software-engineering.pdf#page=2&selection=6,0,6,53&color=yellow|20-laws-software-engineering, p.2]]
> > In particular, we will talk about the following laws:
>
> ![[Pasted image 20260624145412.png]]
![[Pasted image 20260624145432.png]]

BIN
Articles/Notes/Attachments/Pasted image 20260624145412.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 106 KiB

BIN
Articles/Notes/Attachments/Pasted image 20260624145432.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 95 KiB

39
Articles/Notes/Effect of Tiktok on teens.md Executable file
View File

@@ -0,0 +1,39 @@
---
pdf:
- "[[effect-of-tiktok-on-teens.pdf]]"
date started: 2026-06-03
date finished:
type:
done:
---
# # Effect of Tiktok on teens Notes
## Notes for page 1
> The latest TikTok statistics show that, as of July 2022, the platform has over one billion monthly active users worldwide
>
> In the US 62% of TikTok users are aged between 10 and 29
## Article Mention:
"TIKTOK - THE INFLUENCE ON SCHOOLPERFORMANCE AND SOCIAL LIFE OF ADOLESCENTS"
## Notes for page 2
> “Navigating the New Era of Influencer Marketing: How to be Successful on Instagram, TikTok, & Co”
> Just like there is no clock in a casino, Tiktok deliberately blurs the user's time judgment and hides the time in design.
## The negative impact of Tiktok on adolescent psychology
## Notes for page 3
> cyber-bullying generally involves using the Internet to threaten, harm, embarrass, or socially exclude others
> "The key period of personal socialization is the youth stage. In this stage, being bullied will weak adolescents' self-identity and increases the risk of anxiety and depression, which is not conducive to the development of adolescents' mental health and personality shaping"
> The Internet is a virtual world in which many netizens freely vent their anger and dissatisfaction, and abuse others at will to gain psychological catharsis.
## Notes for page 4
> “We are in an era of great change. This is the best time, and it is also a the worst times. Teenagers should constantly improve themselves, strengthen self-control and the ability to distinguish right from wrong, make use of the advantages brought by the Internet, and constantly explore the boundaries of the future, dare to try and create their own value”

33
Articles/Notes/Effects of insufficient sleep on circadian rhythmicity.md Executable file
View File

@@ -0,0 +1,33 @@
---
pdf:
- "[[Effects of insufficient sleep on circadian rhythmicity and expression amplitude of the human blood transcriptome.pdf]]"
date started: 2026-06-17
date finished:
type:
done:
---
# Effects of insufficient sleep on circadian rhythmicity: Notes
> [!PDF|] [[Effects of insufficient sleep on circadian rhythmicity and expression amplitude of the human blood transcriptome.pdf#page=1&selection=32,13,32,17|Effects of insufficient sleep on circadian rhythmicity and expression amplitude of the human blood transcriptome, p.1]]
> > SEM
>
> SEM stands for Standard Error of the Mean, which is a statistical measure that estimates the accuracy with which a sample mean represents the population mean. It is calculated by dividing the standard deviation (SD) of the sample by the square root of the sample size (n). SEM provides insight into how much variability there is in the sample mean and is often used to create confidence intervals around the mean. A smaller SEM indicates that the sample mean is likely to be closer to the true population mean, while a larger SEM suggests more variability and less precision in the estimate.
> [!PDF|] [[Effects of insufficient sleep on circadian rhythmicity and expression amplitude of the human blood transcriptome.pdf#page=1&selection=33,12,33,16|Effects of insufficient sleep on circadian rhythmicity and expression amplitude of the human blood transcriptome, p.1]]
> > RNA
>
> RNA stands for Ribonucleic Acid, which is a molecule essential for various biological roles, including coding, decoding, regulation, and expression of genes. RNA is typically single-stranded and is involved in the synthesis of proteins through the processes of transcription and translation. It serves as a messenger carrying instructions from DNA for controlling the synthesis of proteins, although some RNA molecules have catalytic and regulatory functions as well.
> [!PDF|] [[Effects of insufficient sleep on circadian rhythmicity and expression amplitude of the human blood transcriptome.pdf#page=1&selection=38,36,38,50|Effects of insufficient sleep on circadian rhythmicity and expression amplitude of the human blood transcriptome, p.1]]
> > Transcriptome
>
> Transcriptome refers to the complete set of RNA transcripts produced by the genome under specific circumstances or in a specific cell. It includes all types of RNA, such as messenger RNA (mRNA), ribosomal RNA (rRNA), transfer RNA (tRNA), and non-coding RNAs. The transcriptome provides insights into gene expression patterns, cellular functions, and responses to environmental changes, making it a crucial area of study in genomics and molecular biology.
> [!PDF|] [[Effects of insufficient sleep on circadian rhythmicity and expression amplitude of the human blood transcriptome.pdf#page=1&selection=118,0,121,1|Effects of insufficient sleep on circadian rhythmicity and expression amplitude of the human blood transcriptome, p.1]]
> > epidemiological studies
>
> Epidemiological studies are research investigations that study the distribution and determinants of health-related states or events in specific populations. These studies aim to identify risk factors for diseases, understand patterns of health and illness, and inform public health interventions. Epidemiological research can be observational (such as cohort, case-control, and cross-sectional studies) or experimental (such as randomized controlled trials), and it often involves analyzing data from large groups of people to draw conclusions about health trends and causes of disease.
> [!PDF|] [[Effects of insufficient sleep on circadian rhythmicity and expression amplitude of the human blood transcriptome.pdf#page=1&selection=177,26,179,62|Effects of insufficient sleep on circadian rhythmicity and expression amplitude of the human blood transcriptome, p.1]]
> > In fact, the liver transcriptome is affected to a larger extent by sleep loss than the brain transcriptome
>
>

88
Articles/Notes/Every Senior Engineer has read these books.md Executable file
View File

@@ -0,0 +1,88 @@
---
pdf: "[[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf]]"
type: pdf-notes
done: true
date started: 2026-06-15
date finished: 2026-06-15
note type:
- dev-articles
---
# Every Senior Engineer has read these books Notes:
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=1&annotation=743R|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.1]])
> But they also read specifically, they read books that challenge assumptions about how software should be built.
![[2026-05-22-senior-books.png]]
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=2&selection=2,41,2,42&color=yellow|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.2]])
> 1. The Pragmatic Programmer Hunt & Thomas
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=2&selection=7,0,7,33&color=yellow|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.2]])
> The DRY principle originated here
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=2&selection=10,0,57,42&color=red|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.2]])
>
> Tracer bullet approach:
> Instead of:
> [Full DB layer] → [Full business logic] → [Full API] → [Full UI]
> (nothing works until everything is done)
>
> Do this:
> [Minimal DB] → [Minimal logic] → [Minimal API] → [Minimal UI]
> (thin slice works end-to-end, then iterate
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=2&selection=62,57,62,58&color=yellow|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.2]])
> 2. Designing Data-Intensive Applications Martin Kleppmann
![[2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium.png]]
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=2&selection=133,16,133,17|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.2]])
> Author’s website
<https://dataintensive.net/>
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=2&annotation=748R1|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.2]])
> 3. The Mythical Man-Month Fred Brooks
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=2&annotation=749R|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.2]])
> Nine women cannot deliver a baby in one month.
![[2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-01.png]]
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=3&selection=48,28,48,29&color=yellow|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.3]])
> 4. Refactoring Martin Fowler
![[2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-02.png]]
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=3&selection=158,56,158,57&color=yellow|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.3]])
> 5. Software Architecture: The Hard Parts Richards & Ford
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=4&annotation=753R|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.4]])
> 6. Working Effectively with Legacy Code Michael Feathers
![[2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-03.png]]
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=4&selection=81,33,81,34&color=yellow|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.4]])
> 7. Database Internals Alex Petrov
![[2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-04.png]]
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=4&selection=180,50,180,51&color=yellow|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.4]])
> 8. A Philosophy of Software Design John Ousterhout
![[2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-05.png]]
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=4&selection=182,40,184,14&color=yellow|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.4]])
> Ousterhout’s core argument: the primary enemy of software quality is complexity, and complexity accumulates through shallow modules, information leakage, and temporal decomposition.
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=5&selection=94,30,94,31&color=yellow|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.5]])
> 9. Clean Code Robert C. Martin
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=5&annotation=760R1|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.5]])
> The Reading Order That Makes Sense
![[2026-05-22-every-senior-engineer-i-respect-has-read-these-books-have-you-by-the-latency-gambler-mar-2026-medium-06.png]]
> ([[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf#page=6&selection=3,0,3,34&color=yellow|Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium, p.6]])
> Nine books. Maybe 4,000 pages tota

30
Articles/Notes/I thought I knew system design.md Executable file
View File

@@ -0,0 +1,30 @@
---
pdf:
- "[[I Thought I Knew System Design Until I Met a Google L7 Interviewer.pdf]]"
date started: 2026-06-03
date finished: 2026-06-03
type: pdf-notes
done: true
---
# AI summary:
- System design is not about memorising architecture patterns; it is about knowing why each component is needed.
- Start with real numbers first, such as traffic, read/write ratio, latency, and throughput, before drawing the design.
- Every component, like caching, sharding, or replication, only helps under certain conditions.
- Good designers think through failure cases, such as database crashes, cache delays, or datacentre splits.
- The best approach is to start simple, measure the system, and only add complexity when a clear metric proves it is needed.
# Article Notes
> ([[I Thought I Knew System Design Until I Met a Google L7 Interviewer.pdf#page=2&annotation=341R|I Thought I Knew System Design Until I Met a Google L7 Interviewer, p.2]])
> sharding or replication.
Sharding is the process of splitting a database into smaller, more manageable pieces called shards. Each shard is a separate database that contains a subset of the data. Replication, on the other hand, is the process of copying data from one database to another. This can be done for backup purposes or to improve performance by distributing read requests across multiple replicas.
[[I Thought I Knew System Design Until I Met a Google L7 Interviewer.pdf#page=2|I Thought I Knew System Design Until I Met a Google L7 Interviewer, p.2]]
> This is the part that changes everything. Every component has this envelope of conditions where it actually helps. Caching works
> when reads dominate and access patterns cluster together. Sharding makes sense when write throughput matters way more than
> transactional guarantees. Replication helps when read availability beats consistency.
> ([[I Thought I Knew System Design Until I Met a Google L7 Interviewer.pdf#page=4&annotation=345R|I Thought I Knew System Design Until I Met a Google L7 Interviewer, p.4]])
> Start with one database, one server, no cache. Only scale when some specific metric like latency or throughput or cost crosses a threshold you can actually name. When you add a component, explain what new failure mode it introduces and how you’d even detect it.

22
Articles/Notes/Reason some people are likable.md Executable file
View File

@@ -0,0 +1,22 @@
---
pdf:
- "[[reason-some-people-are-likable.pdf]]"
date started: 2026-06-03
date finished: 2026-06-03
type:
- pdf-notes
done: true
---
# Reason some people are likable: Notes
> [!PDF|] [[reason-some-people-are-likable.pdf#page=4&selection=12,1,18,70|reason-some-people-are-likable, p.4]]
> > acceptance prophecy” — the psychological phenomenon where your expectation of being accepted or rejected subtly shapes your behavior, which in turn influences whether others actually accept or reject you.
> [!PDF|] [[reason-some-people-are-likable.pdf#page=7&selection=0,67,2,33|reason-some-people-are-likable, p.7]]
> > “Don’t wait to be welcomed. Be the welcomer.”
>
> Interesting conclusion people come to, something we are taught 1400+ years ago.
> [!PDF|] [[reason-some-people-are-likable.pdf#page=10&selection=6,0,8,31|reason-some-people-are-likable, p.10]]
> > Someone has to lower the wall first. Magnetic people are simply the ones who decide that person is them.

10
Articles/Notes/Redefining the Software Engineering Profession for AI.md Executable file
View File

@@ -0,0 +1,10 @@
---
pdf:
- "[[Opinion.pdf]]"
date started: 2026-06-03
date finished:
type:
- pdf-notes
done:
---
# Redefining the Software Engineering Profession for AI: Notes

22
Articles/Notes/Software Quality.md Executable file
View File

@@ -0,0 +1,22 @@
---
pdf:
- "[[software-quality.pdf]]"
date started: 2026-06-03
date finished: 2026-06-03
type: pdf-notes
done: true
note type:
- dev-articles
---
# Software Quality: Notes
> [!PDF|254, 254, 0] [[software-quality.pdf#page=1&annotation=122R|software-quality, p.1]]
> > We've normalized software catastrophes to the point where a Calculator leaking 32GB of RAM barely makes the news.
>
![[2026-05-22-software-quality.png]]
> [!PDF|] [[software-quality.pdf#page=10&selection=34,0,40,50|software-quality, p.10]]
> > Teach fundamental engineering principles again. Array bounds checking. Memory management. Algorithm complexity. These aren't outdated concepts—they're engineering fundamentals
>