Our product pages exist to sell engagements. They’re tight, scoped, and predictable on purpose — a CTO who lands there should know in 60 seconds whether Quarter Stack fits their problem.
But the actual day-to-day at TwiceData is messier than that. Half the value we deliver to customers starts as a small experiment, a one-off script, or a “what if we just shipped this” conversation on a Tuesday afternoon. Those don’t belong on a service page. They belong here.
What you’ll find here
- Tool releases. Small things we built — open-source or internal — that we think are worth showing. dbt macros, lineage gates, semantic-layer helpers.
- Engineering notes. Hard decisions from real engagements, anonymized. Why we chose a certain refactor path. Why we backed off a different one.
- Field results. “We tried X on a real customer’s warehouse and got Y.” Real numbers, real tradeoffs, no demoware.
What you won’t find here
Thought leadership. SEO content. Generic blog posts about “the future of the data stack.” If we’re not shipping something concrete, we’re not posting.
How often
Whenever something is worth posting. No editorial calendar. Some weeks two posts, some months zero. Subscribe via RSS (coming soon) or just check back when you’re curious.
Why now
Two reasons. First, prospective customers keep asking us to show them what we’ve actually built, and Slack messages don’t scale. Second, we genuinely think a few of these patterns deserve to be public — in particular the lineage-gate work and the semantic-entity governance we’ve been hammering on with the last three engagements.
––