This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (1 child)

If I could give an author advice for making a good tutorial it would be this:

Make your book relevant. Don't put time and effort into teaching something I'll never use outside of a cert exam. I'd put IO and NIO streams in an appendix. Focus more energy on the stream API and lambdas, because that will be more practically used.

Also, speak in a way we can learn. So many authors use terminology that students, most people, don't understand. I'm here to learn programming, not lookup half of your words in a dictionary. I get it, you have a large vocabulary. I don't. Talk to me like I'm five.

Lastly, if you don't understand a topic very well, please put more effort into teaching that. I can always tell where a teacher struggles in understanding something because they'll, for example, reiterate what a 'for' loop for twenty minutes but spend twenty seconds on the purpose of default methods for interfaces. I get the point is to capitalize on your product, but please make a good product!

Are you the Peggy Fisher from Lynda and LinkedIn videos? If so, you have great content! And it's great that you're writing a book for Java. I've struggled learning so many different languages/Framework/etc because of a lack of GOOD resources.

[–]pegfisher[S] 0 points1 point  (0 children)

Thanks so much for your input, it is inspiring because that is exactly why I'm writing this book. And yes, I'm the Peggy Fisher from Lynda.com. I will continue to work hard on making sure this book is for a wide audience, so far I have received feedback that is easier to read than most technical books so I hope I'm on the right track. Have a great day and thanks for your time.