From: r00nk@simplecpu.com (r00nk at simplecpu.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How do _you_ read the linux source?
Date: Mon, 20 Apr 2015 17:46:57 -0700 [thread overview]
Message-ID: <ba8ba1007252c22511e55142c868c84f.squirrel@webmail.simplecpu.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1504200752440.21282@localhost>
> On Sun, 19 Apr 2015, nick wrote:
>
>> On 2015-04-19 09:57 PM, r00nk at simplecpu.com wrote:
>> > The problem a lot of newbies are having is in 'separating the trunk
>> > from the leaves.' So my question is this: Experienced kernel
>> developers, how
>> > do _you_ read source code? How do you separate the trunk from the
>> leaves?
>> > What do you do when you read code you're not familiar with? How do you
>> learn?
>> > What's your algorithm?
>
> *sigh* ... this is the wrong question, in the same way that asking,
> "how do i start writing kernel code?" is the wrong question...
How to start isn't what I'm trying to ask. Like, if this were
mountain climbing, I'm not asking how to start climbing. I've
gotten to the point where I've developed my own technique to climb,
now I'm asking others how they climb, so I can learn/improve my own
technique based on theirs.
> it seems that there is a regular supply of posters whose opening
> question is something like, "i'm interested in the kernel ... how do i
> get started?" i submit that it's not the mandate of this list to
> answer that question. rather, i submit that it's the mandate of this
> list to answer questions you have *after* you get started and have
> shown that you've invested the time to dig in on your own.
Right, I'm not asking how to get started, I'm asking how you (not I)
go about digging, to see if your method is better then mine. I have
already done a fair amount of digging myself (knock on wood).
I think that meta-cognition is a important part of any skill set.
I'm trying to learn the way skilled kernel developers think, because
learning how skilled people think generally leads into valuable
insights for that said skill.
In my (admittedly small) personal experience, trying to get an idea
of how kernel developers think is difficult. There are a few places
that sort of do it (Documentation/CodingStyle, Documentation/*, lkml),
but those are a bit more geared to management then skill.
I figured rather then trying to parse those and come up with a model
that probably isn't true, I'd just directly ask. I dunno. Maybe its
not an appropriate question for this mailing list.
next prev parent reply other threads:[~2015-04-21 0:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 1:57 How do _you_ read the linux source? r00nk at simplecpu.com
2015-04-20 3:11 ` nick
2015-04-20 5:45 ` Christoffer Holmstedt
2015-04-20 12:47 ` nick
2015-04-20 15:45 ` Valdis.Kletnieks at vt.edu
2015-04-20 12:04 ` Robert P. J. Day
2015-04-21 0:46 ` r00nk at simplecpu.com [this message]
2015-04-21 16:45 ` John de la Garza
2015-04-21 1:08 ` Miles Fidelman
2015-04-20 14:51 ` Greg KH
2015-04-21 0:16 ` Milton Krutt
2015-04-21 0:38 ` Ruben Safir
2015-04-20 16:32 ` Jeff Haran
2015-04-20 16:43 ` Ruben Safir
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=ba8ba1007252c22511e55142c868c84f.squirrel@webmail.simplecpu.com \
--to=r00nk@simplecpu.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).