[brntbeer]

Pretty spot on. I'm constantly bothered by people who are "Front End" Engineers and only want to slap some html/css around or only do DOM manipulation.

Sure, you should do that stuff better than me (back end), but knowing how you are getting your data, where it's coming from, etc will only make you better.

[Zimahl]

but knowing how you are getting your data, where it's coming from, etc will only make you better.

How will it make any difference if they aren't actually making changes to the backend?

[brntbeer]

Requires you to have to ask them less questions when you run into a blocker. Helps you debug issues.

it helps you help them design the interface or design an API.

Are you just missing the fundamental point of why anyone learns anything? You learn more so you can do more and make more effective/informed decisions.

[Zimahl]

Requires you to have to ask them less questions when you run into a blocker. Helps you debug issues.

Possibly.

it helps you help them design the interface or design an API.

Ugh, that's a disaster waiting to happen. Dedicated backend engineers are usually terrible when it comes to what the user really needs and how to display it.

Are you just missing the fundamental point of why anyone learns anything? You learn more so you can do more and make more effective/informed decisions.

No reason to be condescending.

My point is that a front end engineer can make plenty of informed decisions without needing to know the schema of the database or the code in the MT. Does the API return what is expected? Yes = bug in UI. No = bug in server. Does the UI need something the API doesn't provide? Talk to the backend dev to get that into the API. It should be that simple.