Asyncio: A library with too many sharp corners
sailor.li
Personal aviation is about to get interesting (2023)
elidourado.com
Show HN: QuickTunes: Apple Music player for Mac with iPod vibes
furnacecreek.org
What went wrong for Yahoo
dfarq.homeip.net
Paul Dirac and the religion of mathematical beauty (2011) [video]
youtube.com
Rust running on every GPU
rust-gpu.github.io
Getting decent error reports in Bash when you're using 'set -e'
utcc.utoronto.ca
Torqued Accelerator Using Radiation from the Sun (Tars) for Interstellar Payload
arxiv.org
Coronary artery calcium testing can reveal plaque in arteries, but is underused
nytimes.com
Tinyio: A tiny (~200 line) event loop for Python
github.com
SV AI Startups Are Embracing China's Controversial '996' Work Schedule
wired.com
The natural diamond industry is getting rocked. Thank the lab-grown variety
cbc.ca
Large ancient Hawaiian petroglyphs uncovered by waves on Oahu
sfgate.com
Test Results for AMD Zen 5
agner.org
Algos and Code Performance: Your Code Works but Can It Handle Real Traffic?
beon.tech
Millet mystery: Why staple crop failed to take root in ancient Japanese kitchens
phys.org
OCaml Programming: Correct and Efficient and Beautiful
cs3110.github.io
Teach Yourself Programming in Ten Years
norvig.com
Shallow Water Is Dangerous Too
jefftk.com
The worst start -up I ever joined (and this is saying something!) had this problem that this article really describes well, of focusing on downside problems while in the upside phase. It looked like the founder insisting on literally 100% unit test coverage (the code would set a constant to 5 and the tests asserted the constant was set to 5), even while the product had literally no users (in fact the growing code base had never been run outside of test).
The founder was ex-Google so this also tracks with the article.