From: "Eric S. Raymond" <esr@thyrsus.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] the serial alternative/radio noise
Date: Mon, 12 Mar 2012 21:28:51 -0400 [thread overview]
Message-ID: <20120313012851.GA18695@thyrsus.com> (raw)
In-Reply-To: <CAA93jw5dyt0RhEY2bSthmqcpggVkTvdPOdb0Bo4bZGR-cuhGBA@mail.gmail.com>
Dave Taht <dave.taht@gmail.com>:
> I note that in the early stages of any project, I tend to appreciate
> all sorts of blue-sky thinking, rather than tie down to any one goal,
> and try to encourage such in others.
Fair enough. But, as the person who has sort of dropped into the role
of project manager, it'a my job to ensure that (a) we have a coherent
and achievable set of objectives, and (b) the engineers keep their eye
on that ball. (For completeness, I consider the third major challenge of my
job to be (c) negotiating with vendors and fabricators.)
For me, this is an amazing adventure, really. Me, a defrocked
mathematician, cat-herding a...*hardware* project. Riiiight. Good
thing I'm a naturally arrogant person or I'd probably be curled up in
fetal position in a corner somewhere.
Note, I also want to try this as a kind of experiment in just how far
down the post-industrial road we actually are. I've been reading and
thinking for years about the demassification of production, silicon
foundries, 3D fabbing and other technologies that are supposedly
making semi-custom and individualized products more viable then ever.
The economist in me wants to grok these changes from ground level.
> I guess in part what drives me in
> suggesting alternatives (and please note my alternative above was
> intended as a lead-in into the noise question more than an actual
> suggestion), is that I would like to find markets for a 'new device',
> that 'does new stuff', that justifies the manufacturing run, more than
> a 'usb gps with hyper-accurate pps and time output' may, as a
> differentiator.
I understand that urge, but the increment in complexity required for
us to do "new stuff" would be all too likely to complexify the project
out of the zone of feasibility. Let's do a design for which we *know*
that we have established need and a clear specification first. If the
team gels and we develop good relationships with our vendors and
fabricators, we can then use that to go back around to things like
randomness sources and environmental sensors.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
prev parent reply other threads:[~2012-03-13 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 21:54 Dave Taht
2012-03-12 22:01 ` tz
2012-03-12 22:06 ` Eric S. Raymond
2012-03-12 22:59 ` Dave Taht
2012-03-12 23:22 ` Dave Taht
2012-03-12 23:51 ` Dave Taht
2012-03-13 1:31 ` Eric S. Raymond
2012-03-13 1:26 ` Patrick Maupin
2012-03-13 2:46 ` Ron Frazier (NTP)
2012-03-13 1:28 ` Eric S. Raymond [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=20120313012851.GA18695@thyrsus.com \
--to=esr@thyrsus.com \
--cc=dave.taht@gmail.com \
--cc=thumbgps-devel@lists.bufferbloat.net \
/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