I admit, when I started writing this series, my main thought was to attempt to write something that I would have wanted to read myself. All too often I've seen solution posts in which the code is just displayed, sometimes with only a bare minimum of explanation. Other posts do a lot to highlight how a particular data structure or algorithm works, which is great, but they fail to describe the information's connection to the specific problem.
I mean, let's face it: pretty much anyone who is a coder will have long-since mastered the art of looking up data (thanks, stackoverflow!), but the biggest challenge, I've found, lies in figuring out the right question to ask. So when I write up a solution, I try to focus on how you get from the problem description to the "right question".
So again, thank you !
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.
Thanks for the comment!
I admit, when I started writing this series, my main thought was to attempt to write something that I would have wanted to read myself. All too often I've seen solution posts in which the code is just displayed, sometimes with only a bare minimum of explanation. Other posts do a lot to highlight how a particular data structure or algorithm works, which is great, but they fail to describe the information's connection to the specific problem.
I mean, let's face it: pretty much anyone who is a coder will have long-since mastered the art of looking up data (thanks, stackoverflow!), but the biggest challenge, I've found, lies in figuring out the right question to ask. So when I write up a solution, I try to focus on how you get from the problem description to the "right question".
So again, thank you !