It's a clever cheat, though.

I like buffers.

Did we really let this person suffer for 4 years?
Just iterate and keep track of non-null values, my friend.

for elem in array:
   if elem != Null:
      #do something

To implement this suggestion, the description

... "egg" inserted directly after each consonant.

will also have to be changed into

... "egg" inserted directly after some consonants.

Given the task here is to restore an "eggcoded" string to its original string.

So eggcoding "no egg" give us "neggo egegggegg", restoring it will give us back "no egg".

I think "neggo egg" is an invalid input -- there are no original string that maps to it.

Imagine you just started to learn to code. You managed to write "Hello world!" in a browser document and think you're now ready to start with some easy kata's on codewars.

Imagine this is the first one you try and find this piece of art as the "Best practices solution". :-)

That depends on what went wrong...

I've got the right pepes like in the examples, but something went wrong. What should i do?

I thought my solution was very clever... then I saw this.

glad you enjoyed it, and thanks for doing my kata man! Your solution looks really clean btw, and yeah, at least for me, this kata (and the series in general) wasn't as easy as I thought it was. (also partially because I cannot understand regular expressions for the life of me).

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!

Lua translation

I have a couple of more ideas, but oh gosh, creating these is exhausting. Most of the bugs presented in the XCOM bug fixing tasks are very simple, and I want them to be interesting for unexperienced programmers to draw their attention to traps and pitfalls lurking out there in the wild. But then I need to be careful to not make the theme too scary for beginners, and the problem must be set up in a way that it is worth actually fixing rather than discarding the whole initial code and rewriting it from scratch. I am glad that the experienced users seem to like the challenges. I would still love to hear what the target audience thinks about them. It would not be much sense in creating easy problems which scare off beginners and which are liked by hardcode coders solely due to the theme and setup :)