We only know what we can measure. We don’t really know what an atomic nucleus looks like, for example. We can only measure what happens when another particle hits it. Between measurements, it might not even be real. We don’t even know what measurement is.

Pick your favorite quantum interpretation: Copenhagen, Broglie–Bohm, Many Worlds. We’ll probably never know the truth.

Lack of space was Fermat’s excuse for not proving his last theorem.

analysis finds that cameras lead to persistent and sustained reductions in crashes.

You should have put that in the title.

Elitzur–Vaidman bomb tester

I would argue it’s still mysterious. If it were simple, we wouldn’t have what’s called the measurement problem.

Also, there is more than one way to measure something, and not all of them require a real photon to hit some particle. In the Elitzur–Vaidman bomb tester, you can “measure” whether the quantum bomb’s sensor is working or not without actually hitting it with a photon. Instead, you hit it with the “chance” of a photon hitting it, and that’s good enough. (It’ll still blow up half of the time, but you can design the tester with multiple recursive tiers to increase your tested-but-unexploded bomb yield to arbitrarily close to 100%.)

That’s pretty mysterious in my mind.

In a folder called javpy, of course!

No, he just hefty!

He thinks he’s a skunk

https://www.youtube.com/watch?v=TjcuqX1_WYE

Water can be up to 15% vegetables and/or noodles!

Starvation is a great motivator!

Checks out.

A U R. It rolls off the tongue pretty easily.

Oh god, that’s worse than I’ve seen where a SQL query joining 10 tables aliased all of the tables as a, b, c, d, e, f, g, h, i, j.

It was a mess, and as a new dev on the project, trying to figure out which where clause was for which table and how things worked was a fucking nightmare. Trying to keep a dictionary of letters to real table names in your head as you looked at the query was very taxing. In the end, I just fixed it all to stop using aliases. Or to use short abbreviations.

Here’s a mock example:

SELECT
    j.delivery_eta,
    c.cat_desc,
    a.part_number,
    h.region_label,
    f.wh_loc,
    e.emp_last,
    g.state_flag,
    b.mfg_title,
    i.ship_track_code,
    d.order_sum,
    a.created_on,
    j.last_scanned_at,
    e.emp_first,
    c.cat_code,
    g.state_level
FROM parts AS a
INNER JOIN manufacturers AS b 
    ON a.manufacturers_id = b.id
INNER JOIN categories AS c 
    ON a.categories_id = c.id
INNER JOIN orders AS d 
    ON a.orders_id = d.id
INNER JOIN employees AS e 
    ON d.employees_id = e.id
INNER JOIN warehouses AS f 
    ON a.warehouses_id = f.id
INNER JOIN inv_state AS g 
    ON a.inv_state_id = g.id
INNER JOIN regions AS h 
    ON f.regions_id = h.id
INNER JOIN shipments AS i 
    ON d.shipments_id = i.id
INNER JOIN logistics AS j 
    ON i.logistics_id = j.id
WHERE
    (b.mfg_title LIKE '%Corp%' OR b.mfg_title LIKE '%Global%')
    AND c.cat_desc NOT IN ('Unknown', 'None', 'Legacy')
    AND (d.order_sum > 1000 OR d.order_sum BETWEEN 250 AND 275)
    AND e.emp_last ILIKE '%berg'
    AND (f.wh_loc IN ('A1', 'Z9', 'M3') OR f.wh_loc IS NULL)
    AND g.state_flag IN ('ACT', 'PENDING')
    AND h.region_label NOT LIKE 'EXT-%'
    AND (i.ship_track_code IS NOT NULL AND i.ship_track_code <> '')
    AND (j.delivery_eta < NOW() + INTERVAL '90 days' OR j.last_scanned_at IS NULL)
    AND (a.part_number ~ '^[A-Z0-9]+$' OR a.part_number IS NULL)
    AND (
        (c.cat_code = 'X1' AND g.state_level > 2)
        OR
        (e.emp_first ILIKE 'J%' AND d.orders_id IS NOT NULL)
    );

It was a quote from the story. 😑

massive

I thought he was short and average weight.

Spectroscopic tests revealed ultrafast spin conversion and nearly 99% triplet-energy transfer, marking an unprecedented level of control over exciton dynamics.

Ah, yes. I see. 99% triplet-energy transfer. Good, good.

Windows is 100 layer lasagna.

https://youtube.com/shorts/QEVaIbhwTHI

I think you need to re-examine your assumptions.