Tests.
Target the “business logic”.
You can structure your code to facilitate unit or integration testing.
Setup tests for the key functionality. Whenever a bug gets reported, create a test or test case to address that bug, fix the bug, and ensure the test now passes.

Have a staging environment, so the site can be interacted with and tested without touching anything in production.
You can push to this often, and request some help with QA to ensure nothing is broken.

Have a testing environment. Again, a complete duplication of the infrastructure.
Set up end-to-end tests. These automate interactions with the entire application.
Have tests that run against key features. “Setup appropriate state, load form page, fill in form, click button, check that database entries are correct”… “setup appropriate state, check that submission summary shows correct data”.
These are quite handy, but a lot slower and fragile than unit and integration tests.

There are automated testing platforms that can capture a “good” state of a website, then use image matching to ensure further runs visually match what it should look like.
These are normally expensive and finiky.

Hopefully you will get to a stage with your testing that your unit and integration tests catch 90% of your potential bugs, and e2e tests will ensure the core functionality is working correctly.
Then, as you do a bunch of work, you can run your tests, see they all pass, and be confident.

Finally, I will say that tooling like frameworks and typescript can catch a lot of these errors quite quickly.
However, these won’t catch logic bugs - which is what tests are for.

The 2nd quote does.
They are investigating, and don’t want to list anything because it’s all up in the air.
If they listed alternatives, the discussion would be based about them, the pros/cons etc. They also explicitly state they don’t want suggestions.
This seems like a formalised information post about previous discussions, rather than anything concrete.

Whatever backend/service they use will also dictate the app used to access it.
For example, if it’s a forum based software then jerboa isn’t going to be able to interact with it at all (as jerboa is specifically for lemmy).

DVI and HDMI are actually the same video signal. Which is why adapters are so cheap.
DP can carry an HDMI encoded signal (and thus a DVI signal), which is why DP->HDMI and DP->DVI adapters are so cheap. It’s called DP Dual Mode or Multi Mode or something like that.
I haven’t encountered a device that outputs DisplayPort that cannot output the Dual Mode HDMI encoded signal as well.

HDMI/DVI->DP is an active conversion - ie it is re-encoding it. Which is why the converters are significantly more expensive.

However, it’s all digital. If the signal quality degrades, it will be very obvious because it stops working (sparkles on a black screen, lines, flashes, all sorts).