Any tips for losslessly encoding 200 bits of information into one bit?
Graham Christensen
11.3K posts
- I do this too, it’s sick. The graph is a tree of named nodes, the source code lives in those nodes. The node names have context for what they contain.🤯 this genius stores his entire codebase syntax in a graph database and queries it so provide context to an llm
- My neck. My back.What stops you from working 4 hours straight in a coffee shop?
- Replying to @luciascarletI had a hard time at first figuring out what you were trying to show me. So for the folks like me, here you go:
- Actually, API endpoints should listen for http and immediately revoke any tokens submitted.
- Replying to @ineratiYou’d think it’d be faster, with that highway and whatnot.
- Every so often I remember shell’s line-continuation character “\” is “just” escaping the newline that comes next in the bytes and I lose some brain cells.
- We didn’t.Why did humans stop building wonders?
- Replying to @geerlingguyMeanwhile I flagged a video about using extension cords to connect low voltage DC equipment using NEMA 5-15 ends as dangerous and harmful, but was deemed acceptable.
- That’s a big no from me. Clear ownership and rights to the software is critical. Adding co-authorship to a random company isn’t it.Claude Code casually giving itself co-author credits on all of my commits (I can't be mad about it!)
- average rust developer reading the average blog post about base64 in rust
- Nix is what happens when you get a phd in copying software from one computer to another and having it work when it gets there.homebrew is what happens when you can't invert a binary tree

















