166 karma · joined November 1, 2017
For me, music started out as a practice of getting better and developing my abilities as a songwriter. As I’ve gotten older though it’s shifted more towards sharing the joy of playing with others. Jamming with people and making them happy by sharing songs is a reward in and of itself.
I feel pretty justified in my previous decisions to move away from Azure. Using it feels like building on quicksand…
Damn, that’s brutal. I mean, I never said I knew how to fix ComponentProps or generic components, just that they have issues…
All that said, I wouldn't rely on this extension as a way to deliver anonymized data to downstream consumers outside of our software team. As others have pointed out, this is really more of a pseudonymization technique. It's great for removing phone numbers, emails, etc. from your data set, but it's not going to eradicate PII. Pretty much all anonymized records can be traced back to their source data through PKs or FKs.
I also think there’s an avoidance to simply “translate” a GQL query into an SQL query. Not that it can’t be done, but it allows a lot less flexibility in the backend as far as code patterns that can be adopted. Basically it minimizes the use of ORM models, which may be a pro for some and a con for others.
I haven’t worked with GraphQL in over 4 years since I left my last job. I actively made a choice not to use it at my current job and steered the ship towards REST endpoints, mostly because it would be easier to build authorization middleware. Also like the author of the article discovered, code littered with dataloaders is a pain to maintain.
Honestly I’m a little surprised you haven’t seen this pattern. The only times it wouldn’t be used are when people rename variables, which is frankly a practice I abhor.