CognitiveLens

I think the parent is referring to how you write PHP templates, which are HTML at the top level, but escape to raw PHP code inside particular delimiters (<?php>), whereas for JSX you write JS at the top level and 'escape' (kinda) to HTML in your returned element. Not exactly an inversion, but I can see the connection.

I think the statement was "It is rare to find people doing good security", not "It is rare to find people leaking internal IDs"

The causal link to social media is presented very simply in the article, but I suspect that's mainly because the article is not about diagnosis, but about the prevalence of the pattern.

There is a lot of data to support the social media effect specifically (some referenced in the linked articles from Twenge), and I suspect the next few posts from Rausch will dive in more deeply, so it's not right to claim that they're jumping to convenient answers - these aren't casual bloggers sharing their reckons.

edit: actually there's a heap of related writing on that site, e.g. https://www.afterbabel.com/p/social-media-mental-illness-epi...

Vibrating a piston at low frequencies isn't hard, but getting it to move enough air is very hard. You're right that "big enough" with "enough power" could solve that problem, but the mechanics of a conventional driver result in unavoidable output roll-off as you go lower, whereas the fan/rotary solution won't roll off because it has essentially infinite excursion - it just keeps blowing in the required direction at the required pressure level for any low-enough frequency, even fractions of Hz.

Re: custom electronics - my understanding is that the electronics just need to handle very low frequencies (in part by being able to sustain enough current without fading), which would also be true for a conventional subwoofer system trying to operate at those frequencies.

I remember reading about this thing a long time ago and wondering how close I could get with a DIY solution. It would probably sound terrible but it would be fascinating as an transducer learning platform.

The actor pattern exists for this reason - it's not like AI is a singular thing checking itself - you could easily have 1000 instances with supervisors automatically rotating out unhealthy instances so that the system is self-repairing even if instances can fail.

There's an interesting parallel between this critique and bad interviewing practices - the kind where the interviewer has a toy problem with a particular "correct" answer in their head and asks the interviewee to figure it out. A lot of the prominent critiques of AI seem to be taking the form "LLM are based in statistics, so they fail to produce strictly-defined solutions, therefore they have little value", which is as close to a straw-man argument as you can make.

Instead, I tend to value critiques that check whether LLMs are useful for the huge number of challenges that we have as programmers where we have to infer 'best' solutions from under-defined problems, or where we have a large set of reference data but need to infer patterns/correctness - those challenges are just as hard (if not harder) than implementing algorithms precisely, so

  - I accept that LLMs aren't good at implementing specific algorithms
  - Can they help write exhaustive unit tests based on code and/or a written spec?
  - Can they help identify potential errors in your best attempt at a solution, even if they can't 'fix' the errors?
  - I can think of a hundred ways to get use out of "a cocky graduate student, smart and widely read, also polite and quick to apologize, but thoroughly, invariably, sloppy and unreliable" - that's a skill that programmers now need to develop, but there's a huge amount of potential in such people, and an analogous potential in LLMs.

I think the pithy saying is that we learn best from failure, not that there is no other way to learn.

Going entirely on gut feel, I suspect that outages like this will be 1) less common and 2) addressed more quickly with AI-supported DevOps in the not-too-distant future.

I know that some other comments indicate that it's not fair to say "you're prompting it wrong", but using ChatGPT with GPT-4, and using advice to set up prompts to give accurate answers, GPT-4 provides an excellent answer here

    ME: You understand everyday tasks very well and can correctly calculate or estimate the time it takes to complete various tasks. I will ask you questions about how long it takes for various things to happen and you will tell me the correct answer using brief, accurate statements.

    If it takes 4 hours for 4 clothing items to dry in the sun, how long does it take for 8 clothing items to dry?

    ChatGPT: The drying time for clothes in the sun typically depends on the amount of sunlight and wind, as well as the type and thickness of the clothing material. However, if we are considering that the drying conditions remain constant and that the drying rate does not depend on the number of clothing items (as they are spread out and not piled on each other), it would still take approximately 4 hours to dry 8 clothing items. This assumes the clothes are spread out sufficiently to all receive equal sunlight and airflow.

I might be misinterpreting the article, but the first two paragraphs specifically describe the over-abundance of marketplace sellers offering similar and sometimes identical products. They're using the same seller platform - Amazon - but that doesn't seem the same as lacking marketplace options as a consumer.

Not sure if it's a perfect analogy, but if we compare the Amazon marketplace to a giant flea market, I think the claim that consumers need a reasonably high level of 'savvy' to operate effectively is pretty easy to defend. When there are lots of sellers, lots of noise, and difficulty verifying quality, the consumer will frequently lose out despite the surplus of marketplace options.

This language style is a bit more common in academic writing outside of the Anglo tradition that is most commonly reported in the English-speaking world. British and American university training emphasises more clinical language, for better and worse.

@elliottkember is giving the correct complimentary antonym to "reinforce" in behavioral psych - "punishment" reduces the frequency of a behavior, "reinforcement" increases the frequency. There's a spectrum, but the terms only refer to the opposing effects on behavior rates. In the GP's comment, "deinforcement" appears to also mean "actively reducing the frequency of the behavior".

The 'Medium' trend seems to most off to me, but I've seen it repeated as truth by a number of people

Medium: text -> images -> video -> 3D graphics -> VR

A lot of people/companies don't seem to appreciate that the appeal of images and video come from the fact that they represent 'real' (or at least staged-real) events/people/places. Animated videos and scenes from movies seem like categorically different kinds of things, less likely to get attention in news feeds other than as fodder for memes.

3D graphics + VR are never going to be real, and I suspect will never (or not for a long time) have the engagement of images + videos despite being ostensibly more 'immersive'.

The article specifically points out that Germany has similar regulatory and cost overrun challenges, so in general it can't be used as a counterpoint - the example case where things went well for Germany is attributed to waiving procedural requirements mandated by the EU.

Even when with guaranteed EU protections, the system can be inefficient.

Results sections typically do not try to make any inferences about the population at large, only the studied sample. They are also stated in the language of statistics - because the results failed to statistically uphold the "TRE is more beneficial" hypothesis, the correct interpretation is that the result is "not 'more beneficial'". In other words, the result "does not confirm that TRE is more beneficial for the sample".

Although the authors don't make a claim about the population overall in the Result section, they may be more optimistic about future research in the Discussion section of the article - I haven't accessed the full document.

I've started searching for something similar, and it looks like such devices are now referred to as DAPs (digital audio players), and the market is very small, mostly served by devices targeting audiophiles. I'm considering getting a used iPod touch (2019) and then locking it down to just the music player app(s) using parental controls.

Could you expand on this? I can't think of places where a string enum would be less useful than a numeric, although I can think of places where numeric enums fall over, e.g. if you have a value that can be one of two different enums and you have to figure out which it is - runtime numeric enum values shouldn't be compared because they regularly have the same value.

Just a stab in the dark, but I was having HMR issues as well and it turned out to be an obscure transitive dependency conflict - details and solutions here on the outside chance it's the same thing affecting your project https://github.com/parcel-bundler/parcel/issues/6685

I don't get the sense that runtime CSS parsing is really much of a concern - it's more about build speed and asset size - since 'green' might be used hundreds of times in a large CSS bundle, the optimization might make sense even with an imperceptible speed cost in the browser.

Parcel has been around for awhile, and the project currently has a lot of activity - I've made the call to migrate an old create-react-app project to Parcel 2 and in general it is going well.

The nice thing about Parcel is that it is intentionally low-config with relatively intuitive defaults, which tells me that it wouldn't be terribly difficult to move to a different bundler in the future. Webpack has gotten better, but you can quickly end up with a _lot_ of Webpack-specific config that makes future migrations hard.

That said, optimizing for future migrations shouldn't generally be your #1 priority - I also like Parcel's speed, and new things like ParcelCSS just validate that further.

The good old what days? All I'm seeing is '*******'

Language evolves, as the wiki article you linked describes. Your prescriptivist nit-picking doesn't contribute to the discussion.

From the HN guidelines:

  - Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.
  - Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.
  - Eschew flamebait. Avoid unrelated controversies and generic tangents.

I had a similar thought, but I wonder how much a 'powder' would qualify as microplastic - can a microplastic be so small that it doesn't have the same food-chain impact as slightly-larger microplastic? Is it possible to make a substance that is universally 100% excreted by every organism?

I haven't read this interpretation of the Arctic Vault project - presumably most users of GitHub are okay with their code being reproduced/backed up across many production servers for fault tolerance. Making an 'extra special' long-term backup in the Arctic Vault doesn't seem like a meaningfully different action to me - i.e. using a cloud-based host is essentially opting in to this kind of 'license violation'.

If they had taken one of their existing DB/disk backups and called it a vault, would that have been an issue?

The grandparent post compared the farmer's experience to being lobotomized - if that's not denigration of someone's life, what is?

Interesting take on the challenge of determining professional trust. Seeing pictures of 3 white/European males on the homepage might turn off a more diverse audience of users, however - even if it's representative of the early adopters, it's important to present the product more inclusively.

I agree with some other commenters that these are very pared-back icons, but I don't see that as a bad thing - they might not be quite right to use as-is for many projects, but they're a great starting point that a design system could use to build out from.

If the starting point has too much personality, it becomes very hard to integrate with existing designs and risks making everything using this icon set look like everything else using this icon set.

of course not, but the effort to bring real-time collaboration to native apps is much higher, e.g. MS Office's still-poor current experience compared with Google Docs's capabilities 5 years ago

Presumably - Sketch is great software, well built, but the fact that in late 2020 they still have to write "And soon, the ability to collaborate in real-time" is the the best counter-argument to building native for me personally.

This is so key - there was some awareness early on that people weren't "working from home" in any normal sense - we were/are "working during a global pandemic". Forced WFH is only one side effect, and trying to analyze the success/failure of WFH with a sample during Covid is probably one of the worst possible management strategies. I see the naive appeal, but the base conditions are completely unrepresentative of the target state.

If you are a manager evaluating the effect of WFH during Covid without the ability to compare it with WFH before Covid, just stop.