Bugs bugs bugs
Added 2019-08-06 14:01:00 +0000 UTCSee those errors? Those are bad.
One of the things I try to focus a lot on with beestat is making the software robust. Every time someone encounters an error they are more and more likely to give up on the product and leave. Even though beestat is free, I still don't want to let people down and hate when I've caused them a problem. I want to have the best thermostat analytics app and having frustrated users is not the way to achieve that.
Additionally, every time there's an error it means I have to fix it. If I'm fixing bugs then I'm not developing new features. I don't like that, either.
So as I develop I try to test as carefully as I can. Of course, sometimes I miss things and that's OK. But that's why I have ways of tracking them.
JavaScript
I use a service called Rollbar to track JavaScript errors. Every time something goes wrong, a full report and stack trace is set to this service. This helps me aggregate problems; I also get emails when things happen.
API
I do not currently use any third party service to track API errors. I need to add these to Rollbar, but for now I just log all of them in my database and remember to check periodically.
Fix all the bugs!
You may have been the recipient of some of these bugs lately. If so, I apologize! Error rates have been up recently and I am definitely aware. I've pushed out lots of little changes over the past few weeks and that's resulted in a number of issues that I will be working to resolve this week.
For everyone who has reported bugs: thank you! Please keep doing so. I'm beginning to settle in and make some plans for beestat this fall. Part of that is improving stability and evaluating server needs for all the features I want to add.
