proomt

Search

Search posts, papers, and topics

All posts

Simon Willison1 min readintro

Note on 18th September 2026

Summary

This entry is a brief, sponsored blurb that offers a vague opinion on using LLMs for security scanning, without any concrete data or analysis. It links to other recent articles but adds no substantive content of its own.

  • The post is a sponsored note promoting Teleport’s LLM‑based codebase analysis, without presenting any results.
  • It only asserts that "quality > quantity" for finding security bugs, but provides no evidence or details.
2/10

Related reading

  1. How to Write with an LLM

    The post proposes a two‑rule workflow for using LLMs as copy‑editors rather than ghostwriters: never adopt a phrase the model suggests, and block its encouragement feedback. It then shows how to automate iterative copy‑editing with a small Python/HTMX/Tailwind app and a set of concrete prompts.

    Hacker News front pagesockpuppet.org6 minHN712401
  2. llm-keys-ui 0.1

    Simon Willison released llm-keys-ui 0.1, a tiny web UI that lets you store LLM API keys on a remote machine and retrieve them via the llm CLI, avoiding pasting keys into chat sessions. It runs with a single uvx command and exposes local network URLs for access.

    Simon Willisonsimonwillison.net1 minrelease
  3. Why I'm still bearish on LLMs after Navier-Stokes

    The author argues that despite headline successes (e.g., Navier‑Stokes proof, security exploits), current frontier LLMs still require heavy human oversight and rigorous specifications that are costly to produce. Reward‑hacking, narrow generalization, and the need for domain‑expert spec writing limit autonomous deployment to only a few niche domains (high‑failure‑cost work, tightly defined tasks,…

    Hacker News front pagedank.systems5 minHN487644lobste.rs49
  4. How To Write With An LLM

    Simon Willison argues that LLMs should be used as copyeditors, not as writers, and proposes a strict rule never to reuse any phrase they suggest. He shares a prompt for building a personal LLM proofreading tool.

    Simon Willisonsimonwillison.net1 min