← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 10
  1. A retrospective on productivity and (lack?) of quality with coding agents

    On one end of the spectrum, people are achieving tremendous feats of engineering, such as the massive rewrite of Bun from Zig to Rust.

  2. Rules of thumb for harness engineering

    This blog post is for folks working on harness engineering.

  3. From AI Agent Prototype to Product: Lessons from Building AWS DevOps Agent

    This article was originally published on the AWS DevOps Blog.

  4. Leave integration choices to agent builders

    If you’re building an agentic product, especially in a large tech company, you’ll likely need to integrate with multiple partner teams that offer unique context or actions that enhance your agent’s performance.

  5. Experimentation over capabilities

    In traditional software engineering, we create customer value by working on small, focused features delivered frequently.

  6. On promotion and growth beyond senior

    As I progressed from a junior to senior software engineer within Amazon, I came to view leveling up as a function of wisdom - f(wisdom) - where as your applied or practical knowledge increased you were rewarded with a promotion.

  7. Goodput degradation in rate-limited systems

    In this post, we’ll explore how “goodput” (the rate of useful, successful work completed) degrades under increasing load, particularly in multi-step workflows that depend on rate-limited services.

  8. Fighting against duplication

    At large companies like Amazon, it’s inevitable that multiple independent teams will attempt to solve the same, or closely related, problems.

  9. Sweating the small stuff

    At Amazon, we refer to any usability frictions or, more broadly, small product issues as paper cuts.

  10. Persuasion through collaboration

    The goal of this blog post is to enumerate techniques, adapted from Ward Farnsworth’s The Socratic Method [1] and Adam Grant’s Think Again [2], for effective feedback while reviewing technical writings such as a RFCs or PR-FAQs.