public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: alternative to thunderbird?
Date: Wed, 22 Feb 2012 12:56:47 -0800	[thread overview]
Message-ID: <CAN0CFw1cz0CGry56fgQBkLWY8NzP92WdtVPekyCt57W3T6tKmw@mail.gmail.com> (raw)
In-Reply-To: <20120222221405.0b0da8b9@khamul.example.com>

>> > kdepim devs are just making a simple classic mistake that's
>> > been made over and over and over again. Developers do not learn from
>> > history, every time this mistake is made the team doing it thinks
>> > *they* will be different.
>>
>> What is that classic mistake?  Is it the shark jumping thing?
>
> No, the mistake is the mistakes that are always made on the second
> big project. You'd have to read "The Mythical ManMonth" to truly do it
> justice (it's a really good book for developers btw), but in a nutshell
> it goes like this:
>
> For your first big project, you will proceed very slowly and carefully
> and not take on too much, as you know you know nothing. You will
> probably make a project that does one thing and does a decent job of it.
>
> Enter the second project. Buoyed by the success of the first, most devs
> will try and build something that is waaaaaaaaaay beyond their
> capabilities - I mean, how hard can it be right? It will over-reach, be
> unbuildable and timeframe estimates will be bat-shit crazy insane.
>
> The attrition rate of second big projects is rather large.
>
> Enter the third project. Humbled by the experience of the second and
> still feeling quietly (and realistically) confident by the first, most
> devs will settle down to something useful, of wide scope and still
> achievable.
>
> This same rule seems to apply to almost every project a bunch of humans
> could tackle.

Brilliant explanation.  Thank you for taking the time to write this out.

- Grant



  reply	other threads:[~2012-02-22 20:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-18 20:28 [gentoo-user] alternative to thunderbird? Grant
2012-02-18 20:36 ` Alan McKinnon
2012-02-18 20:44   ` Michael Mol
2012-02-18 21:06   ` Grant
2012-02-19  0:40     ` Grant
2012-02-19 11:26       ` Alan McKinnon
2012-02-18 20:37 ` Michael Mol
2012-02-18 21:26   ` Alex Schuster
2012-02-18 22:02     ` Alan McKinnon
2012-02-18 20:42 ` Alecks Gates
2012-02-19  1:30 ` Michael Trausch
2012-02-19  1:38   ` Grant
2012-02-20  6:58   ` Fuzz
2012-02-20 18:11     ` Jorge Martínez López
2012-02-20 21:33       ` Alan McKinnon
2012-02-20 23:24         ` Neil Bothwick
2012-02-20 23:39           ` Alan McKinnon
2012-02-22  0:56         ` [gentoo-user] " walt
2012-02-22  6:55           ` Alan McKinnon
2012-02-22 17:26             ` Grant
2012-02-22 20:14               ` Alan McKinnon
2012-02-22 20:56                 ` Grant [this message]
2012-02-23  0:21                 ` Peter Humphrey
2012-02-23 14:23                   ` Juan Diego Tascón
2012-02-19  3:09 ` [gentoo-user] " ny6p01
2012-02-19 10:09   ` Mick
2012-02-19 16:02 ` [gentoo-user] " Grant Edwards
2012-02-19 18:01   ` Michael Orlitzky

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

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

  git send-email \
    --in-reply-to=CAN0CFw1cz0CGry56fgQBkLWY8NzP92WdtVPekyCt57W3T6tKmw@mail.gmail.com \
    --to=emailgrant@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox