6 Comments

To me, a well-defined problem is half a solution (and this doesn't just apply to Leetcode problems). 🙂

> Documentation not only aids in future reference but also facilitates knowledge sharing within the team.

This is powerful! I've been doing this since the early days of my career, and it has proven to be just another reason to write.

More interestingly, it also happened to me I came to the solution while I was writing about the problem.

I'll have a newsletter soon about a mathematician who solved an old problem doing 5).

Great Writing, John!

Expand full comment

I agree, I too see too many solutions that don't clarify the problem to be solve and so solve another - wrong - problem.

Thanks.

Expand full comment

Great read

Expand full comment

Clearly defining the problem and requirements is half the battle. But don't wait for the perfect requirements either. Remain in experimental mode during the early stages.

Expand full comment

There’s no silver bullet for every problem or situation. That’s why good exploration sets the path to success. In the end, it’s all about tradeoffs.

Great advice, John! 🙌

Expand full comment

Thank you, John. I have just started my career and this guide is going to help me forever. Thank you, Again.

Expand full comment