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

adding properties
All checks were successful
Build Quartz Notes / build (push) Successful in 51s
Details

Browse Source
This commit is contained in:
Zaine
2026-06-03 12:48:18 +01:00
parent 9be5006617
commit 0a52228e2e
55 changed files with 400 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
Articles/20 Software Engineering Laws.md
View File

@@ -1 +1,10 @@
---
pdf:
- "[[20-laws-software-engineering.pdf]]"
date started: 2026-06-03
date finished:
type: pdf-notes
done:
---
# Link: <https://substack.com/inbox/post/194605697>
# 20 Software Engineering Laws: Notes

5
Articles/Articles MOC.md
View File

@@ -0,0 +1,5 @@
## Software Articles:
- [[I thought I knew system design]]
- [[Every Senior Engineer has read these books]]
- [[Software Quality]]

20
Articles/I thought I knew system design.md
View File

@@ -1,3 +1,10 @@
---
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
---
# AI summary:
- System design is not about memorising architecture patterns; it is about knowing why each component is needed.
@@ -8,18 +15,15 @@
# Article Notes
## sharding or replication.
> ([[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.
## Notes for page 3
[[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.
## Notes for page 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.
> ([[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.