Make little apps for you and your friends
pontus.granstrom.me
MiniMax-M1 open-weight, large-scale hybrid-attention reasoning model
github.com
The Grug Brained Developer (2022)
grugbrain.dev
AI is eating our brains. MIT study: Your brain on ChatGPT
media.mit.edu
Honda conducts successful launch and landing of experimental reusable rocket
global.honda
Show HN: Lstr – A modern, interactive tree command written in Rust
github.com
Your Brain on ChatGPT: Accumulation of Cognitive Debt When Using an AI Assistant
fermatslibrary.com
Timescale Is Now TigerData
tigerdata.com
Resurrecting a dead torrent tracker and finding 3M peers
kianbradley.com
Locally hosting an internet-connected server
mjg59.dreamwidth.org
Windows x86-64 System Call Table (XP/2003/Vista/7/8/10/11 and Server)
j00ru.vexillium.org
Bzip2 crate switches from C to 100% Rust
trifectatech.org
OpenSERDES – Open Hardware Serializer/Deserializer (SerDes) in Verilog
github.com
3D-printed device splits white noise into an acoustic rainbow without power
phys.org
Building Effective AI Agents
anthropic.com
What Google Translate can tell us about vibecoding
ingrids.space
AMD's CDNA 4 Architecture Announcement
chipsandcheese.com
"Don't Mock What You Don't Own" in 5 Minutes
hynek.me
Which company would you prefer to join?
companymatches.com
Dinesh's Mid-Summer Death Valley Walk (1998)
dineshdesai.info
Now might be the best time to learn software development
substack.com
Strangers in the Middle of a City: The John and Jane Does of L.A. Medical Center
latimes.com
LLMs pose an interesting problem for DSL designers
kirancodes.me
> Supercharge Your
I’m totally fascinated by AI coding stuff, but please don’t have an LLM write marketing copy and then shovel the first draft onto the internet. Particularly in a README which should be primarily technical.
The use of “Supercharge” and “Leverage”, the bulleted lists and the reams of non-information (glad to know this is good for “developers working on complex projects”) are all dead giveaways this is unedited LLM-generated content. More to the point, this writing style makes it difficult to tell which parts of the README have actually useful information and which parts of the README are just padding that’s there to waste my time.
As a result I’m gonna have to pass on this. Most LLM-generated READMEs I’ve seen have hallucinated installation guides and usage instructions, and I don’t have time to waste figuring out if that’s the case here. If you rewrite the README from scratch I’ll take another look.