i don't mean as an end-user, i mean as a developer.
What I want, as an end-user, is that if i program it for 2 minutes @ power level 5, for it to run at half-power for 2 minutes. No microwave oven I know of does that, so I suspect there may be an issue with running at less than full power. Let's take that as a given.
Thinking as a developer, I now have the task of running the oven for 2 minutes, but applying full power for 1 minute. I'm probably also looking at a minimum time of "engagement", i.e. the hardware guys tell me that the MTBF plummets if the engagement time is anything less than, say, 15 seconds.
Okay, now I have my parameters. Engage for 15 seconds, disengage for 15 seconds for 2 minutes. But I quickly -- and by quickly I'm comparing 5 minutes vs 30 years -- realize that for those last 15 seconds, the oven will not be engaged. Just spinning uselessly with the light on, but no heating taking place.
I then think to myself, "hey, as a developer, I could probably write a simple algorithm whereby the oven is always engaged when the timer starts, and when the timer ends."
And that may be a thought that has never occurred to any programmer of microwave ovens, ever, at any point.
so what gives? are there no "real" programmers programming these devices? is it all forestry majors and electrical engineers? (sorry, i think traditional-discipline engineers make crap programmers). Perhaps there are, ultimately, just one or two manufacturers of microwave oven control chips, and all the logic is built into there?
what gives? why is this so hard?