Quote:
Originally Posted by TechniSol
I think people are just tired of the overall pattern of one step forward, two steps back that seems so prevalent with Kobo firmware upgrades. My opinion is that more time should be spent on what we called Systems Analysis and Design 101 back in the day.
They seem to waste a lot of time trying one thing and then reversing themselves in the next update rather than spending a little time getting their bearings or presenting alternatives to a focus group for feedback prior to implementing full blown versions and then having to back peddle because they blew it. I guess this can't be viewed as anything but critical, but it's not said in a negative way. I'd like to see them do better, and think they really could if properly lead or allowed to do their jobs. I often wonder just what the stumbling blocks are at Kobo? They're obviously skilled enough to roll out entire new basic interfaces, why can't they figure out the details before committing resources foolishly and having to endlessly back peddle and tweak?
|
My opinion is that they are afraid to start over. Someone posted that the last update was to get rid of unused code segments. This can be quite a task if you not the only programmer working on a project and have not worked on all parts. Even worse if several people are doing it at once. Not easy even if it is all your code.
This is a point where one competent person should be allocated the task of starting over one step at a time. Don't just grab chunks that you think might be working and copy and paste and link them together. Don't assume that every library routine is perfect. Keep it nice and keep it simple. A person once taught me a lot about programming and soldering and circuit board design. For all three his motto was "If it looks good, it usually is good, make it neat and shiny"
Helen