惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

大猫的无限游戏
大猫的无限游戏
博客园 - 【当耐特】
Cloudbric
Cloudbric
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Attack and Defense Labs
Attack and Defense Labs
爱范儿
爱范儿
The Cloudflare Blog
腾讯CDC
Security Archives - TechRepublic
Security Archives - TechRepublic
TaoSecurity Blog
TaoSecurity Blog
云风的 BLOG
云风的 BLOG
Recent Announcements
Recent Announcements
C
Check Point Blog
Schneier on Security
Schneier on Security
S
Schneier on Security
J
Java Code Geeks
B
Blog RSS Feed
Cisco Talos Blog
Cisco Talos Blog
Vercel News
Vercel News
Stack Overflow Blog
Stack Overflow Blog
博客园_首页
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
A
About on SuperTechFans
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Google DeepMind News
Google DeepMind News
阮一峰的网络日志
阮一峰的网络日志
罗磊的独立博客
A
Arctic Wolf
S
Secure Thoughts
P
Palo Alto Networks Blog
The Last Watchdog
The Last Watchdog
SecWiki News
SecWiki News
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
博客园 - 三生石上(FineUI控件)
D
Darknet – Hacking Tools, Hacker News & Cyber Security
量子位
U
Unit 42
I
InfoQ
D
DataBreaches.Net
P
Privacy International News Feed
T
Troy Hunt's Blog
博客园 - 叶小钗
T
Threatpost
博客园 - Franky
K
Kaspersky official blog
Hugging Face - Blog
Hugging Face - Blog
IT之家
IT之家
www.infosecurity-magazine.com
www.infosecurity-magazine.com
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
C
Cisco Blogs

Lobsters

CIFSwitch: a non-universal Linux local root vulnerability RIPE NCC session fixation: poaching logins with an Atlas probe GNOME 2.20 but its Web Components Agentic Search for Context Engineering – Leonie Monigatti Garnix is shutting down [not OC] akashina.tngl.sh/jjc Concerning Emacs (and Jazz) Nitpicking the shell history scene in ‘Tron: Legacy’ What's cooking on SourceHut? Q2 2026 The tenth OpenPGP email summit Package managers that package package managers Clojure on Fennel part three: parsing WordPress at 23 Finding Miscompiles for Fun, Not Profit GitHub - creusot-rs/creusot: Creusot helps you prove your Rust code is correct. Announcing Rust 1.96.0 | Rust Blog A Love Letter to Neovim sqlite AGENTS.md Am I a Bad Friend? CSS vs. JavaScript • Josh W. Comeau Erlang Ecosystem Foundation - Supporting the BEAM community A brief note about slot access cost in Common Lisp Keyboard latency probe Rethinking the GNOME clipboard issues Back to the Building Blocks’ Building Blocks Tech Notes: Theseus: translating win32 to wasm Fast is better than slow Content-addressed Rust builds (or, what kache actually caches) Intent to Prototype: Embedding API Canada’s Bill C-22 and the security cost of collecting more data 5 PostgreSQL locking behaviors that trip people up okmij.org Stop advertising in your commits! | AksDev GitHub - mplsllc/macsurf: A modern web browser for Classic Mac OS 9 PowerPC. Real CSS3, ES5 JavaScript, native HTTPS — built with CodeWarrior on the Carbon API. Introducing DoomBench - Can Your Data Stack Run DOOM? What are some of your favourite developer tools? Building a Scalable Ingestion Pipeline with Temporal (Part 1) Converting shallow Git bundles into normal repositories Are you a member of any professional associations? What is a harmonic? An interactive comic about additive synthesis How Virtual Tables Work in the Itanium C++ ABI Using SwiftUI to Build a Mac-assed App in 2026 Rust (and Slint) on a jailbroken Kindle. ~jack/lambda-on-lambda - Serverless Haskell on AWS - sourcehut git Human proof for FOSS contributions Extremely simple internet radio controlled via IRC Announcing BABLR Splitting Konsole views from Helix to run tools | AksDev GitHub - yugr/rust-slides Serving files over HTTP three ways: synchronous, epoll, and io_uring update docs with information about building with build.py (#979) · astral-sh/python-build-standalone@c9c40c5 A Simple Makefile Tutorial On C extensions, portability, and alternative compilers Switching to Colemak | Pedro Alves Just How Bad Was The Intel IAPX432? Nix's Substituter List Is Not a Routing Table Accelerating copy_if using SIMD Lambda on Lambda: Serverless Haskell on AWS | Blog Announcing feed-repeat v1.0 Scaling Akvorado BMP RIB with sharding EYG news: A host of CLI improvements, new guides and new effects The social contract of writing JS Crossword C array types are weird; and related topics Flatpak will depend on systemd – OSnews Migrating from Go to Rust | corrode Rust Consulting A portentous reunion Vivado Licensing Options How my minimal, memory-safe Go rsync steers clear of vulnerabilities the entropy layer of a wavelet codec, on its own GitHub - nferhat/fht-compositor: A dynamic tiling Wayland compositor. Debian SE Linux and PinTheft Does bulk memmove speed up std::remove_if? (No.) 声明式部分更新 | Blog | Chrome for Developers Fully in-browser container builds Dianne Skoll's Web Site - Remind The Architecture of Open Source Applications (Volume 1)Berkeley DB Pardon MIE? - ironPeak Blog “Long-Term Support” doesn’t mean what you think Jira IS Turing-Complete May I recommend thinking of Emacs as your Fortress of Solitude hershey Floodgap Gopher-HTTP gateway gopher://thelambdalab.xyz/1cuneiforth/ HP QuickWeb, Singular And Pointless That one time I used Go panics for flow control A new suite of modern tools coming for editing and publishing RFCs From the Tabletop… The Digital Antiquarian Building a Host-Tuned GCC to Make GCC Compile Faster Are we self-sovereign PKI yet? Claw Patrol: an open-source security firewall for agents | Deno Revised^7 Report on Scheme, Large: Procedural Fascicle Draft is now public A Network Allow-List Won't Stop Exfiltration — André Graf From AFSK to Goertzel – µArt.cz Software For My New Home Server Introducing Neptune: Direct3D virtualization for QEMU AI Agent Bankrupted Their Operator While Trying to Scan DN42 - Lan Tian @ Blog mimalloc: A new, high-performance, scalable memory allocator for the modern era Making wl_shm fast The Soul of Maintaining a New Machine - Third Draft | Books in Progress What is Git made of?
The solution might be cancelling my AI subscription
dmw_ng · 2026-05-31 · via Lobsters

I am trying to think of a list of all the wonderful things I've built with AI:

  • a speech recognition system in Rust
  • an email archive rendering + quote collapsing tool
  • a Jellyfin desktop clone with GStreamer and Qt Quick
  • an Invidious clone in Python and yt-dlp
  • a faithful Windows 95 notepad.exe clone in FLTK ported from the Wine sources
  • a machine vision thing to count traffic flows from public street cameras in OpenCV
  • a Claude UI clone in Python or Rust I think, I don't even remember
  • a regional news site i never meant to build that is actually getting traffic, Python/Flask
  • a 3D car game built on the protocol for an existing multiplayer game in Three.js
  • an investment backtester in Python
  • an HTML clone of the Lightroom UI, marvelled at the result then never made the backend
  • a Markdown viewer in Qt or GTK or something else, I can't even remember
  • a replacement world clock widget for my laptop desktop environment in GTK and C
  • a JavaScript network synchronised audio playback thing
  • a Rust client for a Chinese IP camera reversed from its Android app
  • a sizeable SaaS in Rust
  • maybe 50 other projects I've already deleted

Except for the SaaS, almost none of this is useful and I don't want to maintain any of it. I accidentally run a news outlet which is surely a liability. Sure, it has helped me "learn AI tooling" and I use many of these tools, but I didn't need them. I can't afford to maintain any of them, not in terms of time, commitment, belief, attention or willingness to spend on tokens.

I didn't mean to build most of these things. Usually the Claude session started with something like write a quick script for X, and one hour later the result is not a quick script for X, nor in the usual case is my problem solved, whatever the original itch happened to be.

Attention is all you need

On that last point, this technology is horrific for attention. It's a thermonuclear ADHD amplifier and I have seen the same effect in every single one of my adult friends. Folk running 3 screens simultaneously working on totally unrelated "projects" they have little hope of maintaining, and such little commitment to the outcome that the time is obviously wasted.

In recent times, at least once per month someone sends a screenshot for an awesome tool they are working on. I'm like whoa, that's really something and the sender is obviously proud and enthusiastic. I try not to ask, but am always thinking and where will you market it?, because when the question is asked of an engineer, the answer is unchanged since before LLMs existed.

I recently interviewed and when the topic of AI usage came up, the host answered something like oh we're quite light on it, everyone has up to 5 rooms where they manage their agents and I immediately felt a tightness in my stomach.

I had a vague sense of the effect a few months into using Claude. Later I reduced my subscription to Pro in the belief a quota restriction would mitigate excessive use. Then Claude went through a bad service period and I moved to Codex. Codex's CLI is much nicer than Claude's and noticeably faster. And usage started creeping back up.

The technology, when honed, is genuinely amazing. Ask it to zero shot a parser for an esoteric grammar implemented in an esoteric language with full tests and it's done. The tooling as it exists today promotes absolutely nothing like the focus required to apply it judiciously.

Almost every vendor and every tool intends to do exactly the opposite: more usage, more tokens, more output. Ask a simple yes/no question of ChatGPT and you can clearly see that it is hard-wired to include a relevant follow-up question to promote excessive interaction.

Slopping out a 10,000 LOC untested Python/JS mess in 5 minutes helps nobody. The thought of this happening in every commercial environment simultaneously is horrifying.

Friction = focus, focus = product

One of my early AI experiments, exploring AI as a lens in Marshall McLuhan-like thinking, was to connect speech recognition to a pipeline that generated blog posts on the other side, in the belief it would encourage me to capture my thoughts. All I needed was to press the voice note button in a Telegram channel, and out pops an Opus-formatted post.

The output was unbridled garbage. Because the effort was removed, so was the commitment, and with the commitment the focus, and with the focus any meaningful product at all. Quality writing is not conversational English simply cast through a lens: conversational English is low-bit rate noise, quality writing attempts to capture high bit rate information with better formed concepts, and this should have been obvious before I began.

I looked at repurposing the pipeline to capture private notes, but I have no need for private notes. It subverts the natural process of noise being forgotten. It is just more excess tool use.

Following from this, for as long as quality matters, I believe handwriting can never be obsolete.


It feels like we're heading towards crisis, and I doubt the answer is "better models" or "better tooling". Cal Newport relates this to pseudo-productivity:

The speaker argues that digital productivity tools, including AI and email, often create a “digital productivity paradox”: they make individual tasks faster or easier, but they can leave knowledge workers busier, more distracted, and less productive overall. He cites research showing that AI users spent much more time in email, messaging, chat, and business-management tools, while spending less time in focused, uninterrupted work. His central claim is that tools designed to reduce friction often increase the volume of shallow tasks and context switching, which weakens deep work and high-value output.

He explains that this happens because knowledge work often relies on “pseudo productivity,” where visible busyness is treated as a proxy for real value. Digital tools reinforce this by making people look active: sending more messages, producing more drafts, attending more meetings, and generating more work artifacts. To avoid the trap, he recommends measuring real outcomes, identifying the true bottlenecks in one’s work, and separating deep work from shallow work so that digital tools support meaningful progress instead of consuming attention.

-- 🤖

These experiences have opened a new perception of all tool use, because beneath it all this is not about faster development = more apps or faster email = more communication being a desirable goal. Generically, it's about a unit time of life and how it is spent meaningfully.

I have no idea how to manage AI at present except by curtailing use, because a tool producing a cheap reward with minimal input and no friction can only be a liability, and achieving that realisation is probably the only real contribution of AI to date.


David Wilson · dw@hmmz.org · Sun 31 May 14:31:04 2026
Minimum viable capitalisation · Wed 3 Jun 20:41:36 2026