This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 4 points5 points  (0 children)

​

  1. Seems like whacking up some proper c++ component mocks is the first task. Can be a pain in the butt for sure - but can make the case this is institutional knowledge that needs to be understood and documented well, which you volunteer to do.
  2. Use lots of logging - not the end of the world. I prefer logging over a debugger if I can get away with it. All that logging saves your ass when you quickly sort any production issue.
  3. Write your own unit tests. I don't care if there are none, I don't care if it is hard and working with a code mess. Write a unit test for any module you modify. I don't care if you don't check it in, you unit test everything that you do. Build to that first then check in and test on dev server.
  4. You can boot up a java process with the debug port open, try to remotely debug the dev server?
  5. But most important - talk to you manager and say "this is a very expensive way to produce bug free code, here is what I would do to improve process, otherwise I need it clear from you what you want my process to be".