beestat
patreon
Cleanup and technical debt
🕑 Added 2019-11-05 15:01:00 +0000 UTCGetting the 1.4 update out the door was a huge step towards some awesome new features. However, as the project grows I have to take careful steps to clean up after myself as I go. This is kind of a pain, because sometimes that means taking something that already works fine and refactoring it with not much of an immediate payout.
The long-term benefits of doing this is getting cleaner code, reducing complexity, and reducing bugs. It's difficult to measure this, so as far as my users are concerned it often seems like nothing is changing. I like to actually make visible improvements, so I usually try to grab a couple feature or bug reports and sneak them into some of this refactoring.
Here are some things that I've worked on in the past two weeks:
- Fixed chart downloads and download filenames
- Removed a bunch of dead code since you can no longer change your temperature profile date range
- Worked on the web server configuration
- Switched a few charts out to a new interface which makes it much cleaner
- Responded to a number of bug reports from people unable to get into beestat
- Turned off some legacy servers and reduced hosting costs
- Re-verified all logging was working and kept an eye on server performance
If you want to see what I'm currently working on, check out GitHub issues that are assigned to me. I try to be diligent about updating this list.
I probably have another 1-2 weeks on some remaining items before I begin work on importing sensor data. The nice part about that project is that it should be relatively quick to complete a very basic version since there's not much complexity. I would love to have this on before the end of the year.
Comments
I have no problem with people jumping in and helping, but I'm not sure the best way to make that happen. In order to actually do anything meaningful, you would have to clone the project onto your own server and actually get it to work. That's theoretically possible, it would just take a few hours of effort to figure out all the quirks and document it. After that it's just a matter of figuring out good things for other people to work on and coming up with a process for merging those changes. If you want to try just let me know and we can give it a shot!
That’s great! With the disclaimer that I’m a Python wizard and not the best with other languages, do you need a hand with development? I could try to offer some help in refining or looking into stuff.
