3 ms·
Yes, its easy to run, but I found that re-creating 'production' input parameters annoying. In rails, that might be setting the request state (set current user,
by itake 4y ago
Yes, its easy to run, but I found that re-creating 'production' input parameters annoying. In rails, that might be setting the request state (set current user, gen a jwt tokens, etc.) which is required for debugging views or controller code.
I also found ruby made me worse at leetcode problems, since my default debugging taught me to run the code, instead of think through program state.
- rco8786 4y ago> re-creating 'production' input parameters annoying Just curious, annoying relative to what language/pattern that does it better?
- itake 4y agoWith Ruby, there is more state stored in the classes than more functional languages (e.g. go-lang or python). Setting that state with ruby in rspec tests is annoying since its not always clear what types and mocks you need without running the code. Since golang is typed and uses dependency injection, its very easy to know what inputs you need or mocking out values.
- exikyut 4y agoHuh, that prompts the thought that it could be cool to have some sort of tracing tool that captures all the state changes associated with a particular HTTP request. I wonder how easy that would be to put together?