Great critique. Enactivating change management through "corrective standards and regulation" distorts surprising moments from opportunities for distributed learnign into a compliance checklist for heirarchy

active link now:

https://dune.readthedocs.io/en/stable/reference/dune/index.html

这里应该是“毛利”

这里应该是“毛利为3057美元”

这里应该是“毛利”

这里应该是“毛利”

这里应该是“毛利”

这里应该是“毛利为1980美元”

这里应该是“毛利为4140美元”

这里应该是“毛利为4080美元”

DataCite is not a data repository.

Como

varias fases

Agregar el pie de imágen, indicando que se tomó de Luna 2019, basado en Leinonen 2008.

calidad

JSON

Uhh, I'd imagine "remove" would refer to "bold" annotation.

Otherwise, there can be another "bold" with t < 20, that would be accidentally removed.

Syntactic intent is not preserved.

La “ubiquidad del error” no invalida el método científico, sino que lo enriquece al fomentar una mayor conciencia de las limitaciones y la necesidad de una aproximación cautelosa y crítica en la investigación científica. Este enfoque reconoce que la perfección absoluta es inalcanzable y que la incertidumbre inherente a las mediciones y observaciones es una parte integral del proceso científico. En lugar de negar o minimizar los errores, se busca adaptarse a ellos y comprender cómo afectan los resultados.

En este contexto, los investigadores deben aplicar estrategias para cuantificar y controlar los errores, como el uso de cifras significativas, la estimación de incertidumbres y la validación cruzada. Además, la reproductibilidad y la transparencia son esenciales para garantizar que otros científicos puedan verificar y validar los hallazgos.

AttributeError: 'Brain_Data' object has no attribute 'fit_transform'

This line of code yielded error "Error in if (ci) { : the condition has length > 1"

Die Überschrift widerspricht den Studienergebnissen.

Wortwörtlich würde sie heißen, dass mehr also die Hälfte der Leute, keine der Parteien in der Regierung haben will. Es würden aber noch immer 70% eine dieser Parteien wählen.

Damit die Überschrift trotzdem stimmt, müssten also zumindest 20% der Leute eine Partei wählen, die sie nicht in der Regierung haben wollen.

for - definition - fundamental attribution error

definition - fundamental attribution error - a psychological condition in which an individual attrbutes a human behavior to an internal characteristic instead of environmental circumstances

Dans le lien github, fichier index.html, il existe une ligne en doublon qui est "" Elle est écrite deux fois, ce qui ne sert a rien sauf si je me trompe. (Ligne 10 et ligne 18)

should be 1 instead of 1/2

it should = te^t not te^-t

確認： 下載 zai4, not zai3 載歌載舞 zai4 記載，刊載 zai4

唯有表達「年」、「時間」時才是 cai3

• for: carbon inequality, question - new COP - focused on elites?

• comment

  • while COP28 fights over which nations bear what responsibility, from this perspective, there is an entirely different class of people that must be held responsible, not at the nation state level, but at the individual level. Why isn't there a COP where the elites are held responsible?

• question

  • Are we making a grave category error in holding the wrong class of people responsible? Should questions of carbon equity concern both high polluting nations AND individuals?
  • At the very least, should we formally recognize a parallel set of responsibilities and elevate that recognition to the level of COP conventions to deal with the problem?

Page formatting is broken in several places and makes the formulas unreadable.

• for: scientific naturalism - circular argument, logical error, subjectivity - explanation, quote, quote - studying consciousness

• quote: consciousness

  • Human subjectivity is the foundation oof all scientific knowledge. Therefore, there is a logical error in trying to explain the foundation through what it has founded.

• author: Doris Elida Fuster Guillen

• comment

  • Alternative way to state it
    • Human subjectivity is the foundation oof all scientific knowledge. Therefore, there is a logical error in trying to explain the foundation through what itself.

These units should be mol/L according to the dimensional analysis

Huh? There's nothing inherent to Web Components that makes this true. That's just how the author is using them.

met

Author is conflating multiple things.

Of course it is. Why wouldn't it be?

if dune command is not found just type $eval $(opam env) in terminal every startup or just add in .zshrc or .bashrc that script. the first dollar sign "$" is terminal level, it isn't shell script. (check documentation)

It's Fig.3.7.15

This is not true. Pressure in the tank does not tell you how much gas is left, and pressure gauges for this purpose cannot be bought (for propane). Pressure in the tank is dependent on temperature, but will be constant at a given temperature, as long as there is any liquid propane in the tank. To determine how much propane is left, you need to weigh the tank. This needs an example for which the gas does not liquefy under the relevant pressures--maybe a compressor for air tools?

• translation error
  • should be
    • Sam Bankman-Fried

• translation error
  • should be
    • ape-brained meat sack

• translation error

  • should be
    • ape-brained meat sack, taken from Elise's book

• comment

  • comparable to Ernest Becker's description of the human condition
  • in his book The Denial of Death
    • quote:
      • "Man is literally split in two: he has an awareness of his own splendid uniqueness in that he sticks out of nature with a towering majesty, and yet he goes back into the ground a few feet in order to blindly and dumbly rot and disappear forever."

• comment

  • the comparison is apt as one of the goals of transhumanism is to use technology to conquer death
  • From this perspective, we might argue that transhumanist aspirations have been with humanity for as long as medicine has intervened to extend life and human wellbeing

• translation error
  • should be
    • aped-brained meat sack

• translation error
  • should be
    • ape-brained meat sack

• comment
  • Is this not a category error in classifying inert technology as life?
  • When does an abiotic human cultural artefact become a living form?

This way of thinking should be treated with care (caution, even), lest it end up undergirding a belief in a false dichotomy.

That can be a sort of "attractive people are shallow and dumb and unattractive people are intelligent and deep"-style mindtrap.

Relative to the experience that Golang developers are used to, yes, it's a pain.

But that isn't to say it's any more or less painful on an absolute scale, esp. wrt what comprises typical experiences in other ecosystems.

This factoring is incorrect, it should be: $$y' = xy+3x-2y-6 = (x-2)(y+3)$$

QuickBooks Error 3371 is a common error that users face while using QuickBooks. This error usually occurs when the user is trying to open QuickBooks or restore a backup. This error can be caused by many factors such as damaged or missing files, corrupt data, or even malware. The good news is that this error can be fixed easily by following some simple steps. In this article, we will show you how to fix QuickBooks Error 3371 and get your QuickBooks running again.

I see this a lot—and it seems like it's a lot more prevalent than it used to be—reasoning from a proxy. Like trying to suss out how competent someone is in your shared field by looking at their GitHub profile, instead just asking them questions about it (e.g. the JVM). If X is the thing you want to know about, then don't look at Y and draw conclusions that way. (See also: the X/Y problem.) There's no need to approach things in a roundabout, inefficient, error-prone manner, so don't bother trying unless you have to.

Se usa algo llamado anotaciones. Para el caso de los booleanos sería {{gtClass:name=Boolean}}

Error in Fig 2.6: The difference in Crab Production (4) shown in graph between 15 down to 9 should read as (5) and not the (4) shown in Figure.

This shouldn't even be an argument. package-lock.json isn't free. It's like cutting all foods with Vitamin C out of your diet and then saying, "but you can just take vitamin supplements." The recommended solution utterly fails to account for the problem in the first place, and therefore fails to justify itself as a solution.

Give this one another go and think it through more carefully.

This is a Comprehensive Guide to Fix ChatGPT Server Error. Follow the link to check the formula >> Internal Server Error ChatGPT<<<

The "single owner" part is no longer true, although I believe it used to be. For example, I am one of three owners of the Metagov org on Github. (I should figure out how to remove myself as an owner.)

The results from using the old version of Microsoft Excel.

I am getting this error while doing make dev I have installed the required version of python, still update with the required version please.

File "/home/ec2-user/projects/h/h/search/config.py", line 213, in _ensure_icu_plugin

names = [x.strip() for x in conn.cat.plugins(h="component").split("\n")]

AttributeError: 'list' object has no attribute 'split'

Node is not a programming language.

(40) has an error. The first term should be -8asin(4ax^2)

Use this to explain why Bernhardt's JS wat (or, really, folks' gut reaction to what they're seeing) is misleading.

again: unmatched class selectors

additionally, it's not the fact that they are unmatched (or that they are class selectors specifically) that it's a problem—it's the fact that there are a lot of them

the entire choice of focusing on classes and class selectors here is basically a red herring

This statement is incorrect. Lewis acids (like sp2-hybridized boron) are electron pair acceptors, not proton acceptors. Lewis bases are proton acceptors, and there are no lone pairs of electrons at the boron atom in typical compounds (BH3 or BH4- or derivatives).

Error here. If you uncomment out the # for the 'live_loop' command, you need a second end to finish things off. One 'end' to close live_loop, one to close off data.each:

``` live_loop :jesuit do data.each do |line| topic1 = line[:topic1].to_f topic2 = line[:topic2].to_f

use_synth :piano
play topic1*2, attack: rand(0.5), decay: rand(1), amp: rand(0.25)
use_synth :piano
play topic2*2, attack: rand(0.5), decay: rand(1), amp: rand(0.25)
sleep (0.5)

end end ```

That's the entire topic, my guy!

"We should be optimising Mastodon so it incentivises more serve[r]s with fewer people." is the very premise of the conversation!

Mastodon "push[ing] the direction of the protocol or make it harder to cultivate an ecosystem of smaller ones."? "it needs to be easier to start smaller ones"? Are you just not paying attention to the conversations you're responding to?

Reminds me of:

What fascinated me was that, with every single issue we discussed, we went around in a similar circle — and Kurt didn’t seem to see any problem with this, just so long as the number of 2SAT clauses that he had to resolve to get a contradiction was large enough.

https://scottaaronson.blog/?p=232

So make your application document-driven (i.e. actually RESTful).

It's interesting that we have Web forms and that we call them that and yet very few people seem to have grokked the significance of the term and connected it to, you know, actual forms—that you fill out on paper and hand over to someone to process, etc. The "application" lies in that latter part—the process; it is not the visual representation of any on-screen controls. So start with something like that, and then build a specialized user agent for it if you can (and if you want to). If you find that you can't? No big deal! It's not what the Web was meant for.

Why are people so seduced by this dumb argument—to the point that they almost seem proud of it?

First, it's presumptuous. Who says we're even using glibc instead of some other libc—which I just might choose to include in the projects I work on? Who says we're even using Linux, for that matter?

Secondly, even if we were, let's assume that we're not, and then see if that teaches us anything about the overall line of reasoning. The original comment was about NPM. NPM is used a fair bit for not just backend stuff but for managing packages used in the browser, too. Let's assume, for simplicity, that our program is entirely a browser-based JS+HTML+CSS app with no backend to speak of. Would the same people argue that, among other things, the Web browser sources would need to be included? Does it even make sense to argue that? Asking the system software question betrays a failure to accurately grapple with the classes of software artifacts we're dealing with, their role in the overall project, and our responsibility for them.

For checking which posts are new/updated, this is always the case. The only thing the HTTP cache-related headers can tell is that the feed itself has/hasn't changed.

not complient with Problem Details, which requires details to be a string

This should read "about 21 million years earlier" since the previous estimate was 166 mya.

Someone is going to need to eventually explain their convoluted reasons for labeling this a downside.

Sure, strictly speaking, a bigger source tree is bad, but delegating to package.json and npm install doesn't actually change anything here. It's the same amount of code whether you eagerly fetch all of it at the same time or whether you resort to late fetching.

Almost none of the hypothetical benefits apply to the way development is handled in practice. There was one arguably nice benefit, but it was a benefit for the application author's repo host (not the application author), and the argument in favor of it evaporated when GitHub acquired NPM, Inc.

No, those are orthogonal. Whether you obtain the code for your dependency* at the same time you clone your repo or whether you get it by binding by name and then late-fetching it after the clone finishes, neither approach has any irreversible, distinct consequences re bugs/fixes.

* and it still is a dependency, even when it's "vendored"...

False. They found the opposite in female rats: Female "[r]ats with 12-h access to HFCS gained" 10 FEWER grams of "body weight than animals given equal access to 10% sucrose." Table 1 shows female rats with 7 months of 12-h HFCS + 12-h chow access averaging LESS body weight (323 g) than those with the matching control group on 12-h sucrose + 12-h chow access (333 g). The former also had LESS body FAT than the latter (Figure 4). And they had the SAME TG levels (mg/dL:128 in both cases.) The highlighted conclusion is both untrue, and the most widely reported conclusion found in mass media news coverage of the research. I've shown the conclusion is directly contradicted by the researchers' results displayed in the article. If it's false for female rats and true for male rats, then it's false for rats in general; that's basic logic. No reasoning (e.g. that which follows about calories) can make the statement true.

Sparkes, M. (2021, November 19). Wikipedia tests AI for spotting contradictory claims in articles. New Scientist. https://institutions.newscientist.com/article/2298169-wikipedia-tests-ai-for-spotting-contradictory-claims-in-articles/?utm_campaign=echobox&utm_medium=social&utm_source=Twitter&utm_term=Autofeed

Corollary: Spolsky (at least at the time of this article) didn't really understand types, having about the same grasp on computing fundamentals as your average C programmer.

So run a typechecker on the code to check your work if you want type checking. That is what TypeScript does, after all. And it's been around long enough that people shouldn't be making the mistake that a runtime that support dynamic types at runtime means that you can't use a static typechecker at "compile time" (i.e. while the code is still on the developer workstation).

독일 하노버대학교 생산공학 및 공작기계 연구소(IFW)의 Denkena 교수의 스핀들 열적 최적화와 관련된 논문. 참조를 보면 공작기계 스핀들 해석과 관련된 핵심 논문들이 많이 포함되어 있다.

Category error; C, C++, and Fortran are programming languages, not tech stacks.

There's a weird (read: "weirdly obvious") category error here. NodeJS is not a language. (This wouldn't be so notable if the comment didn't go on to say "The key point is writing to an interface and not an implementation.")

The puzzle piece that fits the shape of the hole here is "JS". JS is the language, NodeJS is one of its implementations—and chubot knew both of these things already, so it's odd that it was expressed this way. Plus, there's a lot more diversity of JS implementations than exist for e.g. Python...

Even most ostensible FP practitioners who swear they don't.

Until those things go away.

A case study: DuckDuckHack used Codio, which "worked" until DDG decided to call it a wrap on accepting outside contributions. DDG stopped paying for Codio, and because of that, there was no longer an easy way to replicate the development environment—the DuckDuckHack repos remained available (still do), but you can't pop over into Codio and play around with it. Furthermore, because Codio had been functioning as a sort of crutch to paper over the shortcomings in the onboarding/startup process for DuckDuckHack, there was never any pressure to make sure that contributors could easily get up and running without access to a Codio-based development environment.

It's interesting that, no matter how many times cloud-based Web IDEs have been attempted and failed to displace traditional, local development, people keep getting suckered into it, despite the history of observable downsides.

What's also interesting is the conflation of two things:

1. software that works by treating the Web browser as a ubiquitous, reliable interpreter (in a way that neither /usr/local/bin/node nor /usr/bin/python3 are reliably ubiquitous)—NB: and running locally, just like Node or Python (or go build or make run or...)—and

2. the idea that development toolchains aiming for "zero configuration and setup" should defer to and depend upon the continued operation of third-party servers

That is, even though the Web browser is an attractive target for its consistency (in behavior and availability), most Web IDE advocates aren't actually leveraging its benefits—they still end up targeting (e.g.) /usr/local/bin/node and /usr/local/python3—except the executables in question are expected to run on some server(s) instead of the contributor's own machine. These browser-based IDEs aren't so browser-based after all, since they're just shelling out to some non-browser process (over RPC over HTTP). The "World Wide Wruntime" is relegated to merely interpreting the code for a thin client that handles its half of the transactions to/from said remote processes, which end up handling the bulk of the computing (even if that computing isn't heavyweight and/or the client code on its own is full of bloat, owing to the modern trends in Web design).

It's sort of crazy how common it is to encounter this "mental slippery slope": "We can lean on the Web browser, since it's available everywhere!" → "That involves offloading it to the cloud (because that's how you 'do' stuff for the browser, right?)".

So: want to see an actual boom in collaborative development spurred by zero-configuration dev environments? The prescription is straightforward: make all these tools truly run in the browser. The experience we should all be shooting for resemble something like this: Step 1: clone the repo Step 2: double click README.html Step 3: you're off to the races—because project upstream has given you all the tools you need to nurture your desire to contribute

You can also watch this space for more examples of the need for an alternative take on working to actually manage to achieve the promise of increased collaboration through friction-free (or at least friction-reduced) development: * https://hypothes.is/search?q=%22the+repo+is+the+IDE%22 * https://hypothes.is/search?q=%22builds+and+burdens%22

L'uinità codicologica deve essere riformattata.

0.7^2 + 0.3^2 > 0.5

Overall accuracy is 50% to 100%, depending on proportion

No, Fig. 2B only demonstrates that smaller validation N increases variance (law of large numbers). There is no clear bias-variance tradeoff in choice of K (see variance of Fig. 2A).

increasing K decreases (K-1)/K, what?

Is "automated deployments" really the solution?

This is a deductive argument, but I believe theres no error in the way it's used

There's a related phenomenon/paradox: the superinferiority of "native" applications.

{错误：spawn C：\ wamp \ bin \ php \ php7.2.14 ENOENT 在Process.ChildProcess._handle.onexit at on OnErrorNT（internal / child_process.js：406：16） at process._tickCallback（internal / process / next_tick.js：63： 19） errno：'ENOENT'， 代码：'ENOENT'， 系统调用：'spawn C：\ wamp \ bin \ php \ php7.2.14'， 路径：'C：\ \ wamp \ bin \ php \ php7.2.14'， spawnargs：['c：\ wamp \ www \ NULB \ admin \ index.php']} < / pre>

If what we're discussing here is the decision to no longer opt in to playing along with the "Western" regime for IP, then why would they limit themselves to Linux and Wine—two products of attempts to play by the rules of the now-deprioritized regime? Why wouldn't they react by shamelessly embracing "pirated" forms of the (Windows) systems that they clearly have a revealed preference for? If hackability is the issue*, then that's ameliorated by the fact that NT/2000 source code and XP source code was leaked awhile ago—again: the only thing stopping anyone from embracing those before was a willingness to play along and recognize that some game states are unreachable when (artificially) restricting one's own options to things that are considered legal moves. But that's not important anymore, right?

* i.e. malleability, and it's not obvious that it should be—it wasn't already, so what does this change?

QuickBooks error 3371 usually occurs while you attempt to re-configure your system or when you try to activate QuickBooks. This error may also pop up in case of damaged company files. This error is often associated with a damaged QB system file, namely 'entitlementDataStore.ECML'. To know about this error, ensure that you go through this article till the very end. Our expert team provides you with the most reliable support and ensures that all your queries and issues get resolved in a timely manner. This article enumerates the various causes and the necessary troubleshooting measures for fixing the QuickBooks Error 3371 Status Code 11118.

In other words, do a lot of work to route around the problems introduced by the way that using npm routes around your existing version control system.

These packages don't/can't do the amount of exception handling suggested by this comment.

There's an unnecessary dichotomy here between uses JS and page is served as HTML. There's a middle ground, where the JS can do the same thing that it does now, but it only does so at edit time—in the post author's own browser, but not in others'. Once the post author is ready to publish an update, the client-side generated content is captured as plain HTML, and then they upload that. It still "uses JS", but crucially it doesn't require the visitor to have their browser do it (and for it to be repeated N times, once per page visit)...

This post is filled with programming/debugging missteps that are the result of nothing other than overlooking what's already right in front of the person who's writing.

Can anyone help I am getting this error

C:\Users\sande.firefly\stacks\sandeep2>ff start sandeep2 this will take a few seconds longer since this is the first time you're running this stack... ⣷ Error: dial tcp 127.0.0.1:0: connectex: The requested address is not valid in its context. Usage: ff start <stack_name> [flags]

Flags: -h, --help help for start -b, --no-rollback Do not automatically rollback changes if first time setup fails

Global Flags: --ansi string control when to print ANSI control characters ("never"|"always"|"auto") (default "auto") -v, --verbose verbose log output

Error: dial tcp 127.0.0.1:0: connectex: The requested address is not valid in its context.

Using regular expression in this way might cause "Elasticsearch exception [type=search_phase_execution_exception, reason=all shards failed]", especially when together with "query?scroll=1m"

"How much of your love of chocolate has to do with your designs for life that are informed by your religious creed? Is it incidental or essential?"

Table 3

In addition to the note above about this being susceptible to sites that deny execution of inline scripts, this also isn't really solving the problem. At this point, these are effectively GreaseMonkey scripts (not bookmarklets), except initialized in a really roundabout way...

Burt and Obradović (2013)

Consider using DS rather than RS if there is a strong association between baseline assessments and the outcome