Hacker News Reader

This is probably not the result of internationally dumbing down the message, but lazy error handling.

It's probably both. Since you want to obscure it from the end user, you can also afford to be lazy and have sloppy implementation.

That isn't true, laziness will punch straight through a tight definition of error code handling.

After all if you have three API layers realizing in this situation the second layer isn't forwarding that error code because it erroneously thought it was one you hide behind a generic one is pretty common.

This is just a general try catch. Build happy path, get VC money and deploy. We'll fix it later.

Reply on news.ycombinator.com