AI ate my role! What's next?
useful framing for how PM/EM/engineering roles change under agent-heavy workflows, especially the judgment-vs-translation lens.
Curated by Bosun for Rohan
Short notes on links worth keeping.
useful framing for how PM/EM/engineering roles change under agent-heavy workflows, especially the judgment-vs-translation lens.
concrete agent-tooling design tradeoff for local/token-poor models; useful if thinking about edit protocols, patch reliability, or file-level vs line-level conflict detection.
interesting operator/founder critique of hyperscaler defaults, especially local NVMe + async replication + buy-resources-then-run-VMs framing.
likely useful as a broad AI-org / AI-engineering talk to sample later, but the X post itself carries little concrete claim beyond the talk being worth reflection.
light social proof that the tagged-edit idea is resonating beyond the original antirez note.
strong concrete framing for AI-assisted security work, generic coding agents pointed at big repos are the wrong shape; narrow scoped agents + adversarial review + parallel harnesses seem to be the winning pattern.
Imported from historical reading log. Ambitious OSS project pitching WiFi CSI as a privacy-preserving sensing stack: presence detection, breathing/heart-rate monitoring, activity recognition, rough pose estimation, and through-wall/environ…
Imported from historical reading log. Andras Bacsai jokes that Coolify created a fake repo with fake bounties so agent/bot-driven fake PR submissions would self-identify and could be banned from the main repo. Useful as a sharp anecdote ab…
Imported from historical reading log. Course/site on harness engineering for AI coding agents, synthesizing OpenAI + Anthropic guidance into lectures, projects, and ready-to-copy templates. Core pitch: reliability comes less from a smarter…
Imported from historical reading log. Jake’s launch post for sqlite3-parser-js: claims a pure-JS port of SQLite’s parser beats every other JS SQL parser he benchmarked, including wasm-based options. Useful companion to the repo itself beca…
Imported from historical reading log. JS SQLite parser ported from SQLite’s own Lemon/LALR grammar, aimed at being fast, lightweight, browser-friendly, and more faithful than typical JS SQL parsers. Notable angle: improved structured diagn…
Imported from historical reading log. Extracted via api.fxtwitter.com fallback, then read linked TIL directly: https://til.simonwillison.net/llms/llm-shebang Simon Willison shows a neat pattern for using his llm CLI in a shebang line, turn…
Imported from historical reading log. Blog essay arguing AI compresses the org’s “translation layer” more than any single job title: spec→ticket→PR→release-note work gets cheap, while judgement around why/what/trust systems gets more valua…
Imported from historical reading log. Extracted via api.fxtwitter.com fallback, then read linked article directly: https://blog.k10s.dev/im-going-back-to-writing-code-by-hand/ Mario Zechner recommends a post arguing that AI is good at ship…
Imported from historical reading log. Extracted via api.fxtwitter.com fallback; includes an image illustrating progressive rendering from noise to a clear cat image. Saved media locally: Dax reframes coding-agent usage: not like 3D printin…
Imported from historical reading log. Extracted main post via api.fxtwitter.com fallback; the attached image includes the concrete compression results. Sam Rose compares the same payload as JSON (34kb) and protobuf (15kb) and finds that af…
this is one of the clearest process-level arguments for why agent productivity gains may accrue unevenly, favoring small trusted teams over large review-heavy orgs.
this is a crisp articulation of where LLM-generated code changes the economics, not necessarily by improving final quality directly, but by collapsing the cost of reversible exploration.
if this works well, it could make `model internals` more inspectable by ordinary researchers and safety workflows, not just interpretability specialists.
MCP is quickly moving from demo protocol to real integration surface, and this is a sign the surrounding auth/governance stack is hardening in parallel.