public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Will Bickford <wbic16@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	 John Tooker <jtooker@gmail.com>
Subject: [Bitcoin-development] Reading List for Getting Up to Speed
Date: Wed, 24 Dec 2014 11:08:59 -0600	[thread overview]
Message-ID: <CAB2qGxXm1brQLS_T8TWS50iH4me03HEOPh95BYOfk3UN6EnNhw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

I've started to familiarize myself with the source code and build tools.
I'll be posting regular status updates on my blog (linked below) for others
to follow getting started with bitcoin development.

http://hewo.xedoloh.com/bitcoin-dev/

A tally from August indicated that I may need to slog through 280,000 lines
of code to get up to speed. I sampled
https://github.com/bitcoin/bitcoin/blob/master/src/key.cpp and skimmed it
in about 5 minutes, putting me at 2600 lines per hour. At that rate, I
would need to devote 110 hours to read the entire code base.

With that time investment I could get a fair amount of testing done, so I'm
curious if we have a map of the most important areas to study for new
developers and automated test writers.

Thanks for your time,

Will Bickford
"In Google We Trust"

[-- Attachment #2: Type: text/html, Size: 1154 bytes --]

             reply	other threads:[~2014-12-24 17:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24 17:08 Will Bickford [this message]
2014-12-24 19:44 ` [Bitcoin-development] Reading List for Getting Up to Speed Gregory Maxwell
2014-12-24 19:58   ` Will Bickford

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=CAB2qGxXm1brQLS_T8TWS50iH4me03HEOPh95BYOfk3UN6EnNhw@mail.gmail.com \
    --to=wbic16@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jtooker@gmail.com \
    /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