Tell me more ×
Computer Science Stack Exchange is a question and answer site for students, researchers and practitioners of computer science. It's 100% free, no registration required.

I'm six months away from getting MSc in computer Engineering and I am reading papers to write a journal and thesis; I have wrote one paper. But for the past one and half year, I felt like the whole thing was a research in search of a problem. That is, first proposing a problem and then come up with a solution that claims to mitigate the stated problem and write a paper to convince people to buy my solution.

What is frustrating me is, I have never developed a medium sized software let alone big one. I started this MSc program thinking that it was course based and that I would find enough time to participate in open source projects like Apache. Instead, I have spent my time reading papers and getting angry to the extent that I burned out.

I love computing, especially exploiting hardware using software. I have taught myself many things on this field. I have good understanding of Software Engineering, Operating System and Computer Architecture. But these are more theoretical. I feel like a pianist who doesn't know how to play piano. Yea, that sounds an oxymoron but seriously, what good is a Computer Engineer if he cannot develop big software?

Afterall, writing a good paper sometimes entails developing a good software to justify the claim or to act as a prototype. For example, the paper MapReduce: Simplified Data Processing on Large Clusters was written by the very people who build that system on Google.

What do you think?

share|improve this question
I don't know how to relate your first paragraph with the rest. What is really the question here; how good a programmer should I be? If so, this question is too subjective for this site. – Raphael Feb 7 at 7:11
Take a look at the question cs.stackexchange.com/questions/9072/…, in the comments there is lots of (meta)discussion on thesis work. Good luck! – vonbrand Feb 7 at 14:28
1  
I agree with Raphael that this is subjective for this site, yet I empathize with the situation. Six months doesn't sound like a lot of time to change your situation for your MSc, but you do get to choose what you do next and you do have the rest of your life to get engaged with open source projects. I'm not entirely sure if this question would be appropriate on Academia, but asking how to avoid losing focus of one's interests in the process of getting a MSc seems like a valid question. – Merbs Feb 7 at 15:37

closed as off topic by Nicholas Mancuso, Dave Clarke, Merbs, Pål GD, Juho Feb 7 at 22:42

Questions on Computer Science Stack Exchange are expected to relate to computer science within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.

2 Answers

I think its just the uncertainty of perceived success that's bothering you. Research in computer science and software development are two independent parts of the field which help each other in making progress. Software development is like using the existing stuff effectively, while research is to discover that stuff which is not existing. To become a good researcher, you need not be a good software developer and vice-versa. Simply put ask yourself if you are more satisfied in chasing an unknown. If yes, go for research. If you are not sure of the answer, try out software development for a year or so and you will learn whats best suited for you. Needless to say, you got to be analytical to succeed in any of the paths you take.

share|improve this answer
Thanks for the insight Phalguna. – Abraham Guchi Feb 7 at 4:32

As far as I know to be a good researcher in computer science one should have:

  • Solid Background in Mathematics: In many cases you need to analyze and formally define your problems and solutions.
  • Solid Background in System Prototyping: To proof your concepts and systems in many cases you should present feasible solutions and prototypes. This needs to have good knowledge of system implementation.
share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.