5

Never ever ever ever ever ever ever ever ever ever ever ever give the opportunity, not even once, to let a BE decide how a front end is going to work. They will fuck it up 100% of the time. I’m sorry but it’s true.

Comments
  • 6
    I can attest that it works both ways.
  • 2
    yeah, I especially like when FE asks BE devs to create a single webmethod to return megabytes worth of initial data.

    yeeaahhh, good luck convincing the user the webpage is not stuck.
  • 5
    I've been trying to solve this problem for years now.

    Best thing I came up with so far was just talking to the FE devs closely when planning features, so we both understand the limitations and best approaches for the task and meet in the middle

    especially if there's no direction given from an architect. Those kinds of projects are completely dependent on the devs communicating
  • 2
    @Hazarth which is really nice tbh
  • 0
    @netikras

    I find this useful when your API is meant to only be consumed by your frontend.

    However, it's not suitable when you plan to open it up to general users.
  • 1
    UHM.

    Never trust any developers. At all.

    After all that's how we got stuff like JavaScript.
Add Comment