📚 Quinn's Highlights

Join 📚 Quinn's Highlights

A batch of the best highlights from what Quinn's read, .

Inversion: Avoiding stupidity is easier than trying to be brilliant. Instead of asking, “How can I help my company?” you should ask, “What’s hurting my company the most and how can I avoid it?” Identify obvious failure points, and steer clear of them.

50 Ideas That Changed My Life - David Perell

perell.com

The need for transparent and democratic decision-making: Human bullshit and algorithmic bullshit are two sides of the same coin Summary: Data and algorithms are not inherently bad, but they should be used in a transparent and democratic way that empowers everyone. Instead of arguing about whether computer or human decision-making is better, we should focus on accountable and transparent decision-making. This means avoiding human biases and stereotypes as well as naive machine learning without considering its real-world implications. Transcript: Speaker 1 So the point is that it's not that data and algorithms are bad it's that they need to be applied in a way which is transparent and which is democratic and which empowers all of us to carry On these debates rather than simply being tools which accurately or inaccurately are being used to buy the powerful to control the rest of us it's silly to argue about which is better You know computer decision making or human decision making that's really not the point I mean the point is we should have accountable transparent decision making instead of bs there's Human bs which comes in the form of stereotypes in ideology and there's algorithmic bs which comes in the form of naive machine learning without thinking enough about its applications

Glen Weyl & Cris Moore on Plurality, Governance, and Decentralized Society

COMPLEXITY: Physics of Life

DEEP Framework: Documenting Decisions, Events, Explanations, and Proposals in Your Org Summary: The DEEP framework emphasizes the documentation of decisions, urging the recording of the rationale behind business and general decisions. It also stresses the importance of documenting events such as meetings and town halls, highlighting the need for summarization. Furthermore, the framework encourages documenting explanations, especially in the context of onboarding, as they often involve repeated material. Lastly, it emphasizes documenting proposals or ideas, allowing individuals to present their rationale to others and providing time for considered reactions. The acronym 'DEEP' serves as a reminder for teams to consider the documentation created within their workflow. Transcript: Speaker 1 So I came up with an acronym as well, and I call that acronym deep. I think you'll identify with some of these. So deep for decisions, if there's ever a decision, then you should record the rationale for it. And we've talked about it endlessly on our tech radar's decision record systems. But I extend that to business decisions as well and general decisions as well. So similar format. Then there's events. So you have a town hall, you have a meeting, all of those are events, right? And you better document them for the benefit of other people. And when I say document, I mean, summarize, sure, you can have a recording or snippets of recordings if they are useful for people, but the summary is the more important thing. Then there's explanations, and I found these very useful in the context of onboarding, because there's a lot of explainer material that gets repeated in onboarding. And those are definitely great candidates for documentation. And the last one is proposals. And I called that proposals, but really I'm trying to talk about things like ideas. So let's take an example. I want to use this new library on my project. I have a certain rationale for it. Let me write down the thought process. What value is it going to bring? Let me present it to everyone. Everyone has the time to consume it. Oftentimes we go into decision making with a lot of cognitive load, where, you know, Ken explains in rapid fire things that he's been thinking about for the last 15 days. And now I have to consume it in the next 30 minutes and give Ken a year or nay. It's really difficult because Ken's done all the deep thinking, I need the time to process it and writing gives me the time to process it, right? And I can also not give knee jerk reactions, but considered reactions. So proposals, and that starts to include design documentation, idea papers, any kinds of proposals that you make on the team. So that acronym deep is a good trigger for teams to kind of hold on to and think about what is the documentation we're creating in the flow of work.

Asynchronous Collaboration — Getting It Right

Thoughtworks Technology Podcast

...catch up on these, and many more highlights

Readwise.

Join 📚 Quinn's Highlights

A batch of the best highlights from what Quinn's read, .

LEARN

EXPLORE

CONTACT