phone: shortcuts gcp command- pre commit

.obsidian/plugins/recent-files-obsidian/data.json

@@ -1,5 +1,33 @@
 {
   "recentFiles": [
+    {
+      "basename": "scientific-method",
+      "path": "posts/scientific-method.md"
+    },
+    {
+      "basename": "2024-08-06",
+      "path": "goals/2024-08-06.md"
+    },
+    {
+      "basename": "this-is-an-ab-test",
+      "path": "posts/this-is-an-ab-test.md"
+    },
+    {
+      "basename": "data-science-structure",
+      "path": "posts/data-science-structure.md"
+    },
+    {
+      "basename": "give-it-time-and-retry",
+      "path": "silvermineai/give-it-time-and-retry.md"
+    },
+    {
+      "basename": "forget-pythonic-write-code-that-works",
+      "path": "tech/forget-pythonic-write-code-that-works.md"
+    },
+    {
+      "basename": "2024-08-01",
+      "path": "goals/2024-08-01.md"
+    },
     {
       "basename": "10-steps-to-optimize-anything",
       "path": "posts/10-steps-to-optimize-anything.md"
@@ -171,34 +199,6 @@
     {
       "basename": "day-two-of-calls",
       "path": "silvermineai/day-two-of-calls.md"
-    },
-    {
-      "basename": "the-lord-of-the-rings-the-two-towers",
-      "path": "book-review/the-lord-of-the-rings-the-two-towers.md"
-    },
-    {
-      "basename": "designing-machine-learning-systems",
-      "path": "book-review/designing-machine-learning-systems.md"
-    },
-    {
-      "basename": "reading-list",
-      "path": "lists/reading-list.md"
-    },
-    {
-      "basename": "machine-learning-resources",
-      "path": "posts/machine-learning-resources.md"
-    },
-    {
-      "basename": "saints-volume-2-no-unhallowed-hand",
-      "path": "book-review/saints-volume-2-no-unhallowed-hand.md"
-    },
-    {
-      "basename": "a-10-week-self-guided-data-science-intro-course",
-      "path": "posts/a-10-week-self-guided-data-science-intro-course.md"
-    },
-    {
-      "basename": "ab-testing-resources",
-      "path": "tech/ab-testing-resources.md"
     }
   ],
   "omittedPaths": [],

.obsidian/workspace-mobile.json

@@ -13,7 +13,7 @@
             "state": {
               "type": "markdown",
               "state": {
-                "file": "posts/10-steps-to-optimize-anything.md",
+                "file": "posts/scientific-method.md",
                 "mode": "source",
                 "source": false
               }
@@ -52,12 +52,12 @@
         "state": {
           "type": "search",
           "state": {
-            "query": "Bayes",
+            "query": "tag:#ex/Lats/Pulldowns",
             "matchingCase": false,
             "explainSearch": false,
             "collapseAll": false,
             "extraContext": false,
-            "sortOrder": "alphabetical"
+            "sortOrder": "alphabeticalReverse"
           }
         }
       },
@@ -101,7 +101,7 @@
         "state": {
           "type": "backlink",
           "state": {
-            "file": "posts/10-steps-to-optimize-anything.md",
+            "file": "posts/scientific-method.md",
             "collapseAll": false,
             "extraContext": false,
             "sortOrder": "alphabetical",
@@ -118,7 +118,7 @@
         "state": {
           "type": "outgoing-link",
           "state": {
-            "file": "posts/10-steps-to-optimize-anything.md",
+            "file": "posts/scientific-method.md",
             "linksCollapsed": false,
             "unlinkedCollapsed": true
           }
@@ -130,7 +130,7 @@
         "state": {
           "type": "outline",
           "state": {
-            "file": "posts/10-steps-to-optimize-anything.md"
+            "file": "posts/scientific-method.md"
           }
         }
       }
@@ -150,8 +150,15 @@
   },
   "active": "b55872dd4edb37f4",
   "lastOpenFiles": [
-    "posts/hungry-judge.md",
+    "goals/2024-08-06.md",
+    "posts/scientific-method.md",
+    "posts/this-is-an-ab-test.md",
+    "posts/data-science-structure.md",
+    "silvermineai/give-it-time-and-retry.md",
+    "tech/forget-pythonic-write-code-that-works.md",
+    "goals/2024-08-01.md",
     "posts/10-steps-to-optimize-anything.md",
+    "posts/hungry-judge.md",
     "goals/2024-07-27.md",
     "book-review/the-one-thing.md",
     "goals/2024-07-15.md",
@@ -171,14 +178,7 @@
     "goals/2024-06-26.md",
     "goals/2024-06-27.md",
     "goals/2024-06-28.md",
-    "goals/2024-06-29.md",
-    "goals/2024-06-30.md",
-    "tech/galileo-ai-ui-generator.md",
-    "silvermineai/the-overwhelming-chaos.md",
-    "silvermineai/a-tale-of-two-price-mentalities.md",
     "img/2024-06-27-1106-what-do-you-have-to-lose",
-    "silvermineai/three-cold-calls.md",
-    "posts/productivity.md",
     "img/2024-06-16-1406-mark-uses-40-dollars",
     "Pasted image 20240616142008.png",
     "Pasted image 20240616141503.png",

goals/2024-08-01.md

@@ -0,0 +1,38 @@
+---
+date: 2024-08-01
+title: 2024-08-01
+description: x
+categories:
+  - goals
+workout-time: 0
+exercises:
+  - Abs - Crunches
+pelo-warmup: 0
+pelo-time: 0
+pelo-kj: 0
+pelo-avg: 0
+pelo-res: 0
+pelo-rpm: 0
+run-dist: 0
+run-time: 0
+hike-dist: 0
+hike-elev: 0
+hike-time: 0
+basketball-time: 0
+bike-dist: 0
+bike-time: 0
+bike-elev: 0
+draft: false
+---
+**Thursday, August 1st, 2024**
+[⏪ We 7/31](goals/2024-07-31) | Let God Prevail | [Fr 8/2 ⏩](goals/2024-08-02)
+
+
+#ex/DBfloorBenchPress 55.8, 70.5, 75.4
+
+#ex/Shoulders/ArmRaise4x 10.10
+#ex/DBRow2HipPocket 40.15
+
+#ex/Tricep/BarbellSkullCrushers 50.15
+#ex/Bicep/Barbell 50.10
+

goals/2024-08-06.md

@@ -0,0 +1,38 @@
+---
+date: 2024-08-06
+title: 2024-08-06
+description: x
+categories: goals
+workout-time: 0
+exercises:
+  - x
+pelo-warmup: 0
+pelo-time: 0
+pelo-kj: 0
+pelo-avg: 0
+pelo-res: 0
+pelo-rpm: 0
+run-dist: 0
+run-time: 0
+hike-dist: 0
+hike-elev: 0
+hike-time: 0
+basketball-time: 0
+bike-dist: 0
+bike-time: 0
+bike-elev: 0
+draft: false
+---
+**Tuesday, August 6th, 2024**
+[⏪ Mo 8/5](goals/2024-08-05) | Let God Prevail | [We 8/7 ⏩](goals/2024-08-07)
+
+
+#ex/DBfloorBenchPress 70.5, 70.5,70.5.70.5
+
+#ex/Pullups/Towel 10, 8
+#ex/Lats/TRXRow 10, 8
+
+#ex/LowerBack/BackExtension 25.10, 25.15
+#ex/Core/StandingRussianTwist 25.50, 25.30
+
+#ex/Lats/WidePullups 4

posts/data-science-structure.md

@@ -0,0 +1,26 @@
+---
+title: "Data science structure"
+date: "2024-08-04 13:00:01"  
+created: "2024-08-04 13:00:01"
+categories: posts  
+draft: false
+---
+Over my career I've thought a lot about "where should a data scientist sit in an org?" 👇 5 lessons from what I've learned after working in 6 very different companies.
+
+1. DS under an MBA: maybe okay, probably bound for failure. 
+2. DS under the PM: def bound for failure. 
+3. DS under the DS: good for the junior in the short term. 
+4. DS under Eng: good.
+5. DS under a people manager, but works closely integrated team with a DS-experiences tech lead: best. 
+
+Interdisciplinary teams do the best work. It maximizes labor efficiency to have engineers, PMs, and DS's working on the same problem but doing different things. 
+
+When you federate DS, they don't care as much about what they're working on. The incentives are off. 
+
+When a DS works for a PM the PM will make wild assumptions about what they should do. PMs oversimplify problems and DS find that unsatisfying. 
+
+DS reporting to DS means you throw stuff over the fence and the Eng do the real work. And the Eng don't capture all the nuance the DS would like to implement. 
+
+DS reporting to business types is unfulfilling because DS love technical stuff. 
+
+best scenario? Have a DS work in a pod with experienced tech leads. DS reports (HR purposes) to someone outside of the team who can give them guidance but is incapable of micromanaging them. 

posts/scientific-method.md

@@ -0,0 +1,18 @@
+---
+title: "Scientific method"
+date: "2024-08-06 14:11:23"  
+created: "2024-08-06 14:11:23"
+categories: posts  
+draft: false
+---
+I use these seven steps to the scientific method every single day:
+
+1. What’s the problem?
+2. Hypothesis: What’s the believed answer? 
+3. Metrics: how do I measure with data?
+4. Methods: how do I test the belief?
+5. Findings: what are the unemotional facts?
+6. Discussion: what are my opinions about the findings? (These are usually more hypotheses.)
+7. Next steps: self explanatory 🤣
+
+It helps me think more clearly when diving into data! Hope it helps.

posts/this-is-an-ab-test.md

@@ -0,0 +1,27 @@
+---
+title: "This is an A/B test"
+date: "2024-08-05 20:38:38"  
+created: "2024-08-05 20:38:38"
+categories: posts  
+draft: false
+---
+Dude. You're being experimented on. Aren't you a little bit curious how it works?
+
+Bruh, they're experimenting on you. Yes you. Now. Here's how it works. 
+
+
+Im A/B testing out some clickbait, let's see if it works 👇👇
+
+This post is not AI generated. I wrote it. But I'm testing an idea: what if I write and publish two posts at the exact same time but with different clickbait hooks? Same content (what I'm writing here.)
+
+Hypothesis: I'm guessing LinkedIn will naturally favor one post over the other. Hard to know which. 
+
+A/B testing is all about this every day. Newspapers play with their bylines. Search engines play with their titles. Ad copy is all one massive experiment to see what clicks the most. 
+
+So drop a like if you like A/B tests. And keep an eye out for my other identical post, launched at 10am on Tuesday PST. Let's see which gets the more impressions on LinkedIn!
+
+Here are the two intros:
+
+Dude. You're being experimented on. Aren't you a little bit curious how it works?
+
+Bruh, they're experimenting on you. Yes you. Now. Here's how it works.

silvermineai/give-it-time-and-retry.md

@@ -0,0 +1,24 @@
+---
+title: "Give it time and retry "
+date: "2024-08-01 23:07:46"  
+created: "2024-08-01 23:07:46"
+categories: silvermineai  
+draft: false
+---
+A week and a half ago I wanted to shut it all down. Fire all my guys. I was burned out. 
+
+I kept the lights on though. I narrowed in. I worked on my system. 
+
+I remembered I have a lot to learn. 
+
+I'm terrified of getting rejected. But im not a sales person. I don't have to sell anyone. I can treat the call as a free consultation. 
+
+Free is soft. It lets their guard down. 
+
+"Hey this is a free consultation. Just curious to learn what you've done so far, bounce some ideas off you, and see if we can create some value for you. If so, we'll send you some more material and we can do a follow up call with our founder. So why are you interested in marketing services at this time? What's working, what's not working for you?
+
+What have you tried in the past?
+
+Great, our founders busy serving customers so we want to make sure we use both of your time wisely. Let's fix a time for a 15-30 min zoom call to review anything and discuss next steps. 
+
+"Well, calling you at random hours isn't really conducive. You might be busy, or I might be busy. So if you're serious, let's commit to a time to chat and we'll set up a zoom link for 15 minutes."

tech/forget-pythonic-write-code-that-works.md

@@ -0,0 +1,28 @@
+---
+title: "Forget Pythonic. Write code that works"
+date: "2024-08-01 16:21:00"  
+created: "2024-08-01 16:21:00"
+categories: tech  
+draft: false
+---
+For the Python nerds: I've seen data scientists bashing notebooks for years. I was one of them. 
+
+Then I learned yesterday about nbdev and how Jeremy Howard and folks at Nixtla are building production grade software using…notebooks. 
+
+I was taken aback by Jeremy's YouTube "I don't write code like most Python programmers, but I have a reason for how I write it". 
+
+I was also shocked how easy it was to read Nixtla's documentation and source code. Shouldn't that be the goal?? 
+
+Unit tests at the bottom of the Python files where the functions are defined. Wait…that makes a ton of sense. 
+
+Wirh nbdev there's no major emphasis on pep8. No black formatting. No like wrap at 80 characters. 
+
+And I realized: we put so much emphasis on convention and doing what others are doing. 
+
+I'm not saying pep8 or black are wrong. I like them. But Python is just a language. Don't get sucked into "being pythonic". If the code works, and it creates value, it serves its purpose. 
+
+I come from R where there are so many "dialects". Compare base R vs the tidyverse. Worlds apart in how they build and test their code. 
+
+So…make your own dialect. Just don't waste time trying to keep up with all the formatters and linters out there. Because who cares? It's your code. 
+
+It's okay to have you or your team have your own style.