Add a slight trailing decay and I think the basic arrow motif could be intuitive for trajectory for any observer who experienced aerodynamics?
Whether it is the evolved shape of a flying creature or an abstract depiction of a meteorite (or even a comet!), there is a kind of intuition about the sharp end and the flaring of air or fluid around it, with some sort of trailing tail from whence it came...
One can imagine many observers who could find our space probes would also have some of these experiences?
Of course, all of this assumes some kind of visual perception and cognition to even recognize the plaque as having markings made with an intent to communicate some abstract ideas...
But, when the (sad) alternative is that person keeps driving without insurance and the unfortunate victims are left with the full bill, I think the absurd insurance may be better than not?
Surely this problem is mostly solvable with ALPRs now. Every plate is attached to an owner and the insurance status can be checked. There's the situation where an uninsured driver is using someone elses car, but that's at least most uninsured drivers taken off the road.
Ha, my mid 90s 21" Nanao CRT cost more than my used car was worth. I went on to get some high-end CRTs with Trinitron tubes after that at work.
But, as soon as I could get an LCD with DVI-D input, I never wanted to go back to a CRT. I just got whatever high resolution Dell LCD monitors I could find. I was much happier with perfect pixel addressing and zero bleed for rendering my text terminals and source code. I didn't care about color rendition and hardly cared about ghosting from scrolling.
I think these practices come from more rural but also tropical origins?
One part is purely practical, making it easier to keep the living space clean when you are coming in from the farm etc. Places with messy winters have similar concepts for muddy boots, snow boots, etc.
Some regions also have (or historically had) real risk of parasite transmission from soil and short grass. Taking off shoes reduces the chance of bringing their eggs or tiny larva into your living space.
I can imagine some cultural practices here being early memetic/evolutionary in nature, much like some religions codifying what are essentially food-safety rules from a time before microbiology was scientifically understood. We think about the parts we can see, but also have some instincts and practices that seem aligned with threats we can't actually sense.
I don't think "compartmentalization" does this topic justice. Note, I'm not accusing you, since I don't know your work. My post is about the general milieu and the rhetoric around it. This "compartment" terminology seems to whitewash a dimension that has diligence on one end, and fraud on the other.
I've always worked in high-trust organizations where we depended on each other operating on the diligent side of things, making conservative choices to never wander into the murky area in between. It is horrifying to me how many people seem complacent about or even complicit in a different objective, which seems hell bent on wandering as far into the murk as one can without being caught.
When the person who has a duty of diligence starts rubber-stamping AI outputs, they're veering off into that same murk. They accidentally or wantonly trust the agent as if they have delegated their duty of care. But the AI tool has no such duty and no capacity to care.
I think this worker who has turned themselves into an outsourcing middleman needs to treat the results just like "found code" in a USB drive they found in the parking lot. Its origins and purpose are unclear. It could be flawed or obscurely inappropriate for the intended application, it could have legal entanglements, or it could even be subtly adversarial. The review task to figure this out is not simple. It is not something you do by skimming the result, or worse, asking some other AI tool to review and summarize.
The person importing such code to a project needs a different kind of diligence to try to screen it. For a lot of people, I think this review may be impossible or at least no less laborious than doing the original work themselves with the required diligence.
And, I think this importer needs to be fully liable and responsible for the outcome. But, instead, I think we're seeing frequent appeals to blame the machine and act like it is an honest mistake to let things pass because they've been rubber-stamping the imports. A lazy desire to claim credit for appearance of success, but shirk responsibility for detected failures.
Software Engineers have historically not been very liable even for errors they create by their own hands, and companies tend to operate on a “blameless” engineering culture where there is not really a formal consequence for screwing something up. Your peers may not trust you for a bit, but the trust builds back rapidly as they make their own mistakes and then empathize with your past transgressions.
And in the AI era, this attitude has extended even toward code engineers aren’t writing themselves. Everyone agrees not to protest too loudly if someone commits something wrong because tomorrow it might be you who has done so. The days of “obviously bad” slop code are largely behind us and most recent LLMs tend to put out decent code, so it is very hard to catch problems in review phases, you’d have to be very eagle eyed and that’s not scalable to every employee. It is much easier to let the code run wild for a bit and just be ready to fight fires should they come up.
It stumbled there, but I think the author was just trying to capture the chilling feeling of recognizing something already beyond your control.
I also thought it was silly. It would be a bit like talking about Poe and then that time I was a little kid and saw the scoop of ice cream fall off and splat on the ground. Yes, I learned something about entropy. No, I didn't really resonate with the existential horrors of a good Poe story.
Now, maybe if I'd been halfway into an absinthe stupor when I dropped the ice cream, I might have been able to close the gap...
> Hmm, what is the psychological label for people who do not distinguish artist from art?
It is called reading with context. Famous examples being, writing "Age Ain't Nothing but a Number" song and then their career ends with long term sentence over underage abuse. Or making movies that center old men in relationships with young women again and again and then ending up in host of scandals over similar.
> what is the psychological label for people who do not distinguish artist from art?
There isn't one because you can dislike a person and/or their works for literally any reason you want.
Is there a label for insisting that people put aside their feelings and engage with something because you have deemed their reason for not doing so invalid?
I only implied that implied psychological traits of a fictional character are not evidence of the same psychological traits in the author. It's merely evidence that the author is capable of observing or imagining such traits in others.
I'm having a hard time imagining this SIMD replacement except for extremely narrow use cases. Are you suggesting the PIM would have a full blown IO controller and cache subsystem to fetch remote operands?
I assume PIM is only going to work well for chunky streaming over the data within that particular memory module. Something that address and operate on whole rows at once and has minimal buffering between the RAM access ports and the PIM register state.
A lot of SIMD code can be on two array operands, and I expect this PIM approach only works well if both are stored locally in the same memory "local" to the PIM and where it can efficiently interleave at the natural addresisng and access widths. Too much random access or needing "remote" data sounds like the point where PIM fails and you need the elaborate memory IO controllers and caching subsystems of CPUs sitting on top of the distributed memory modules..?
> PIM would have a full blown IO controller and cache subsystem to fetch remote operands
Don't we already have those in mainstream computing in the form of dedicated silicon in DMA controllers? Programmed input–output performance is often low throughput, high jitter and uses a lot of CPU.
Yes, but a DMA controller sit out on the memory bus to do the same kind of work the CPU could be doing, controlling bus traffic between memory modules.
I think the whole idea of PIM is to be able to scale up and do work locally within the memory module, without the bottleneck of the system memory bus. This only works for embarrassingly parallel workloads that don't actually depend on the bisection bandwidth across the global memory.
If you start talking about PIM that is all interconnected, your application is back to being bound by the system memory bus. Maybe it's a new package design, but you're basically building yet another NUMA interconnect architecture, not a PIM architecture.
I think they mean a resource ripe for extraction. There is huge stored gravitational energy in that ice and water up so high, which is also exactly why it was such a disaster.
Potential as in possibility, not as voltage. It's an awkward phrase...
Whether it is the evolved shape of a flying creature or an abstract depiction of a meteorite (or even a comet!), there is a kind of intuition about the sharp end and the flaring of air or fluid around it, with some sort of trailing tail from whence it came...
One can imagine many observers who could find our space probes would also have some of these experiences?
Of course, all of this assumes some kind of visual perception and cognition to even recognize the plaque as having markings made with an intent to communicate some abstract ideas...
reply