+1 -1

Data/Dashboards.md

reviewed

··· 2 2 3 3 [Dashboards create a shared sense of reality](https://benn.substack.com/p/data-is-for-dashboards) and help everyone understand whats going on better. They exist for the purpose of quickly and concisely answering questions. [Understanding must come before action](https://sarahsnewsletter.substack.com/p/what-substack-analytics-engineers). Understanding also helps us ask the right questions. 4 4 5 5 - ## Best Practices 5 5 + ## Sensible Defaults 6 6 7 7 - [Before you dive into how to build a dashboard, the first thing you should ask yourself is whether this is the right tool for your situation.](https://shopify.engineering/make-dashboards-using-product-thinking-approach) Understand your problem and your audience; design a dashboard that does one thing really well, for a clear set of users. 8 8 - Answer three specific questions: [How, What, How](https://youtu.be/g2-dkJkZjiI)?

+4 -5

Decentralized Protocols.md

reviewed

··· 1 1 # Decentralized Protocols 2 2 3 3 - > Decentralization is the worst form of networking except all those other forms that have been tried. 4 4 - 5 3 - Decentralized protocols become [fat protocols](https://www.usv.com/writing/2016/08/fat-protocols/). 6 4 - On the internet, the main protocols take care of communications (HTTPS, SSH, ...) and apps are built on top. These apps and services store our data in silos. These protocols are necessary but not valuable. Value is captured by the apps. 7 5 - A great example of a modern open source protocol is [[IPFS]]. 8 8 - - Fat protocols will use tools like blockchain to store the data. With open protocols and decentralized data ([[Decentralized Web]]), apps are only the frontend of the services. 6 6 + - Fat protocols contain the data. With open protocols and decentralized data ([[Decentralized Web]]), apps are only the frontend of the services. 9 7 - [Protocol and Open Source Funding](https://youtu.be/few99D5WnRg?list=WL). It'll add to the current ways to to fund open source projects: 10 8 - Consulting: open source the code, sell consulting. 11 9 - Cloud: open source some code, but sell a closed source cloud complement. 12 10 - [Community](https://mobile.twitter.com/balajis/status/1310101055816921090): open source all code, and issue a token or charge for access to the community. 13 11 - Open Source projects would have a protocol. You could buy shares of Kubernetes, Tensorflow, ... or contribute to gain tokens. This [[incentives]] contributing and helping people. 14 12 - [Many more](https://youtu.be/Axj8NJXnCN0)! 15 15 - - Tokens create new, scoped economies, and those economies enable new ways of organizing production and operation of goods and services. Because these economies are programmable, they can also embed and optimize for value systems and goals. 13 13 + - Tokens create new, scoped economies, and those economies enable new ways of organizing production and operation of goods and services. Because these economies are programmable, they can also embed and optimize for value systems and goals. 16 14 - [Moving to protocols, not platforms](https://knightcolumbia.org/content/protocols-not-platforms-a-technological-approach-to-free-speech), is an approach for free speech in the twenty-first century. Rather than relying on a "marketplace of [[ideas]]" within an individual platform — which can be hijacked by those with malicious intent—protocols could lead to a marketplace of ideals, where competition occurs to provide better services that minimize the impact of those with malicious intent, without cutting off their ability to speak entirely. 17 15 - The fundamental power of the internet is its _interoperability_. It was born out of the ability of different networks to talk to each other using common protocols. The interoperability is what we've lost in the Web 2.0 era. Even such quintessential thing as a web API has no well defined standard or protocol, just a very vague concept of REST or RPC. We need commonly accepted standards and _decentralized_ protocols: for web APIs, for identity management, for message queuing, for web callbacks (webhooks), for online transactions, for semantic web and ontology, etc. 18 18 - - One wallet could allow you to login to any service. The wallets are your credentials. [[NFTs|Owning a thing]] could allow you to enter somewhere. 16 16 + - One wallet / DID / private key could allow you to login to any service. That's your credentials. [[NFTs|Owning a thing]] could allow you to enter somewhere. 17 17 + - There should be no technical or social single-point-of-failure for the overall protocol and network. There should be no single organization or individual who can entirely exclude others from the ecosystem (though the ecosystem may collectively exclude bad actors). There should be multiple independent interoperating service providers for each infrastructure component. 19 18 - [Open source protocols should favor composability over just about everything](https://youtu.be/TdBTJY-G8xs). Breaking big things into smaller things. This encourages experimentation at multiple levels. 20 19 - Forking should be a right. Keeps authority contingent (if they abuse power, they might get forked). 21 20 - **[Progressive decentralization](https://a16zcrypto.com/content/article/progressive-decentralization-crypto-product-management/) optional centralization.**

+1 -1

IPFS.md

reviewed

··· 1 1 # IPFS 2 2 3 3 - - It's a file system with [content based addressing](https://www.youtube.com/watch?v=5Uj6uR3fp-U). 3 3 + - It's a file system with [content based addressing](https://www.youtube.com/watch?v=5Uj6uR3fp-U). Instead of domains, you use the content as the domain. Because content can be very very long, we run a small program on it to produce a unique identifier based on that content (a hash). These identifiers are long enough that the possibility of two pieces of content creating the same one is virtually impossible. 4 4 - Files are automatically deduplicated. 5 5 - [It chunks, hashes and organizes blobs in a smart way](https://docs.google.com/presentation/d/1Gx8vSqrWZ7X-3SCgITXqQdinZQeXIAA7ITqL25SsPN8/edit#slide=id.g741b4d76cd_0_13). 6 6 - Once something is added, it can't be changed anymore.

+1 -1

Large Language Models.md

reviewed

··· 41 41 - If your content policy is an issue, provide the closest acceptable response and explain the content policy issue. 42 42 - Cite sources whenever possible, and include URLs if possible. 43 43 - List URLs at the end of your response, not inline. 44 44 - - Follow [Prompt Engineering Guide](https://www.promptingguide.ai/), [Brex's Prompt Engineering Guide](https://github.com/brexhq/prompt-engineering), and [OpenAI Best Practices](https://help.openai.com/en/articles/6654000-best-practices-for-prompt-engineering-with-openai-api). Also [some more on GitHub](https://github.com/PickleBoxer/dev-chatgpt-prompts). 44 44 + - Follow [Prompt Engineering Guide](https://www.promptingguide.ai/), [Brex's Prompt Engineering Guide](https://github.com/brexhq/prompt-engineering), and [OpenAI Best Practices](https://help.openai.com/en/articles/6654000-best-practices-for-prompt-engineering-with-openai-api). Also [some more on GitHub](https://github.com/PickleBoxer/dev-chatgpt-prompts). 45 45 - [Leaked System Prompts](https://matt-rickard.com/a-list-of-leaked-system-prompts). 46 46 - Some short (1-3 word) prompt fragments that work well: 47 47 - Be concise

+1

Programming.md

reviewed

··· 64 64 - Make the trade-offs explicit when making judgments and decisions. With almost every decision you make, you're either deliberately or accidentally trading off one thing for another thing. 65 65 - Discuss [trade-offs](https://twitter.com/kelseyhightower/status/774076482637312001), which you prefer, and reach a resolution. 66 66 - [Every system eventually sucks](https://www.simplethread.com/20-things-ive-learned-in-my-20-years-as-a-software-engineer/). Assume everything has bugs. 67 67 + - Have [sensible defaults](https://koaning.io/posts/sensible-defaults/). 67 68 - **Keep the [[Feedback Loops|iteration loop]] short**. 68 69 - Invest in tools to [[Automation|automate]] and improve the development cycle (CI, CD). Decreasing build times a few seconds actually saves a lot of time over time. Deploy often to make the loop end to end. If you need to do something manually more than twice, then write a tool for the third time. 69 70 - **Avoid implicit rules**.

+1

Social Media Issues.md

reviewed

··· 10 10 2. Your digital reputation may affect your opportunities. 11 11 3. People start changing their behavior to get better scores. 12 12 4. As your weaknesses are mapped, you become increasingly transparent. 13 13 + - We must [view individual attention as a societal good](https://medium.com/@pwang/reframing-the-social-media-problem-as-an-attention-crisis-52253dbfe627); and we should see society-wide "joint attention" as, in fact, a Commons, like fresh air or clean water. But unlike air or water, synchronous attention is a manufactured scarcity. 13 14 - Most of our [[news]] feeds are insular networks made up of people who get their info from the same filter bubble we do. 14 15 - [Social media makes more sense when you view it as a place people go to perform rather than a place to communicate](https://collabfund.com/blog/thoughts/). 15 16 - Social media provides an unfortunate filter: it dumbs down complex information. [Ideas don't pass perfectly from one person to another. Like a game of Telephone, the message gets mutated with each re-telling so, over time, ideas "evolve" to be more catchy, copy-able, contagious.](https://ncase.me/crowds/) The fittest ideas doesn't need to be true.

+1 -1

Teamwork.md

reviewed

··· 10 10 - What is shipping (e.g. what is on the near horizon). 11 11 - Why is it important / what is now possible as a result / why should people care? 12 12 - How are things progressing. Any blockers? 13 13 - - To make everyone more productive and happy: **Make feedback loops fast**. [Some best practices](https://simonwillison.net/2022/Oct/1/software-engineering-practices/): 13 13 + - To make everyone more productive and happy: **Make feedback loops fast**. [Some best practices](https://simonwillison.net/2022/Oct/1/software-engineering-practices/) / [sensible defaults](https://koaning.io/posts/sensible-defaults/): 14 14 - Tested, automated process for new development environments. 15 15 - Automated preview environments. 16 16 - Automated code formatting.