bordercases

This would all be true if perceptions matched reality for model performance and productivity.

Hopefully not in the same way you should never naively trust compilers!

Maybe you could ask an ecologist this question.

Somebody's gotta be eaten alive. So why not you, bcjdjsndon?

I refuse to believe that humanity on a whole is that incapable. Or at least unwilling to try to do something different.

Is that typical of people who hold this view?

It could be both correct, and a cheap signal.

Seeding torrrent blocks.

The Berkeley and New York scenes are special in that they lead and guide the community on a whole mainly by example.

To be fair, you don't know what the poster believes about those services either.

This reminds me of how the Dunning Kreguer results might have been misapplied statistics.

How many children do you expect to be combatants?

I think he implied Ozempic.

Indeed, this seems to be the insight around vertical slice architecture? https://www.jimmybogard.com/vertical-slice-architecture/

If parasites were widespread amongst human beings, would those infected humans have incentive to study them?

We are likely biased and can't imagine how we are biased because of the infection! Yet the over-under for an individual is clear: try the medication and find out!

Yeah it's essentially a way to reflect parsimonious assumptions so that your output distribution can be characterized as a law.

Many of these arguements are moot – because for any top-down function definition technique, the How to Design Programs recipe covers virtually all the bases.

- https://course.ccs.neu.edu/cs2500f18/design_recipe.html - https://cs110.students.cs.ubc.ca/reference/design-recipes.ht... - https://docs.racket-lang.org/htdf/index.html

Between a signature, purpose statement and examples, you've declared most of what documentation provides short of a longer contextual statement of the functions role in a codebase.

For larger modules there is How to Design Worlds.

- https://world.cs.brown.edu/1/htdw-v1.pdf

Greenspan's tenth law is that every language ends up with a half baked Common Lisp implementation. This is apparently true, with the stipulo that these implementations end up fully baked over time. This is true since functional programming languages are commonly research languages which mean industry languages catch up.

But is the luck biased to have more survivors in one direction over the other?

What non-circularly defines a money-transmitting business?

> Presumably if publishers were actually pressuring Microsoft to make a child-safe device, they'd have come up with a more advanced protection mechanism than that.

They did. For the next generation. They updated their model of "child safe".

The arguments against planned obsolescence are partially environmental. If planned obsolescence isn't going away, at least this aspect is improved. Consider medical disposables, or one-time packaging that still requires medium term storage survivability.

Someone should write a Wikipedia article on a glibly labeled law to the effect of, "any opportunity for forensic information to be exploited, will be done so."

This is the drive behind comonadic UI frameworks in functional programming - streams of mutual recursion.

What about trees!

Does it scale though?

There being an organic correlate for attention, for memory formation, for emotions and so on – it's likely that the beta-blockers makes certain intents easier to override others, rather than the causality being only one way.

I would love a directional arrow in the table to indicate prices from day to day.

Breathing slowly is a way to short circuit the mind.

I’m guessing is autogenerated by LLMS completions, it’s non deterministic.