Agentic software development hypothesis - Marc's Blog

1 min read Original article ↗

About Me

My name is Marc Brooker. I like to build things that work, and do cool stuff. I like building big things. I also dabble in machining, welding, cooking, and skiing.

I am an engineer at Amazon Web Services (AWS) in Seattle, where I work on agentic AI, especially safety and policy for agentic AI. Before that, I worked on EC2, EBS, databases, serverless, and serverless databases.
All opinions are my own.

Links

My Publications and Videos
@marcbrooker on Mastodon @MarcJBrooker on Twitter

Is this blog written by AI?

Agentic software development hypothesis

This is the quality content you come here for, right?

Agentic Software Development Hypothesis:

  • Weak form: Any coding task for which a complete specification is available will become trivial.
  • Strong form: Any coding task for which a deterministic oracle is available will become trivial.

First objection: Few meaningful tasks have a complete specification. Second objection: Most oracles aren’t deterministic.

  • Strongest form: Any coding task for which a non-adversarial (pythic?) oracle exists will become trivial.