+1 to Linus When you code for anything, you code for the sake of being used by anyone. This person (who use your software) wants it to be WORKING. So, if anything gets broken, its developers respponsability to fix it.
And, of course, if your software is not useful, no one will use it, so.... try to enhance it :) On Wed, Sep 28, 2011 at 11:56 AM, Aleksey Bragin <alek...@reactos.org>wrote: > FYI: > > This is Linus' interview. > http://h30565.www3.hp.com/t5/Feature-Articles/Linus-Torvalds-s-Lessons-on-Software-Development-Management/ba-p/440 > > He very correctly outlines many things. One of the most important: > "The other thing—and it's kind of related—that people seem to get wrong is > to think that the code they write is what matters. No, even if you wrote > 100% of the code, and even if you are the best programmer in the world and > will never need any help with the project at all, the thing that really > matters is the users of the code. The code itself is unimportant; the > project is only as useful as people actually find > it<http://h30565.www3.hp.com/t5/Feature-Articles/6-Products-That-Became-Technology-Roadkill/ba-p/36> > .” > > And this: > "Way too many projects seem to think that the code is more important than > the user, and they break things left and right, and they don't apologize for > it, because they feel that they are ‘fixing’ the code and doing the right > thing.” > > > WBR, > Aleksey Bragin. > > _______________________________________________ > Ros-dev mailing list > Ros-dev@reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev >
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
