Backend developer: "The new functionality is done!" PO: Looks at tests "Seems good, ship it!"
Frontend developer: "The new functionality is done!" PO: Looks at his screen "This spacing could be a little to the right, also I think I didn't really like this text, also it should probably auto-scroll to the top and this button should change colors when I click it and also don't forget to change the error messages I was happy with before and also I think it should......"
Try writing your backend with browser limitations and see what kind of wild wrappers you make to keep yourself sane.
You can write a stateless server. You can’t do stateless front-end since you have to deal with user interaction.
I feel (as a fullstack developer) that letting websites run arbitrary code in your browser was a mistake.
Made the mistake of using react for a mobile app and my god why is it this convoluted, why are the error messages always along the lines of "something went wrong with networking 🤷"
Unfortunately I'm stuck with it now
Linux has better error messages. "Dazed and confused, but trying to continue".
I am spoiled by dotnet and rust error messages. They tell you exactly what the problem is, where it is, and in rust's case sometimes even how to fix it
Then there's C with "segmentation fault"
