davidgasquez.com
+1
Data/Data Engineering.md
+1
Data/Data Engineering.md
···
10
10
- A [consistent pattern](https://www.startdataengineering.com/post/design-patterns/) across your data pipelines helps devs communicate easily and understand code better.
11
11
- Data Engineering can learn from decentralized systems ideas like, Content Addressed Data, Immutability, and [[Idempotence]].
12
12
- [Schemas aren't eliminated by using a "schemaless" data store](https://ludic.mataroa.blog/blog/flexible-schemas-are-the-mindkiller/) (like a NoSQL database). They're just pushed to the reading layer.
13
+
- [Bring compute to data instead of data to compute](https://youtu.be/S0mviKhVmBI)!
13
14
14
15
## Data Pipelines
15
16
+3
-1
Health.md
+3
-1
Health.md
···
10
10
11
11
## Blood Markers
12
12
13
+
These are some of the blood markers that could be useful to measure and monitor.
14
+
13
15
- Cortisol: Stress marker.
14
16
- HbA1c: Glucose/diabetes marker.
15
17
- hsCRP: Inflammation marker.
16
-
- LDL: Bad cholesterol .
18
+
- LDL: Bad cholesterol.
17
19
- HDL: Good cholesterol.
18
20
- AST: Liver function.
19
21
- Ferritin: Indicates inflammation, obesity, excess iron.
+1
-1
Programming.md
+1
-1
Programming.md
···
7
7
- The more you can decompose, the more innovation you'll drive.
8
8
- The best code is no code, or code you don't have to maintain.
9
9
- **Design for simplicity**.
10
-
- Do the [simplest thing](https://landing.google.com/sre/book/chapters/simplicity.html) that could possibly work.
10
+
- Do the [simplest thing](https://landing.google.com/sre/book/chapters/simplicity.html) that could possibly work (e.g: UNIX tools remain incredibly powerful and efficient for "Big Data").
11
11
- Benefits of simplicity: ease of understanding, ease of change (improvement), ease of debugging, flexibility. [The goal of software design is to create chunks or slices that fit into a human mind](https://mobile.twitter.com/KentBeck/status/1354418068869398538). The software keeps growing but the human mind maxes out, so we have to keep chunking and slicing differently if we want to keep making changes.
12
12
- Break down complex problems into simpler, digestible pieces. If you do it right, it will feel like cheating: you just solve simple problems until you're done.
13
13
- We can't change our brain to grasp something complex. We need to simplify complexity so we can handle it.