From: Mark Alan Date: Mon, 07 Mar 2011 13:21:50 +0000 Subject: Re: [mlmmj] Encouraging Message-Id: <20110307132150.28cee71d@desk.localhost.localdomain> List-Id: References: <4D74AE5F.1030708@yahoo.com.au> In-Reply-To: <4D74AE5F.1030708@yahoo.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: mlmmj@mlmmj.org On Mon, 07 Mar 2011 21:07:27 +1100, Ben Schmidt wrote: > Someone raises an idea or asks for > feedback, and most replies are negative or just dismissive. (And I do > realise I am an offender, too.) When we have so much of a good think like mlmmj certainly is, it is only natural to resist any attempts to change it. That resistance will be even greater if the changes, while not being urgent (like security fixes), were not properly debated, or not clearly explained and understood. > Voicing concerns is, of course, really important. But it would be > really great if we could at least try to see the good points in > people's suggestions, and encourage our fellow developers by > acknowledging these good points. You are right of course. But what about seeing the fellow developers explaining better why they think that a change or a new feature is better. > negatively impact us, but we merely see it as unnecessary or we don't > want to use it, it would be better to remain quiet than say something > negative. Even iron wouldn't be hardened into steel if it would not for the many cycles of heating, hard hammering and water cooling. > much, send a note privately. But honestly, how much time does it take > to read a reply that says "I like this idea" or "Me too" and whack > delete? You are right on target here. > When we do voice concerns, it would be great if we could think about > what the developer was trying to achieve Here I disagree. The developer should be the one trying hard to explain what he was whiling to achieve. The developer should be the one asking for help where he thinks he needs help to achieve it. > include in our reply an idea or two for how they could achieve their > desired result while avoiding whatever we thought was problematic. I couldn't agree more. As a general principle in a software development project no one should criticize without offering an alternative idea, or a proper definition of the problem at hand > Just something to chew on. And a very good one. Keep up the good work. M.