Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm sure that's great advice, but I don't respect anyone. :(


In that case, you should probably reexamine a few things, starting with why you don't respect anyone: * are you writing about something "revolutionary"? If so, reexamine your work, as there are very few new ideas that have never been written about or studied before. You almost certainly have missed the previous work on the subject. * Is it because you live somewhere isolated with few of your peers nearby? Welcome to the internet—i'd be willing to bet you can probably find the people writing about what you're writing about and ask them to review it. * Is it because of your ego? I think you can figure out what to do with this one.

Even if your work is on something fairly esoteric, you can almost certainly find someone qualified to review it on technical grounds, even if they're not an acknowledged expert in the precise topic you're writing about.


Sorry, thought my comment was glaringly tongue-in-cheek. The publisher has located some extremely esteemed folks to evaluate and frankly it's gotten me even more self-conscious about what I've written.

I have been unable to locate another book on this subject (its implementation in Go, anyway), but there are scores of experts in Go, many of whom are far more qualified than I am. I would respect their opinions on the book itself.


Ah, my apologies then—tone can be hard to grok here sometimes.

Best of luck in the process! Would you care to share the subject area? Now you've piqued my curiousity...


General and practical concurrency in Go.

This was challenging primarily because it's so idiomatic and easy to handle in Go, so a good deal of the book talks about pitfalls, testing and implementation.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: