It's great! I've had community members point me in the right direction after already "solving" it incorrectly. It really makes you think about it. You have to expand your test cases and really come up with a better solution.
Not to say it isn't difficult especially if you expect the problem to be described perfectly accurately.
I don't need a perfect instruction set, but dang if the examples couldn't be better sometimes. Like sixteen was in there to show it only counted for 6, but nothing with overlapping text.
The problem is the example is actually eightwothree which comes out as 83 so if you replace from start to finish the example passes but the solution is incorrect.
I'm not really sure how to interpret your comment but I'll try my best. The edge case that causes some solutions to fail does not have any definition on how to handle it on the problem page. In other words, it does not state anywhere whether the correct interpretation of 1threeight is meant to be 18 or 13. If your solution replaces the words to numbers from left to right you end up with 13 as the value but it's meant to be 18.
The example answers don't cover this but you will realise something is wrong if you run it against your full problem. Community has been very helpful on providing pointers.
You can't just replace the first letter either, because depending on the order of your replacements, you could be replacing the end of another number. (Encountered this exact problem trying to optimize my solution.)