|Language:||English, Spanish, Arabic|
|Genre:||Academic & Education|
|ePub File Size:||30.67 MB|
|PDF File Size:||14.83 MB|
|Distribution:||Free* [*Sign up for free]|
About the Authors Stoyan Stefanov is a Yahoo! Kumar Chetan Sharma studied to be an electronics engineer and has always wanted to build an ultimate sound system. He then, by chance, got a part time job as a trainee HTML guy. Reviews, Ratings, and Recommendations: site Related Book Categories: All Categories.
Recent Books. IT Research Library. Miscellaneous Books. Computer Languages. Computer Science. Electronic Engineering. Linux and Unix.
Microsoft and. Mobile Computing. Networking and Communications. Software Engineering. Special Topics. Web Programming. Because that will make you think. Should I make this bold? Or maybe italics?
All this takes your energy and causes you to type less. Word is also terrible for writing code. It's simply not a code editor. The best software for writing a computer book is simply your favorite code editor.
It has everything you need, and everything you're used to. Tabs vs. Your favorite macros and shortcuts that you normally use every day.
Your book is best written as plain text, as close to normal source code as possible. I just wrote text. I thought of writing HTML initially and then use something to convert it but quickly reconsidered.
You know, little markup pieces.
Once the first ugly draft was done, I started looking at how to convert this plaintext into something O'Reilly can use. I have heard of something called docbook or bookxml or something similar and suspected that O'Reilly supports it.
AsciiDoc AsciiDoc is an open source project that lets you write plain text with minimal markup and then generate a bunch of different outputs from the source. While typing you just type the code. Macros Writing in your favorite code editor lets you come up with all kinds of macros and shortcuts.
Think about writing code MS Word. It's a pain. You write code and word mangles your "s and your 's. You undo. See it has a syntax error.
Fix it. Copy back to word. Repeat or risk publishing broken code. In a code editor it's much easier, you write code in its natural environment.
Then you can probably think of something to execute the code. Really quick feedback loop to fixing any errors.
Refactoring whole chapters and the whole book is also trivial when you deal with plain text source code in a source code editor. Type all the things!
Removing friction out of typing is an enormous help. And writing a book in your favorite text editor and using something like AsciiDoc or markdown makes the process so much easier. Another cool thing about O'Reilly specifically is that they give you an SVN repository where you check in your. I think this is mainly due to a poor definition of what writing is. In the movies, there is this romantic idea of the process.
The author struggles, drama ensues. Then all of a sudden inspiration strikes.
The author sits down all night just listening to what inspiration says and lo! Everyone who reads it says it's the best thing ever! Or, if the author is ahead of his time, as often happens in drama, at least those who know anything about anything and are not as dumb as the average Joe, love the thing.