• 0 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: September 11th, 2023

help-circle



  • I disagree unless the tests are reasonably high level.

    Half the time the thing you’re testing is so poorly defined that the only way to tighten that definition is to iterate.

    In this sense, you’re wasting time writing tests until you’ve iterated enough to have something worth testing.

    At that point, a couple of regression tests offer the biggest bang for buck so you can sanity check things are still working when you move on to another function and forget all about this one




  • Teams is relative.

    At a previous job (Microsoft shop but in the public sector so 10 years behind), the standard messenger when I started was Skype for Business.

    In case you’ve never used Skype for Business, it’s “Skype” in branding only and actually has nothing to do with the Skype software that Microsoft purchased and is more like MSN Messenger.

    Compared to that, Teams is a huge step up.

    Also, at a Microsoft shop, you have to use what Microsoft provides even though it’s usually balls.

    It’s 90% of the reason I now refuse to work anywhere that’s bought into the Microsoft ecosystem. It’s just so… mediocre













  • Err, no? At what point did I claim to be an expert?

    It doesn’t take a genius to realise that serving 100-record chunks of a billion record dataset using limit 100 offset 582760200 is never gonna perform well

    Or that converting indexed time columns to strings and doing string comparisons on them makes every query perform an entire table scan, which is obvious if you actually take the time to look at the query plan (spoiler: they don’t)

    “Why can’t the system handle more than 2 queries per second? This database sucks”