It’s funny, but there has long been a paradigm in programming called test-driven development or TDD. The idea is that you have a small number of experienced developers who write a suite of tests that an application has to pass, and then you let an army of newbies write whatever the hell they feel like writing and if their code passes the tests it goes into the application (somewhat snarky summary but not entirely). In my experience it does not produce solid applications but a large fraction of the programming world swears by it. I’ve always thought that the construction analog of TDD would be letting a bunch of inexperienced workers build houses and then the experienced contractors drive around in bulldozers knocking down anything that happens to not be built well enough.
It’s funny, but there has long been a paradigm in programming called test-driven development or TDD. The idea is that you have a small number of experienced developers who write a suite of tests that an application has to pass, and then you let an army of newbies write whatever the hell they feel like writing and if their code passes the tests it goes into the application (somewhat snarky summary but not entirely). In my experience it does not produce solid applications but a large fraction of the programming world swears by it. I’ve always thought that the construction analog of TDD would be letting a bunch of inexperienced workers build houses and then the experienced contractors drive around in bulldozers knocking down anything that happens to not be built well enough.