Real talk, programmer people: have you ever had a technical problem (piece of code or infrastructure) where you never did figure out what was going wrong? Or how to fix it?
I'm under the impression that this is never supposed to happen, that we're all supposed to doggedly uncover the truth *eventually*, either alone or with others' help. Or else we suck at our jobs and should quit.
Trying to figure out if that's real or a myth.
@aldeka Sort of. I think I've never seen a case where a feature was shelved because "we didn't know how to do it". But I've seen plenty of cases of: "Dunno how to fix it. Rewrite from scratch a different way?" "Dunno why it sometimes fails. Put it in a try/catch, retry a second time, and if it still fails, move on?" "Tests occasionally fail, but the thing seems to work? Solution: change the test." And of course "Bug would take X time fix. That's too much work, so guess it's going unfixed."
