ozornin

May I ask why?

Best of luck either way.

Hey! I'm not a moderator, but you don't have to delete the post after 3 days.

It's encouraged to share your relevant work, even if it's a paid product.

Is there a way to buy/download the book without an Amazon account?

I totally agree.

At first, I started writing a book about very practical, hands-on debugging practices, but quickly realized that the "mix of tools and best practices" you're talking about is a much more valuable skill, as well as bug prioritization, and even bug reporting.

So, as a result, catching errors early, type guarding, logging to debug asynchronous operations, and error tracking are all major parts of the book.

Exactly. I wrote in (flavored) Markdown with occasional XML inserts.

That's great feedback, thank you!

We'll go through screenshots, check their readability and crop or re-create them before going to print.

Can you point to particular screenshots that feel the worst?

Thank you!

Not really. I am almost sure that eventually I'll do it, but what I have at this point is more like "dreams" or "ideas", very far from being materialized.

Also, I know that I want to write about something less practical and more fun. Maybe, making music. Writing about fun parts is so much easier

no

I did, thank you! It was hard and long, though. Much harder and longer than I expected it to be. The book ended up being very different from what I initially conceived (for the better, I hope.) I have too much to say to fit it all in one comment, to be honest :)

Mostly yes. It touches upon debugging unit tests and server-side code, as well as methodologies applicable to debugging in general, but the practical parts are almost exclusively client-side.

That's a wild oversimplification