6 ms·
The rise of async AI programming
- datadrivenangel 1y agoI did this early in my career as a product owner with an offshore team in India... Write feedback/specs, send them over at end of day US time. Have a fresh build ready for review by start of business. Worked amazingly when it worked. Really stretched things out when the devs misunderstood us or got confused by our lack of clarity and we had to find time for a call... Also eventually there got to be some gnarly technical debt and things really slowed down.
- mcny 1y agoI think it can only work if the product owner literally owns the product as in has FULL decision making power about what goes or doesn't go etc. it doesn't work when a product manager is a glorified in between guy, dictating the wishes of the CEO through a game of telephone from the management.
- ch4s3 1y ago> it can only work if the product owner literally owns the product as in has FULL decision making power This seems like a fairly rare situation in my experience.
- swiftcoder 1y agoIt's not uncommon in the sort of solo-dev bootstrapped startup that is going wild for AI coding right now though.
- ch4s3 1y agoI'm surprised there aren't more of these bubbling up, I can't name a single company like that.
- jt2190 1y agoYou’ll have to be more specific about what you mean by “product owner”, because that’s a very nebulous job title. For example, how technical is this product owner? Are they assumed to “just know” that they’re asking for an overly complex, expensive technical solution?
- balamatom 1y agoI'd guess they'd be assumed to "just know" to trust the developers working with them on that?
- datadrivenangel 1y agoAgreed. A glorified go between person is rarely going to succeed at delivering something good.
- dboreham 1y agoThose of us who worked in hardware, or are old programmers will find this familiar. Chip/board routing jobs that took days to complete. Product build/test jobs that took hours to run. See also that movie with Johnny Depp where AI takes over the world.
- skeezyboy 1y agoHe says define the problem like its the easy part. If we had full specs, life would be a lot easier.
- arethuza 1y agoThey don't really as once the spec gets detailed enough it becomes so large and unwieldy that nobody with any actual power reads the things. An executive at a large company once told me about something where a spec had been written and reviewed by all relevant stakeholders: "That may be what I asked for, but its not what I want."
- lelanthran 1y agoThis works until you get to the point that your actual programming skills atrophy due to lack of use. Face it, the only reason you can do a decent review is because of years of hard won lessons, not because you have years of reading code without writing any.
- MisterTea 1y agoCoding interview of the future: "Show us how you would prompt this binary sort."
- Graphon1 1y agonot a joke. Also, the future you are referring to is... like... 6 weeks from now.
- joenot443 1y agoMy understanding is it's already here [1] [1] https://news.ycombinator.com/item?id=44723289 https://news.ycombinator.com/item?id=44723289
- brothrock 1y agoI think this is better than many current coding interview methods. Assuming you have an agent setup to not give the interviewee the answer directly. Of course there are times when you need someone extremely skilled at a particular language. But from my experience I would MUCH prefer to see how someone builds out a problem in natural language and have guarantees to its success. I’ve been in too many interviews where candidates trip over syntax, pick the wrong language, or are just not good at memorization and don’t want to look dumb looking things up. I usually prefer paired programming interviews where I cater my assistance to expectations of the position. AI can essentially do that for us.
- Herring 1y agoYeah research says the interview process should match the day to day expectations as closely as possible, even to a trial day/week/month. All these leetcode and tricky puzzles are very low on signal. They don't tell you how a person will do on the job at all, not to mention they're bad for women and minorities.
- lazyfanatic42 1y agoAwful font.
- UncleOxidant 1y agoThat's not the kind of async programming I was expecting.
- stahorn 1y agoI was ready for a deep-dive into things like asyncio in python; where it came from and what problems it promised to solve!
- conorbergin 1y agoRedefining commonly understood phrases to mean something else in your own little world make you look ignorant.
- titzer 1y agoIndeed! Why not just call it "asynchronous software development" or something similar? "asynchronous programming" is a bad choice, partly because it will be un-googleable.
- keybored 1y agoThe intent is more likely clickbait. What I do is is I tell the computer to do something and wait until is done Not that catchy (even in fewer words).
- jmull 1y agoThis vision of AI programming is DOA. The first step is "define the problem clearly". This would be incredibly useful for software development, period. A 10x factor, all by itself. Yet it happens infrequently, or, at best, in significantly limited ways. The main problem, I think, is that it assumes you already know what you want at the start, and, implicitly, that what you want actually makes some real sense. I guess maybe the context is cranking out REST endpoints or some other constrained detail of a larger thing. Then, sure.
- thefourthchime 1y agoI disagree with being detailed, many times I want to AI to think of things, half the time it comes up with something I wouldn't have that I like. The thing I would add is to retry to prompt, don't tell it to fix a mistake. Rewind and change the prompt to tell It not to do that it did.
- athrowaway3z 1y agoI agree there is a lot of value to have it do, what it considers, the obvious thing. It is almost by definition what the average programmer would expect to find, so it's valuable as such. But the moment you want to do something original, you need to keep high-level high-quality documentation somewhere.
- ankrgyl 1y ago(Author here) I can certainly appreciate having an alternate perspective, but I think it's unfair to say it's DOA. I've personally used this workflow for the last 6 months and shipped a lot of features into our product, including the lowest levels of infra all the way to UI code. I definitely think there is a lot to improve. But it works, at least for me :)
- dec0dedab0de 1y agoFiguring out what you want is the hard part about programming. I think that's where AI augmentation will really shine, because it lowers the time between iterations and experiments. That said, this article is basically describing being a product owner.
- bpt3 1y agoIt takes my longer to thoroughly review code I didn't write, especially code written by a junior developer. Why would I choose to slow myself down in the short term and allow my skills to atrophy in the long term (which will also slow me down)?
- webstrand 1y agoI actually enjoy writing code... most of the time. I find myself turning to AI to write code I have an aversion to writing, not as a substitute for my own practice, but to get code that I would not have written in the first place. Like benchmarks, bash scripts, dashboards, unit tests, etc. I can live without these things, but they're nice to have without expending the effort to figure out all the boilerplate necessary for solving very simple problems at their core. Sometimes AI can't get all the way to a solution, but usually it sets up enough of the boilerplate that only the fun part remains, and that's easy enough to do.
- bpt3 1y agoThat sounds reasonable and similar to how I use it. Managing a team of interns isn't fun, and I have no idea why someone who is a competent developer would choose to do that to themselves.
- sarchertech 1y agoI don’t know anything about the competency of the AI boosters online. But among people I’ve worked with whose capabilities I can judge, the competent programmers are not building things like this. Among my own sample size there is a near perfect negative correlation between AI use and competency.
- antimoan 1y agoI think there is a confusion here between Coding and Programming. I think what is described here as "Async Programming" is just programming the way it should be which is different than coding. This is what Leslie Lamport pointed out a while back [1] and recently [2]. According to him programming has 3 stages: 1- Define what task the program should perform 2- Define how the program should do it 3- Writing the code that does it. Most SWEs usually skip to step 3 instead of going through 1 and 2 without giving it much thought, and implement their code iteratively. I think Step 3 also includes testing, review, etc. With AI developers are forced to think about the functionality and the specs of their code to pass it to AI to do the job and can no longer just jump to step 3. For delegating to other devs, the same process is required, senior engineers usually create design docs and pass it to junior engineers. IMO automated verification and code reviews are already part of many developers workflows, so it's nothing new. I get the point of the article though, that there are new requirements for programming and things are different in terms of how folks approach programming. So I do not agree that the method is new or should be called "async", it's the same method with brand new tools. [1] https://www.youtube.com/watch?v=-4Yp3j_jk8Q [2] https://www.youtube.com/watch?v=uyLy7Fu4FB4
- hackingonempty 1y agoSounds great in principle but I have been trained to value individuals and interactions over processes and tools and working software over comprehensive documentation.
- suddenlybananas 1y agoThis kind of workflow really doesn't appeal to me in the slightest. Maybe it works for some people, but it just seems to drain all the pleasure out of programming. For me, at least, solving the little problems are like little satisfying puzzles which makes it easier to maintain motivation.
- techlatest_net 1y ago[dead]
- curtisszmania 1y ago[dead]
- sirwhinesalot 1y agoBefore I read the article I thought this meant programming with "async". Just call it Agent-based programming or somesuch, otherwise it's really confusing!
- SCUSKU 1y agoSame! I was hoping this would have some insights into pitfalls or the like with javascript promises or python async, but alas no such luck.
- ankrgyl 1y ago(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!
- theknarf 1y agoThere is already a term for it! It's called "Ralph coding": https://ghuntley.com/ralph/ https://ghuntley.com/ralph/
- didibus 1y agoI want to understand the distinction you're making against vibe coding. In vibe coding, the developer specifies only functional requirements (what the software must do) and non-functional requirements (the qualities it must have, like performance, scalability, or security). The AI delivers a complete implementation, and the developer reviews it solely against those behaviors and qualities. Any corrections are given again only in terms of requirements, never code, and the cycle repeats until the software aligns. But you're trying to coin a term for the following? In ??? coding, the developer specifies code changes that must be made, such as adding a feature, modifying an existing function, or removing unused logic. The AI delivers the complete set of changes to the codebase, and the developer reviews it at the code level. Any corrections are given again as updates to the code, and the cycle repeats until the code aligns. Did I understand it right? If so, I've most seen the latter be called AI pair-programming or AI-assisted coding. And I'd agree with the other commenters, please DO NOT call it async programming (even if you add async AI it's too confusing).
- lolive 1y agoI am teaching asynchronous programming in typescript to junior developpers. And i find really tricky to tell them that async and await do MAJOR magic behind their back to make their code readable as synchronous code. And then, I need to detail very precisely what "Promise.all()" (and "return") really mean in the context of async/await. Which is something that (I feel) could have been abstracted away during the async/await syntax definition, and make the full magic much more natural.
- uncletaco 1y agoMan are you going to be disappointed when you read the article.
- lolive 1y agoMan, for the first time in HN, I am teased to actually read the article. Update: oh my god, I read the article. And feel completely cheated!!!! Note for my future self: continue to read only the HN comments
- lolive 1y agoTo elaborate a bit, telling them that you should not "aList.foreach(asyncMethod)", but you'd better do "Promise.all(aList.map(asyncMethod))" is NOT very easy for them.
- swid 1y agoAsync/await themselves are not that much magic really, it's a bit of syntactic sugar over promise chains. Of course, understanding promises is its own bag. ChatGPT explanation: https://chatgpt.com/share/68c30421-be3c-8011-8431-8f3385a654ba https://chatgpt.com/share/68c30421-be3c-8011-8431-8f3385a654...
- lolive 1y agoThat reminds me of my Unix guru of the 90s: "man pages ARE easy to read". [spoil: "when you are already an expert of the tool detailled in it"]
- ankrgyl 1y ago(Author here) Hi everyone, thanks for the spirited debate! I think there are some great points in the discussion so far. Some thoughts: * "This didn't work for offshoring, why will it work all of a sudden?" I think there are good lessons to draw from offshoring around problem definition and what-not but the key difference is the iteration speed. Agents allow you to review stuff much faster, and you can look at smaller pieces of incremental work. * "I thought this would be about async primitives in python, etc" Whoops sorry, I can understand how the name is confusing/ambiguous! The use of "async" here refers to the fact that I'm not synchronously looking at an IDE while writing code all the time. * "You can only do this because you used to handwrite code". I don't think this workflow is a replacement for handwriting code. I still love doing that. This workflow just helps me do more.
- datadrivenangel 1y agoI do think that AI will work well compared to the low end of offshoring, where to get good results you need people who could do the work themselves tightly involved. AI will give you slop code faster and cheaper, and that is sometimes enough. The question is how it compares to the medium level of offshoring. Near term I think that at comparable cost ($100s of dollars per week), it'll give faster results at an acceptable tradeoff in quality for most uses. I don't think most companies want to spend thousands of dollars a month on developer tools per developer though... even though they often do.
- ankrgyl 1y agoIt's just a different workflow IMO. AI is effectively real-time, whereas offshoring, no matter the quality, is something you have to do in batches.
- lelanthran 1y agoI think this does not bode well for you; be honest with yourself - if you're making simple mistakes like using the term "Async Programming" to refer to something new, your prompting and/or code reviewing is probably not going all that well. Sure, it can look good now, when there's no legacy, but if you ever move into having to maintain that code you're going to be in a tough spot.
- snozolli 1y agoEffective async programming specs read like technical documentation The thing I like least about software engineering will now become the primary task. It's a sad future for me, but maybe a great one for some different personality type.
- anyg 1y agoOff topic, but I assume the name braintrust comes from Creativity, Inc. Amazing book by Pixar co-founder Edwin Catmull.
- kylereeve 1y agoWhen this bubble finally pops, someone is going to have to clean up all the nonsense AI code out there.
- kordlessagain 1y agoDream on!
- ge96 1y agoIdk if I'm a luddite or what I actually like writing code, it does get tedious I get that when you're making yet another component. I don't feel joy when you just will a bunch of code into existence with words. It's like actively participating in development when typing. Which yeah people use libraries/frameworks/boilerplate. My dream is to not be employed in software and do it for fun (or work on something I actually care about) Even if I wrote some piece of crap, it is my piece of crap
- krapp 1y agoSome people will probably call you a luddite, but don't listen to them. There's nothing wrong with taking joy in the craft, with learning and exploring and creating. That's what hacker culture used to be about. Unfortunately, you won't be able to get a job in software with anything but AI skills, since humans no longer write software in the industry. People will look at you the way they used to look at anyone who wrote their own HTML or Javascript without frameworks and Typescript, like you must drive your car to work with your feet.
- ge96 1y agoIt was funny I was handed this project to work on and I skimmed the ReadMe, there were a lot of readmes in the code like how to use pipenv or whatever basic stuff... at first I was like "nice job with the docs" but then I later realized it was a vibe coded project I felt like I was owned. It's funny Also funny how much time was wasted since it had random code in it that was not removed (not working old code vs. current working new code) that's not to blame on the AI part but yeah. I have a job now in the industry it's funny I work with AI eg. AWS Bedrock/Knowledgebases/Agents... RAG/LLM AI. The AI I want to work with is vision/ML (robotics) but don't have the background for that (I do it as a hobby instead). I'm feeling the effect of vibe coding now, where the 2nd leader in our team was only recently a developer but uses ChatGPT/windsurf to code for him which enables him to work on random topics like OpenSearch one day Airflow the next... idk I get I'm the one being left behind by not doing it too but I also want to really learn/understand something. You can do that with an AI-assisted thing but yeah... idk I don't want to that's what I'm saying, I will get out eventually once I've saved enough money. My learning process for a while has been watching YT crash courses/reading the docs/finding articles... The project I mentioned above there was literally a prompt in the repo "Write me an event-driven app with this architecture..." The 2nd leader I mentioned above is a code at work/not at home type of person which is fine but yeah. I'm not that person, I like to actually code/make stuff outside of work. It's not just about getting a task done/shipping some code for me. But I guess that's what a business is, churn out something. Idk there's some validity there isn't there... "I've been a developer for 10 years, then a guy with 2 years comes in vibe coding stuff" is the leader. Which I'm past it, I don't do office politics anymore, I've got a six-fig job, no need to climb, I'm coasting. Debt is really the only problem I have.
- keybored 1y agoOh, async? > This version of "async programming" is different from the classic definition. It's about how developers approach building software. Oh async=you wait until it is done. How interesting.
- Graphon1 1y agoI don't know why we need a term like "Async AI programming." this is literally what you would do if you were a Tech Lead directing a team of other developers. You define what you want and hand it to one of your devs. This is just being a TL. the agent is an assistant or a member of the team. I don't know why we need to call it "Async AI programming", unless we want to shy away from or obscure the idea that the agent is actually performing the job a human used to perform.
- septune 1y agoi was reading this article while my laptop was auto-vscoding
- gabrieledarrigo 1y ago> My workflow has changed since adopting async programming. I now work on four or five tasks simultaneously: one complex problem synchronously and three or four in the background. Someone, please, try to convince me why this is a positive thing.
- Sparkle-san 1y agoPerhaps the background tasks are ones with obvious solutions? I use Claude code to write boilerplate terraform for me as I know what it should look like and I often don't want to write it myself as it is not novel or exciting. I could see the argument that I batch a couple of these out to AI, focus on something more complicated, and then come back later to essentially code review them or make necessary adjustments.
- zeroonetwothree 1y agoThe article felt too rosy as I read it and then it got to the part where it’s just an ad for the author’s company.
- nasmorn 1y agoWhere are the agents running? Locally all at once or hosted somewhere