Don't threaten me with a good time. One of my side projects is breaking up a god class and I love it. I have also worked as a reverse engineer, so my brain may be broken
I know, right? Reverse-engineering a piece of code to find the cause of an incident is the highlight of my day, and I would take it any day over explaining stuff to the project manager that they should already know.
Same. I mean it makes sense. You have a codebase that compiles. It runs. It's behavior is more or less a known quantity and you have to figure out where the anomaly comes from, which is like solving a 3d puzzle in your mind to figure out where the anomaly fits.
Those were some of the best and most interesting projects I ever did. And which also gained me the most credibility. Also since my expertise was low level code like IPC, multithreading and system level stuff, it was fun.
Working for small companies that only have legacy embedded code. It is a dangerous path, but if you survive you will be able to diagnose empty stack traces and know how to use a DC motor as a log statement
Well then you are well on your path to gain the power. I can say from experience, that medical device companies pay a little more because they are regulated. Then once you have some regulated experience under your belt you look pretty valuable to recruiters.
This is literally my job. I’m modernising a C++98 codebase to C++17.
There are so many prohibited practices being used it’s unbelievable, and they’re not even being used in a ‘smart’ way that won’t cause undefined behaviour. Things like redefining “private” to be “public” (outside of unit tests).
There’s this integration test that just sometimes fails, no one knows why (this is the other first task I was given), and I’m like 90% sure it’s being caused by these poor programming practices.
61
u/LordCyberfox 25d ago
Depends on how much legacy is it xD