Without trying to devalue zeromus' words, programmers can learn tact. But it takes a long time, time that could be spent doing other things, and it's not an easy thing to practice.
Responding to the thread in general, Kurabupengin asked a question. It was, quite plainly, a question asked out of ignorance, but it received two equally valid responses. Go back and read them, they're up there. Kurabupengin didn't understand the answer (which was predicted) and responded negatively.
Not in this thread, Kurabupengin took to IRC where the context and subtext of the thread was explained to him several times, prompting him to come back and write his apology and rephrase his question. To which he received another polite response, and misinterpreted again.
I don't know how better to say, "What you are asking is difficult, but if you had the skill apply an answer, you would have the skill to figure out the answer for yourself and thus not need to ask the question; furthermore any answer given to you right now will likely be out of date by the time you can use it," than what zeromus said originally, while still affording respect and not talking down to the other person.
What Kurabupengin actually wants, as stressed by his second question, is to learn how to code, and again, as zeromus replied, the best way to learn how to code is to sit down and start writing code. There is no malice in those words, no disrespect.
This thread derailed into "who's being rude" because there are two languages being spoken here. One is English, as spoken by programmers, which values being concise and precise, the other is English, as spoken by non-programmers, which appreciates ambiguity and vagueness. The vague question ("How do I do X?" which actually meant "How can I learn how to program to eventually do X?") was met with a precise answer ("You lack the skill to do X, otherwise you would not need to ask.") and disjunction followed.
Kurabupengin, answering your actual question again, pick a language (C# is a good starting point if you want to work on BizHawk, but any of the object-oriented languages is good), tinker with it, get better at tinkering with it, and when you think you have the skill level required to start poking at BizHawk's internals, track someone down, ask them where the bug and feature list is, and see if there is something you can take on for yourself.
I am still the wizard that did it.
"On my business card, I am a corporate president. In my mind, I am a game developer. But in my heart, I am a gamer." -- Satoru Iwata
<scrimpy> at least I now know where every map, energy and save room in this game is
