4 ms·
Having the opposite experience with it as a small team, and I can see how it would work great in my past large teams. I bet you're gonna have the same complaint
by welder 3y ago
Having the opposite experience with it as a small team, and I can see how it would work great in my past large teams. I bet you're gonna have the same complaints about any API you use not just tRPC (junior developers not thinking about interfaces).
- haney 3y agoI’m willing to admit that poor usage can make any tool a problem. But, tRPC is set up to make it easy to directly expose your backend for use in a component. For new projects that’s fantastic, for larger projects and teams having the ‘friction’ of defining a gRPC, GraphQL or REST endpoint is leading to more thoughtful API design and ability to keep isolation between layers.
- welder 3y ago> having the ‘friction’ of defining a gRPC, GraphQL or REST endpoint is leading to more thoughtful API design Make devs slower so they code smarter? More friction is just that, it just frustrates devs it doesn't make them code better. tRPC enables good teams to ship faster. Less friction means doing what the team was already going to do anyway, but faster.