↵
↵
Hello Codeforces!↵
↵
Lately I’ve been asking myself a question that many competitive programmers eventually face:↵
↵
**How do you actually become a problem setter? And why does it sometimes feel impossible?**↵
↵
I’ve always admired the problem setters who create elegant tasks, clever observations, and beautiful solutions. But the more I think about it, the more doubts appear:↵
↵
- Where do they get their ideas?↵
- How do they know a problem is original?↵
- What if the difficulty is wrong?↵
- What if people hate my problem?↵
- Am I even creative enough to be a problem setter?↵
- Do I need to master advanced topics first?↵
- Is there a secret “path” only experts know?↵
↵
These questions keep circling in my mind.↵
And honestly, the more I think, the more I wonder:↵
↵
#### Is becoming a CF problem setter a skill, or a talent? ↵
Or maybe just a long process of trial and error?↵
↵
↵
[cut]↵
I want to hear from those who have tried, succeeded, or even failed:↵
- How did you start?↵
- What resources did you use?↵
- How do you come up with ideas?↵
- How do you estimate problem difficulty?↵
- How do you avoid repeating already existing problems?↵
- What is the path from “I have an idea” to “my problem is in a round”?↵
- And what mindset should a beginner have?↵
↵
I believe there are many hidden barriers, psychological and technical, and I want this blog to collect real advice for everyone who dreams of becoming a problem setter but constantly doubts themselves.↵
↵
Feel free to share:↵
- Your personal story↵
- Your failures↵
- Your first draft ideas↵
- The challenges you faced↵
- Tips for creativity↵
- Tips for testing problems↵
↵
Anything that helps beginners understand the journey↵
↵
I hope this discussion helps not just me but many others who feel the same uncertainty.↵
↵
#### Looking forward to learning from the community!
↵
Hello Codeforces!↵
↵
Lately I’ve been asking myself a question that many competitive programmers eventually face:↵
↵
**How do you actually become a problem setter? And why does it sometimes feel impossible?**↵
↵
I’ve always admired the problem setters who create elegant tasks, clever observations, and beautiful solutions. But the more I think about it, the more doubts appear:↵
↵
- Where do they get their ideas?↵
- How do they know a problem is original?↵
- What if the difficulty is wrong?↵
- What if people hate my problem?↵
- Am I even creative enough to be a problem setter?↵
- Do I need to master advanced topics first?↵
- Is there a secret “path” only experts know?↵
↵
These questions keep circling in my mind.↵
And honestly, the more I think, the more I wonder:↵
↵
#### Is becoming a CF problem setter a skill, or a talent? ↵
Or maybe just a long process of trial and error?↵
↵
↵
[cut]↵
I want to hear from those who have tried, succeeded, or even failed:↵
- How did you start?↵
- What resources did you use?↵
- How do you come up with ideas?↵
- How do you estimate problem difficulty?↵
- How do you avoid repeating already existing problems?↵
- What is the path from “I have an idea” to “my problem is in a round”?↵
- And what mindset should a beginner have?↵
↵
I believe there are many hidden barriers, psychological and technical, and I want this blog to collect real advice for everyone who dreams of becoming a problem setter but constantly doubts themselves.↵
↵
Feel free to share:↵
- Your personal story↵
- Your failures↵
- Your first draft ideas↵
- The challenges you faced↵
- Tips for creativity↵
- Tips for testing problems↵
↵
Anything that helps beginners understand the journey↵
↵
I hope this discussion helps not just me but many others who feel the same uncertainty.↵
↵
#### Looking forward to learning from the community!
