Live data from Hacker News

Viewing profile — drothlis

drothlis

HN member
Joined
Sun, Feb 15, 2009, 11:36 PM UTC
HN karma
720
Public activity
261 items

About drothlis

https://stb-tester.com/ | https://david.rothlis.net/ | david@rothlis.net

Recent public activity

  1. comment
    Comment #41943583

    > Claude's ability to count pixels and interact with a screen using precise coordinate I guess you mean its "Computer use" API that can (if I understand correctly) send mouse click…

  2. comment
    Comment #41943292

    I noticed in your demo it generated the prompt "tap on the 'Log in' button located directly below the 'Facebook Password' field". Does your model consistently get the positions rig…

  3. comment
    Comment #39510512

    Beautiful.

  4. comment
    Comment #39407601

    https://en.wikipedia.org/wiki/Characterization_test aka snapshot tests.

  5. comment
    Comment #35230200

    According to the ViperGPT paper their "ImagePatch.find()" uses GLIP. According to the GLIP paper,† accuracy on a test-set not seen during training is around 60% so... neat demos bu…

  6. comment
    Comment #35039106

    Could you implement (some of) astroid's inference using stack graphs? [1],[2] That would allow a lot of caching optimisations, as you can "index" each file in isolation. [1]: https…

  7. comment
    Comment #34967167

    It side-steps the problem of git conflicts, I suppose. You'd have to use their tool (`touca diff`? I don't know if that exists) instead of `git diff`.

  8. comment
    Comment #34967088

    Some ideas I got from Jeremias Rõßler's talk: https://t.co/xWtA58Q9q5 - Snapshot testing is like version-control but for the outputs rather than the inputs (source code). - Asserts…

  9. comment
    Comment #34503420

    Obviously a sensationalised title, but it's a neat illustration of how you'd apply the language models of the future to real tasks.

  10. story
  11. comment
    Comment #34438511

    Think systems integrators and compliance tests. I would imagine that each of the individual systems being "integrated" do have their own unit tests, upstream, in their own repos.

  12. comment
    Comment #34414234

    Some good ideas here for when your tests are in a separate repo than the system under test (GPUs/drivers/compilers in the case of the author, but it's applicable to a variety of in…

  13. story
  14. comment
    Comment #34399733

    Related: I think it was Kernighan & Pike's "The Practice Of Programming" where I read the idea of testing a complex implementation by comparing its output against a simpler but les…

  15. comment
    Comment #34399695

    Interesting thought, somewhat related to the articles on "snapshot testing" that have been trending on HN lately.

  16. story
  17. comment
    Comment #34399145

    "Regression testing" can also refer to a process: When the QA team says they're doing regression testing, it means they're testing that existing functionality hasn't regressed (as …

  18. comment
    Comment #34388466

    In the article they don't change /etc/machine-id, but APT::Machine-ID in apt.conf.

  19. comment
    Comment #34384327

    https://approvaltests.com/

  20. comment
    Comment #34381844

    ...and my favourite term, "characterization test": https://en.wikipedia.org/wiki/Characterization_test "Regression test" means something else, at least at the companies I've worked…

  21. comment
    Comment #34352789

    I realised this is another example of "trees" as first-class citizens in a build system. In my comment above the tree we're passing around is a docker layer; in my LWN article it's…

  22. comment
    Comment #34352078

    I suppose they're ideal for cases where there's a simple, obviously correct but slow implementation that you can use to test a more complex but faster implementation.

  23. comment
    Comment #34352062

    Fixed your link to the full article: https://lwn.net/Articles/821367/ OSTree is still working very well for us. At the time I wrote the article we had been using OSTree (and the bu…

  24. comment
    Comment #34351342

    P.S. They're also great for writing tests for new code, for many of the reasons described in the OP.

  25. comment
    Comment #34351327

    I'm not the OP but I think Fibonacci is a contrived example. In practice these "characterisation tests" are great for adding tests to an existing codebase. The "snapshot" just reco…