Quartz sync: Feb 9, 2024, 11:12 PM

content/architecture/Cache concepts.md

@@ -4,6 +4,11 @@ tags:
   - cache
   - architecture
 ---
+## Caching
+
+Caching is the process of storing copies of files in a temporary storage location, known as a cache. The temporary storage location is faster to access than the underlying slower storage layer. The primary goal of caching is to increase data retrieval performance by reducing the need to access the underlying slower storage layer.
+
+When an order comes through and the food item already exists in the oven, this is called a **cache hit**. When it doesn’t exist, this is a **cache miss**. The success of a cache is quantified by the cache hit ratio, calculated as the number of cache hits divided by the total number of cache requests.
 ## Sharding
 
 Distributing the keys of the cache in multiple cache instances. There's usually a function that determines which key goes in which instance. (Hashing.)
@@ -88,3 +93,4 @@ Random Replacement (RR) selects a random item for eviction when the cache is ful
 
 - [EP93: Is Passkey Shaping a Passwordless Future?](https://blog.bytebytego.com/p/ep93-is-passkey-shaping-a-passwordless), ByteByteGo Blog
 - [Caching Policies and Algorithms Explained Simply - SWE Quiz](https://www.swequiz.com/learn/caching-strategies-and-algorithms)
+- [A Crash Course on Caching Fundamentals - SWE Quiz](https://www.swequiz.com/learn/caching-fundamentals)

content/management/Technical Debt.md

@@ -0,0 +1,14 @@
+---
+title: Technical Debt
+tags:
+  - architecture
+  - programming
+  - management
+---
+Technical debt has less to do with the code itself and more about the choices and compromises that emerge from the challenges within software development.[^notreal]
+
+In the realm of software development, the inception of a project is often marked by a paradoxical certainty: we know the least about the project at its beginning. This is an inherent trait, not a flaw, of the developmental process.[^notreal]
+
+The concept of refactoring sprints, while seemingly a solution, is often misguided. The root problem often lies not in the code itself, but in the processes that built that code. In cases of what might be termed “corporate technical debt,” a continuous, proactive approach to managing technical debt is more effective than sporadic refactoring sprints.[^notreal]
+
+[^notreal]: [Technical Debt is not real – Foxhound Systems](https://www.foxhound.systems/blog/technical-debt-is-not-real/?utm_source=tldrnewsletter)