We track three specific vectors: Heal, One Thing, and Walk with Jesus.

p.s. Want the visual map? You'll find a full FieldNote Sketch Summary of this inside the 'hidden' layer. Click this highlight to see the synthesis, share it with someone you know needs it and save a copy for yourself.

How do we support the emergence of a powerful GCM that expresses strategic and relational congruences (of analysis and action) within a GCM where diversity (ontological and epistemological) is inherent?

But if you're working on a bigger project, with multiple packages and a complex dependency tree, you might want to combine npm with a tool like Lerna.

This is why for a recent Angular+Rails project we chose to use a testing stack from the backend technology’s ecosystem for e2e testing.

We used testing tools that were in the same ecosystem as our backend technology stack for primrily three reasons: We owned both ends of the stack Team experience Interacting with the database

We chose to define the frontend in one technology stack (Angular+TypeScript/JavaScript) and the backend in another (Ruby+Ruby on Rails), but both came together to fulfill a singular product vision.

he goes on to talk about third party problems and how you're never guaranteed something is written correctly or that even if it is you don't know if it's the most optimal solution

Knowing all this, what would you do? Which path would you choose and why? The answer might seem obvious now that you come from the future - React