03.06

Articles/20 Software Engineering Laws.md

@@ -0,0 +1 @@
+# Link: <https://substack.com/inbox/post/194605697>

Articles/Every Senior Engineer has read these books.md

@@ -0,0 +1,83 @@
+---
+pdf: "[[Every Senior Engineer I Respect Has Read These Books (Have You_) _ by The Latency Gambler _ Mar, 2026 _ Medium.pdf]]"
+type: pdf-notes
+---
+# 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
+

Articles/I thought I knew system design.md

@@ -0,0 +1,25 @@
+# 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
+
+## 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
+
+> 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.

Articles/Software Quality.md

@@ -0,0 +1,17 @@
+---
+pdf:
+  - "[[software-quality.pdf]]"
+date started: 2026-06-03
+date finished: 2026-06-03
+type: pdf-notes
+---
+
+# Software Quality: Notes
+
+> (\[\[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]]
+
+> (\[\[software-quality.pdf#page=10&annotation=123R|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.

Articles/Substack Articles.md

@@ -0,0 +1,3 @@
+  - [The 20 Software Engineering Laws](id:973f2e9c-f161-45ad-8f19-2e4d563f56ac)
+
+  - [Microsoft banned AI because it cost too much.](https://medium.com/data-science-collective/microsoft-banned-ai-because-it-cost-too-much-135bcbf15a18)