tech-ninja

It is great to reduce file size but also the quality drops faster than it does with JPG. I did some testing and could confirm, it is quite documented.

Which I think it might be one of the reasons why Instagram still uses JPG for their images. The rule of thumb is that if your product is picture quality sensitive (like photos in IG) then use JPG, if not then WebP is fine since the compression is higher.

I agree with you and I didn't think your comment was rude. Some people are against using LLMs and they will always find an excuse instead of experimenting with them so it doesn't matter how helpful you try to be they already made their mind.

> In _most_ cases that means delivering code that you should be able to confidently prove satisfies the requirements like the OP mentioned

That is an insane distinction that you are trying to do there. In which cases delivering code that doesn't satisfy the requirements would solve a business problem?

I disagree, no company no matter the size will have E2E or integrations tests for all of its features, it's just not feasible.

Unless you are working on a tiny change on a highly tested part of the code you should be manually testing your code and/or adding some tests.

Agreed, I'm also on a $200/year plan and for me too the fact that I can skim multiple books on a single topic before settling on one is well worth the money.

I also pay $200/year, well worth the cost for me.

I've had good experiences with Wise but jesus this is a nightmare, it looks like their customer service is crooked. It's a shame that such a great company can be so inflexible and let this type of situations fly.