7 Matching Annotations
  1. Nov 2020
  2. Oct 2020
    1. Anti-Features

      I don't think this is what Anti-Features means. Here he's listing things that this tool lacks, some of them being good things, like the "Does not require updating every time a new Ruby version comes out". That's a feature, not an anti-feature!

      Check out how F-Droid uses the term. Anti-feature means things that are present that aren't wanted. Undesirable "features" that are present.

      Unless they are just implying (but not explicitly saying):

      Anti-features that are not included

  3. May 2020
    1. except, as anticipated a little earlier, any custom services

      This seems like it might not be the correct way to use "anticipated". Seems like it is meaning "as mentioned earlier". Certainly an uncommon usage, anyway.

  4. Apr 2020
  5. Nov 2019
    1. Because they're more integrated and try to serialize an incomplete system (e.g. one with some kind of side effects: from browser/library/runtime versions to environment to database/API changes), they will tend to have high false-negatives (failing test for which the production code is actually fine and the test just needs to be changed). False negatives quickly erode the team's trust in a test to actually find bugs and instead come to be seen as a chore on a checklist they need to satisfy before they can move on to the next thing.