5 ms·
Sounds like we're talking about different levels of conceptual abstraction. Here's an example: I need to generate a report where I need to cross-reference data
by munchbunny 8y ago
Sounds like we're talking about different levels of conceptual abstraction.
Here's an example: I need to generate a report where I need to cross-reference data from A and B. I need to know where A is going, where B is going, how to modify the schema of the events going into B to add a specific piece of data, where we can process inputs from A, how to do the join, and how to add the report into the dashboard.
On the one hand, I could ask the surface level question "how do I generate the report for ____?" but really there's a whole lot to unwrap, and what I need is the information to do the unwrapping. I don't need a course on statistics, I just need to understand our specific architecture.
- wgerard 8y agoI think I see what you mean, though maybe I'm misunderstanding still. The answer (from my experience at Etsy, anyway) to questions like: > how to modify the schema of the events going into B to add a specific piece of data, was "Run schema_modifier", the docs for which were frequently obsolete. Figuring out how to "run schema_modifier" was usually a very frustrating experience in that particular instance, whereas unwrapping the actual problem was usually less frustrating.