From: Hans Reiser <reiser@namesys.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Andrew Morton <akpm@osdl.org>, Nick Orlov <bugfixer@list.ru>,
linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com
Subject: Re: bitmap loading related reiserfs changes in 2.6.17-mm1 are broken
Date: Thu, 22 Jun 2006 00:02:09 -0700 [thread overview]
Message-ID: <449A4071.50600@namesys.com> (raw)
In-Reply-To: <20060621204303.47facd01.akpm@osdl.org>
One of the things about my getting older is that I stopped thinking that
I would ever be anything but a fool, and started looking for ways to
cheat so that being a fool doesn't hurt so much.
1) record all experiments/benchmarks in some form so that I can find
them later (because 6 months later when I am thinking I should have
checked XYZ, I won't remember them well enough to be sure of them anymore).
2) have someone review all code and ideas before I give them to a large
audience
3) if some benchmark result doesn't make sense, I don't let go of it
until it does, because chances are high it is the only clue I will ever
get that something bigger than the obscure measurement is wrong in the
code and in my understanding.
There is a remarkable tendency that I have noticed, that the best
scientists in most fields are more quick to assume themselves to need
careful methodology than most others in the field.
I encourage you to figure these things out at a younger age than I
did.;-)
Hans
prev parent reply other threads:[~2006-06-22 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 3:27 bitmap loading related reiserfs changes in 2.6.17-mm1 are broken Nick Orlov
2006-06-22 3:43 ` Andrew Morton
2006-06-22 3:50 ` Jeffrey Mahoney
2006-06-22 5:09 ` Barry K. Nathan
2006-06-22 10:11 ` Barry K. Nathan
2006-06-22 6:33 ` Hans Reiser
2006-06-22 7:02 ` Hans Reiser [this message]
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=449A4071.50600@namesys.com \
--to=reiser@namesys.com \
--cc=akpm@osdl.org \
--cc=bugfixer@list.ru \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.