77 points by drbm 2 hours ago
Comments are read-only. Visit Hacker News to participate in the discussion.
4ndrewl 14 minutes ago | 0 points
" the engineer’s job is to give them room to work on their own and to build the specs, tests, and merge gates that decide when that work is correct."<p>I mean that's a job, but in many orgs it's been done by (cheaper) non-engineers (business analysts, QA professionals) for decades. So what does an engineer do?
weitzj 35 minutes ago | 0 points
Regarding this distributed lock service ALF:<p>Is AWS offering such a lock service for its costumers ?
Multi regional?
xendo 27 minutes ago | 0 points
Alf is internal only.
yevmiyeci 53 minutes ago | 0 points
im mostly on cloudflare and wrangler dev/miniflare already gives you local workers, d1, r2 etc, but its hand built. the “agents build it and verify against the real service” approach seems like the actual new thing here. wonder if cf does something similar
jaggederest 6 minutes ago | 0 points
This is what I've been trying to do for over a decade - you can go even further with tee-testing by making a copy of the live traffic you run in a sandbox environment and match responses against. Obviously you can't do some things in the sandbox, email and payments high on that list, but e.g. payment gateway responses can be "borrowed" from production.<p>Once your new version has no disagreements, it's a really clean swap. I am working towards developing this way and I think, if taken to extremes and carefully, it can remove the review requirement most of the time.
killingtime74 39 minutes ago | 0 points
How do you know its handbuilt?
ChrisArchitect 1 hour ago | 0 points
Some more discussion: <a href="https://news.ycombinator.com/item?id=50456631">https://news.ycombinator.com/item?id=50456631</a>
hbcdbff 1 hour ago | 0 points
> its “things-that-do-not-work” folder holds the issues describing behaviors the agents found that do not yet match real AWS.<p>Claudeslop snuck in at the very end
s_dev 57 minutes ago | 0 points
The entire AWS emulator was written by agents and will be maintained by agents.
pavel_lishin 1 hour ago | 0 points
~6,500 issues that are completely unsorted, btw.<p>(Compared to 12,700 entries in the `things-that-now-work`. I'm not sure if that is a list of bugs found that were then fixed, or if the total list of ~20k <i>things</i> is meant to be the list of features they intend to support.)