Are you a developer of CoprHD?
Do you copy source files over to your devkit, build the rpm and install it for each code change?
Have you ever fixed a line of code but needed to "start from scratch" or rerun a long-running task/order to test your fix?
When you reset services, do you tail a logfile or just go get a coffee because you don't really know when the services are up?
Have you ever walked over a line of code in the debugger and said "Oh carp (sic)! I wanted to go into that method!", causing you to start over?
Do you use the "gradlew" scripts to swap out jar files and have to wait for minutes for that whole thing to finish?
Have you ever wanted to just save state of your CoprHD quickly so you can restore to it and run the same operation over and over while debugging it?
Have you ever cried at your computer?
Hi everyone, I'm Bill. And I might not be able to help you with the last question. I cry ALL THE TIME at my computer. It can be frustrating. But I'm going to teach you a few tricks of the trade that just might help you become more efficient as a developer. This series is dedicated to making the CoprHD developer more efficient, wait less, and be more productive in their day-to-day work.
When you're done with this series, you can hopefully:
- Keep your modified source code on your IDE machine and not copy it to your devkit for every change.
- Deploy updated jar files to your devkit without even thinking about what project you're affecting directly from your IDE. And waiting a lot less.
- Remotely debug on your devkit.
- Reset the program counter when you accidentally step over a line of code.
- Change the source code while debugging. (Yes, you can do this without external tools, trust me)
- Save and restore CoprHD state quickly and easily.
- Have a command that tells you when the services are up.
This is a draft of the things I would like to cover. More to come!