Some years ago I worked in the heady world of developer tools and learned the hard way that changes to an API that other people rely on must be carried out in a careful way. Failure to do so will result in people's code being broken or them being forced to do a lot of work and people being pissed at your product doesn't do sales any good.
Unfortunately, the newbie programmer cubs at Apple don't understand this. They obviously see API changes being a way of sweeping out old mistakes and replacing those ideas with the new-hotness of their own.
I despair of so-called "architects" who have no concept of how to maintain and develop code. Too many cub-programmers solve problems at the keyboard, that is to say that they type stuff in rather than draw a flowchart or "design" a coherent API. As a result, interfaces get changed, API's don't have consistent parameter usage, API's don't get consistent naming and so on.
Cubs are cute, they run around doing cute cub things and they are all fuzzy and lovely. However, when it comes down to the business of being a bear, the cub has a shitload of growing up to do and a lot of scars to obtain before they can be big and badass when they need to be. Hey Apple. Don't leave cubs in charge!
No comments:
Post a Comment