3 ms·
I did it at least once for a credit card terminal. The application saved state to internal database, and even if you cycled power it would just come back to th
by lmilcin 5y ago
I did it at least once for a credit card terminal.
The application saved state to internal database, and even if you cycled power it would just come back to the same screen and same state it was before power cycle.
This wasn't to deal with memory problems (in fact, it had no dynamic memory allocation at all) but rather to deal with some crappy external devices and users that would frequently power cycle things if it didn't progress for more than couple of seconds.
- IshKebab 5y agoSo now if your code gets into a broken state users have no way to fix it. Awesome.
- lmilcin 5y agoDon't make it possible to get your system into broken state? Why everybody assumes every developer doesn't know what they are doing just because most of them don't?
- notriddle 5y agoBecause most developers also think they’re one of the rare exceptions.
- IshKebab 5y agoWhy do so many developers assume that they are the perfect ones who never make mistakes? They think that their programs have no bugs despite the overwhelming evidence that all programs have bugs. But no. Not theirs. Literally all other programmers are idiots and only they write perfect code.