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?

Unfortunately, it's not available anywhere other than Amazon :( I'm sorry.

May I ask why?

Best of luck either way.

Amazon isn’t letting me :( I published there because it’s a big marketplace and they can print my book easily.

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?

no

let me read it to verify

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 :)

Great that you finished :)

Do you have a next book project lined up?

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

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

Sometimes it's good to look beyond myriad of narratives to see what actually makes a thing tick.

Would you please like to tell everyone how that's oversimplified?

> Would you please like to tell everyone how that's oversimplified?

People aren’t one dimensional. Simplifying businesses into perfectly-rational automatons is high-school economics.

Businesses aren't people and people's motivations aren't businesses motivations. Business are automatons, just running on carbon instead of silicon and if they are not perferct they are just bad.

Framer | Multiple positions | Remote (Netherlands, Germany, Spain, United Kingdom) or Hybrid (Amsterdam, Barcelona) | https://www.framer.com | Full-time | Visa Sponsorship

Framer is the design tool for websites

Senior+ Product Engineer - https://www.framer.com/careers/senior-product-engineer Staff+ Back-end Engineer - https://www.framer.com/careers/principal-backend-engineer Senior+ Site Reliability Engineer - https://www.framer.com/careers/senior-site-reliability-engin...

You can email me if you find it interesting: andrey.ozornin@framer.com

Do you use their actions at all?

can someone with lore knowledge share the deal between gitea, forgejo and codeberg

It actually starts with Gogs.

Gogs is FOSS but basically BDFL. What does and does not make it into Gogs (it's still around) is ultimately decided by one person, and he's fairly conservative. Gogs is very fast but lacks a lot of features that would allow it to go head-to-head with GitHub or Gitlab.

So, Gitea was forked from Gogs to allow it to take a different direction, with a larger group of maintainers and more input from the user community.

There were two major attempts to have hosted Gitea. The first was Codeberg, a nonprofit based in the EU. The second is a business that took the name Gitea, is based in the US, and changed Gitea (the software) to the "open core, closed premium" model.

This change led to the creation of the Forgejo fork, which Codeberg adopted.

gitea is the OG. forgejo is a fork, focused on lower resource needs (i think?). codeberg uses forgejo and adds static-site generation (like github pages) and CI/CD (via woodpecker).

gogs existed, gitea forked from it, gitea made some corporate structure change some people didn't like, they forked forgejo, codeberg is a hosted instance of forgejo.