Strange, it worked here. Tested with the above solution and 'tThe Holy Bible' correctly results in 'BbeehHillotTy'. Had to update the test as well to account for the 't'.
All in all... It's just a matter of reading through the lines for the ordering of the entry vectors...
And IMHO, the 'idea' of a 3D to 2D projection is... weird => should be more specific in the description.
This comment is hidden because it contains spoiler information about the solution
xd
it's like a reverse workaround of mine. very interesting.
hah, I did the same thing, lol. Look, they're not good solutions for the computer science aspect, but man the brute force solutions are funny.
Strange, it worked here. Tested with the above solution and 'tThe Holy Bible' correctly results in 'BbeehHillotTy'. Had to update the test as well to account for the 't'.
this is wild. i demand an explanation lol
🥷🏿's js trying his best to make the shortest line of code possible atp 😭🙏
In the random test it expected "Expected: equal to [ [ 0, 91, 15, 13 ], [ 4, 159, 108, 13 ], [ 4, 159, 108, 13 ], [ 4, 159, 108, 13 ], [ 4, 159, 108, 13 ], [ 4, 159, 108, 13 ], [ 4, 159, 108, 13 ], [ 4, 159, 108, 13 ], [ 4, 68, 93, 0 ] ]" but first vector must contain equal numbers please fix it
If this isn't best practice, I don't know what is.
How did you come up with the hardcoded strings?
If you didn't know them ahead of time, how would you approach this coding challenge?
All in all... It's just a matter of reading through the lines for the ordering of the entry vectors...
And IMHO, the 'idea' of a 3D to 2D projection is... weird => should be more specific in the description.
how is it supposed to work?
what is this AHAHAHHAHA
Most readable code of year award goes to..
Is this a joke? 🤐
Loading more items...