44 ms·
I think it's maybe related to 2 things, especially for web development. 1. Unless you strictly design functions that are decoupled from any type of UI (such as
by nickjj 6y ago
I think it's maybe related to 2 things, especially for web development.
1. Unless you strictly design functions that are decoupled from any type of UI (such as your back-end "business logic"), it's not straight forward to do REPL driven development on its own.
2. If you're going to go down the path of using the REPL, you might be inclined to do TDD instead because now your efforts are saved to repeatable tests rather than a short lived REPL.
- dgb23 6y agoTDD and REPL driven development are not mutually exclusive.
- Scarbutt 6y agoYes, the problem is too many skip the tests because "they already tested at the REPL".
- Jtsummers 6y agoThe thing those people miss is that "tested in the REPL" means tested once, and tests are there to be rerun many times, basically any time something is changed. You write your first test in the REPL, and then you transfer those tests to a proper test suite so you can reevaluate them all quickly. And because you ran it in the REPL, you also have a way to easily grab what should be the correct value.
- oweqruiowe 6y agoI'm guilty of this :/