After all, we programmers write bug free code, don't we?īut, I think we are getting off the topic. And testing is one of the favorite things to get reduced. And stuff gets cut to allow the project to meet the targets. Then there is the problem that all this was based on someones estimates. Hence bugs, bad design, missing features creep in. When doing this, you start to move away from the ideal that was originally envisioned. Sometime they allow something to be remove. The stakeholders will manage to add things without adding time. Yep, that's how it is supposed to be done. If this doesn't happen, then they are not running projects properly. The project owner should be empowered to say no, if agreement cannot be reached. If they wish to vary/increase what the project is tasked to deliver, then they need to allow more resources and/or time. Probably getting too deep into project management, but, one of the first tasks of a project is to get signoff, by the stakeholders, on the project deliverables. And frequently the team gets told they must put a particular fix or feature in but then don't get the chance to test it. But, there eventually gets a point with development projects where the release timing gets taken out of their hands. I am sure from comments made by them that this firmware was planned for a lot earlier. To the Kobo developers, all I'd say, is that you guys need to worry less about when updates occur and more about them being ABSOLUTELY bulletproof before announcement, let alone release. I think ultimately, we need to remain grateful that they are bothering to continue updating firmware on products that have been superseded by newer versions. I updated from 2.0.0 and I still have no idea what people were complaining about with that version, unless it was as petty an issue as pages turning more slowly. I think we just need to be patient and give them time to resolve the issue before they continue the upgrades.
Kobo touch update#
On the upswing side of things, I have 2.1.4 via wireless update and it works great near as I can tell, but I am not yet using an SDHC card nor am I actively pursuing how it might fail, I am merely enjoying reading with it and the bonus of faster page turns. I greatly admire that they aren't abandoning older devices as they roll out newer, but they have to get hold of this tiger's tail and stop releasing firmware that is found to be buggy or lacking almost overnight.
Kobo touch code#
Seems to be the Aussies mostly, so maybe their version was different due to a wireless hardware issue due to different frequencies being used or something along those lines(pure conjecture.) This has apparently been compounded by finding problems with readers with side loaded content on SDHC and is causing the delay in further rollout of the current 2.1.4 firmware, or so I gather.įrankly, I think someone at Kobo needs to beg, borrow, steal or quietly buy back some affected units so they have in house at least one of every model that ever differed in any way for future testing and clearance of any revised code and basically get all their sh-t in one sock before they look like bigger bozos.
Kobo touch software#
No one really likes to branch unless necessary, because of the extra work of having to apply any new updates to multiple versions of base code and test them separately.Īll that said, near as I can figure from posts I've read is that there exists either a hardware difference on some readers or software difference in firmware 2.0.0(there were apparently 3 versions, A, B, C) that forced Kobo to produce a 2.0.4 necessary to allow an update to 2.1.4 on some range of devices. However, if codespace is an issue, or hardware versions diverge too radically then separate firmwares make more sense.
It's a lot easier to maintain one and not have to update code in several versions and track in each which updates or revisions have been applied. It usually makes a lot more sense to keep one base firmware and simply allow/disallow or ignore certain things based on switches in the code that correspond to what hardware the code is running on and enable or process sections of code only if allowed.