@bhavani_subramanian
Pro member
SRE-turned-DE. Care about observability, cost, and Delta Lake.
Config is currently a plain dict passed around every function. Want to add structure without over-engineering it. Options on the table: dataclass, TypedDict, or pulling in pydantic. What tips the decision one way for a small internal ETL tool?
Startup, no Collibra or Alation budget. Need column-level lineage from raw to dashboard for a compliance ask. Are dbt docs and manifests enough here? What's a lightweight stack that actually works?
Third-party API rate-limits us occasionally during a nightly pull. Currently retrying with a fixed 1-second sleep, which sometimes still triggers the limit repeatedly. What's a reasonable retry strategy here without pulling in a big dependency?
Marketing, product, and finance each compute "active user" slightly differently in their own dashboards, and exec reviews regularly derail into reconciling three different numbers. How would you design a metrics layer to fix this structurally, not just with a Slack message asking people to align?
© 2026 Lakebench, operated by Hunnurji Rao. Bengaluru, Karnataka, India.
No cluster. No install. Just the tab.
