Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> The solution to running only e2e tests on affected files has been around long before LLM.

This doesn't work in distributed systems, since changing the behavior of one file that's compiled in one binary can cause a downstream issue in a separate binary that sends a network call to the first. e.g. A programmer makes a behavioral change to binary #1 that falls within defined behavior, but encounters Hyrum's Law because of a valid behavior of binary #2.



That's easy:

- avoid distributed systems at all costs

- if you can't avoid them, never make breaking API changes


Determining breaking API changes is the whole point of tests.


While we're at it, give things good names and don't invalidate caches at the wrong times!


Also always keep your documentation updated and complete.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: