Draft
Automaton (Part 1)
172Mishaboo
Loading description...
Refactoring
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
This comment has been hidden.
so embarrased by my code for this one, for some reason this was tough :)
This comment has been hidden.
Writing good bug fixing katas are hard.
Most of them I've encountered are basically "obfuscate a working solution with random nonsense and throw the result pile of spaghetti to the user", which is not interesting at all, and doesn't provide any insights. But I guess it's a quick way of generating white katas.
(Incidentally, even this kata is showing a better job to create bug fixing katas than all those katas!)
I was more targeting people who just start to code and want to learn / test / try some debug skills. I just saw tons of times that programmer can't find a simplest bug. So I decide to try to help at least someone and try myself in writing debug kata in the same time. Thank you for comments. I'll try to came up with something more interesting next time =]
It is quite messy. It doesnt even tell us what the kata is supposed to do. At least if you want us to resolve the mistakes at least add comments in your code or make your code more readable
Fair comment. This kata is more to debug existing code and just simply make it work. I'll think How I can improve discription. Thanks.