imagesbyjas
lvl.4
Flight distance : 286198 ft
Offline
|
Talking about two different things (and sorry if I wasn't clear). I DO agree that the release notes are at best thin. My comment was broadcasting the full scope of an issue when found. Doing that could also lead to additional breaches in security, reduction in sales, changes in marketing direction (if something turned out to be really severe), etc. I too managed development and test, at a very large company.. testing was no less strict, code releases and life cycle management from start to finish managed daily and even with ALL that in place mistakes happen.. It can be architectural/design in nature, human error, the ever present "one ore line of code", etc. Point is development is not perfect. Testing sometimes worse (testing always seemed to suffer) :-( ...
Want cannot happen (and what I fear I'm seeing happen) is that we now have a somewhat fragile code base and multiple configurations that are being serviced by one base code set. I understand the need for modularity.. It is a bedrock principle in coding these days, but that only works if the base is solid and where modules have clean and clear input and output designs.
I'd much rather have DJI slow down.. Get back to a rock solid code base and work from there. To add problems on top of problems only creates more problems on top of problems and fixes on top of fixes.
NOW all this said, I do not for an instant pretend to know just how complicated this code base must be. I cannot imagine the amount of data that has to be processed - realtime (not in batch) - to make these things do what they do. Telemetry programming is a science onto itself.. One I can't imagine the depths of.. Which is why I'm cutting them "some" slack... but they must see that patience is wearing thin.. IF (and this is the big question after all) they truly care, they'll recognize, reorganize, re-architect, re-code, etc. Do what's necessary to get a handle on this.. The sad truth otherwise, in these days of much less customer loyalty, is that people will take their business elsewhere and not lose a wink of sleep over it.
Again (as I mentioned earlier).. Windows is a perfect example.. Think of how many different code bases that continue to have to be supported, in part, because the later version was built on an older one.. A problem deep in the earlier code effects them all.. and try unwinding that code to figure out where the issue is. |
|