|
I'd still buy the Kobo first too, they have features I just plain like. I wonder that they just don't get the chance to sit down and flesh out the overall look and feel and kick it around long enough for everyone to take potshots and force the design failings to get addressed up front, or something like that. I've always taken every opportunity to seek feedback before committing further resources to a design. There is nothing more beneficial than letting others take a shot at kicking your design in the teeth. It builds character and forces you to be critical of your own work. There is also nothing like the feeling of getting it right when you throw it out on the sacrificial altar and it's bulletproof because you busted your hiney and ran every problem down yourself.
As far as cleaning up code, it should be the responsibility of each module's coder, IMHO. If the original specs for I/O are properly envisioned and the purpose for sections clearly understood, and don't need to be redefined on a minute to minute basis because of feature creep it's not unmanageable and likely easiest for the original author of the code. But then it's easier for me to say that as I've always done each step from system analysis and design down through coding and testing myself, usually while building hardware prototypes and often laying out PC boards, so in fairness any changes ripple through me as easily as changing hats from one aspect of the job to the next.
Frankly, it's usually hardest for me to stop working, and start again as I have to take a little while to reconstruct the whole gestalt of the project in my head each time and how each change or addition will affect all other parts of a design and then narrow my scope to the particular task I'm performing.
Obviously harder to do for a larger shop, and when you must deal with others, etc. I've been blessed to have good help and good guidance when I've needed it. Not everyone can say that. I've been lucky to work with people that I could hand tasks off to and expect they'd either complete them properly on their own or or be sensible enough to ask for clarification or help. I think you have to get people into the mindset that ego is not important and that all that matters is the task at hand. No one likes to make mistakes, but if you can foster a sense of teamwork and the idea that you will all laugh together or not at all and help each other it goes a long way. Either the team succeeds or the team fails, but they do it together. Only the guy at the top of the pyramid gets to have an ego, and he knows how to keep it in check because he is only afterall a member of the team.
|