Wrote a piece of bug riddled code that took me ages trying to debug. Gave up and tried again next day.
Gave up again, started from scratch. Got it done in 10 minutes with a slightly different approach.
Either I'm a complete moron, or this thing is a lot harder than it looks.

Loved it!

I like these. You start with thinking "What the heck is he on about now?" Then you try to run the code and it takes a split second to understand what's the problem. Hats off, sir.

I came here to give the same comment.
Upvote this one instead.

Not sure what to make of vector V. Are the entries b1, b2 ... bn the result of a calculation, or just some random numbers ?

8 years old and only 12 solved this thing?
Very curious of what I'm getting into. :-)

I love how this beauty received 26 Best Practises upvotes, and 8 clever ones.
Too bad you have to choose: it's clearly both.

Water Rat (me, nice...) solved this thing in the year of the Wood Dragon.

My advice is to look into 'type coercion' and while you're at it, 'type conversion' and figure out the difference. It's quite interesting stuff.

GO sounds so special that I'm not even going to try.

Having my hands full anyway with struggling through 120,000 lines of DXL code, written by even more incompetent programmers than I am, at work.

Sorry, but I had to get that of my chest. ;-)

Dont mind me.

I got the same and "solved" it by including \t as an acceptable character. It's a bit weird.

My brain must be myjinxined after solving a few hundred of his Kata's.
I perfectly understood what he meant. :-D

It's not pretty, I know.

I'm sure this can be solved with some kind of smart bitwise magic.
And I'm also sure that I'm not smart enough to figure this out.

One of the earlier Kata's. Nowadays this thing would have been rated an 8kyu. ;-)

is that an order?