Transferring Ideas...

There's always something that I want to write it down. Transferring idea is always important in everybody's life. Esp for the things that I'm doing, I need to program according to the PhD student's ideas. To start off, I'll need to implement/modify software/codes that does idea [A.1]. He thought of a new idea, [A.2], and he needed to tell me what his idea is about. I know a little about [A.1]. But first told the [A.2] by explaining the *finest* detail of a small part of [A.2], call it the [A.2.1.1.1.3] (imagine it follows the chapter/section/subsection in a book hierarchy), then [A.2.1.1.1], [A.2.1.1]., finally [A.2.1]. I was so bored that I dun get a thing after the whole discussion. Then today, I finally realize that I'll need to do [A.2.2] and [A.2.3] in order to complete [A.2]. I can't comment on him, but if I were to do that, I'll use the "top-down" approach rather than the bottom-up approach.

Situatin for me is always a lose-lose situation. If I bring it up with him, he'lll think that I'm just whining and I'm looking for excuses in front of that professor. If I don't, I'll continue to bug him for [A.2.2] and [A.2.3], which he may think that they are all trivial (but I don't even have the big picture!) and continue to look down on me. I don't like this idea, I don't like the way as if he's giving tuition by asking me questions before he manage to paint the full picture.

-- mr blog