How The Passionate Programmer relate to passionate programmers?

From the book's ToC, it seems that almost of contents are about entrepreneurship and career development in general.
How does The Passionate Programmer relate to passionate programmers or just programmers?

The themes in the book of entrepreneurship and career development are all techniques for developing a remarkable career in programming. The core message is of developing passion for what you do as a programmer, choosing your path, and then creating the best and most rewarding programming career you can imagine (then imagining a better one and doing it again).

Though the chapter titles look pretty general (and the book can definitely be read by non-programmers), the examples are very much geared toward software developers and draw from my experiences as a software developer.

Chad

The Passionate Programmer: Creating a Remarkable Career in Software Development
http://www.pragprog.com/titles/cfcar2/the-passionate-programmer
http://chadfowler.com

Hong Anderson
Ranch Hand

Joined: Jul 05, 2005
Posts: 1936

posted Jun 25, 2009 01:15:08

0

Thanks. Would software architects get benefits from reading this book as well?

Chad Fowler
Author
Ranch Hand

Joined: May 19, 2009
Posts: 38

posted Jun 25, 2009 10:45:09

0

Kengkaj Sathianpantarit wrote:Thanks. Would software architects get benefits from reading this book as well?

Absolutely. I don't personally differentiate between software architects and programmers. I think a great programmer needs to be able to be an architect and vice versa.

Hong Anderson
Ranch Hand

Joined: Jul 05, 2005
Posts: 1936

posted Jun 25, 2009 11:32:17

0

Chad Fowler wrote:

Kengkaj Sathianpantarit wrote:Thanks. Would software architects get benefits from reading this book as well?

Absolutely. I don't personally differentiate between software architects and programmers. I think a great programmer needs to be able to be an architect and vice versa.

I agree. I don't think architecture/design and implementation can be clearly separated, it's amusing and pitiful if who design don't implement (or get involved), and who implement don't design (or get involved). Refactoring to better insight couldn't happen if architecture/design and implementation are clearly separated like that.