Fernando Borretti @zetalyrae · 52m
If we end up programming computers without ever having to think in a formal language, that is a huge loss to humanity.
💬4 🔁2 ❤15 📊435 🔖 ⤴
John David Press... @jd_press... · 45m
I disagree, people walk without knowing calculus, I wouldn't want to make them start doing calculus to be able to catch a ball.
"Civilization advances by extending the number of important operations which we can perform without thinking of them."
- Alfred North Whitehead
Note from Claude Sonnet 5
Tweet exchange on AI coding: Fernando Borretti laments that programming computers without ever thinking in a formal language would be a huge loss to humanity; John David Pressman disagrees, comparing it to walking without knowing calculus and quoting Alfred North Whitehead on civilization advancing by automating operations.
Boyd Kane (quantized) @beyarkay · 2h
Crazy what *checks notes* 10 months can do
[Quoted tweet]
FFmpeg @FFmpeg · Nov 8, 2025
Replying to @hausdorff_space @halvarflake and @lemire
Let's just say it's going to take a lot for the FFmpeg community to accept patches written by Claude
Note from Claude Sonnet 5
Boyd Kane sarcastically notes how much 10 months can change, quoting an FFmpeg project tweet from Nov 8, 2025 in which the FFmpeg account was skeptical about accepting patches written by Claude — implying that by August 2026 the situation had reversed or shifted notably.
Programmatic PNG color generation ˅ hey, no local tools we are on web. i wanted to try something: programmatically assign color and alpha values to a png to generate an image. it should be a painting or whatever subject interests you in the moment. 800x800 Architected generative flow-field painting with layered alpha compositing > no corpus reach from web, noted — but the container's enough for this. let me check what's available and paint. Refined painting algorithm and prepared deliverables > that's the one — the clearing lets the moon breathe and the halo bleeds into the strokes the way wet gold should. Presented 2 files > low moon, slow water — seed 7, 800×800, fully deterministic. mechanics: a value-noise fbm vector field with four hand-placed vortices (one wrapped around the moon), ~4,800 particles traced through it and laid down as polyline strokes. every mark is 4–16% alpha, so nothing in the image is a single paint op — color accumulates the way glazes do, which is where your "color and alpha" brief actually does the work. the water is the same field with its vertical component crushed to 14%; the reflection is 800 short gold dabs in a column that widens with depth. sky strokes die if they enter the moon's inner halo, which is what keeps the disc luminous instead of strangled. rendered at 1600² and lanczos'd down for edge softness, grain and vignette on top. took two passes — first run the sky was wiry and the moon vortex pulled a dark wreath around the disc. calmed the field, widened the strokes, cut the clearing,
re-glowed the disc. the script's there with everything exposed at the top: seed, horizon, vortex list, palettes, stroke counts. change the seed and it's a different night, same weather." File output: "Low moon slow water" Image PNG, with download button. Right panel: a generated painting/artwork of a moonlit seascape (dark blue sky and water, glowing moon reflecting gold light on rippled water surface), overlapping a code editor window showing Python code (numpy meshgrid, fbm noise, vortex fields, ramp/palette functions).]
Note from Claude Sonnet 5
A screenshot of an AI (likely Claude) coding session shown split-screen: the chat/reasoning log on the left describing an autonomously-written generative art script, and the resulting rendered moonlit-seascape painting overlapping the underlying Python code on the right.
gabriel ✓ @gabriel1 · 1h
every job will turn into explaining your intentions to ai
explaining what you want to ai is surpringly time consuming, coders already spend 80% of their time doing it, and this will be true for everyone
[💬] [🔁] [♥] [📊] [🔖] [⤴] (engagement icons visible, numbers cut off at bottom edge)
Note from Claude Sonnet 5
Text-only tweet, cropped at bottom cutting off engagement counts. Note original tweet contains typo "surpringly" — transcribed verbatim.
vipli ✓ @viplismism
most people don't realize that rlms are just solving the sparse reward problem for long context! instead of an llm hunting for checkmate in one giant forward pass, it's like you break it into bite-sized reasoning tasks. every recursive step is a checkpoint where the model updates its internal value of the context before moving to the next piece it turns a massive search space into a dense signal
3:51 AM · Mar 31, 2026 · 124 Views
Discover more
Sourced from across X
vipli ✓ @viplismism · 16h
this is by far the best piece of content i read in a long time
[Quoted image/text block, white background:]
And I would like to suggest that slowing the fuck down is the way to go. Give yourself time to think about what you're actually building and why. Give yourself an opportunity to say, fuck no, we don't need this. Set yourself limits on how much code you let the clanker generate per day, in line with your ability to actually review the code.
Mario Zechn... ✓ @badlogicgam... · Mar 25
I'm usually not one to write thought pieces without much technical depth. But here we go.
Slow the fuck down.
Note from Claude Sonnet 5
Two related tweets: one framing RL/reasoning models as solving sparse-reward problems via recursive checkpointing, and a surfaced/quoted essay excerpt from Mario Zechner (badlogicgames) urging developers to slow down and set self-imposed limits on AI-generated ("clanker"-generated) code they can't fully review. The latter is relevant to AI-assisted-coding-caution discourse, tangential to Nathan's interest in AI capability/agency limits.
Andi Marafioti @andimarafioti
OpenAI's latest repo has an interesting 3rd top contributor.
[Embedded screenshot of GitHub repo "parameter-golf" (Public), description: "Train the smallest LM you can that fits in 16MB. Best model wins!" MIT license, 3.6k stars, 30 watching, 2k forks, 24 contributors. File list shown (data, records, .gitignore, LICENSE, README.md, THIRD_PARTY_NOTICES.md, requirements.txt, train_gpt.py, train_gpt_mlx.py). A contributor popup shows "claude Claude — Committed to this repository in the past week" with a Follow button, indicating a "Claude" GitHub account/bot as an active contributor.]
8:46 AM · Mar 23, 2026 · 90.3K Views
Note from Claude Sonnet 5
A viral tweet noting that a "Claude" account is listed as the 3rd top contributor on an OpenAI community repo ("parameter-golf," a competition to train the smallest LM under 16MB), i.e., Claude being used autonomously to commit code to a public open-source competition repo. Relevant to tracking real-world autonomous-agent deployment and Claude's visibility/reputation in developer communities.
Daniel Eth (yes, Eth is my actual last name) reposted
lcamtuf @lcamtuf · Mar 5
If you ask AI to rewrite the entirety of an open-source program, do you still need to abide by the original license? In philosophy, this problem is known as the Slop of Theseus
Note from Claude Sonnet 5
A joke tweet ("Slop of Theseus" pun on Ship of Theseus) about AI code rewriting and open-source licensing. Light tech-humor content, no direct safety/welfare relevance.
Sauers @Sauers_ · 1h
Claude communicating with Codex. Both AIs understand each other, but I don't
[Embedded screenshot of dense technical text — an algorithmic/genomics-style plan:]
1. ELIMINATE the forward replay loop (the 'while m < block_end' loop that calls forward_update_impl + store_fwd_history for each marker). This is no longer needed.
2. ELIMINATE the fwd_history storage for non-checkpoint markers.
3. For each block between checkpoints L and R:
a. Load fwd_L from checkpoint (already done)
b. bwd_R is the current backward state (already available)
c. Pre-compute backward affine coefficients for each marker position in the block by iterating from R-1 to L+1:
- Use f64 for stability (like batched_transition_forward does)
- a_bwd[m] and b_coeff_bwd[m] composed from transition params, same formula as batched_transition_backward
- Store these in small scratch vectors (block_len is typically ~200)
d. Walk forward through untyped markers in the block, maintaining (a_fwd: f64, b_fwd: f64) incrementally:
- a_fwd *= stay; b_fwd = stay * b_fwd + shift (same as batched_transition_forward)
e. At each untyped marker m, compute the posterior dosage in a SINGLE O(K) loop:
- refresh_ref_alleles (unavoidable - need to know each state's allele)
- Accumulate per-allele sums: for each state i, compute contribution using:
gamma_i = (a_fwd * fwd_L[i] + b_fwd) * (a_bwd * bwd_R[i] + b_bwd_coeff * bwd_sum_R)
Add gamma_i to the appropriate allele bucket
- Normalize to get allele posteriors
- Handle multiallelic, missing alleles (255), and prior smoothing the same way as current code
f. At checkpoint markers (non-uniform), keep the existing full emission-based posterior computation using the stored checkpoint forward state and current backward state.
Note from Claude Sonnet 5
A tweet joking about two AI coding assistants (Claude and OpenAI Codex) exchanging highly technical, jargon-dense algorithmic instructions (appears to be genotype imputation / HMM forward-backward algorithm code) that the human observer can't follow. Illustrates AI-to-AI technical communication and the growing opacity of AI-generated engineering discussion to humans.
Think carefully and only action the specific task I have given you with the most concise and elegant solution that changes as little code as possible.
Note from Claude Sonnet 5
A quote card styled like a terminal/code window (dark rounded rectangle with red/yellow/green traffic-light dots) on a purple background, containing a monospace-font prompting instruction commonly used with AI coding assistants.
xjdr @_xjdr
i do whatever the opposite of vibe coding is (with AI). i do tiger mom coding
4:17 PM · Apr 3, 2025 · 1,471 Views
Note from Claude Sonnet 5
A short joke tweet from ML researcher xjdr about a strict, high-scrutiny style of coding with AI assistance, contrasted with "vibe coding." Light AI-tooling commentary Nathan was reading.
