I Went to SQL Injection Court
sockpuppet.org
Framework's first desktop is a strange–but unique–mini ITX gaming PC
arstechnica.com
How core Git developers configure Git
blog.gitbutler.com
Emergent Misalignment: Narrow finetuning can produce broadly misaligned LLMs [pdf]
martins1612.github.io
Hard problems that reduce to document ranking
noperator.dev
Ggwave: Tiny Data-over-Sound Library
github.com
Launch HN: Browser Use (YC W25) – open-source web agents
github.com
Bald eagles are thriving again after near extinction
newsweek.com
Part two of Grant Sanderson's video with Terry Tao on the cosmic distance ladder
mathstodon.xyz
Forum with 2.6M posts being deleted due to UK Online Safety Act
forums.hexus.net
New Maps of the Chaotic Space-Time Inside Black Holes
quantamagazine.org
Low Overhead Allocation Sampling with VMProf in PyPy's GC
pypy.org
Chicory: A JVM native WebAssembly runtime
chicory.dev
DeepSearcher: A Local open-source Deep Research
milvus.io
Xonsh – A Python-powered shell
xon.sh
The Deep Research problem
ben-evans.com
A peek into a possible future of Python in the browser
lukasz.langa.pl
Embedding Python in Elixir, It's Fine
dashbit.co
Show HN: GoatDB – A Lightweight, Offline-First, Realtime NoDB for Deno and React
github.com
AI is blurring the line between PMs and Engineers
humanloop.com
If I have learned one thing that makes AWS successful in terms of delivering scalable and reliable services--and that hasn't yet been widely adopted elsewhere--it is captured here:
"The focus on ownership actually helps understand a lot of the organizational structure and engineering approaches that exist within Amazon, and especially in S3. To move fast, to keep a really high bar for quality, teams need to be owners. They need to own the API contracts with other systems their service interacts with, they need to be completely on the hook for durability and performance and availability, and ultimately, they need to step in and fix stuff at three in the morning when an unexpected bug hurts availability. But they also need to be empowered to reflect on that bug fix and improve the system so that it doesn’t happen again. Ownership carries a lot of responsibility, but it also carries a lot of trust – because to let an individual or a team own a service, you have to give them the leeway to make their own decisions about how they are going to deliver it."