Join 📚 Quinn's Highlights

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

Layers of Information Continually Accumulate *Within* Objects Over Time Summary: Information can be shared between objects as evidence of a common history, indicating that objects are deeply rooted in time. As the biosphere has evolved, it has increased the layers of information processing and abstraction, resulting in the generation of objects that are deeper in time. Consequently, some features of these objects appear less physical and more abstract. Each individual accumulates information over time, making parts of them brand new and parts billions of years old. Transcript: Speaker 1 And so information we talked about has a sort of interesting property that seems very abstract. And it seems to be that information can move between objects, like we're speaking the same language, but when you can share information between objects like you and I speaking, what That is is evidence of a common history. These things that we call information and abstractions, I think, are just evidence that these objects are actually deep in time. So things look more abstract, the deeper and timely are. And it's one of the reasons I think that as the biosphere has evolved over time, it's increased the layers of information processing and abstraction that it's built. But really what it is is you're generating these objects that are deeper and deeper in time. And so some of their features look less and less physical because they're not physical now, they're physical in the structure that's extended in time. Speaker 2 You have a lovely line in one of your papers where you say that each of us are our own age, but in many ways, we're thousands and thousands of years old because we have accumulated all that Information instead of genes to be who we are today. Speaker 1 That's right. So parts of you are brand new. And parts of us are all brand new from this conversation because we've exchanged information and generated new structures. Parts of us are billions of years old.

Big Ideas — Time

Simplifying Complexity

"What Information Consumes Is Attention" and The Thermodynamics of Communication Summary: Herbert Simon's quote about information consuming attention is a crucial point to consider. Emails can be overwhelming, as there is a limit to the amount of time and attention we have. It is important not to solely rely on the internet as a copying machine, but to acknowledge the real material scarcities and limitations. While there is room for improvement, there are still real world limits to communication effectiveness. Transcript: Speaker 3 Herbert Simon's famous 1971 quote that what information consumes is attention feels like such a crucial point that I made it my email signature you know because like you said earlier Glenn that you know the value is really in in the relationships and there are differentially scalable qualities here I think a lot about the way and Doug Rushkoff and others have pointed Out that you can have at least you know indefinitely many emails a day but you only have so much time and attention to read them and that this is part of the argument for the importance of Not just following the sort of logic of the internet as a great copying machine off a cliff right where we're imagining an abundance that is nonetheless still founded in real material Scarcities you know like David Wolpert talks about you know the thermodynamics of communication and there being a theoretical limit to how effective that can be and while we still Have plenty of room you know orders of magnitude to improve on that you know that there are these real world limits that we're eventually going to bump up into

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