Asking the important questions

it was me sorry

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......"

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

Try writing your backend with browser limitations and see what kind of wild wrappers you make to keep yourself sane.

Than*

You can write a stateless server. You can’t do stateless front-end since you have to deal with user interaction.

I didn't read the community name and wondered who tf thought the back end of a goose requires more attention than the front end

Often me. I make tools/interactions for learning management systems. So the back end is a thid party I have no controll over. Just take the api and make the magic happen.

You need me to save data somewhere but don't want to buy server space? Sure we can cram that into places it's not ment to go within the system. It will slow things down and likly cause issues but it's free.

That goose should be made mandatory in all customer meetings.

Lol. I fucking hate websites that take up half the page with a navbar.

The proliferation of libraries that exist only to fix the problems introduced by making everything an SPA is hilarious. Everything in web tech from the last decade is basically “there was an old lady who swallowed a fly”*.

*see also Cloud and container DevOps