PoE basics and beyond: What every engineer should know
edn.com
rlsw – Raylib software OpenGL renderer in less than 5k LOC
github.com
The Hidden Engineering of Niagara Falls
practical.engineering
Replacing a $3000/mo Heroku bill with a $55/mo server
disco.cloud
Neural audio codecs: how to get audio into LLMs
kyutai.org
NASA chief suggests SpaceX may be booted from moon mission
cnn.com
Ask HN: Our AWS account got compromised after their outage
Wikipedia says traffic is falling due to AI search summaries and social video
techcrunch.com
Mathematicians have found a hidden 'reset button' for undoing rotation
newscientist.com
"Butt breathing" might soon be a real medical treatment
arstechnica.com
Daniel J. Bernstein updated cdb (Constant database) to go beyond 4GB
cdb.cr.yp.to
Doomsday scoreboard
doomsday.march1studios.com
Getting DeepSeek-OCR working on an Nvidia Spark via brute force with Claude Code
simonwillison.net
King vs. Rich: The Founder's Dilemma
thevcedge.substack.com
Foreign hackers breached a US nuclear weapons plant via SharePoint flaws
csoonline.com
Minds, brains, and programs (1980) [pdf]
home.csulb.edu
60k kids have avoided peanut allergies due to 2015 advice, study finds
cbsnews.com
What do we do if SETI is successful?
universetoday.com
The death of thread per core
buttondown.com
Understanding conflict resolution and avoidance in PostgreSQL: a complete guide
pgedge.com
> An ounce of prevention is worth a pound of cure, after all.
Best points are this summary near the end. IMO it's better to also allow for slower writes doing something simpler than trying to complex distributed stuff just so writes are quick. Users seem to have pretty long tolerance for something they understand as a write taking even many seconds.