The management answer is that you compare yourself against your peers using qualified metrics. You stop sucking when your numbers are high enough on your organization's bell curve. Most developers can't measure things, and most organizations won't train them, which limits them to forever sucking at what they do.

But by then it becomes a number game and it stops being about quality but about optimizing given metrics. If you can you should always strive to suck less. If you can't then it's time to maybe seek some other working environment which will enable you to do so.

I have had the opportunity to try your optimized JS code and it sucks tho. It is almost comedic seeing you bragging about such a "blazing fast" bad app.

Sucks how and do you have an example of a React SPA that executes faster?

Sucks as not being interesting enough for the fast load to be worth anything. Why compare it to React, if React is shit?

So I take it the application works well for you but you aren’t interested in home server administration and that you have no examples of any SPA that is faster.

It would have been more helpful had you said that, because otherwise your comment just sounded like empty whining.

well you can take it the way you want to feel better, that was not the case tho. And the code was even worse than the results, lots of boilerplate. I don't want to be mean, but it is funny to see you brag so much about bad code that you think is good.