We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
This Problem Is A Prime Example Of Why Hackerrank Is Such A Bad Platform
In HR, the input to the function isn't always similar to the input to the program/submission. Alright. But in this case the function they want us to implement takes the input as a 2D array and outputs the same data structure as a 1D array. This adds an unnecessary layer of complexity on top of the actual problem in the question.
The platform should stay consistant with the input and output representation. Why the hell would a tree look like A in the input but look like B in the output? It's a poor design choice that just makes file io easier for the person who made the question. Not to mention that in an interview we have to understand everything and nail both the problem and structuring the output in 30 minutes to get a job.
Cookie support is required to access HackerRank
Seems like cookies are disabled on this browser, please enable them to open this website
Swap Nodes [Algo]
You are viewing a single comment's thread. Return to all comments →
This Problem Is A Prime Example Of Why Hackerrank Is Such A Bad Platform
In HR, the input to the function isn't always similar to the input to the program/submission. Alright. But in this case the function they want us to implement takes the input as a 2D array and outputs the same data structure as a 1D array. This adds an unnecessary layer of complexity on top of the actual problem in the question.
The platform should stay consistant with the input and output representation. Why the hell would a tree look like A in the input but look like B in the output? It's a poor design choice that just makes file io easier for the person who made the question. Not to mention that in an interview we have to understand everything and nail both the problem and structuring the output in 30 minutes to get a job.