Here are some good questions I ask myself with projects:

• Does it even function? (Either user or unit testing)
• In terms of web development: Is it mobile/desktop friendly?
• Would it easily break if I handed it off to someone else, or if a client-side user got creative?
• Did we check for human error using the linting process?
• Can I put this project down for a week, come back, and be able to pick it up again without digging through source files deciphering meaning?

If I can successfully say yes to all of these (except no to the 3rd), I'd be content enough with the project to let other people see it 👀😅

I'll tell you how I judge other people's code, and that's by how much I can strip out.

It never ceases to amaze me in anything from a code review – or in larger cases a refactor – that you can routinely remove around 10% - 50% of the codebase because it's either not needed, the problem can be solved more simply, the problem did actually not need solving in the first place, or as in many surprising cases, the code was doing absolutely nothing apart from making it look like they'd done lots of work.

It is obvious to test the code before and after code deployment to public servers. Testing is necessary to make sure if your code is working fine in every configuration. There are many online platforms available from where you can test your creation on the go. One of platforms is LambdaTest to test the cross-browser compatibility of the web app.