summaryrefslogtreecommitdiff
path: root/go/robot-name/README.md
diff options
context:
space:
mode:
authorDimitri Sokolyuk <demon@dim13.org>2016-08-28 14:41:56 +0200
committerDimitri Sokolyuk <demon@dim13.org>2016-08-28 14:41:56 +0200
commita9ae4ebc6006271fc0e95626e0c95e6b9cc786de (patch)
treeda95be2382b384b52dd0157c1b6126e9b57b3d4f /go/robot-name/README.md
parentfef4ced569da1bdbc167d0786ab0a188973de3c5 (diff)
Solve robot
Diffstat (limited to 'go/robot-name/README.md')
-rw-r--r--go/robot-name/README.md35
1 files changed, 35 insertions, 0 deletions
diff --git a/go/robot-name/README.md b/go/robot-name/README.md
new file mode 100644
index 0000000..5063b90
--- /dev/null
+++ b/go/robot-name/README.md
@@ -0,0 +1,35 @@
+# Robot Name
+
+Write a program that manages robot factory settings.
+
+When robots come off the factory floor, they have no name.
+
+The first time you boot them up, a random name is generated in the format
+of two uppercase letters followed by three digits, such as RX837 or BC811.
+
+Every once in a while we need to reset a robot to its factory settings,
+which means that their name gets wiped. The next time you ask, it will
+respond with a new random name.
+
+The names must be random: they should not follow a predictable sequence.
+Random names means a risk of collisions. Your solution should not allow
+the use of the same name twice when avoidable. In some exercism language
+tracks there are tests to ensure that the same name is never used twice.
+
+To run the tests simply run the command `go test` in the exercise directory.
+
+If the test suite contains benchmarks, you can run these with the `-bench`
+flag:
+
+ go test -bench .
+
+For more detailed info about the Go track see the [help
+page](http://exercism.io/languages/go).
+
+## Source
+
+A debugging session with Paul Blackwell at gSchool. [http://gschool.it](http://gschool.it)
+
+## Submitting Incomplete Problems
+It's possible to submit an incomplete solution so you can see how others have completed the exercise.
+