Francisco Caballero fjcero

Installation for GUI Users

Right click the file and choose information and choose to always open this file with Terminal.app
Go to the Terminal.app and do something like this chmod 744 Reset Spotlight.sh
There you go, you can now double click it so reset the Spotlight location
Optional: Uncomment line for the useCount to prevent Spotlight to forget that you already used it

GraphQL

Structuring App

https://medium.com/@colecodes/structuring-data-with-apollo-server-e114a302aec7 https://github.com/entria/graphql-dataloader-boilerplate https://github.com/thebigredgeek/apollo-resolvers/blob/master/src/resolver.ts

Authorization strategies

Data Model based: https://blog.apollographql.com/authorization-in-graphql-452b1c402a9

On implementing a client for feature flags in your UI codebase

This document isn't an explainer on Feature Flags, you can find that with my amateur writeup, or literally hundreds of better writeups out there.

This document is also agnostic to the choice of service you'd use: LaunchDarkly or split.io or optimizely or whatever; that's orthogonal to this conversation.

Instead, this document is a list of considerations for implementing a client for using Feature Flags for User Interface development. Service providers usually give a simple fetch and use client and that's it; I contend that there's a lot more to care about. Let's dive in.

To encourage usage, we'd like for the developer experience to be as brutally simple as possible. So, this should be valid usage:

	upstream ws_server {
	server 127.0.0.1:8080;
	}

	server {
	listen 80;
	server_name 10.1.2.225;

	location / {
	proxy_pass http://ws_server/;