korrents
Jon Seager

What Jon Seager thinks about software quality

@jon-seager · 16 positions · On ppll ↗

Software engineer and engineering leader at Canonical, working on Ubuntu; writes about his homelab, Nix and tooling at jnsgr.uk.

Jon Seager did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

4 dated positions, 2026, in their own words. Our reading of what Jon Seager has said — not written or endorsed by them.

4 positions so far — this page is not yet offered to search engines.

  1. Rewrites have long been expensive and risky, and do not often materialise obvious improvements.

    ↗Investing in automated C to Rust translationjnsgr.uk 1st of 3 in this piece

  2. code generation

    Generated code should be treated as untrusted until there is evidence that it preserves the desired behaviour.

    ↗Investing in automated C to Rust translationjnsgr.uk 3rd of 3 in this piece

  3. 5 months earlier
  4. coding agents

    If you care about such constraints (function length, etc.), encode them as lints rather than hoping the agent internalises your preferences.

    ↗Brewlog: Coffee & Agentsjnsgr.uk 2nd of 3 in this piece

  5. I think the key to useful output from these tools is that you remain the driver.

    ↗Brewlog: Coffee & Agentsjnsgr.uk 3rd of 3 in this piece