he0001

48 ms·

211.
by he0001 7y ago
So the main sell point is to reduce traffic and let the backend sort out the n+1 and caching problems. I can see a bunch of problems with that, like required fields etc, which also must be fulfilled by the client and would be very fragmente
212.
by he0001 7y ago
Again, I don’t see how it can reduce read APIs. If you haven’t read the data you can’t change the data. Also I fail to see how graphql can simplify an API, the graphql operates on the actual APIs so if you don’t understand those, you’ll pro
213.
by he0001 7y ago
But Graphql doesn’t enable more functionality than the API already gives you. You don’t get more access to data just because you use graphql? And a team that gives direct access to their data is in very much deep trouble already. I really d
214.
by he0001 7y ago
But graphql cannot do more than the API already does? It’s constrained to the capabilities of the API. Such as if there’s no way of updating a field, graphql won’t do that either? So it can only make over-fetching more efficient? And by wha
215.
by he0001 7y ago
But that’s the thing. Should you invest in an obsolete API or just change it? If you don’t, you have both an obsolete API and a more complex solution instead of just changing your API. And if you don’t change your API to adapt to the newer
216.
by he0001 7y ago
But that’s not what I mean. I mean that your original resources are not the the actual ones you should expose. Hence you have designed your API wrong. And I don’t agree that a resource becomes more tightly coupled if you write it right. I
217.
by he0001 7y ago
Are you saying that graphql bunch those multiple requests into a single, actual, not perceived, request?
218.
by he0001 7y ago
If I write an API that exposes the resources A,B and C. Now I use graphql to access a subset of all of those resources, doesn’t this just mean that I have written the wrong API? That I would ditch A,B and C and write a resource D which just
219.
by he0001 7y ago
How can graphql reduce the number of reads? If you are reading stuff you don’t need why are you making those calls? And if there’s no API for for you to get the data how would Graphql know about it?
220.
by he0001 7y ago
I’ve always thought the perceived rapidness is because you are now able put code in the front end which really should be existing in the back end and while at the beginning it’s faster development, you just delay the inevitable problems of
221.
by he0001 7y ago
I run a one-man project and I write test first unit tests for all of my code. This has enabled me to advance the code with new functions without breaking current API’s. The tests are not in the way and usually doesn’t need to change because
222.
by he0001 7y ago
I think it really have destroyed the idea of how the previous generation think that the next generation should look like. I think we’re only in the beginning of a very different world the post WWII folks lived. People grow up much faster no
223.
by he0001 7y ago
I’m not so sure about this. A one liner may have its merit when you write it at that very precise location right now, but as the code grows the one liner may not have the same merit any more. But that may not always clear when you wrote it.
224.
by he0001 7y ago
An organization can only be flat if you can’t be fired by someone else or you can fire anyone else. As long someone can do that there’s always that inequality.
225.
by he0001 7y ago
How does it handle transactions and locking? It seem to support multiple databases, does it handle distributed transactions?
226.
by he0001 7y ago
Should every API be modeled after how react works?
227.
by he0001 7y ago
Correct me if I’m wrong here, but wouldn’t these attacks be translatable to anywhere there are read/write discrepancies?
228.
by he0001 7y ago
Isn’t all reads and writes already separated?
229.
by he0001 7y ago
I think you are right, though doesn’t your conclusion mean that this pattern, and any pattern that isn’t “simple enough”, is automatically disqualified? I do think that any pattern that is more complex than your business case is always the
230.
by he0001 7y ago
How do you cut your service boundaries?
231.
by he0001 7y ago
I think the most common problem with ORMs is that people doesn’t know when to use the ORMs functionality or when to write their own query. This always leads to N+1 problems and unmaintainable code, because when you eventually finds those pr
232.
by he0001 8y ago
Do they guarantee that if a write is done one region, when completed upon return, is available when read in another region?
233.
by he0001 8y ago
Functional programming is beautiful and contained, the real world is cruel, toxic, chaotic and doesn’t give a damn about functional programming.
234.
by he0001 8y ago
I think the poster is spot on. However I think that this reasoning would lean towards defensive programming. And this produces “ugly” code. And for that reason a lot of people don’t like it.
235.
by he0001 8y ago
While I agree mostly what you are saying, I would want to add that one thing we should have in mind and it’s that most of our current risk assessments of nuclear power are done on current technologies. And also the other technologies we cou
236.
by he0001 8y ago
I’ve been using Kubernetes for a while (1,5y). And I can’t say I’m very impressed. For anything simple it works fairly well. But as soon you get outside the “normal” workflow it gets downright hard. Certain areas are opaque AF and if things
237.
by he0001 8y ago
And you don’t think it’s legitimate to write those two pieces, although there are 4 years between them, two different cases, and two different persons that wrote them? I think for this particularly case, you can’t say it’s wrong. It’s two d
238.
by he0001 8y ago
I’m curious, what's wrong with the two CNN articles? One is written 2015 and the other 2019 by two different persons and one seems to be a doctor?
239.
by he0001 8y ago
I’d say microservices for the sake of microservices is an anti pattern. Microservices does have their usages.
240.
by he0001 8y ago
I think these things are the holy grail of computing. It would be very nice if it worked but frankly it won’t. I’ve been working in the insurance industry and for many many years they have tried to come up with a consistent scheme for insur

More ›