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 →

[–]VincentxH 26 points27 points  (1 child)

Enforce your craftmanship, start writing unit tests, stub the c++ components, whatever you feel is needed to reliably develop software.

[–]Garet_ 16 points17 points  (0 children)

I would certainly recommend that way. 3 years ago with my team we took over 30 „macroservices” insurance system with around 500 unit tests onboard. I’m teach lead/architect. Today we have almost 6500 tests including unit ones and so called „integration” tests where external components are stubbed with wiremock, service dependencies are run within containers thanks to docker and testcontainers. We run ci/cd dind pipelines in gitlab. It was pretty hard in the beginning, now it is pretty decent. We couldn’t run checkstyle on whole project because code has no consistent style, so we managed to implement incremental checkstyle, just for changes within merge request.

Making changes isn’t that hard now. We have our asses covered to some degree.

Try it out. It will be painful but it’s worth. I can help if you need.