proomt

Search

Search posts, papers, and topics

All posts

Freek Van der Herten1 min readintro

Amped up

Summary

The post highlights Sebastian’s shift to using Amp as his primary AI coding harness, emphasizing improved user experience over model churn, and mentions AGENTS.md tweaks that cut down unnecessary verification during everyday coding.

  • Amp is now the author’s default AI coding harness because its UX feels smoother than chasing model updates.
  • Adjustments in AGENTS.md reduce over‑eager verification steps, making day‑to‑day coding faster.
  • The summary links to the original write‑up but provides no implementation specifics.

Engineers evaluating AI coding assistants should note that UX and verification noise can impact productivity more than raw model performance.

3/10

Related reading

  1. From Individual Experiments to a Shared AI Practice: How Avant Scaled AI-Assisted Engineering

    Avant replaced many personal AI‑assistant setups with a single, organization‑wide Claude Code configuration that embeds the company’s coding standards, project‑tracking links, and documentation. Treated as an internal product, the setup is versioned, owned by delivery engineers, and iteratively improved. The shared tool speeds routine tasks (scaffolding, tests, migrations, docs) and enforces cons…

    Moove-itqubika.com2 min
  2. Towards Self-Driving Codebases

    The post argues that AI agents could eventually handle low‑level engineering tasks—bug fixing, debugging, UI consistency, growth experiments—if the dev toolchain is made “agent‑legible”. It outlines missing primitives (global memory, code‑base rot prevention, better dev environments) and proposes a bootstrapping process to measure and improve a repo’s “agent readiness”. The piece is largely specu…

    Hacker News front pagedetail.dev9 minHN12099