3 ms·
Not the same question, but related. Over the years I feel I've got very good at tracking down reasons for crashes in C and C++ programs, and I quite enjoy the
by CJefferson 2y ago
Not the same question, but related.
Over the years I feel I've got very good at tracking down reasons for crashes in C and C++ programs, and I quite enjoy the experience of tracking down such bugs.
I've often fancied a way to monetise this, maybe even a "no fix, no fee" system (assuming you can give me a way of reasonably predictibly reproducing the crash, even if it needs a while / has a random element).
It would require the company giving out their source code to me, and giving me a way to build it, so I imagine in most situations it wouldn't be worth the effort, unless the bug was absolutely mission-critical.
- chrisldgk 2y agoWe’ve found him, we’ve found the one guy that likes debugging. Honestly though, good for you. There need to be more people like this in the world.
- eitland 2y agoEy, next to teaching it is the favorite part of my profession! (I like modeling systems and greenfield development as well, but I feel my time is absolutely best utilized when I can train others or crack hard bugs that are worth paying someone good money to crack.)
- ungamedplayer 2y agoPlease add me to your newsletter.
- eitland 2y agoI can't find your email address, send me a mail if you want.
- jlokier 2y agoI assure you there's at least two of us :-)
- hyperman1 2y agoI like it too, sometimes. A good bug can be like a whodunnit, with multiple suspects, all doing something nefarious, scheming their little schemes and thinking they're the only ones. Now find the miscreants causing the death of the process. Some codebases have every participant screaming they stabbed the goddamn basterd, and the job is more a whodidn't.
- scarlehoff 2y agoI love it too! As another commenter says, it's like a murder mistery, specially when it is not your code. The only frustrating bit (at least for me) is being just told "there's a crash around here", but once you have a way to reliably reproduce it I enjoy it quite a bit.
- em-bee 2y agoi like debugging too. the problem is, when it's unfamiliar tech then it can take some time to get familiar with it. but i found that when i was unable to find a solution, i was to embarrassed to ask to get paid, so i realized that "no fix, no fee" is ok for me. i just have to estimate the risk involved. how much time can i afford to work on this problem if i don't get paid. in part that is influenced by how much i am interested in learning that tech.