Too many surprises. Don't like that at all. Camera behaviour and its limits should be specified in the description.
The description says nothing about Network or Camera classes, their behaviour, methods which should be defined, how they will be used etc.
No sample tests.
This comment is hidden because it contains spoiler information about the solution
Thanks for answer and good advice! :)
Depends on Node version. And please use spoiler flag next time.
As matt said, it is no issue.
How can the uplink be so awfully terribly expensive that commands have to be compressed into one byte, while apparently the downlink is inexpensive enough to transport the image from up to 16 cameras ?!?
Other than that, nice work. I got bit by the inconsistency of the move commands same as quite a lot of other people, but that just added a bit of Real Life Flavour (c) to the story. :]
i guess there is no way to change it from issue to suggestion? I'll just mark this as resolved for now.
Probably more a suggestion than an issue.
there is one in the desrcription, I think this would rather suit a suggestion more than an issue.
an example breakdown of a camera command byte would be helpful
I enjoyed this kata! As with others, I agree that it would be helpful to clarify that you take the 'first bit' to be the lowest bit.
Also, is much gained by having the movement bits go [positive, negative, negative, positive]? It highlights the importance of reading the spec carefully, but is a bit weird, so I'm split on the issue.
Suggest changing the instructions from "first bit" to "lowest bit", or provide some tests which clarify.
I found out through submit tests. It was a simple fix.