Kenney.nl: Free Game Assets
kenney.nl
Zuckerberg approved training Llama on LibGen [pdf]
storage.courtlistener.com
What is an invariant? (2023)
matklad.github.io
HMD Key – A lightweight, affordable smartphone
hmd.com
Obvious things C should do
digitalmars.com
Physicists Want to Ditch Dark Energy
nautil.us
Phi 4 available on Ollama
ollama.com
How hucksters are manipulating Google to promote shady Chrome extensions
arstechnica.com
Harper (YC W25) Is Hiring #1 Founding Growth/Operations Lead
ycombinator.com
AI founders will learn the bitter lesson
lukaspetersson.com
The Illustrated Guide to a PhD
matt.might.net
World's darkest and clearest skies at risk from industrial megaproject
eso.org
IP addresses through 2024
potaroo.net
Running Animations Without Keyframes
css-tip.com
De-smarting the Marshall Uxbridge
tomscii.sig7.se
How outdated information hides in LLM token generation probabilities
blog.anj.ai
Cannonball: An enhanced OutRun engine
github.com
Mullenweg Shuts Down WordPress Sustainability Team, Igniting Backlash
therepository.email
Track your devices via Apple FindMy network in Go/TinyGo
github.com
Who would have won the Simon-Ehrlich bet over different decades?
ourworldindata.org
What it's like working for American companies as an Australian
seangoedecke.com
I’m not sure that I agree with the article.
In the course of my work, I think of an invariant as a state that must hold true at all points during the software’s execution.
For example, “port xxx must never accept inbound traffic”.
I don’t think of invariants as mindsets; I think of them as runtime requirements that are observable and testable at any point during execution, and whose violation is an indication that some assumption about state that the proper execution of the software depends on, no longer holds.
Maybe a good analogy would be “a runtime assert”.