An extranordinary claim needs a bit more evidence than one datapoint where in his defense maybe he is scared of anyone he doesn't know trying to talk on the street.
The other way might be testing VMs vs agent VMs but that would be slower as to "fork" it would need to run the test again to that point. But wouldn't need agent context.
That + its not always simple to replicate state. A QA agent in the future could run for hours to trigger an edge case that if all actions to get there were theoretically taken again it wouldn't happen.
That can happen via race conditions, edge states, external service bugs.
I wish you were getting replies instead of downvotes. I want to know why people think Bun is preferable here. For cross-platform non-performance-important code, I’ll use Bun all day. Once speed enters the equation, I don’t see why you’d still be using it.
Write down 10 of your TODOs that generate income. As per natural law, it's likely that 1-2 of those TODOs will have 80% of the impact while the other 8-9 will have almost no impact. Now here comes the interesting part. You propably already know the 8-9 tasks that have almost no impact, but as per another law, those are also the easiest tasks (checking mails and such). On that list the TODO that feels like the biggest hassle and you least want to do will likely have the biggest impact. Sit down and just do it. Now, without delay. That already makes you more productive than 98% of your colleagues.
reply