I'm not really sure I understand your use of the words "convoluted", "over involved", and "vague" in the context of a single function with 20-30 lines of code, but... okay.
I'm also happy for you that, at 20+ years of software experience, you feel like you can walk out of an interview with a potential employer over this. Not all of us have that luxury, of course. And despite the fact that these types of problems are not necessarily the most ideal way to evaluate a potential employee, whiteboarding challenges have become somewhat of an industry standard interview experience.
As such, and your condescension aside, there are quite a lot of us who are simply forced to learn and hone these skills in order to have a better chance of getting a job in the industry, especially from one of the top companies.
More importantly, these posts are not made with an aim towards "self-gratification" (unlike your rather patronizing response). If they were, only the code would have been included. On the contrary, I write these posts (which each take a fair bit of time) with the aim of helping others to be able to see not just how the solution works, but also how to recognize which approach to look for and use in these and similar situations.
Since starting to make these posts, I've received a number of responses noting appreciation for the explanations. You'll excuse me if I consider their opinion to be more important to me than yours. Moreover, if the content of my posts bothers you, you can quite easily avoid them.
With all that said, you're entitled to your opinion; I, however, will consider your opinion to be "far too nonsensical to be significant for me."
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.
I'm not really sure I understand your use of the words "convoluted", "over involved", and "vague" in the context of a single function with 20-30 lines of code, but... okay.
I'm also happy for you that, at 20+ years of software experience, you feel like you can walk out of an interview with a potential employer over this. Not all of us have that luxury, of course. And despite the fact that these types of problems are not necessarily the most ideal way to evaluate a potential employee, whiteboarding challenges have become somewhat of an industry standard interview experience.
As such, and your condescension aside, there are quite a lot of us who are simply forced to learn and hone these skills in order to have a better chance of getting a job in the industry, especially from one of the top companies.
More importantly, these posts are not made with an aim towards "self-gratification" (unlike your rather patronizing response). If they were, only the code would have been included. On the contrary, I write these posts (which each take a fair bit of time) with the aim of helping others to be able to see not just how the solution works, but also how to recognize which approach to look for and use in these and similar situations.
Since starting to make these posts, I've received a number of responses noting appreciation for the explanations. You'll excuse me if I consider their opinion to be more important to me than yours. Moreover, if the content of my posts bothers you, you can quite easily avoid them.
With all that said, you're entitled to your opinion; I, however, will consider your opinion to be "far too nonsensical to be significant for me."