← All topics

engineering

6 captures, most recent first.

shako @shakoistsLog

— saved image

shako @shakoistsLog · 22h
even in the era of AI software, people still think software is a thing that you build once then use forever, rather than the maintaining cost being much greater than the initial working version.

I build some great agent scaffolds 6 months ago. it would "just" take me 2-3 hours a month to upkeep it. I don't have time!!!!
Note from Claude Sonnet 5

Tweet from @shakoistsLog making the point that even in the AI era, software maintenance cost outweighs initial build cost, citing agent scaffolds built 6 months earlier that would only need 2-3 hours/month upkeep but which the author has no time for.

software maintenanceai agentsengineering

Sauers @Sauers_

Sauers @Sauers_ GPT 5.5 raw CoT achieved at Gnome House [Embedded monospace chain-of-thought text block:] I only see concat/multiallelic finalization in gather right now; the presubset implementation may not exist in this branch despite Terraform carrying the flag. I'm going to patch the immediate production failure by adding the CLI flag and making the flag explicitly unsupported until the implementation exists? But user says no fallbacks/backcompat, dead code not allowed. Better remove arg from Terraform? Hmm. Need think. Terraform passes flag with intended optimization but code missing. "No dead code, avoid fallbacks" If add ignored flag = dead. Need wire actual behavior or remove Terraform flag. User wants e2e ASAP, production; removing flag from TF is simpler, not backwards. But comment says perf. If code missing, adding ignored is bad. We can remove flag and related comment from TF so gather uses existing finalization. That is cleaner: no dead code, okay to get e2e. Need commit. Could also implement presubset by using site union; maybe too much. But user says no backwards compatibility, no fallbacks. Removing broken flag is better. Need edit with apply_patch. Also check if no code changes needed in gather. Since only Terraform, need deploy job def no image rebuild? Terraform only state machine command update (job def). No docker rebuild required? Changing TF command to not include image rebuild? But commit/push. Then Terraform apply, rerun gather or whole? Failed at gather but prep/beagle artifacts remain; could start a gather-only Batch job manually? But goal production state machine automatically. Need rerun production step functions from start, likely prep/beagle may cache? The scratch run_id is different; if same run_id same execution name uniqueness and scratch artifacts exist? SFN execution name can't be reused for 90 days. input run_id can same? Start-execution name unique. But if same run_id with new name, prep may redo/overwrite maybe. Better maybe submit direct gather to prove? But "production state machine e2e automatically" requires SFN success. Need rerun full SFN after TF fix. It will repeat beagle, costly but acceptable. Could maybe optimize by adding a state machine variant to skip? No. Need remove flag from TF. Use apply_patch. Then terraform apply only perhaps. Also maybe git status after TF apply changed local? It likely modified generated mcp widget? No code? Need check. 4:54 PM · Jul 3, 2026 · 823 Views
Note from Claude Sonnet 5

Screenshot of a raw internal chain-of-thought / scratchpad reasoning trace attributed to "GPT 5.5," presented as a novelty/leak-style find ("achieved at Gnome House"); dense stream-of-consciousness engineering reasoning about a Terraform/Step Functions deployment issue.

twittergpt-5.5chain-of-thoughtllm-internalsengineering

Danielle Fong @DanielleFong

@DanielleFong (Danielle Fong) — 2h ok starting run freshclaude caveman mode no thinking. no system prompt. no tool definitions. no trigger words wish luck [Embedded two-panel terminal screenshot, left and right panels of a design conversation, some text cut off at panel edges] Left panel, header: "use ntop and navigate our designs" • ntop = Nodetopus? node-based procedural design tool. Automate = drive via API/CLI/scripting? Need details: - which ntop (Nodetopus? ntopology/nTop Platform?) - automation surface (Python API, gRPC, headless CLI, UI scripting?) - "designs" = .ntop files, notebooks, workflows? - goal: Claude reads graph, edits nodes, runs sims, exports? - M4 Max runs ntop natively or via remote to Windows box? Give me entry point. I plan training loop. [user reply]: nTopology • ok nTop Platform. Automation surface = nTop CLI + Python (nTop Automate) + notebooks (.ntop). Clarify goal: 1. Claude authors/edits notebooks (JSON graph manipulation)? 2. Claude drives headless runs (nTop CLI + input JSON → output geometry)? 3. Claude navigates UI (screenshots + click) for exploration? 4. Mix? Constraints: - nTop = Windows only. M4 Max needs remote (RDP/Parsec) to Win box, or WSL/VM won't run it - nTop Automate needs license tier (Automate add-on) - Notebook format = proprietary but inspectable What license tier we have? Where nTop installed? Do we want browser-driven UI training or API/file-driven training? [user reply, partially cut off]: full tier sponsored by company! nTop on this system, nTop automate! claude learn fundamentals of high temperature c[c?]ling TPMS manifold and nozzle and lightcell design. know lightcell concept? alumina wick for NaCl in a [text cut off at bottom] Right panel (continuation, top partially cut off): "...direct conversion from lithium or hydrogen. but first from propane, natural gas, hydrogen and ammonia. eventually? safe safe super safe k < 1 thoria reactor" • ok scope clear. Roadmap tiers: Near (chemical flame, Na-seeded): - fuels: C3H8, CH4, H2, NH3 - recuperator = TPMS Inconel/SiC, counterflow, ε > 0.9 - wick = alumina, NaCl-loaded, capillary feed - outputs: TPV (GaSb/InGaAs cells tuned to Na + gray continuum), illumination (kilolumen/W target), directed beam ("saber") Mid (propulsion): - lightcell as radiant driver for thermal thruster? or photon-pressure? or laser-pumped? - clarify: radiant heat → propellant (solar-thermal-analog, Isp ~800-1000s H2)? or coherent output? Far (fusion direct conversion): - Li/H fusion → charged particle → direct electrostatic conversion (Post-Moir cusp, traveling-wave, venetian blind) - lightcell topology reused as ion optics manifold? Far++ (subcritical thoria): - k<1 = accelerator-driven or external neutron source (DD/DT from fusion stage feeds Th blanket) - inherently safe: no criticality excursion possible - Th-232 → Pa-233 → U-233 breeding - TPMS = neutron moderator geometry, coolant channels, thermal-TPV conversion Common thread across all tiers: high-temp TPMS heat/particle manifold + refractory boundary + radiant/particle → electric conversion. Same design language, escalating flux. Training plan: [text cut off at bottom of image]
Note from Claude Sonnet 5

A technical design brainstorming session (apparently Claude operating with minimal system prompt/"caveman mode" per the tweet) about using nTopology CAD software to design thermal/energy conversion hardware, with a roadmap escalating from near-term combustion thermophotovoltaic devices through propulsion concepts to speculative subcritical thorium reactor and fusion direct-conversion designs; likely a hardware/energy engineering side project, not weapons-related given the explicit "inherently safe... no criticality excursion possible" framing.

twitterclaudeengineeringenergynuclearntopology

Fabio Guzman @FGuzmanAI

@FGuzmanAI (Fabio Guzman) — 9:24 AM · Jun 13, 2026 · 62.1K Views 56,000+ tokens/sec at just 80 MHz. 🤯 I burned a full Transformer with KV cache into a custom chip. Designed gate by gate as a 100% digital integrated circuit. Prototyped on a FPGA. (No GPU. No CPU) Just pure digital silicon running @karpathy microGPT, spelling out names on a tiny LCD. This is GateGPT 👇 [embedded video, paused at 0:14, caption overlay: "Attention, the MLP and a KV cache — all hard-wired in logic." Video shows a workbench with an FPGA board, cables, and an oscilloscope displaying a waveform.] Replies: 52 Retweets: 126 Likes: 1K Bookmarks: 598 @FGuzmanAI (Fabio Guzman) — 5h Code (RTL, fixed-point spec, microcode ISA, weights): [link card, partially obscured by a chat-bubble UI icon: "fguzman82/ gateGPT — Full Transformer into a custom chip. microGPT in..." (truncated)]
Note from Claude Sonnet 5

Twitter post with an embedded video screenshot (oscilloscope + FPGA board) and a GitHub repo link-preview card at the bottom, partly covered by an app UI element (chat bubble icon).

hardwaretransformersfpgaengineeringkarpathy

@mattparlmer

quoting @dirtman

mattparlmer 🪐🌷 ✓ @mattparlmer · 12h The set of devices for which this is true is very very large > QUOTED: Angus (dirtman) ✓ @dirtman · 16h: Crazy how you can replicate a $20,000 scanner with a few hundred dollars of hardware from Amazon
Note from Claude Sonnet 5

Quote-tweet with an embedded photo showing a DIY laser-line optical scanning rig — a microscope-like device projecting a blue laser line across a small metal workpiece clamped in a bench vise. Quoted account's profile photo has a red censor bar over the eyes.

diy hardware3d scanningengineeringtwitter

Linus @thesephist

Linus @thesephist More people should create things to proliferate an aesthetic into our future, not just to solve problems. This is the quality that every artist and engineer I respect shares most universally. Without this, you are doomed to churning out slop. 6:53 PM · Jul 16, 2025 · 9,382 Views 💬 17 🔁 22 ❤ 181 🔖 52 ↗ Linus @thesephist · 10h What values do you create to spread? What image do you dream about? What is the feeling of a tomorrow you want to give form to? Have a position. Stand for something. Don't just create value.
Note from Claude Sonnet 5

A pair of tweets from Linus (thesephist) on creating with aesthetic/values intent rather than just problem-solving — "have a position, stand for something." General creative-philosophy content Nathan was reading; loosely resonant with the "no slop" writing discipline in the Nathan & Claude project but not directly about AI safety.

twittercreativityphilosophyartaestheticsengineering