the answer is you can know it, but but you know it when you let go of all concepts and you don't try. If you're trying to get there, then you don't see what you already are.
for - A Answer - you know it when you let go of all concepts and you don't try. If you're trying to get there, then you don't see what you already are. - Donald Hoffman
we try to understand the large scale um utility of of the of these patterns.
for - quote - we try to understand the large scale utility of these patterns - Michael Levin - implicit and embodied demonstration - of higher scale intelligence - communicating with - lower scale of intelligence
quote - we try to understand the large scale utility of these patterns - Michael Levin - This is an implicit demonstration or embodied demonstration of interscale communication - The higher level agent (Michael Levin's consciousness) - is attempting to understand the functioning of his own lower scale intelligence
Be explicit in the demo's intend. Eg. if you're building a demo for argTypes, don't create a Button.svelte component and Button.stories.svelte stories and come up with examples for how to write argTypes for buttons. Instead, build an ArgTypes.svelte component and stories that clearly and only demonstrates argTypes.
we're using post in the way postmodernists use post, which is it's informed by modernism, it's informed by capitalism without being able to transcend it necessarily because capitalism and it's the most recent incarnation of capitalism, which is neoliberalism, is like the oxygen that we breathe. It's all encompassing. It's totalitarian in its nature. And it's pervasive. And so in that sense, we say we have to be informed by the logic of the dominant system.
for - key point - Post Capitalist - informed by the logic of the dominant system - but not necessarily try to transcend it because it is so ubiquitous - Post Capitalist Philanthropy - Alnoor Ladha - Lynn Murphy - 2023
key point - Post Capitalist - informed by the logic of the dominant system - but not necessarily try to transcend it because it is so ubiquitous - Post Capitalist Philanthropy - Alnoor Ladha - Lynn Murphy - 2023 - It is so ubiquitous, like the air we breath - all encompassing - totalitarian - pervasive
the first one is the paradox of pronouncement. And here we recognize that language is both incredibly useful for us and is evocative and helps us create and and see and be in this reciprocal exchange. And we also are trying to open to a non dual embodied cognition that is beyond the written word and beyond the hegemony of the written word, and indeed the hegemony of the English written word
for - paradoxes - first one - pronouncement - the written word - evocative - but also hegemonic - especially the English language - there are other oral traditions - try to open nondual embodied cognition using English - Post Capitalist Philanthropy Webinar 1 - Alnoor Ladna - Lynn Murphy - 2023
per Espen Stokes is the author of what we think about when we try not to think about global warming
for - book - What we think about when we try not to think about global warming - author - Per Espen Stokes - climate crisis - psychology of - Per Espen Stokes
1:15 Kyle forced his progress from 25-30 years. Trying too hard, chasing too hard, is counter-productive ("cosmic paradox")
See ZK on trying too hard is counterproductive
" I spend most of my time in jails, in prisons, on death row."
“Who cares? Let’s just go with the style-guide” — to which my response is that caring about the details is in the heart of much of our doings. Yes, this is not a major issue; def self.method is not even a code smell. Actually, that whole debate is on the verge of being incidental. Yet the learning process and the gained knowledge involved in understanding each choice is alone worth the discussion. Furthermore, I believe that the class << self notation echoes a better, more stable understanding of Ruby and Object Orientation in Ruby. Lastly, remember that style-guides may change or be altered (carefully, though!).
Micromachines always focused on local multiplayer, and the fun their eccentric races of small toy vehicles competing on tracks made with everyday objects; and all that is present.
There's probably a thousand different directions you can go, but there just needs to be some kind of deeper hook to make this a full-fledged game.
As you can see, we end up with a lot of boilerplate if-statements. The code is more verbose. And it’s difficult to follow the main logic.
Some devs prefer Svelte’s minimal approach that defers problems to userland, encouraging more innovation, choice, and fragmentation, and other devs prefer a more fully integrated toolkit with a well-supported happy path.
tag?: what scope of provided features / recommended happy path is needed?
It’s worth mentioning that Svelte limits its scope to being only a UI component framework. Like React, it provides the view layer, but it has more batteries included with its component-scoped CSS and extensible stores for state management. Others like Angular and Vue provide a more all-in-one solution with official routers, opinionated state management, CLIs, and more. Sapper is Svelte’s official app framework that adds routing, server-side rendering, code splitting, and some other essential app features, but it has no opinions about state management and beyond. Some devs prefer Svelte’s minimal approach that defers problems to userland, encouraging more innovation, choice, and fragmentation, and other devs prefer a more fully integrated toolkit with a well-supported happy path.
tag?: what scope of provided features / recommended happy path is needed?
It’s worth mentioning that Svelte limits its scope to being only a UI component framework. Like React, it provides the view layer, but it has more batteries included with its component-scoped CSS and extensible stores for state management.
I'd be happy to take on this issue, if no one else has up to this point!
you took 4 hours to respond, so I implemented it myself
/node_modules/
This might be better than explicitly listing all external modules...?
I would be willing to take a stab at it if you think it would be a task within reach.
Now I know what you're thinking, "this is an atrocity, what a horrible mess!" and you're right, it's kind of ugly. In fact it's just about impossible to think this is a good idea the first time you see it — you have to actually try it.
We also use a home-made RspecFlaky::Listener listener which records flaky examples in a JSON report file on master (retrieve-tests-metadata and update-tests-metadata jobs).
Alternatively, you can use the Explore function to ask Google Sheets any number of questions about your to do list. It'll give you suggestions like "Most frequent Task" or "What percentage of Tag is [tag name]" and so on. This can give you insight into what you're working on the most and how you're spending your time, which can help you plan your workdays more productively.
i should try this.