echrisinger

4 ms·

1.
by echrisinger 1mo ago
> X. Dev/prod parity > Keep development, staging, and production as similar as possible Gets interesting at the seams of software & data environments. If my preprod stack operates independently of my prod stack (due to differ
2.
by echrisinger 3mo ago
Typically this would be prohibited (at least as an employee)
3.
by echrisinger 5mo ago
As someone that works in a data domain, I'd say it's unlikely the ads are served on a single conversation basis in the near future, if they even are today. Any modern data org like advertising is optimizing metrics of conversion (
4.
by echrisinger 6mo ago
Has anyone considered a VCS that integrates more vertically with the source code through ASTs? IE if I change something in my data model, that change & context could be surfaced with agentic tooling.
5.
by echrisinger 2y ago
What's with the dismissiveness? The author is a senior staff engineer at a huge company & has worked in this space for years. I'd suspect they've done their diligence...
6.
by echrisinger 2y ago
I'm also curious how you went from a non-platformatized approach to adopting this platform; what were the important insights for strategizing, prioritizing, motivating teams to lift existing pipelines into the new thing? Open ended que
7.
by echrisinger 2y ago
How do you/AirBnB handle deeply linked features (2-hop+?) that are also latency sensitive? Maybe I'm missing something, but I don't imagine that with the transformation DSL described in Chronon. For our org, those are by far
8.
by echrisinger 2y ago
This isn't really a drop-in replacement; they don't offer transforms out of the box. Admittedly some of the transforms proposed in this article are a little simple & don't represent the full space of feature eng requireme
9.
by echrisinger 2y ago
I'd imagine a continuation... he is also the author of Zipline