Hardware book like "Code Complete"?

[Davy]

Hi all,

Is there some hardware RTL book like "Code Complete" by Steve
McConnell?

Thanks!
Davy

 

[Eric]

Is there some hardware RTL book like "Code Complete" by Steve
McConnell?

I don't think so, but that would be super cool if there was. Have you
considered writing one?

My impression is that hardware people don't like to write much, and
even if they do, they don't have time to sit down and document all of
the important "big issues" that new people need to learn in order to be
effective.

But if anyone writes a book like this it will fly off the shelves!

 

[Weng Tianxiang]

Hi Eric,
It is not because hardware engineers are lazy, but most of what they
have written for any interesting projects are properties of their
companies that prevent them from disclosing, not mention writing a
book.

SunMicro system published their CPU core with 350K code lines. If there
is a retired Sun engineer who had involved in the design and will write
something about the CPU project, I would like to be the first one to
order his book. Nobody can read a CPU design with 350K code lines and
at the same time without comments and introductions.

Weng

Eric wrote:

Is there some hardware RTL book like "Code Complete" by Steve
McConnell?

I don't think so, but that would be super cool if there was. Have you
considered writing one?

My impression is that hardware people don't like to write much, and
even if they do, they don't have time to sit down and document all of
the important "big issues" that new people need to learn in order to be
effective.

But if anyone writes a book like this it will fly off the shelves!

 

[Mike Treseler]

Eric wrote:

But if anyone writes a book like this it will fly off the shelves!

A few hundred copies would fly off the shelves.

There's probably about 10,000 digital designers
in the US. Not all of those do hardware description
and not all of those write their own RTL.
Those are not numbers that would excite
a major publisher.
Writing and editing a book is two long years
of work, whatever the subject.

-- Mike Treseler

 

[JJ]

Mike Treseler wrote:

Eric wrote:

But if anyone writes a book like this it will fly off the shelves!

A few hundred copies would fly off the shelves.

There's probably about 10,000 digital designers
in the US. Not all of those do hardware description
and not all of those write their own RTL.
Those are not numbers that would excite
a major publisher.
Writing and editing a book is two long years
of work, whatever the subject.

-- Mike Treseler

And even in a metro hub like Boston, MIT Cambridge area, a good book
store inside the Microcenter hardly ever sold any of these Hardware
books to any of us, the books were really too expensive at $70-$150 &
up so were mostly browsed (and dated). They dumped them at $10 a pop
instead and now stick to the VB, Java, Web, & ofcourse "Code Complete"
stuff that does move.

Softbooks in Marlboro also moved on sigh.

When you visit DAC & other big hardware design events, you can often
talk directly with several fine publishers, they are often quite eager
to talk to would be authors too. They also have all the relevant and
upcoming books in their booths with a modest show discount too.

I get the impression that unless you are writing for the college
market, the payback for the author would never cover the time spent.
And by the time you are ready to write, the subject is already changed.

John Jakson
transputer guy

 

[Phil Tomson]

In article <4iak6qF2v1p3U1@individual.net>,
Mike Treseler <mike_treseler@comcast.net> wrote:

Eric wrote:

But if anyone writes a book like this it will fly off the shelves!

A few hundred copies would fly off the shelves.

There's probably about 10,000 digital designers
in the US. Not all of those do hardware description
and not all of those write their own RTL.
Those are not numbers that would excite
a major publisher.
Writing and editing a book is two long years
of work, whatever the subject.

In the software world if it took two years to write a book the content
would be seriously outdated by the time the book came out. A lot of the
publishers of software books (O'Reilly, The Pragmatic Programmers even
APress now) are aiming for a six month cycle. In fact those publishers
have now gotten the idea of selling pre-release titles as PDFs: you buy
the pre-release PDF early for a reduced fee so you have access to the
content and then later on when the final book comes out you get the paper
version for an additional fee. That way your readers can access time-sensitive
information early on.

The other issue with hardware books like this is that the market is
relatively small (I'm guessing that the ratio of software engineers to
hardware engineers is at least 30:1). It
could be a good opportunity to self publish where
you publish not paper books but PDFs (this is happening on the software side).
Then instead of having to pay $70 for a title because the audience is
small, the author charges $20 for a pdf and gets to keep all of it instead
of getting a small royalty from a publisher. If you manage to sell 1000
of them you've made $20K and that's generally a lot better than what you'd
get from a publisher. One publisher (The Pragmatic Programmers) even
publishes mini-books which are less than 100 pages (not paper, pdf only)
which they sell for $8 to $10. It wouldn't be hard to write 100 pages in
2 to 3 months (part-time even).

Phil

 

[Bob Perlman]

On 21 Jul 2006 04:42:09 GMT, ptkwt@aracnet.com (Phil Tomson) wrote:

<Stuff snipped>

The other issue with hardware books like this is that the market is
relatively small (I'm guessing that the ratio of software engineers to
hardware engineers is at least 30:1). It
could be a good opportunity to self publish where
you publish not paper books but PDFs (this is happening on the software side).
Then instead of having to pay $70 for a title because the audience is
small, the author charges $20 for a pdf and gets to keep all of it instead
of getting a small royalty from a publisher. If you manage to sell 1000
of them you've made $20K and that's generally a lot better than what you'd
get from a publisher. One publisher (The Pragmatic Programmers) even
publishes mini-books which are less than 100 pages (not paper, pdf only)
which they sell for $8 to $10. It wouldn't be hard to write 100 pages in
2 to 3 months (part-time even).

Self-publishing on actual, old-fashioned paper has become surprisingly
affordable of late. Take a look at lulu.com or blurb.com and be
amazed.

Bob Perlman
Cambrian Design Works
http://www.cambriandesign.com

 

[Ted]

In the Wallace & Gromit film "The Wrong Trousers", Gromit uses a book
called "Electronics For Dogs" to help him convert the NASA
technotrousers to remote controlled operation. Is this the kind of
thing you had in mind?

Cheers
TW

 

[Jon Forrest]

Eric wrote:

Is there some hardware RTL book like "Code Complete" by Steve
McConnell?

It's not exactly the same but "The Pentium Chronicles" by
Robert Colwell is worth looking at.

--Jon-

 

[Ian Bell]

Davy wrote:

Hi all,

Is there some hardware RTL book like "Code Complete" by Steve
McConnell?

Unlikely. Creating software is far less complex and variable than creating
hardware.

Ian

 

[Dean Kent]

At least one. I'd buy it. ;-).

Suggestion: Do it like the guy who wrote "Thinking in JAVA" did. As he
finished a chapter, he posted it on his website for people to review. He
got tons of corrections and feedback, which he then used to update the
chapter. At the end of it all, he published a hardcopy and to his surprise
found out he sold more than expected - because everyone who had read it
online wanted a copy on his/her desk, and because it was online originally
it was highly anticipated when it was actually published.

Seems counter-intuitive, but I believe it would work for a tome such as
this... (and if you did it right, you could generate a few bucks before it
every gets published, wink-wink, nudge-nudge, hint-hint,
know-what-I-mean--know-what-I-mean?).

Regards,
Dean

"Andy Glew" <first.last@employer.domain> wrote in message
newseyp8xmjgc51.fsf@PXPL8591.amr.corp.intel.com...

My impression is that hardware people don't like to write much, and
even if they do, they don't have time to sit down and document all of
the important "big issues" that new people need to learn in order to be
effective.

But if anyone writes a book like this it will fly off the shelves!

Care to estimate the size of the market?

I.e. how much would the author expect to make, given typical publishing
contracts?

(I've long wanted to write such a book, but have trouble with the
business case - i.e. persuading my wife. And, of course, I cannot
write it as an employee of Intel.)

 

[David Kanter]

[snip]

I think what Dean means to say is that he knows an excellent, reputable
website that would put something online and attract a lot of good
readers : )

And if you do a good job, I bet you could persuade Intel to start
buying up copies in bulk for NCGs.

DK

 

[J o h n _ E a t o n (at)]

Mike Treseler wrote:

Eric wrote:


But if anyone writes a book like this it will fly off the shelves!


A few hundred copies would fly off the shelves.

There's probably about 10,000 digital designers
in the US. Not all of those do hardware description
and not all of those write their own RTL.
Those are not numbers that would excite
a major publisher.

It can't justify the cost and delay of hard-copy but
could easily be sold as a pdf. Forget the idea of
publishing a single work. This should be a work
in progress that is always adding new chapters and
ideals and evolving with the industry.

Writing and editing a book is two long years
of work, whatever the subject.

-- Mike Treseler

Two long man years. Quadruple that if you have multiple
authors that need to coordinate their works and then
divide by the number of authors on the project.

Many hands make light work. Get a couple of dozen of
experienced designers, a bunch of proof reading fact
checkers and one decent editor and you got yourself
an open source book writing project.

Put it out on sourceforge for free and make it useful for any
digital designer at any stage in their career or hobby.Do
a really good job and it can become the "bible" of the
industry that everyone has in the library.


Do we have the critical mass to pull something like this off?


Lets do a survey. If we did a cooperative book on digital
design guidelines then what chapters would you like to see
and or contribute.


my list:


1) Reset systems and how they work.

2) Designing logic for scan testing (atpg)

3) Designing bist test logic

4) Designing and using jtag test logic

5) Designing and using in-chip diagnostic and debugging logic





John Eaton

 

[KJ]

Many hands make light work. Get a couple of dozen of
experienced designers, a bunch of proof reading fact
checkers and one decent editor and you got yourself
an open source book writing project.

Put it out on sourceforge for free and make it useful for any
digital designer at any stage in their career or hobby.Do
a really good job and it can become the "bible" of the
industry that everyone has in the library.

Certainly an interesting idea.

Do we have the critical mass to pull something like this off?

Always a big question...the other important question is finding the

'leader' to prod this along to get it going in the first place.

KJ

 

[Paul Floyd]

On 24 Jul 2006 10:12:42 -0700, Andy Glew <first.last@employer.domain> wrote:

My impression is that hardware people don't like to write much, and
even if they do, they don't have time to sit down and document all of
the important "big issues" that new people need to learn in order to be
effective.

But if anyone writes a book like this it will fly off the shelves!

Care to estimate the size of the market?

I can't guess that.

I.e. how much would the author expect to make, given typical publishing contracts?

(I've long wanted to write such a book, but have trouble with the
business case - i.e. persuading my wife. And, of course, I cannot
write it as an employee of Intel.)

From the software world, I suggest that you take a look at Scott Meyers
web site: http://www.aristeia.com/authorAdvice_frames.html

A bientot
Paul
--
Paul Floyd http://paulf.free.fr (for what it's worth)
Surgery: ennobled Gerald.

 

[Mark VandeWettering]

On 2006-07-24, Ian Bell <ruffrecords@yahoo.com> wrote:

Davy wrote:

Hi all,

Is there some hardware RTL book like "Code Complete" by Steve
McConnell?


Unlikely. Creating software is far less complex and variable than creating
hardware.

That's funny!

Mark

> Ian

 

[Davy]

Hi all,

For I think software engineer is more near to the application, they
"may think more thank hardware engineer".

And "software engineering" is a research topic (they have a lot of
methodology like design pattern). But I haven't find any book named
"hardware engineering" (and hardware design and verification method is
based on software experience, for example, SystemVerilog is something
like C++).

Anyone finish a good book about "hardware engineering" will be known by
hardware engineer all of the world. Thanks!

Davy

Davy wrote:

Hi all,

Is there some hardware RTL book like "Code Complete" by Steve
McConnell?

Thanks!
Davy

 

[Jogi]

Ian Bell wrote:

Davy wrote:

Hi all,

Is there some hardware RTL book like "Code Complete" by Steve
McConnell?


Unlikely. Creating software is far less complex and variable than creating
hardware.

Ian

That's a sweepingly uninformed and unpredictably naive comment!

- Jogi

 

[Weng Tianxiang]

Hi Christer,
I bought Knuth's books and McConnell's Pentium story. But I don't know
Hennessy and Patterson. What are their popular books?

Thank you.

Weng

 

[BobG]

I read the whole thread and no one recommended "The Art Of Electronics"
by Horowitz and Hill??