There is a point where you have the whole program in your head at once, one with it, and you don’t want to let it go, so you keep working in a marathon burst of energy. Memexplex

Saturday was a cold, rainy, dreary day. Wifey was watching her Lifetime movies, I had nothing constructive to do. Having worked in Eclipse/Java/Android all week (and sick of it), I was looking for something different.

Changing how data is stored/shared in the WebApps had been on my ToDo list for months, but I kept putting it off because I knew it would be a mammoth undertaking. Also, I have hesitated to implement cookies because everything I’ve read says how limited (useless) cookies are for storing data. Nothing could be further from the truth. Fifty variables and one very large string array easily fit within the 4KB limits of a cookie. Chrome developer tools make the task of checking cookie size quick and easy.

It started slowly, but I soon had the whole site in my head, at once, and would not stop until I had finished. After a 10 hour marathon coding session, it was complete. The WebApps now store session data in cookies instead of server memory. This will dramatically reduce or eliminate the “Session timeout” issue with the site.

So, now you can park on a page, get a cup of coffee, eat a doughnut, do some yoga, watch some YouTube clips, check your Facebook page, and then finish up your pk consult.

Enjoy

PS. Of course, I missed one page, the CrCl page (which I never use), and was immediately called out for it. I never hear from anyone who uses the site, except when they complain. Never a “thank you”, or a “good job”. In other words, just like any regular pharmacy job 🙂