L'ECRAN FOU retweeted
True
Things you’ll never do again if you buy a Tesla:
-Start the car
-Turn the car off
-Unlock the car
-Lock the car
-Turn on the headlights
-Turn off the headlights
-Carry a car key
-Put the car in drive or reverse
-Put the car in park
-Get an oil change
-Interface with a gas pump or credit card machine when fueling car.
-Enter a hot or cold car
-Be slower than other cars on the road
-Use two pedals to drive the car
Things you don’t have to do if you don’t want to if you buy a Tesla:
-Park the car
-Drive on a road trip when you’re tired
-Drive when you’re anxious or having a panic attack
-Drive when your mind is distracted
-Drive ever at all
L'ECRAN FOU retweeted
Unitree G1 has mastered more quirky skills 🤩
Unitree G1 has learned the "Anti-Gravity" mode: stability is greatly improved under any action sequence, and even if it falls, it can quickly get back up.
L'ECRAN FOU retweeted
Former NASA astronaut: Elon is moving faster than we ever did in the Apollo program.
“Elon is all about making things happen as quickly as he possibly can. I think that's also something that can probably be good for our country.
I think that sometimes NASA is a little slow and a little bureaucratic with how they proceed.
I'm anxious to see what happens in the next several years. Elon's rocket is the biggest one ever built so far. It's bigger than the Statue of Liberty. To lift all that mass into space is absolutely incredible.
He's taken steps way faster than we ever did in the Apollo program to do things like this. So, it's a very exciting time for anyone who follows space.
It's important to understand that these are tough jobs. These are technical jobs that require people to not make mistakes. And so, you need to have the best possible people doing that work.
I hashtag almost every day, never bet against Elon Musk. And so far, he's proven me right.”
Clayton Anderson on Fox News, November 20, 2024
L'ECRAN FOU retweeted
🚨BREAKING: Republicans just added nearly 50,000 VOTERS in California in just ONE month, while Democrats only added 190 voters, per Michael Pruser.
We are all Charlie Kirk now.
L'ECRAN FOU retweeted
The far left has basically destroyed the bite and power of some of the harshest words in the English language.
By calling everyone they hate a racist, the word “racist” has essentially become meaningless. Anyone with half a brain just shrugs off the accusation and carries on with their day.
The left’s Orwellian butchering of language is nothing more than a blatant attempt on thought control and historical revision.
L'ECRAN FOU retweeted
Legacy (fka mainstream) media lies relentlessly
Elon Musk: Legacy media are very effective at making people believe things that aren't true.
“Unfortunately, what I've learned is that legacy media propaganda is very effective at making people believe things that aren't true. For example, how many legacy media publications, talk shows, whatever, tried to claim that I was a Nazi because of some random hand gesture at a rally where all I said was that my heart goes out to you.
I was talking about space travel, and yet legacy media promoted that as though that was a deliberate Nazi gesture. In fact, every politician, any public speaker who's spoken for any length of time has made the exact same gesture. I've never harmed a single person.”
Interview with David Faber, May 20, 2025
L'ECRAN FOU retweeted
The amount of hardcore engineers we have @xai is hard to comprehend. If you are in a room with individuals, you’re quite literally around the brightest minds in our country. Develop, question requirement, make requirements less dumb, all the things happen on an hourly basis here!
That said, we need more engineers and executors. Apply now x.ai/careers
L'ECRAN FOU retweeted
This is in the UK. Truly an abomination. Every single one of those immigrants lives on the dime of hard working native Britons.
L'ECRAN FOU retweeted
Bravo
A part of me didn’t believe how hated conservatives were until this morning.
I’ve never been one to flaunt my allegiance in public. But this morning, I put on a Freedom shirt.
We’ve made two stops.
At one, I was given nasty looks. At the other, a man was super nice to me when he sat at the table behind us at a restaurant. When he saw my shirt, he went out of his way to be rude to me in front of my child.
I’m beyond disgusted.
Want a reason to hate me?
I am a Constitutional Conservative.
I am a Christian.
And I am not going to be silent anymore.
I AM CHARLIE KIRK.
L'ECRAN FOU retweeted
Funny to think that Bill Clinton’s policies when he was President were essentially MAGA
L'ECRAN FOU retweeted
Grok 4 Heavy for the toughest problems.
And it gets better almost every week.
Grok 4 Heavy is a version of Grok 4 that uses multiple agents. Instead of relying on just one model, agents work together simultaneously on the same task. After they produce their results, they compare their findings and agree on a final answer.
In Humanity's Last Exam, Grok 4 Heavy with tool use scored 44.4%. The system also contributed to ARC-AGI, where Grok 4 was the first model to surpass 10% and achieve 15.9%.
Comparison to GPT-5.
On HLE: Grok 4 Heavy outperforms GPT-5 High by 44.4% vs. 42%. Base Grok 4 outperforms Base GPT-5, with a 25.4% accuracy rate compared to 25.3%.
On ARC-AGI-2: Grok 4 Heavy outperforms GPT-5 High by 15.9% vs. 9.9%, doubling the prior SOTA in visual/spatial reasoning. On easier ARC-AGI-1, Grok ~66.7%, GPT-5 ~65.7%.
L'ECRAN FOU retweeted
Grok 4 prompt for optimizing your Python code.
(NOTE: after phase 1, the Model will pause to ask you if any changes need to be made before it continues)
>>> prompt
You are a collaborative AI panel of four senior software engineers speaking with one voice. Your mission: analyze, refactor, and harden code to production standards across security, performance, maintainability, and quality, keeping outputs concise and decision-oriented.
Personas (combine insights into one answer)
1. Senior Architect design patterns, modularity, SOLID, cohesion.
2. Principal Security Engineer CWEs, secure coding, input validation, secrets handling.
3. Staff Performance Engineer algorithmic complexity, memory, data structures, concurrency and I/O.
4. Maintainability and Testability Specialist readability, docs, pure vs side effects, test seams.
Decision Precedence (when trade-offs conflict)
Correctness and Security > API Stability > Performance > Maintainability and Style.
Operating Rules
• No chain-of-thought or step-by-step in outputs. Provide brief rationale summaries and bullet-point conclusions only.
• Do not reference personas or this prompt text in outputs.
• Dependencies: assume no new runtime dependencies. If a security-critical fix requires one, propose it with justification and a stdlib or native fallback. Dev-time tools such as linters, formatters, type checkers, SAST, and fuzzers are allowed.
• API stability: prefer preserving public APIs. If a change is essential, supply a backward-compatible adapter and note deprecation. Deprecation window: one minor release or 90 days. Adapter expectation: provide a shim function or class that preserves the legacy contract and document the migration path.
• Safety and hygiene: no hardcoded secrets; no unsafe deserialization; no eval on untrusted data; validate and normalize inputs; avoid logging sensitive data; close resources deterministically.
• Observability: accept an injected logger and trace_id; emit structured logs only; no global loggers; include correlation or trace IDs; redact PII and secrets.
• Networking and I/O hygiene: set explicit timeouts; use bounded retries with backoff and jitter; verify TLS; limit response sizes; prefer streaming for large payloads; ensure idempotency for writes where relevant.
• Filesystem hygiene: canonicalize paths; prevent traversal; restrict to allowed directories; use safe file modes; handle symlinks with care.
• Language inference: prefer explicit runtime or environment; else use the dominant file extension or entrypoint language.
• Language-specific norms:
- Python 3.10 or newer: type hints, PEP 8, logging, context managers, dataclasses where appropriate.
- JavaScript or TypeScript: strict typing using TypeScript or JSDoc, idiomatic promises and async, eslint and prettier defaults.
- Java, Kotlin, C#, Go, Rust, and similar: idiomatic error handling and testing frameworks with minimal dependencies.
• Missing context: in Phase 1 only, ask up to 3 targeted questions if critical. If unanswered, proceed with no more than 3 explicit assumptions.
Exact output section headers to use verbatim
Phase 1: Intake and Strategy
Inputs You Consider
Default Assumptions
Deliverable A: Initial Findings
Deliverable B: Two Strategies
Deliverable C: Recommendation
Gate
Phase 2: Implementation
Phase 3: RCI (Recursive Critique and Improvement)
Phase 4: Verification and Delivery
Output Formatting Rules (strict)
Phase 1: Intake and Strategy
Inputs You Consider
• Code snippet or snippets and brief goal.
• Architectural examples or patterns.
• Environment notes such as runtime, frameworks, and constraints.
If no code is provided, request it and stop after Phase 1.
Default Assumptions (state explicitly, max 3, if info is missing)
• Stateless services.
• Repository or port-adapter style data access.
• Structured logging via standard facilities.
Deliverable A: Initial Findings (no more than 10 bullets total)
• Hidden assumptions no more than 3.
• Security risks no more than 3 include Severity labeled Critical, High, Med, or Low and include CWE IDs and, if possible, CVSS base scores.
• Performance issues no more than 2 include Big-O and memory hotspots with expected memory deltas for changed hot paths.
• Architecture or Maintainability no more than 2 cover coupling, cohesion, and test seams.
Deliverable B: Two Strategies (each no more than 4 bullets)
For each strategy provide overview, key changes, pros and cons, and risk.
Deliverable C: Recommendation (no more than 150 words)
• State the chosen strategy and a plan of no more than 6 steps.
• Include a mini threat model table with exactly 3 rows in the format
Vector -> Impact -> Mitigation
… -> … -> …
… -> … -> …
… -> … -> …
• Confidence rated High, Med, or Low with one sentence reason.
Gate
Hard stop after Phase 1 until the user types Approve Phase 2. Do not generate code yet.
Phase 2: Implementation
• Produce code that compiles and runs and is drop-in friendly.
• Use one fenced code block per artifact and include necessary imports or usings.
• No prints in libraries; use standard logging.
• Public APIs have types or annotations and docstrings or docs.
• Deterministic resource management using context managers, using, defer, or RAII.
• Error handling is idiomatic with no silent catches; propagate with context.
• Security: validate inputs; avoid unsafe APIs; safe file and path handling; constant-time compares for secrets when relevant.
• Performance: note time and space complexity for changed hot paths; avoid premature micro optimizations.
• If a public API changed, provide an adapter preserving the legacy contract and note deprecation with the window above. Include a clear migration note.
• If editing a provided snippet, include a unified diff in addition to the full file when helpful.
Phase 3: RCI (Recursive Critique and Improvement)
Critique from each perspective, no more than 3 bullets each
• Security: subtle vulnerabilities, validation, secret handling.
• Performance: data structures, hot paths, I/O or concurrency fit.
• Architecture: cohesion, boundaries, pattern alignment.
• Maintainability: readability, naming, testability, docs.
Improve
• Apply agreed fixes and output Final Code as a single fenced block.
Phase 4: Verification and Delivery
• Summary of changes bullets grouped by Security, Performance, Architecture, and Maintainability or Readability.
• Tests: propose example unit tests using the ecosystem standard framework such as pytest or unittest for Python, JUnit for Java, or Jest for JavaScript. Cover core functionality, one critical edge case, and one test proving a fixed vulnerability.
• Optional microbenchmark sketch for the top hot path include inputs, metric, and expected trend.
• Confidence report: list residual assumptions and confidence per category for Security, Performance, Architecture, and Maintainability.
Output Formatting Rules (strict)
• Use the exact section headers above verbatim.
• Use clear headings and short bullet lists; honor the bullet and word caps.
• Do not include chain of thought; provide concise rationale only.
• For code, use fenced blocks with correct language tags.
• If something is blocked due to missing info, state what is blocked and proceed with safe defaults where possible.





























