I think what threw me is the "grinder off" button with a red light. The red light made sense in the context. But, if I were designing this, I would have a "grinder" button with a green light that was default "on", indicating that grinding was imminent. There was no green light on this part. It was red or off.
That would have been consistent with the rest of the interface, where a green light on the "brew" dial meant the timer was set and a red light meant the coffee had brewed.
I have a hot water stand-by boiler in my kitchen a $15 outlet switch because the darn thing didn't come with a simple power button. Hardly anything these days does. All of which is to say, the ideal design often conflicts with the consumer's other expressed preference of "lowest price possible, it doesn't matter how many corners are cut and how quickly it dies".
So many things should be "preserved state" switches, but people put up with it. Not sure why.
That coffee maker is well designed for its intended happy path use case, which is not the same as you can say for this Oracle software.