• Reader9@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    That makes sense that it’s easier to flash directly since there are so many different parts and variations to the actual destination hardware.

    I read that one of Toykeeper’s original design decisions was to separate out the generic UI code from the specific code that interfaces with the hardware (being vague due to lack of knowledge). Maybe it would be possible to incorporate some testing code that only evaluates the user inputs compared to expected outputs within the Anduril layer? Such as a single state transition like “when multi-channel is enabled and user selects 4H, selected output level is equal to turbo”. Such a test could be indicate unexpected behavior when UI code is being customized.

    Just adding to the imaginary backlog here!