From: Martin H. <ma...@he...> - 2005-08-25 10:17:34
|
Hi Mike, Mike Noyes wrote: > On Wed, 2005-08-24 at 15:51, Martin Hejl wrote: > >>In the end, I tend to agree with Luis. I'm not going to tell anybody to >>stop discussing new possibilities - but discussion without the >>ability/willingness to actually do more than just discuss things is >>pretty much what I contribute to management these days (I spent a fair >>share of my work time in meetings with people who discuss things they >>neither know how to do, nor would they be willing to provide the >>manpower to get it done - they just like discussing things). Maybe >>that's why I'm very skeptical about the value of discussions all by >>themselves. Discussing how to solve a problem at hand is perfectly fine, >>and usually also very useful - but discussing things despite the fact >>that every participant of the discussion has a different idea of what >>the actual issue one might be discussing is something else... > > > Martin, > That excludes me from any comments regarding leaf development, and > relegates me to irrelevance. I'm not a programmer, or knowledgeable > compared to most of you. :-( that surely wasn't the point I was trying to make - and I'm pretty sure you know that. We all appreciate your work and input - leaf is a group effort, not something that's done by a couple of coders. People don't have to be programmers to be able to express their ideas on leaf-devel, or pass some sort of a test or anything like that, and that's a good thing. I was merely trying to point out that discussions like that often develop a life of their own and become disconnected from what's actually happening on the development front. >>Again, maybe I just see too much of that kind of thing in my day job, >>and are therefore unable to see the honest attempt to find the best >>technological solution for leaf. If that's the case, I sincerely >>apologize for my cynicism/sarcasm. > > > No need for you to apologize. You've contributed lots of time, effort, > and code to LEAF. True, but people who write code can misunderstand something too, or read too much into something. Martin |