Skip to main content

Command Palette

Search for a command to run...

Power-Up #7: Let AI Research Your Code While You Sleep

Updated
β€’2 min read
Power-Up #7: Let AI Research Your Code While You Sleep
D

Hi πŸ‘‹, I'm Dung Huynh Duc A passionate engineer from Singapore

πŸ”­ I’m currently working in AirCarbon

πŸ‘¨β€πŸ’» All of my projects are available at https://productsway.com

πŸ“ I regularly write articles on https://productsway.com

πŸ“« How to reach me dung@productsway.com

πŸ“Ή I often publish my video every Sunday on IT Man Channel

In the previous Power-Up posts, I've explored AI coding assistants, AI workflows, agent-based development, and AI launchers.

This week, I want to talk about something that feels like the next step: autoresearch.

The idea comes from Andrej Karpathy's autoresearch project and has recently been brought to Pi through pi-autoresearch.

Instead of asking AI to generate code, we ask AI to improve a measurable outcome.

For example:

  • Reduce startup time

  • Improve benchmark scores

  • Reduce memory usage

  • Increase test coverage

  • Reduce bundle size

The workflow is surprisingly simple:

  1. Give the agent a goal

  2. Let it propose a change

  3. Run tests and benchmarks

  4. Measure the result

  5. Keep improvements

  6. Revert regressions

  7. Repeat

The key difference is that the agent is no longer optimizing for "writing code."

It is optimizing for outcomes.

Traditional AI coding:

Goal β†’ Prompt β†’ Code

Autoresearch:

Goal β†’ Experiment β†’ Measure β†’ Improve β†’ Repeat

This is important because software engineering is fundamentally an optimization problem.

The best solution is rarely obvious from a single prompt.

Human engineers already work this way:

  • Form a hypothesis

  • Make a change

  • Run tests

  • Analyze results

  • Iterate

Autoresearch simply automates that loop.

I recently tested pi-autoresearch on one of my projects. What impressed me wasn't the code generation itself.

It was the process.

The agent created experiments, validated assumptions, measured results, and produced a pull request with supporting evidence.

That feels much closer to having a junior performance engineer than a code generator.

Why this matters:

  • Less prompt engineering

  • More measurable improvements

  • Discover non-obvious optimizations

  • Fully reproducible experiments

  • Works while you focus on other tasks

I don't think autoresearch will replace developers.

But I do think it points toward a future where AI agents spend more time experimenting and less time waiting for instructions.

What would you ask an AI agent to optimize in your codebase?

#ITMan #AI

14 views