I really love it and I'm very impressed. I'm actually just a high schooler and I was working a book for Java that I was planning on self-publishing as well. I was wondering if you could lend some insight into how you formatted your book (especially with the code)? Did you use any software or get it done by someone else? Or did you use any template that you recommend?
Show HN: I just released my first self-published book
11–20 of 23 posts
Re: Show HN: I just released my first self-published book
#12I hate to be picky but I know I'd want someone to point these out in my work, so I'll hope you feel the same way. You have a few grammatical errors on your page:
"Building proper tests for a Magento extension can be difficult for seasoned veterans let's not say the junior developer just getting started with Magento."
You at least need a comma before "let's not say", but even then it still feels like a strange construction to me. Maybe "...veterans, not to say..."
"After all, you have written code like this a thousand times before; You know what you are doing right?"
Turn that semicolon into a period. I have a simple rule on when to use a semicolon:
Should I use a semicolon?
1. Nope.
2. There is no second answer.
"And yet, how much time of your day to day do you spend tracking and fixing bugs?"If you really want to use "day to day", hyphenate it. But I would simplify it to "how much of your day do you spend...".
"What if you could do something that gave you confidence, not only on the quality of the code that is being promoted, confidence that if and when, someone has to make changes to the code there are tests that can confirm that nothing has been broken and the application still performs as expected."
There's some dead weight here and the clauses sort of run on. How about:
"What if you could do something that gave you confidence — not only on the quality of the code, but confidence that when someone changes the code, there are tests that confirm nothing has broken."
When I write, I do (at least) three drafts:
1. Get all the words down. Put all the clay on the table.
2. Rearrange and control structure and pacing. Push the clay into the right shape.
3. Edit every single sentence to tweak or remove words that don't add value. Trim the sculpture down to its final shape and texture.
My goal on the third draft isn't to strip it down to Hemingway. There's still room for character and charm to shine through. But it's to make sure that every ounce of prose adds some value, be it information, clarity, cadence, or humor.
Re: Show HN: I just released my first self-published book
#13I don't know if you'll have an editor go through everything later on, but just wanted to mention a couple of the things from the early access sample :)
Re: Show HN: I just released my first self-published book
#14Couple of points - I had to dig back to your blog to find anything about you personally. It was odd to read about the book but not the author - especially for something like this where personal expertise counts. I suggest a small about me section on the landing page.
Good luck
Re: Show HN: I just released my first self-published book
#15Looks awesome. I just wanted to mention a couple stylistic things I noticed in the sample copy: subsubsection under Part 1 named "It;s all about communication" (the it;s), and the capitalization style for section titles is pretty inconsistent. I don't know if you'll have an editor go through everything later on, but just wanted to mention a couple of the things from the early access sample :)
I have a couple of people helping me out with the proofreading. I will make sure to double check that kind of formatting issues.
Re: Show HN: I just released my first self-published book
#16Congrats Couple of points - I had to dig back to your blog to find anything about you personally. It was odd to read about the book but not the author - especially for something like this where personal expertise counts. I suggest a small about me section on the landing page. Good luck
Re: Show HN: I just released my first self-published book
#17Hi, I really love it and I'm very impressed. I'm actually just a high schooler and I was working a book for Java that I was planning on self-publishing as well. I was wondering if you could lend some insight into how you formatted your book (especially with the code)? Did you use any software or get it done by someone else? Or did you use any template that you recommend?
Sure I'm using leanpub.com for generating the ebooks; they have great tools and manuals for the markdown style they use.
The book itself is saved into a private GitHub repo; so I can keep tabs on all the changes. Formatting the code becomes a walk in the park thanks to leanpub.com
If you need more help, advice or any help at all feel free to email me at amacgregor [at] allanmacgregor.com
Re: Show HN: I just released my first self-published book
#18Congrats on finishing your book! I know exactly how much work that can be. I hate to be picky but I know I'd want someone to point these out in my work, so I'll hope you feel the same way. You have a few grammatical errors on your page: "Building proper tests for a Magento extension can be difficult for seasoned veterans let's not say the junior developer just getting started with Magento." You at least need a comma…
A lot of the fun with this book has been finding a writing style that feels natural but is still clear enough; a bit difficult since I try to ramble.
Cheers!
Re: Show HN: I just released my first self-published book
#19Re: Show HN: I just released my first self-published book
#20Have you written at all about the tools you used to work on the book? I'd be interested for sure.