Had to think about it, but no. I think the reason is that I'm not a reader just yet. I'm trying to build this habit. So if I buy a book, then it had to cross my way a couple of times before. For all the info that I'm interested in, I usually use Google and YouTube to get insights into the topic.

I have to admit that for me it is only about recommendation. The more often I see a book that is recommended, the more likely it is I will read it. And if a book caught my interest. I just buy it. Either on Audible, Amazon (physical), or Kindle. I neither download sample chapters nor look at reviews.

However, I only find books in communities that I'm in. So I don't just take any book that I get recommended. The book has to be about the niche that I'm interested in.

I can only agree to that. In this early stage, the tech stack doesn't matter. So choose the one that you are familiar with.

Over the past 2 years, I tried many web frameworks/backends/tools/... until I came up with my current stack. It always took me weeks to really get going. Now I keep my stack because it literally takes ~10mins to have everything set up to start working on the actual idea. And I'm using this all the time. (just FYI: React/Redux + Snowpack + Tailwind + Firebase)

I read a tweet lately (couldn't find it) where a maker said that you should not care about the tech stack at the beginning. At this point in time, it is about product evaluation. When the product starts to grow (customer-wise), then you will have time to switch (and a good reason to do so).

That being said. It's always good to learn something new. Extend the horizon, and maybe see whether the other language helps you to achieve more. It's also fun and challenging. Even if your first site takes 3x longer (which it will). (Still, it might lead to frustration as you are not working on your actual product idea)

Currently, it catches errors (reported by console.err) of the same browser session. I'm working on capturing those even when you refresh the page (console lost usually).

I will also use the general error event listener for web sites to make sure that every single error is catched.

That's exactly how I did it for quite a while when I was still developing mobile apps for mobiles (good old Windows Phone days :D). Later I switched to some kind of one button solution that (when clicked by the user) packaged up everything (logs, system info, ...) and send that package via eMail.

For the last two years I worked more on web apps where I always felt like something similar is missing.

Think of a feedback button. When selected by the user, he is able to briefly describe his issue. In addition he should be able to directly capture screen casts and screen shots, or add any arbitrary file that could help me to solve the problem faster. Logs and basic browser info is attached automatically. So I as a dev would receive such package that contains all the info that I need to solve that problem.

Hi Paul, thanks for the answer. How do you get logs in case of issues on customer side? (Or does crisp.chat allow you to get those somehow?)

Thanks, Markus. But I was more looking from a client's perspective on that question.

For me as a dev, I'm doing exactly what you're saying. The dev env is similar to the prod env as much as possible. Without Docker ;)

But even if both envs are the same, there are bugs that just cannot be reproduced on the dev env. So let's assume a client reaches out to you with such a problem. What tools do you use to tackle that problem? (see list I mentioned in my question)

100% WIP Menubar (for now)

But I'm just getting started. Just learned in this thread that I can also add the WIP bot into a personal chat group and then post todos from there as well :D

To get inspirations, I use www.brandcrowd.com/ usually. I even bought a logo once with design support from them. But in most cases, this is more of an inspiration to create my logo in Illustrator then.