linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Krause <xerofoify@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: Work on ext4
Date: Mon, 28 Jul 2014 11:17:45 -0400	[thread overview]
Message-ID: <CAPDOMVijNtsfZwEn_D41ZU82KJ4W7dcjPMj4Pi6XkVpfR8PzeA@mail.gmail.com> (raw)
In-Reply-To: <20140728124523.GM6725@thunk.org>

On Mon, Jul 28, 2014 at 8:45 AM, Theodore Ts'o <tytso@mit.edu> wrote:
> On Mon, Jul 28, 2014 at 12:01:54AM -0400, Nick Krause wrote:
>> I have got some work in brtfs for now , Ted so I won't
>> be able to run the tests for you for the next few weeks
>> probably. Sorry about the issues, but brtfs seems
>> more work then ext4 as of this point in time.
>
> Yes, that's probably true.
>
> One bit of advice.  I'd encourage you to think about this not about
> your lending help to a project.  At your level of experience, you will
> be consuming far more project development resources than you will be
> contributing, no matter whether it is btrfs or ext4.  I'd suggest that
> you focus on learning, and in order to do that, you will need to focus
> on one area --- and by that I mean not just one subsystem, but one
> feature or one specific subarea --- for a sustained amount of effort.
> I have to agree with Hugo Mills' observation that you are "bouncing
> all over the place like a hyperactive puppy".  His advice is on the
> mark; listen to it.
>
> There are no short cuts.  Malcolm Gladwell's book "Outliers" quotes
> some studies which show that on average, master musicians have
> accumulated an average 10,000 hours of practice before they achieved
> mastery.  Some other sources have "debunked" Gladwell's claim by
> showing in their studies, it has required 10,000 to **30,000** hours
> of practice.  So if anything 10,000 hours is not a magic threshold,
> and it might be much more than that for some.
>
> No doubt you will be higher functioning contributor --- a journeyman
> --- before you achieve complete mastery of the craft of programming,
> but at this point, you are barely an apprentice.  And as such, people
> who spend time hand holding you are doing so in the hopes that some
> point, the investment the OSS community has put into you will pay off,
> and you will start adding more value than you are subtracting, and
> then, in turn, that you will "pay it forward".  But that point, at
> which the breakeven is reached and you can start contributing at a
> high level and perhaps, mentoring other enthusiastic newocmers, is
> months if not years away.
>
> Good luck on your journey,
>
>                                                 - Ted
Ted,
I am already reading the brtfs good and found some work there.
Regards Nick

  reply	other threads:[~2014-07-28 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25  2:29 Work on ext4 Nick Krause
2014-07-25 14:59 ` Theodore Ts'o
2014-07-25 15:22   ` Nick Krause
2014-07-25 15:41     ` Theodore Ts'o
2014-07-25 16:07       ` Eric Sandeen
2014-07-28  4:01         ` Nick Krause
2014-07-28 12:45           ` Theodore Ts'o
2014-07-28 15:17             ` Nick Krause [this message]
2014-07-25 15:24 ` Wang Shilong
2014-07-25 15:59   ` Nick Krause
2014-07-25 16:06     ` Nick Krause

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=CAPDOMVijNtsfZwEn_D41ZU82KJ4W7dcjPMj4Pi6XkVpfR8PzeA@mail.gmail.com \
    --to=xerofoify@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).