←back to thread

The rise of async AI programming

(www.braintrust.dev)
123 points mooreds | 1 comments | 11 Sep 25 12:20 UTC | HN request time: 0.21s | source
Show context
sirwhinesalot ◴[11 Sep 25 17:01 UTC] No.45213772[source]▶
Before I read the article I thought this meant programming with "async".

Just call it Agent-based programming or somesuch, otherwise it's really confusing!

replies(4): >>45213794 #>>45213865 #>>45213976 #>>45214510 #
ankrgyl ◴[11 Sep 25 17:09 UTC] No.45213865[source]▶
(Author here) Haha that is a great point. I was trying to come up with a term that described my personal workflow and specifically felt different than vibe coding (because it's geared towards how professional programmers can use agents). Very open to alternative terms!
replies(3): >>45214504 #>>45218492 #>>45219894 #
1. brothrock ◴[12 Sep 25 03:47 UTC] No.45218492[source]▶
This type of coding has been extremely helpful to me in the past few weeks. I’m on parental leave, but also a co-owner of a small company and can’t completely log off.

I can one handed spec out changes, AI does its thing, and then I review and refine it whenever my kid is asleep for 20 minutes. Or if I’m super tired I’m able to explain changes with horrible english and get results. At the same time, I am following a source control and code review process that I’ve used in large teams. I’ve even been leaving comments on PRs where AI contributes and I’m the only dev in the codebase.

I wouldn’t call this vibe coding— however vibe coding could be a subset of this type of work. I think async coding is a good description, but bad because of what it means as a software concept (which is mentioned). Maybe AI-delegation?