Slashdot Mirror


Advice On Creating an Open Source Textbook?

Occamboy writes "I wrote a slightly successful (30,000+ copies sold) computer communications textbook a number of years back that was published via the traditional textbook publishing route. The royalties were nice, but, frankly, the bigger money came from the boost in my professional standing (I'm a practicing engineer, not a professor). I also felt bad when the publisher hiked the price dramatically every year because students were stuck once a professor adopted a text — $50 for a smallish paperback seemed very high (although I like to think what they learned was worth it!). I'm thinking of writing another textbook, this time about the practice of software engineering in critical systems, using the experience I've gained in the decades I've spent developing, and managing the development of, software-driven medical devices. Poking around on the Net, I've found several intriguing options for distributing open source texts, such as Flatworld Knowledge, Lulu, and Connexions. This concept of free or inexpensive texts intrigues me — the easy adoption and lack of price-gouging. Do any Slashdotters have experience with this new paradigm? Any suggestions or experiences to share from authors, students, and/or professors, who've written, read, or adopted open source or low-cost texts from any source?"

1 of 178 comments (clear)

  1. Re:Make sure you're clear on what you want to do by calmofthestorm · · Score: 0, Troll

    I'd argue that's not bullshit, it's a minor mistake. My understanding of history is shattered if I mistake that one year difference. If that one fact were important enough to matter, surely one would read more than one source anyway, and Wikipedia at that!

    --
    93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.