IMO interceptors are bad. they hide what might get transformed with the API call at the place it is being used.

> Likewise, every response I get is JSON. There's no reason to manually unwrap the response into JSON every time.

This is not true unless you are not interfacing with your own backends. even then why not just make a helper that unwraps as json by default but can be passed an arg to parse as something else

Me: we cant do X bceause it has Y and Z implcations for end users

Manager: It fits our brand and we have to do it.

Dev: I can do it and the implications are mitigated by (handwavy explanation)

Maanger: sounds good. (To me) Maybe you can make a (useless) diagram for this featuer that will be realy handy for KT

--Days later--

Feature is delivered and the Y and Z were ethier not mitigated or there was a attempt-ish to mitigate them

Recently had to put so many huge blurs that there was screen tearing like effect whenver you srcolled a table. AND No i was not allowed to use prebake-blurs because they wouldnt resize "responsively"

For me it was a website with turotirals on how to make flash games. It literally launched my career and improved the quality of life for my whole family by an order of magnitude.

I am primarily the naysayer of AI but I admit that current LLMs could have easily replicated the whole website.