The long-standing debate between "problems" and "questions" is rife with political turmoil and irrelevant tangents, but ultimately there is merit to its resolution. Both sides have valid concerns and they aren't necessarily at odds with each other.

Concept Over Semantics

1. The word itself doesn’t matter. Calling something a “question” doesn’t make someone inferior or less capable. Language is fluid, everchanging and contextual, so going down a rabbit-hole of dictionary definitions is ultimately unproductive.

2. What matters is the burden of constraints. The difference lies in whether you are merely seeking information or actively solving something with real-world implications.

I am only describing what these words mean to me and why I found it helpful in my journey. The concept is what matters, not the actual word choice.

The Core Distinction

• A question seeks an accurate answer. Open-ended questions receive loose answers, so the responsibility lies with the asker to clarify what they want. No action is required beyond acquiring correct information.

• A problem demands a workable solution. Open-ended problems require resolution, so the burden shifts to the solver to clarify constraints and determine what’s wanted. This includes non-functional requirements like time management, debuggability, and personal development.

Why This Matters

As a pupil coming from LeetCode, I often overcomplicated solutions—using BFS for a problem that had a one-line math formula, applying DP when greedy was shorter and more elegant, or summoning a Segment Tree for a Div 2 B. When I approached these as static questions ("What code passes the test cases?"), I limited my growth. But when I shifted to viewing them as dynamic problems, I started engaging at a deeper level to acknowledge all the constraints of submitting a solution, not just the ones given to me:

• Is this solution appropriate for the expected difficulty?
• Am I being observationally lazy?
• Is this the best tool for the job or am I limiting myself to what is comfortable and familiar?

A solution isn’t just about correctness—it’s about effectiveness, efficiency, and growth. Recognizing this distinction unlocks a more thoughtful and intentional approach to problem solving.

Conclusion

Whether you use "question" or "problem" doesn't matter in terms of actually improving. Spoken language is complex and differs by culture and the intention matters more than what is said.

The point is just to view solving problems as more than just an answer of code to a question of test cases.

Respect the problem, respect the challenge, and respect yourself. Don't just settle for an Accepted. Be greedier.