4 ms·
It looks like one poor choice leading to another poor choice. They probably chose Prisma because it may have helped them with GraphQL, whereas they most likely
by ivanb 3y ago
It looks like one poor choice leading to another poor choice. They probably chose Prisma because it may have helped them with GraphQL, whereas they most likely don't need any GraphQL at all.
Then they are screwing around with AWS Lambdas and package size, but what is the advantage of the Lambdas if they don't make your deployment easier? Just have a ECS and run whatever you want for better price/performance ratio and much higher performance ceiling.
I don't get which of their tools are improving developer productivity or software quality. It looks like every tool stands in their way. Why won't they just learn SQL and use it? What's is so low productivity about it? It's the highest level data manipulation language there is. Now they are bringing Kysely for supposed type safety. Yeah, good luck debugging, optimizing or changing the queries in any way. You'll have to convert from SQL to TypeScript and back whenever you'd want to develop the query in your SQL console.
What I see is a bunch of poor choices. Shiny tools standing in the way of getting stuff done.
- ehutch79 3y agoYour last sentence nails it. They’ve been sold a bunch of tools by tech influencers. Told that if you don’t use X you’re doing it wrong. They believed the hype. It’s hard to remember that, at this point, most tech influencers are shitposting or are full of shit.
- dimgl 3y agoThe thing is that they themselves are tech influencers. So it's not surprising this article is the way it is. https://www.youtube.com/watch?v=J2j1XwZRi30 https://www.youtube.com/watch?v=J2j1XwZRi30
- deleted 3y ago[deleted]