How Not To Deal With Data In Java

If you have ever asked yourself, “Self. How should I really screw up an application that otherwise works pretty well,” and you weren’t sure what to answer, I can tell you. What you do is you use serialization for several large data structures and allow the serialization code to stay in the code long after you should have replaced it with a database.
Needless to say, that’s precisely what I’ve done with HotSheet and I’m paying for it now. If you allow yourself to get up to many hundreds of news items in your list then performance is poor, startup time and shutdown time suffer, and best of all, if there is a crash or other event that causes HotSheet to exit without getting a chance to save, you are thown back to whatever the last saved version of everything was. Ow…