emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: New maintainer
Date: Sun, 21 Apr 2013 15:22:43 +0200	[thread overview]
Message-ID: <8738ukow64.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87ppxoqhx1.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sun, 21 Apr 2013 18:47:38 +0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> It's also been a pleasure to witness the surprisingly successful
> marriage of two different coding styles: Bastien's damn-the-torpedoes
> patch-the-SOB-and-get-it-out-the-door approach, matched with Nicolas'
> return to first principles: structure and cleanliness. I'm quite
> convinced that the two approaches have been equally essential to Org
> mode's current success (and advance apologies for any perceived
> mischaracterizations!).

Yeah.

Let me quote Jamie Zawinski's interview from "Coders at work":

  Zawinski: [...] It's great to rewrite your code and make it cleaner
  and by the third time it'll actually be pretty.  But that's not the
  point---you're not here to write code, you're here to ship products.
  
  Seibel: Folks engaged in overengineering usually say, "Well, once
  I've got this framework in place everything will be easy after that.
  So I'll actually save time by doing this.
  
  Zawinski: That is always the theory.

  Seibel: And there are times when that theory is true, when someone
  has good sense and the framework isn't too elaborate, and it does
  save time.

I actually agree with both points of view, especially with the last
sentence.  And it's easy to play jwz when you can trust someone for
playing the other role :)

-- 
 Bastien

  reply	other threads:[~2013-04-21 13:22 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 16:53 New maintainer Bastien
2013-04-18 17:10 ` Jambunathan K
2013-04-18 18:10   ` John Hendy
2013-04-18 18:20     ` Bastien
2013-04-18 18:38       ` Jambunathan K
2013-04-18 19:48         ` Alan L Tyree
2013-04-18 20:07           ` Jambunathan K
2013-04-18 20:16             ` Alan L Tyree
2013-04-19  8:30             ` Tassilo Horn
2013-04-20  7:57               ` Jambunathan K
2013-04-21  8:06                 ` Jambunathan K
2013-04-21 12:41                   ` Carsten Dominik
2013-04-18 18:53     ` Jambunathan K
2013-04-18 17:19 ` Glyn Millington
2013-04-18 18:14 ` Aaron Ecay
2013-04-18 18:15 ` Rasmus
2013-04-18 18:23   ` Bastien
2013-04-18 18:20 ` Detlef Steuer
2013-04-18 18:26 ` François Pinard
2013-04-18 19:58 ` Alan Schmitt
2013-04-18 20:07 ` Thomas S. Dye
2013-04-18 20:13   ` Bastien
2013-04-18 20:16 ` Jonathan Leech-Pepin
2013-04-18 21:52   ` Tom Davey
2013-04-20  8:29     ` Ian Barton
2013-04-19  0:24 ` Charles Berry
2013-04-19  7:07   ` Suvayu Ali
2013-04-19  0:32 ` Bernt Hansen
2013-04-19  1:02 ` Yagnesh Raghava Yakkala
2013-04-19  4:12 ` Noorul Islam Kamal Malmiyoda
2013-04-19  6:09 ` Robert Klein
2013-04-19  7:00 ` Christian Moe
2013-04-19  7:58 ` Thank you very much Bastien! Hello Carsten! (was: New maintainer) Karl Voit
2013-04-19  9:36 ` New maintainer Thorsten Jolitz
2013-04-19  9:59 ` Sean O'Halpin
2013-04-19 11:33 ` Charles Philip Chan
2013-04-19 12:52   ` Adolfo Benedetti
2013-04-19 12:53 ` Rainer Stengele
2013-04-19 14:30 ` Russell Adams
2013-04-19 16:04 ` Christopher Allan Webber
     [not found]   ` <CAFChFyjpy2R10gJmxJ-DKDbAVjj6MnD5JN+vX5bY5MvHbf3z3w@mail.gmail.com>
2013-04-20  1:03     ` Fwd: " Gary Oberbrunner
2013-04-21 10:24 ` T.F. Torrey
2013-04-21 10:47 ` Eric Abrahamsen
2013-04-21 13:22   ` Bastien [this message]
2013-04-21 14:08     ` Eric Abrahamsen
2013-04-21 18:04 ` Andreas Röhler
2013-04-21 22:39   ` Bastien
2013-04-22  7:57     ` Andreas Röhler
2013-04-21 22:18 ` AG
2013-04-22 10:27 ` Julian M. Burgos
2013-04-22 16:53   ` Jay Kerns
2013-04-22 16:55   ` Matt Price
2013-04-23 16:46 ` Jason Dunsmore

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8738ukow64.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).