Skip to main content

Timeline for Generating Robot Name

Current License: CC BY-SA 3.0

17 events
when toggle format what by license comment
May 5, 2016 at 17:35 vote accept CodeYogi
May 5, 2016 at 15:35 comment added brian_o @200_success Perhaps part of the exercise is grokking "random" is not synonymous with "unique", even if randomized values are desired for aesthetic purposes.
May 5, 2016 at 4:24 answer added deamentiaemundi timeline score: 2
May 5, 2016 at 1:25 history tweeted twitter.com/StackCodeReview/status/728032827044941824
May 5, 2016 at 0:29 comment added 200_success The challenge makes no sense. If we already prevent collisions by tracking which names have been used, then there is no need for randomness — a simple counter with a duplicates filter will do.
May 4, 2016 at 22:47 answer added Ext3h timeline score: 2
May 4, 2016 at 22:25 comment added Tunaki @brian_o Yes, the problem is unclear on this point. I initially thought that it should but the resetName test made me think otherwise: it reset the name of first robot and asserts that a new generated name is still different.
May 4, 2016 at 22:06 comment added Hank D @SimonForsberg, May the 4th be with you.
May 4, 2016 at 22:02 answer added brian_o timeline score: 2
May 4, 2016 at 21:28 comment added brian_o When a robot is reset, should it return its name to the name pool?
May 4, 2016 at 17:25 comment added CodeYogi @SimonForsberg no :)
May 4, 2016 at 17:25 answer added nickb timeline score: 4
May 4, 2016 at 17:19 comment added Simon Forsberg Is R2-D2 or C-3PO possible names?
May 4, 2016 at 17:02 answer added Tunaki timeline score: 13
May 4, 2016 at 16:39 history edited CodeYogi
edited tags
May 4, 2016 at 16:25 history edited CodeYogi CC BY-SA 3.0
added 122 characters in body
May 4, 2016 at 16:17 history asked CodeYogi CC BY-SA 3.0