alan kay
for hardware engineers
Why this scored 14
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Outlook
low confidence · estimate, not a guarantee7-day
~8
range 0–20
14-day
~0
range 0–14
30-day
~0
range 0–19
Signal history
7-day window (free)projected trajectory (estimate, not a guarantee)
The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 118
Alan Kay's answer to “Did the ENIAC have a BIOS”?
Explores historical BIOS concepts, relevant for understanding low-level system design. · for hardware engineers
hackernewsSteadyhardware21h ago - 216
Alan Kay: Shannon gave us a way of dealing with noisy channels [video]
Recalls Shannon's noisy channel theory, reminding engineers of fundamental limits in data transmission. · for software engineers, researchers
hackernewsSteadyscience3d ago