Research being a very different task compared to software development, it focus on findings compared to software product, you cannot claimed you did a research even if you created a piece of software no one ever did, you can only do so after you documented your method of doing in a repeatable way as proof and as a communication medium between researchers. It is more towards answering a question that providing a solution. Proof is essential.
So, I happened to enter my final year of bachelor studies, where Final Year Project is a mandatory part. I, unfortunately chosen a research topic for my FYP, and here's two lessons I've learned through the mistakes I've made.
1. Think about "WHY" and justify it before you start!
If you did not think hard on "WHY", you'll probably end up with findings that's either known or useless. By answering WHY, you need to think about
- is there a need for this research?
- is there anything similar with my intention?
- does other research similar enough to invalidate mine?
- how does my research make a difference with others and does it matters?
With a strong answer to WHY, you are focusing on a very specific case where there is no clear answer yet and would make an impact if found.
2. Do not attempt to research a field without knowing its latest status
If you're not aware of the state of the art in the field, you would probably be solving a problem that already been solved or answering a question that have been answered. This only makes sense when you find the previous findings suspicious, which can only be justified provided you've read about it. You only decide what question to answer after you know what questions have been answered.
Both advice should be enforced at the very beginning of your research, before any investment of research time.
No comments:
Post a Comment