no need to spend an iteration reversing

worst practice, eval can run any arbitrary code

Don't reinvent the wheel. <3

Job Security with obfuscating

This is O(3n), there is a 0(n) solution, 3 times more performant.

I feel like if a problem can be solved mathematically it is a better solution.. as long as the math is explained (with good variable names and/or comments)

I agree that they should not be creating a new object but simple regex and dictionaries should be understandable to any developer.

I apologise, it seems like the robots have pulled your answer then.

After doing some perf tests, I'm not sure this is more performant in most cases. Even if the LLM told you so.

Less code does not mean less instructions unless you are writing assembly.
Even then each instruction can run a varied amount of cycles.

Understanding time & space complexity ie. big O and applying that wisely is more important than less lines.

hilarious

This is amazing