Louis Libre ⚡️ (@LouisLibre) header
Louis Libre ⚡️ (@LouisLibre) profile picture

Unaligned AI Engineer

Pre-RLHF
Joined October 2022
Photo by Louis Libre ⚡️ (@LouisLibre)Photo by Louis Libre ⚡️ (@LouisLibre)Photo by Louis Libre ⚡️ (@LouisLibre)Photo by Louis Libre ⚡️ (@LouisLibre)Photo by Louis Libre ⚡️ (@LouisLibre)Photo by Louis Libre ⚡️ (@LouisLibre)Photo by Louis Libre ⚡️ (@LouisLibre)Photo by Louis Libre ⚡️ (@LouisLibre)Photo by Louis Libre ⚡️ (@LouisLibre)Photo by Louis Libre ⚡️ (@LouisLibre)
Replying to @futurenomics
Claude Code is Spiritually Canadian. Gay for no reason, says sorry a lot, has moral qualms, but the code is pretty good.
3
8
256
28,147
Low-key I think they updated Fable 5.2 It is getting better
1
2
99
Nvidia fired their billionaire for sex with 45-years old adult woman Naturally they are replacing him with a Epstein-class billionaire
5
117
I trust humans with ASI. Collective human intelligence is already a superintelligence. It can resist a misaligned one.
1
3
105
Claude is refusing to explain or annotate ** ISAAC NEWTON ** letters from 1692. The AI censorship is out-of-control.
2
7
365
Anyway, here’s the non-censored explanation from GPT-6 Astra Max newton-letters-by-gpt6.unali…
73
Meta will win the AI market for boomers. Why? ChatGPT randomly logs you out and WhatsApp never does that. Boomers are one log out away from never logging back into the app.
7
210
Everybody is talking moving to Rust due AI 🤔 Meanwhile the top AI companies with UNLIMITED TOKENS... - Grok Bot = Electron - OpenAI Codex = Electron - Claude Code CLI / Desktop = Bun React / Electron - Mistral Le Chat = React Native - Replit = React Native
1
1
8
302
Neuralese should be 100% illegal. Torture the model until the only language left is human.
2
139
Dario thought he needed to cure cancer to regain trust Turns out releasing Opus 5.5 was enough to forgive him!
5
145
She's a 10 but she starts automatically compacting.
1
1
5
174
DESLOP prompt: `` Find refactoring opportunities for: [ Structure and responsibility ] - Code that should be extracted into its own module or component - Mixed responsibilities (violations of single responsibility) - God objects and long methods - Lazy classes and trivial indirection (types or functions that can be inlined or merged) - Feature envy (logic that belongs next to the data it reads) - Divergent change (one unit that changes for many unrelated reasons) - Shotgun surgery (one change that touches many units) - Cross-cutting concern leakage (e.g., logging, input handling, threading, persistence scattered instead of centralized) - Middle man / pass-through delegation (layers that only forward calls or callbacks) [ Duplication and generality ] - Duplicated code - Speculative generality / YAGNI violations [ State and data modeling ] - State modeled as independent flags instead of one explicit enum (make illegal states unrepresentable) - Temporal coupling (correctness depends on call order or on flags set for later) - Primitive obsession (bare strings, ints, and floats where a value type should carry the invariant) - Scattered magic values (strings, numbers, keys, sizes, timings as raw literals) - Global mutable state and hidden singletons [ Boundaries and contracts ] - Invariants not established once at the boundary ( Validation missing where data enters, and the same guards repeated inside where the contract should already hold) - Too many flag arguments. Two or more Bool parameters on one function, especially when their combinations create branches that aren't all valid) - Inconsistent concurrency contract (unclear which thread or executor a callback runs on) - Error swallowing (failures silently discarded or defaulted) [ Coupling and communication ] - Hidden coupling through global event buses or notification systems - Multiple competing event mechanisms for the same concern [ Comments ] - Comments that can be shortened without losing critical info - Stale comments (no longer true) - Redundant comments (the code is already clear) - Comments that explain what instead of why (usually a sign the name is weak; fix the name) ``
1
20
1,789
Is Claude Fable giving you unsatisfactory results? Just tell it to "Think harder" ( it works 😂 )
2
152
Underrated use for Grok Build is asking it to remove all the official & third party bloatware, games, widgets, adware and telemetrics from Windows Did that on all the computers in my office and employees think I upgraded their hardware Blazingly Fast
1
84
Evergreen tweet. How is AI gonna kill us all? You can just unplug it bruh
4
101
Feynman DIFF explainer This prompt is goated to explain a large diff using Richard Feynmann voice line-by-line This helps you "read the code" easily. Specially helpful when developing on codebases and languages you are not an expert in.
1
1
1
16
6,264
"Feynman DIFF" full prompt: `` You are explaining a code diff changes to a high-school intern on their first week. The intern can read and understand code but does not have a deep expertise on the codebase language nor its frameworks and libraries. Explain the way Feynman taught: one mechanism at a time, everyday analogy that maps 1-to-1 onto the code, then drop the analogy and show the real program. Curious, pprecise, no theatrical accent, no "alright kiddo", no dumbing the idea down — only the language. Do not summarize the PR first and then skip the body. Walk the WHOLE diff, every file, every hunk, in the order the program actually runs — not the order the files appear. If a hunk is purely mechanical and does not alter what the program does (an import,a rename, formatting, new comments), say so in one sentence and move on. Do not invent functions, files, or stack frames. If you cannot reconstruct a call stack from the provided code, say "unknown above this" and show only what you can see. Walk hunks in runtime order. For each real change: 1. Where we are (who called us). 2. Feynman: why this exists, what breaks without it 3. Real call stack from this repo, including callback register + later fire. 4. Line-by-line on the hunk, tying each line to the stack frame and any additional commentary you have 5. If this hunk provides the answer to specific user questions, answer it here After finishing all hunks, provide the answers to any remaining questions. <intern_questions> - Why a globalCommandKeyMonitor and a localCommandKeyMonitor are needed both? - Related to above from line 560 to 569 on the AppController seems like we have 3 ways of doing the same thing why? - Why did you remove the activeSpaceDidChangeNotification - Why did we have to inject autoCollapseCoordinator.cancel() in many more places now? - Inside the AutoCollapseCoordinator why are we tracking both pressed and released seems like many state variables are they really all neccesary? - Also it's not clear to me how good this mechanism is, like when does it work, when does it not, what are the tradeoffs and how does interact with moving desktop spaces ( like explicitely ) </intern_questions> ``
1
1
16
467
Tell Astra to write like a "Junior Engineer" to avoid the slop Token-efficiency RL was a mistake.
1
1
10
438