3 ms·
I have no need to do any of this locally outside of debugging when I can commit/push early/often and get the same feedback from my CI/CD process. It also solves
by bastardoperator 5y ago
I have no need to do any of this locally outside of debugging when I can commit/push early/often and get the same feedback from my CI/CD process. It also solves the "local history" problem because my code lives on a remote. If anything what you're describing sounds like a lack of standardization or gates in order for code to reach production. That's an engineering problem, not an IDE vs text editor issue.
- elondaits 5y agoMy point was that an IDE runs the static analysis in the background and gives feedback as soon as you type, in the editor itself, instead of having a separate step. Same with the test... it's easier to react to the test result, check what's failing, re-run the test directly from the IDE. This would be in addition to the CI/CD... to aid the coder, not just to secure the integrity of the codebase.