37 ms·

The test is to ask ask a full stack developer responsible for both sides what they would do! (And of course, accommodating the data needs of the UI is the answe

• sibit 4y ago
  Exactly. My understanding is the API accommodates the frontend data which accommodates the design which accommodates the users needs.
• wruza 4y ago
  What a fullstack guy would do is irrelevant here, because if their requirements changed, they’d just redo it. It’s not about who does the job, but about where we end up at when the format becomes obsolete. Likely scenario: backend formats data and moves on / gets busy elsewhere. Frontend changes, so that data is now required in a different format. Frontend decides to just reformat it at their side because of schedules. Now it’s a mess and nobody knows why. The root of the problem is this stupid frontend/backend team division when it’s actually a single program. That’s where the idea of “let’s ask fullstack” comes from. But there’s no good answer this guy could give you, apart from “stop drawing stupid dividers across the whole”.
  • survirtual 4y ago
    This is why you version an API. Or just use GraphQL-esque methods, but versioning will poke its head in somewhere eventually.
  • operatingthetan 4y ago
    >What a fullstack guy would do is irrelevant here, because if their requirements changed, they’d just redo it That was obviously a really general rule of thumb not intended to be an actual architecture guideline...