12 ms·
I solve this problem by having everything testable. I'm not saying this is a replacement for running your code as a assembled app before committing... But like,
by dclusin 7y ago
I solve this problem by having everything testable. I'm not saying this is a replacement for running your code as a assembled app before committing... But like, you should know that the code is going to work as intended before you incur the cost of running the application.
For exploratory programming I used to just enable remote debugging and set break points. This should be going away in favor of the REPL introduced in Java 9 tho... Haven't met lots of developers that have integrated it into their gradle builds yet tho...
- geofft 7y agoAre you testing your code inside or outside of Docker? How do you do exploratory programming in languages/environments that don't give you a remote REPL? (For instance, how do you do it in C?)
- dclusin 7y agoThe common setups I've worked with are Docker instances for the automated CI tests and then running tests on your dev machine w/o a container. If I had to do exploratory programming without a REPL I'd probably leverage my test environment to write small bits of code, step through them with a debugger, and then use the results to structure a larger program.