When I'm working on my master's thesis 8 years ago. I also had a hard time to choose a topic. Here's where I got it wrong. I started to think of all the technologies I wanted to work on, thinking of the programs I wanted to write for my thesis. A thesis is a study, it's not a hackathon or bring your best program to school task. So I suggest you focus on the problem rather than the solution. Although coding is an important skill, but how you present your documentation will give you more benefit when it comes to your defense. The harder the problem you solve, the better the results will be. You have to focus on proving that the problem you are trying to solve is actually a problem. Then comes the easy part, you can now wear your hacker's hat and code your solution.
Thank you so much, that's great advice!
Though, I guess my biggest problem is, to find a problem that I want to solve. I do know some, but I always have the feeling, that they have already been solved and that I am actually not generating any new value :-/. That's the hard part for me, as I am not writing the thesis in a company context, where each problem would be unique and has to be solved in a way that suits the company environment.
Every study/research ends with things for improvement. You can start researching on previous thesis or studies. If you have an ACM account you can download research that other people did. Or you can go to a library where you can see previous studies. These materials will also help you support your problem. Reading is the key. Try to select up to 10 studies everyday that interests you and see where they left off.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
When I'm working on my master's thesis 8 years ago. I also had a hard time to choose a topic. Here's where I got it wrong. I started to think of all the technologies I wanted to work on, thinking of the programs I wanted to write for my thesis. A thesis is a study, it's not a hackathon or bring your best program to school task. So I suggest you focus on the problem rather than the solution. Although coding is an important skill, but how you present your documentation will give you more benefit when it comes to your defense. The harder the problem you solve, the better the results will be. You have to focus on proving that the problem you are trying to solve is actually a problem. Then comes the easy part, you can now wear your hacker's hat and code your solution.
Thank you so much, that's great advice!
Though, I guess my biggest problem is, to find a problem that I want to solve. I do know some, but I always have the feeling, that they have already been solved and that I am actually not generating any new value :-/. That's the hard part for me, as I am not writing the thesis in a company context, where each problem would be unique and has to be solved in a way that suits the company environment.
Every study/research ends with things for improvement. You can start researching on previous thesis or studies. If you have an ACM account you can download research that other people did. Or you can go to a library where you can see previous studies. These materials will also help you support your problem. Reading is the key. Try to select up to 10 studies everyday that interests you and see where they left off.