When I popped out for some food today it dawned on me that there are basically two type of tests. First try to find out if you're good at drilling and memorising, and second one is looking for an ability to create your own solution. Sadly enough, first type claims to the the second type, but never vice versa.
My version of code is below and original task can be found here: LINK
Showing posts with label coding challenges. Show all posts
Showing posts with label coding challenges. Show all posts
Tuesday, May 28, 2019
Monday, May 27, 2019
Coding challenge - Jumping on Clouds
Here is another one. Didn't use collections this time.
Original task is here: LINK
My version is below
Original task is here: LINK
My version is below
Sunday, May 26, 2019
Coding challenge - Sock Merchant
I hate test tasks so much I spend four hours out of five to think why I hate them so much. This time I came up with the following list of whys:
-- expectations are never clear and when they are clear they are clearly about knowing rules for the game, not actual solving something from the scratch, to be successful you need to be familiar with known working solutions, not work on your own;
-- ruminating about what your interviewer brain processes is very distracting, cause practice proves that they may be thinking lots of things, almost all of them not in your favor.
What would be better, array or collections? If you use array they will think you don't know collections. If you use collections they'll think you have a habit of over-complicating things. And if you use for or if they'll think you've worked with legacy for too long and sustained irreparable brain damage.
Well, anyway, original task is here, and my version of code looks like this:
-- expectations are never clear and when they are clear they are clearly about knowing rules for the game, not actual solving something from the scratch, to be successful you need to be familiar with known working solutions, not work on your own;
-- ruminating about what your interviewer brain processes is very distracting, cause practice proves that they may be thinking lots of things, almost all of them not in your favor.
What would be better, array or collections? If you use array they will think you don't know collections. If you use collections they'll think you have a habit of over-complicating things. And if you use for or if they'll think you've worked with legacy for too long and sustained irreparable brain damage.
Well, anyway, original task is here, and my version of code looks like this:
Subscribe to:
Posts (Atom)