this repo has no description
docs: ✏️ update content on curiosity, dashboards, mindfulness, and teamwork
Added insights on content consumption, enhanced dashboard metrics with YoY growth and goal comparison, emphasized cultivating an information diet, and aligned teamwork practices with best practices for prompt engineering.
+10
+1
Curiosity.md
+1
Curiosity.md
···
14
14
- [Practice hunting for bugs](https://radimentary.wordpress.com/2018/01/29/hammertime-day-1-bug-hunt/?utm_source=pocket_mylist)! A bug is anything in life that needs improvement. Even if something is going well, if you can imagine it going better, there's a bug.
15
15
- Knowing we really want is hard and takes effort. Explore yourself and your [[values]].
16
16
- Experiment more! It is very very easy to do what comes naturally and never deviate from that. Break the pattern.
17
+
- Consume content that is hard to produce. If the producer can spam the content, it is probably not worth your time. E.g: audiobooks vs podcasts.
+1
Data/Dashboards.md
+1
Data/Dashboards.md
···
37
37
- Make it obvious what the main takeaway is.
38
38
- Follow the Z pattern.
39
39
- Provide context.
40
+
- Include additional highlight numbers, such as last month's total revenue vs. the planned revenue and the YoY growth. Plot against goals if possible. Have a reasonable goal, and plot your numbers against it!
40
41
41
42
The value is that now discussions are happening about the data.
42
43
+1
Mindfulness.md
+1
Mindfulness.md
···
47
47
- E.g: [[Social Media Issues|social media]] encourages rage, [[blockchain]] protocols "waste" energy using Proof of Work.
48
48
- A person holding a hammer interacts with the world in a different way. It is a different entity. Same with ideas.
49
49
- Most of the world is held together with duct tape so don't be surprised when it breaks.
50
+
- Cultivate your information diet.
+7
Teamwork.md
+7
Teamwork.md
···
121
121
- Keep a [private work log](https://youtu.be/HiF83i1OLOM?list=PLYXaKIsOZBsu3h2SSKEovRn7rGy7wkUAV). It'll make easier for everyone to advocate what you did.
122
122
- [Don't sabotage the team](https://erikbern.com/2023/12/13/simple-sabotage-for-software)!
123
123
- [Nobody gets credit for fixing problems that never happened](https://news.ycombinator.com/item?id=39472693). People get credit for shipping things. Figure out how to reward and recognize people for preventing problems.
124
+
- The same practices that make great [[Large Language Models]] [promts](https://platform.openai.com/docs/guides/prompt-engineering) also make [great practices with humans](https://x.com/tayloramurphy/status/1849269205155123568):
125
+
- Give clear instructions.
126
+
- Share relevant background info.
127
+
- Break big problems into chunks.
128
+
- Give them time to think.
129
+
- Point them to helpful tools.
130
+
- Test their work systematically.
124
131
125
132
## [How Small Teams Work](https://posthog.com/handbook/people/team-structure/why-small-teams#how-it-works)
126
133