Hacker News Reader

Actually that's exactly how it is done in highly structured "clean room" software projects. If you fixed the "bug" in your software, then the process team couldn't fix the "bug" in the process that resulted in the bug in the software.

View on HN

Could you give me an example of such a project with this kind of restriction?

Space industry software is siloed in exactly this way. I write code, someone else unit tests it (C), someone else entirely writes integration tests (Java), then someone else writes a final integration test (Java).

It's horrendously redundant and wouldn't be applicable to most software, but it does work well; when bugs are picked up by the third or fourth layer of testers, which happens from time to time.

Neat. As long as there is reliable communication throughout the different teams, I guess this kind of thing makes sense for space tech and other highly critical software.

Is this based on seniority, as in the new guys have to write the tests? That way you would at least have some experience with how to code in an easily testable fashion.

Reply on news.ycombinator.com