4 ms·
I did. I did look into the source code and wired gdb to go through. I should mention that in the reply but I didn't because I didn't figure out the why. That's
by markus_zhang 2y ago
I did. I did look into the source code and wired gdb to go through. I should mention that in the reply but I didn't because I didn't figure out the why. That's why I guessed the scancode is the issue, because it never went into the if statement for BACKSPACE, but I didn't confirm that, neither did I change the scancode to see which value is the correct one, because I got really tired after a few nights of debugging.
Like I said I agree with you in principle. Sometimes I feel guilty not knowing the real issue instead of just glossing away. Wouldn't the 10x programmers want to figure out the root issue of this kind of bugs? But realistically -- this probably sounds defeatism, it burns me out quickly if I do that. It might just be that I'm genetically prone to be impatient and easy to frustrate, or be that I'm not mentally well, or whatever. I know it sounds defeatism so I would prefer not to speak these lines.
But again I must thanks for your reply, and will keep trying pushing a bit further every time.
- jaredsohn 2y agoI think AI can help reduce the burnout. Send it some code that you think may be relevant and ask about it and then verify after you see the AI's explanation. Of course AI can burn you out, too, if it doesn't find something useful but it can be a time-saver for this purpose sometimes. Basically try to take advantage of when verification is easier than what you're asking AI to do for you.
- markus_zhang 2y agoThanks. I did use AI for my first pieces of the code because I couldn't wrap my head around ImGui at the moment. I was very alert about using AI to write code though, because I still want to understand things. So I stopped using it during the last two nights. I can't complain about the code quality as it's decent, but I just want to get better at reading the source code, I guess.