- Joined
- Jul 16, 2009
- Messages
- 5,071
- Reaction score
- 8,108
FWIW -
I have provided what amounts to pages of feedback on improvements and shortcomings that I identified during my time using the ReefBit. Some here, some on on FB and piles of them private to Hady.
I don't wish to rehash them all, but one of the biggest sore spots for me is changelog and software update policies.
First and foremost, it is absolutely essential and imperative that RK immediately implement a change log where every... I MEAN EVERY code change short of spelling corrections is PUBLICLY LOGGED and the VERSION NUMBER INCREMENTED.
This means reagent tweaks, calibration tweaks, bug fixes... EVERYTHING. I don't care if it is 17 times a day.
As it stands, RK constantly tweaks things with the app code and possibly device firmware, both at a global level and to my understanding per individual users devices or app profiles.
Not being 100% transparent and upfront about changes (any changes) or fixes puts the user at both a disadvantage with regard to not having the option of accepting or declining changes, especially if they are happy with their current performance and features. Secondly, it prevents the end user from identifying breaking changes or tweaks and bug fixes that may negatively (or positevly) affect them. Example - you go from acceptable readings for a week and then suddenly things go wonky. Is your tank going wonky, are the reagents going bad, or did RK push a tweak that affected your readings.?
Moreover, RK needs to be 100% transparent with EACH and every user to which they have made individual profile or settings tweaks. Same reasons as above.
This is software development 101 for a device of this complexity and deployment architecture. Until RK implements such a system, I wouldn't trust the software and stability further than I could throw the ReefBot.
Lastly - there really needs to be a "calibration" feature that allows the end user to SCALE results. That way if, for example KH is reading consistent, but 1.5 dKH LOW for a batch of reagent, then one could simply tell the ReefBot to scale the results by an additional 1.5 dKH.
Have a nice evening.
I have provided what amounts to pages of feedback on improvements and shortcomings that I identified during my time using the ReefBit. Some here, some on on FB and piles of them private to Hady.
I don't wish to rehash them all, but one of the biggest sore spots for me is changelog and software update policies.
First and foremost, it is absolutely essential and imperative that RK immediately implement a change log where every... I MEAN EVERY code change short of spelling corrections is PUBLICLY LOGGED and the VERSION NUMBER INCREMENTED.
This means reagent tweaks, calibration tweaks, bug fixes... EVERYTHING. I don't care if it is 17 times a day.
As it stands, RK constantly tweaks things with the app code and possibly device firmware, both at a global level and to my understanding per individual users devices or app profiles.
Not being 100% transparent and upfront about changes (any changes) or fixes puts the user at both a disadvantage with regard to not having the option of accepting or declining changes, especially if they are happy with their current performance and features. Secondly, it prevents the end user from identifying breaking changes or tweaks and bug fixes that may negatively (or positevly) affect them. Example - you go from acceptable readings for a week and then suddenly things go wonky. Is your tank going wonky, are the reagents going bad, or did RK push a tweak that affected your readings.?
Moreover, RK needs to be 100% transparent with EACH and every user to which they have made individual profile or settings tweaks. Same reasons as above.
This is software development 101 for a device of this complexity and deployment architecture. Until RK implements such a system, I wouldn't trust the software and stability further than I could throw the ReefBot.
Lastly - there really needs to be a "calibration" feature that allows the end user to SCALE results. That way if, for example KH is reading consistent, but 1.5 dKH LOW for a batch of reagent, then one could simply tell the ReefBot to scale the results by an additional 1.5 dKH.
Have a nice evening.