Don't let your team working be like this:

Frontend: Hey, is the API ready?
Backend: Sure, will give you later

Frontend: @backend, is the API ready?
Backend: yeah, yeah, will give you later, yesturday is busy.

Frontend: @backend, is it ready?
Backend: Been working on some prd bugs, will give you later

Frontend: @backend...
Backend: ...

Frontend: @backend...
Backend: Oh, I just find out that you should ask @backend_b for this API...

(I was actually trying to get my avatar, but this story is real)

  • 9
    So is it the frontend or backend fault?
  • 11
    @devTea I feel like when stuff like this happens, the whole dev team gets the shit, so at the end of the day, it kinda doesn't matter, lol
  • 7
    @devTea I think it's mostly that the whole team lacks a well-established rule to get things done, instead of any parts problem, though personal issue may exists.
  • 0
    @devOc oh I thought you was blaming someone, my bad
  • 4
    @devTea Still, I suppose this should be a prevailing problem between most of the teams who only hire people to get job done instead of having a vision of building something. personal opinion tho.
  • 6
    Why not agree the API contract up front and produce a swagger doc for it? Then frontend can mock it out to their hearts content while backend build it. As long as everyone sticks to the pre agreed API.
  • 3
    @taRunTime is the API ready?
  • 2
    @EloquentPrick yeah yeah sure.. soon I'll share the war.. 😬😬
  • 9
    Plot twist: It's actually a FullStack developer's monolog.
  • 3
    Mocking back end APIs are the first thing front end team should figure out, let the back end team sweat out to implement it. Just loving GraphQL for it.
  • 1
  • 2
    @devTea both, they are mutually !important
  • 2
    @devTea Why are you always to reply to 80% of the rants I read 🤔
  • 1
    @DefiniteGoose I... I don’t know?
  • 2
    Typo, the first* to reply. Still cool though
  • 2
    Good Thing when you write both like me 😄
  • 0
    @frontend API is ready 😎
Add Comment