I like research to get new ideas... I wouldn't like writing a detailed point by point analysis though. One of the most tedious things I thought about research was citations/bibliographies.
What i like doing more is creating *based* on that research/gathered ideas. If I am not creating, I feel stifled. Researching for the sake of research with just "results".
I dislike discovering facts, for the sake of facts. Memorizing "terms"... They are unimportant to the big picture. I'd much rather write the essay based on the research than to *show* my research methods, tedious and pointless I think, if the big picture answer is there and the concept is understood.
For example...
Does it really matter if I know exactly what date the war started...If I know a 2-3 page background of *why* a war started?
And in IT... if I can get the project and systems functioning and stable, sometimes by using obscure methods? I hated code documentation / code reviews / SOX auditing...so damn tedious and besides the point, busy work, grunt work. Just those kind of detailed workings. I hated *reinventing* the wheel if there was already a known plugin/snippet for it, why the hell am I going to write it again, from scratch? Wasn't our purpose to help the users and create them a better interface? So damn what if it uses 5k more memory. Oh how blessed I was when I got pulled aside from my normal job functions so I could work on an interesting project. So many "not seeing the forest for the trees" people in IT... hated it.
So first I need the research *gathering* through the Ni process. Then I need to express that through an Fe outlet, showing my feelings to the world, and evoking emotions/thoughts in others.
The research part comes easy, so does the Ti analysis of it... And it is probably why I've been good at jobs, but hated those same jobs... b/c they never allowed my Fe Expressions/Interpretations.