On Mon, Apr 20, 2009 at 2:14 PM, Earl Miles <span dir="ltr"><<a href="mailto:merlin@logrus.com">merlin@logrus.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Dries Buytaert wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
weigh in and participate in the review process. It is also important<br>
that you convince other people as why your patch should bubble up --<br>
this is something a lot of people can get better at.<br>
</blockquote>
<br></div>
This statement right here is what's wrong with Drupal core development. At this time, you must be better at debate, arguing and general Drupal politics than you are at actual code design and implementation.<br>
<br>
At one point 'talk is silver, code is gold' was the motto. But this has changed. Now talk is gold and code is defined by those who talk the best.<br>
</blockquote></div><br>The barrier for me isn't the complexity by any means. It's more the
politics and sheer stubborness required to implement change. I'm not a
politician. I'm a programmer.<br>