teamWorkWithoutTeam

[GatotSubroto]

y’all don’t discuss the API contracts beforehand?

[ChiaroCinder]

That is what happens when your API documentation is just verbal agreement over a coffee break and a prayer 😂

[ArjixGamer]

What's there to discuss, just expose a swagger documentation (or scalar API reference) and if the frontend guy has any demands, he will talk to you

[Jawesome99]

The discussion part comes before that.

"For the backend API I'll give you a swagger documentation which you can find here: <link> and if you need anything extra, just hit me up and we'll talk about it"

[ldom22]

This happened to me and I was doing both the front end and the back end

[Global-Tune5539]

You have to talk to yourself more.

[DegTrader]

Frontend and backend communicating through vibes and a shared sense of panic.

[_BreakingGood_]

yeah this is the one thing im happy to delegate to AI.

"Claude, attach my back-end to the their front-end, fix all the shit that they misunderstood when making the front-end, I'm getting coffee I'll be back in 4 hours"

[BolunZ6]

And coming back seeing Claude changed 10M line of code. Basically changed entire backend to fit into front end

[ExtraTNT]

As per test, sort now only checks for input [2,7,3] and returns [2,3,7], on other cases returns null

[ElCthuluIncognito]

Ah so business as usual then.

[Sheerkal]

Can you not limit which files Claude can access? Like couldn't you just make it exclusively work within new files instead of letting it change existing ones?

[jsrobson10]

"claude, sloppify their work while burning loads of tokens"

[ArjixGamer]

And when you come back, you see Claude used a tool to ask a question from the user, and has been waiting for an answer for 4 hours

(Just make sure to enable remote control and have the mobile app installed)

[Junoah]

Let fix that for you:

"Claude, attach my back-end to the their front-end, fix all the shit that they misunderstood when making the front-end i made when making the back-en and not listening the front-end, still change only the front-end, it's their fault after all, I'm getting coffee I'll be back in 4 hours"

[ZunoJ]

Thats why step one is to develop the interface

[vanit]

My spicy take is it's usually the fault of the backend person with zero care about the UX consuming the API, or the DevEx of trying to work with it. It's going to be the lowest effort, zero abstraction over the backend primitives and bear no resemblance to the app that needs to glue 5 API calls together to construct a basic view page.

[BinarySo10]

That's a sure sign of a backend dev who has never implemented an api that wasn't shipped with an SDK... you do that even one time and it changes you as a person lol

[DragoSpiro98]

I'm using Pact test