• 0 Posts
  • 10 Comments
Joined 1 year ago
Cake day: June 9th, 2023
  • towerful@beehaw.orgtoWeb Development@programming.dev•Avoiding tunnel vision when debugging
    7·
    10 months ago

    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.

  • towerful@beehaw.orgtoTechnology@beehaw.org•DisplayPort: A Better Video Interface
    4·
    10 months ago

    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).

  • towerful@beehaw.orgtoAsklemmy@lemmy.ml•Who was worse: The Nazis or the British Empire?
    3·
    11 months ago

    How about, they were both utterly terrible?
    Like, what does it matter?

    British Empire were shits, enslaved people, stole relics/art/wealth, murdered people, tortured people, probably experimented on people.
    Nazis were shits, enslaved people, stole relics/art/wealth, murdered people, tortured people, experimented on people.

    The Nazi’s atrocities are certainly better documented.
    Both because they are more recent in history, and because they were the losers. The winner’s atrocities were less likely to be documented throughout history.

  • towerful@beehaw.orgtoSteam Deck@lemmy.ml•[MOD] SteamDeck upgrade to 32gb of ramEnglish
    1·
    11 months ago

    It’s because ram is even faster with lower latency.

    Pcie4.0x4 nvme is 40Gbps (I presume you mean pcie4.0 which is the newest and greatest over pcie3.0).
    And that’s if it can actually sustain that level of read/write consistently, and isn’t just dumping data into a buffer.

    DDR3 1333mhz is 80Gbps (which is 15 years old).
    DDR4 2133 is 136Gbps.
    These are just rough numbers. Actual throughput is going to depend on number of channels, mobo, CPU etc.