How to make steady progress in my research?
I worked so damn hard but "IT JUST DOESN'T WORK!"😤
How can I unblock myself quickly and make good progress toward the goals?
Below I compiled a list of tips that I found useful. 👇
I worked so damn hard but "IT JUST DOESN'T WORK!"😤
How can I unblock myself quickly and make good progress toward the goals?
Below I compiled a list of tips that I found useful. 👇
*Imagine success*
Forget about all the technical difficulties for a moment. Imagine you finish your project successfully, would you find the outcome exciting?
If not, drop the project. Yep, just drop it. Free up your time to work on important problems.
Forget about all the technical difficulties for a moment. Imagine you finish your project successfully, would you find the outcome exciting?
If not, drop the project. Yep, just drop it. Free up your time to work on important problems.
*Work backward 🔙(1/2)*
Say your project involves three steps: A➡️B➡️C.
First, assume that you have perfect output of B and work on the step C.
Next, assume that you have perfect output A and work on the step B and so on.
In the end, you will have a fully working method.
Say your project involves three steps: A➡️B➡️C.
First, assume that you have perfect output of B and work on the step C.
Next, assume that you have perfect output A and work on the step B and so on.
In the end, you will have a fully working method.
*Work backward 🔙(2/2)*
Okay, this is weird. WHY?
Because you get to
1) see final outcome early
2) measure the performance upper bound
3) focus on each task with perfect inputs without distraction
4) figure what are needed to achieve the desire results.
Okay, this is weird. WHY?
Because you get to
1) see final outcome early
2) measure the performance upper bound
3) focus on each task with perfect inputs without distraction
4) figure what are needed to achieve the desire results.
*Toy examples*
Design toy examples that capture the essence of your problem. They are sufficiently simple so you can focus on the core problem.
It's also often helpful to construct/synthesize such toy examples so that you have access to all the ground truth in all the steps.
Design toy examples that capture the essence of your problem. They are sufficiently simple so you can focus on the core problem.
It's also often helpful to construct/synthesize such toy examples so that you have access to all the ground truth in all the steps.
*Baseline first*
Don't know where to start? Start with trying out baseline methods on your problem.
It helps identify limitations of the state-of-the-art. If they work perfectly well, why do you need to work on this problem?
Finding specific gap helps motivate your work.
Don't know where to start? Start with trying out baseline methods on your problem.
It helps identify limitations of the state-of-the-art. If they work perfectly well, why do you need to work on this problem?
Finding specific gap helps motivate your work.
*Simple case first*
If your method does not work on simple/trivial cases, how could you expect it to work on unconstrained, real-world cases?
If your method does not work on simple/trivial cases, how could you expect it to work on unconstrained, real-world cases?
*One thing at a time*
When doing experiments, change exactly ONE thing at a time. This helps you understand what the results mean.
When doing experiments, change exactly ONE thing at a time. This helps you understand what the results mean.
*Identify proxy*
Do not use full-scale experiments (that may take weeks to complete) as the only way to validate your ideas. Run smaller-scale/simpler experiments with short turnaround time so you get to iteratively refine your ideas a lot faster.
Do not use full-scale experiments (that may take weeks to complete) as the only way to validate your ideas. Run smaller-scale/simpler experiments with short turnaround time so you get to iteratively refine your ideas a lot faster.
*Automate everything*
If you find that you need to do the same task twice, write a script for that.
Your future self will thank you.
If you find that you need to do the same task twice, write a script for that.
Your future self will thank you.
*Visualize everything*
You cannot debug what you cannot see. Investing time in visualizing your inputs/intermediate steps/outputs is definitely worthwhile!
You cannot debug what you cannot see. Investing time in visualizing your inputs/intermediate steps/outputs is definitely worthwhile!
*Quantify success*
Instead of always eyeballing a few results on your own, identify a couple of quantitative metrics for your problem and let them guide your exploration.
Instead of always eyeballing a few results on your own, identify a couple of quantitative metrics for your problem and let them guide your exploration.
*Make the best use of machine time*
Plan your experiments so that your machines still work for you while you are not working.
Plan your experiments so that your machines still work for you while you are not working.
That's all! Would love to learn more from your tips! What are your best strategies to make steady progress?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
