one of the problems of the 00:44:54 behaviorists back in the 1960s and so on was that to some extent they unrooted organisms from their environment and put them into boxes and tested how they 00:45:08 behaved under these extraordinary artificial circumstances

we've got to leave the bottom left-hand corner and that only gives you three other spaces to go to and I've already noted that one of those spaces may be a place that has a certain utility short-run 00:50:27 but don't try to build your culture there because you can't do it it's a place that you want to be in for a while but then you wanna leave so it really only gives you two places

Periods of normal science are interrupted when anomalies between observations and the expectations suggested by the paradigm begin to demonstrate the paradigm’s weakness.

Stop to think about "normal app" as like desktop app. Android isn't a desktop platform, there is no such this. A "normal" mobile app let the system control the lifecycle, not the dev. The system expect that, the users expect that. All you need to do is change your mindset and learn how to build on it. Don't try to clone a desktop app on mobile. Everything is completely different including UI/UX.

When you call 'foo' in Ruby, what you're actually doing is sending a message to its owner: "please call your method 'foo'". You just can't get a direct hold on functions in Ruby in the way you can in Python; they're slippery and elusive. You can only see them as though shadows on a cave wall; you can only reference them through strings/symbols that happen to be their name. Try and think of every method call 'object.foo(args)' you do in Ruby as the equivalent of this in Python: 'object.getattribute('foo')(args)'.

what Marvin Harris said was the most important thing projecting the viability of a historical cultures is infrastructure, which is your expertise. But before we get into the infrastructure part, how do you envision society at the higher levels of belief, motivation, institutions? 00:25:09 Have you thought about that? Simon Michaux: Yes. So I believe society will shift into four parallel groups based on paradigm

he limited hisdiscussion of Kuhn to a short article crediting Georg Christoph Lichtenbergwith a much more sophisticated concept of “paradigm.” 9

Okay thank you. I'll need to do some thinking then on how to apply that to things like git config --global core.editor

However, this request-by-request mindset doesn’t map well to GraphQL because there’s only one controller and the requests that come to it may be very different.

Svelte is different in that by default most of your code is only going to run once; a console.log('foo') line in a component will only run when that component is first rendered.

This article explains why you shouldn't use getters and setters (and when you can use them) and suggests a design methodology that will help you break out of the getter/setter mentality.

Svelte doesn't re-render, so you need to respond to component mount/dismount and prop changes separately as they are distinct concepts and never tied together, unlike in React.

Sometimes, you may be tempted to write that wrapper. Because all your (React or Vue or insert your reactive framework here) instincts tell you so.Resist the temptation. There is a better way. A svelter way. Introducing: the use-directive (a.k.a. “actions”).

However, especially when starting out, it’s very easy to fall into the “this is how I did things in my previous framework” trap.

multi-paradigm

such as scope, simplicity, fruitfulness, accuracy

Like in evolution, the process does not change toward some fixed goal according to some fixed rules, methods or standards, but rather it changes away from the pressures exerted by anomalies on the reigning theory (Kuhn 1962, 170–173). The process of scientific change is eliminative and permissive rather than instructive.