Programming & support
Work through software, SDKs, connectivity, and commissioning.
A15repliesJ9repliesI13repliesT1repliesF20repliesN15repliesL8repliesO3repliesS16repliesV0repliesH7repliesA4repliesF12repliesJ5repliesR0repliesT17repliesB1repliesL1repliesN8replies
4replies
our bad cover folder contains the same cover looking good
How should startup handle a verification it may already have sent?
The log gets busy and the status window goes quiet
The bezel passes when I stand on the other side
Why are we sorting three clocks and calling it an event sequence?
Why is an error response lighting the healthy indicator?
Same trim plate, migrating scratch
The quoted vision trial assumes our scratch labels are correct
Window blind masquerading as bezel damage
our offline status display is always cheerful
my handover assumes every pocket is full
Can I stop startup replaying work whose outcome we don't know?
The faceplate reference folder contains contradictory judgements
The handover covered Start and left out the awkward bits
the same faceplate is good on Monday's slide and scratched on Tuesday's
My bezel has a scratch shaped exactly like the window frame
Three reviewers labelled the same faceplate three different ways
I taught the green button and forgot the empty pocket
The old result won the race again