May 13, 2021 § Leave a comment
May 5, 2021 § Leave a comment
May 2, 2021 § Leave a comment
A concrete proposal for Imagining a Data Resort as enforcing a Model-View-Controller architecture across multiple Software-as-a-Service applications. The key is replacing transient enterprise data integrations with a persistent “sync house,” and making that the one full-service Source of Truth for data, schemas, and business logic.
- Ingest data from Salesforce, NetSuite, etc. (e.g.,
- Store raw data in a LakeHouse (e.g., Databricks, Delta Lake; or just Redshift)
- Aka “ELT vs ETL“
- Manage schemas via dbt (e.g., dbt Cloud)
- View and report on appropriate data (e.g., Mode, Data Studio)
- Push updates (reverse ETL) back to source applications (e.g.,
Celigo, Get Census)
April 21, 2021 § 1 Comment
A data resort is where data comes to get pampered, so that it is prepared to get back to work.
The good news is that I finally understand how we really need to be managing all the business data in my organization. The bad news is that I don’t know how to articulate that in terms of industry-standard terminology (examples below). Worse, I’d probably use the wrong term (or the right term incorrectly) leading to endless rounds of frustrating conversation.
Therefore I’ve coined a new term (“data resort“) which I can define as the exact thing I want. Hopefully you my dear readers can help translate that into something concrete I can efficiently buy+build today!
Let me know your suggestions in the comments or via email.« Read the rest of this entry »
December 10, 2020 § Leave a comment
- Obsess over a Wildly Important Problem that has not been properly characterized
- Identify a novel point of technological leverage for solving that problem
- Discover a market hurting enough to pay for even a crappy solution to that problem
- Iterate and improve on all the above until you die, fully solve the problem, or hand it over to someone who can do better.
July 21, 2020 § Leave a comment
October 4, 2019 § Leave a comment
Documenting this in a blog post because it drove us crazy trying to figure out exactly what was involved, even though it was actually easy to implement once we understood all the terminology.
In order for our previously-authenticated users to automatically log into Salesforce, we needed to:
- Create a “/sso-url” on our node server for our web app to access
- When our web app GETs that URL, create and a return a SAML Identity Provider (IdP) using
- That IdP is interpreted by the web browser a redirect to the Salesforce URL (returned by the function assigned to `getPostURL`)
- Salesforce just needs to have the IdP certificate and Entity ID in its SSO Settings
Below are additional details on why we needed this.
December 17, 2018 § Leave a comment
- Disrupting Programming
- Can we enable people who don’t know programming to build applications?
- Is there a way to structure, pipe, and manage data better?
- Disrupting Education
- Can we educate humans in interesting ways so that they learn to think in multi-disciplinary ways?
- Can we educate people in small, continuous ways so they keep learning throughout their lives?
- Disrupting Urban Transport
- Can we build new transportation methods that enable us to take someone form point A->B faster?
- Is there a way to build better, cleaner cities?