this is perfect real life example.
customer: "encode it!!"
you: "Looks easy"
...
next day at 2AM...
you: "why noone told me about all these endge cases"
unbelievabe.
while solving this kata I thought that most likely there is only one way how to fit in 94 characters.
... and then I saw amount of solutions
Amazing kata
oh my.
I feel so sad with my solution when I see this.
this is probably the cleanest solution
I would be very careful with
+=
and=+
syntax is short but can introduce unexpected behaviour
This comment is hidden because it contains spoiler information about the solution
you need to specify radix to stay on the safe side
this is not best solution.
it does look clean but performance wise it's not nice.
You definitely learn thing or two in this kata.
same here.
I do find descriptions of SQL tasks bit cryptic.
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
🤔 return without value
bit to much of magic here for my taste
LOL
this is perfect real life example.
customer: "encode it!!"
you: "Looks easy"
...
next day at 2AM...
you: "why noone told me about all these endge cases"
Sorcery 🔥
now I learned that in golang you have runes not characters.
why not :)
at least not
hieroglyphs
unbelievabe.
while solving this kata I thought that most likely there is only one way how to fit in 94 characters.
... and then I saw amount of solutions
Amazing kata
Loading more items...