How to solve any coding challenge
First, why?
Coding challenges (or tests) have been used by software companies to determine suitable candidates for decades. Some of us have questioned why EVERY single developer position must be made subject to the Ivory Tower play of algorithms and data structures. Afterall, a recent survey found that more than 50% of successful candidates who passed those tests ended up doing tasks that required practically nothing related to what the tests were meant to determine/assess.
So, why?
Why put otherwise talented/creative prospects through the mental-meat-grind? Especially as another survey found that more than 70% of companies lost out on good prospects simply because these companies were so fixated on the tests.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer vehicula risus quis vestibulum feugiat. Praesent dui augue, pellentesque at lobortis sit amet, volutpat eu felis. Suspendisse a eleifend sem, quis lobortis sapien. Nunc eu lectus dolor. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Donec nulla lorem, viverra eu nunc a, euismod ultrices eros. Praesent et ipsum bibendum turpis tempor auctor. Aenean porta eu nunc eget eleifend. Donec tempor, ipsum eget venenatis fermentum, augue risus sollicitudin dolor, ut porta odio neque id tortor. Vestibulum id hendrerit eros, a euismod ligula. Vestibulum at ultrices lacus. Quisque non efficitur velit, posuere scelerisque tortor.
Why do they do it then?
Find out the answer in Part 2