BadCode.rocks

BadCode.rocks is a bad art competition and an educational tool all together. Every month, we will release a new coding challenge. Participants have one month to compose and submit the worst working implementation to the challenge that they can devise. Our judges will review all submissions on the snark mailing list, and select a winner or two. Winners get the privilege of having their code used to compose a full teardown article describing why the code is so bad, and how the submission exemplifies what not to do.

From the above you will hopefully have an idea of what sort of "bad" the judges will be looking for. We realise this is somewhat subjective, and that's why we're using human judges and not metrics. This isn't an obfuscation or golf competition; you won't win just by using an esoteric programming language. Write a solution that solves the problem, and is correct from the point of view of functionality, something your worst self or most incompetent junior co-worker might conceivably have written. If you can combine together so many real malpractices that your submission is exaggeratedly, comically bad, that's great. If your submission is just unintelligible line noise, we're not interested.

All submissions must contain a statement that the code is your own work (groups are ok!) and placing the code under either CC0, CC-BY, or CC-BY-SA. Submissions are by email to submissions@badcode.rocks. Attaching each source file is preferred, but tarballs or git URLs will also be accepted (especially when directory structure matters). Submissions may be in any programming language that can be compiled or interpreted on a Debian Stable system.

Robot Simulator

Note: if you still want to submit for the beer song challenge, we’re going to accept submissions there for awhile longer.


A robot factory’s test facility needs a program to verify robot movements.

The robots have three possible movements:

Robots are placed on a hypothetical infinite grid, facing a particular direction (north, east, south, or west) at a set of {x,y} coordinates, e.g., {3,8}, with coordinates increasing to the north and east.

The robot then receives a number of instructions, at which point the testing facility verifies the robot’s new position, and in which direction it is pointing.

The command string “RAALAL” means:

Say a robot starts at {7,3} facing north. Then running this stream of instructions should leave it at {9,4} facing west.

Testing

To ensure the correctness of your implementation, see test.sh with usage:

sh test.sh /path/to/program

It is expected that your program takes four command line arguments: initial x position, initial y position, initial direction, and command string.

On STDOUT your program must print: final x position<space>final y position<space>final direction.

All positions are integers, and valid directions are: N, S, E, W.

Submission

All submissions must contain a statement that the code is your own work (groups are ok!) and placing the code under either CC0, CC-BY, or CC-BY-SA. Submissions are by email to submissions@badcode.rocks. Attaching each source file is preferred, but tarballs or git URLs will also be accepted (especially when directory structure matters). Submissions may be in any programming language that can be compiled or interpreted on a Debian Stable system.

If relevant, please make it clear what name, pseudonym, or group name you would like your submission attributed to. This name (and the code content of your submission) will be made public.

Submissions are due by and the winning teardown post will be published the following month.


This excercise and its tests based on https://github.com/exercism/rust/tree/master/exercises/robot-simulator, original license:

Copyright (c) 2017 Exercism, Inc

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.