Varigence
@Varigence
Followers
469
Following
179
Media
1K
Statuses
2K
Varigence builds automation software for the modern data stack, empowering teams to rapidly design, deploy, and own data solutions across the MSFT ecosystem.
Joined September 2009
Ship on Friday, sleep on Saturday. BimlFlex helps teams make change safe—and quiet.
0
0
0
Elasticity saves money only if pipelines are efficient. Push logic close to storage and drop unused columns early.
0
0
0
Make late‑arriving data boring: declare policies once (hashdiffs, tolerances), and let templates enforce them.
0
0
0
Automate the boring parts so weekends are boring too. (In the best way.)
0
0
0
Snowflake, BigQuery, Synapse, Databricks—pick what fits. Just don’t tie business rules to a runtime.
0
0
0
Thinking cloud migration? Gains are real—but so is the rebuild. Our playbook highlights where automation saves weeks on schema, pipelines, and docs. https://t.co/JZr0mfDVnm
0
0
0
Refactor fearlessly: when tests and lineage are generated with code, refactors get boring (that’s good).
0
0
0
Small wins compound: one domain, one pipeline, one week. Define metadata, generate artifacts, publish docs. Repeat.
0
0
0
Runtime engines come and go. Invest in metadata that outlives the tool du jour.
0
0
0
A great naming standard is a gift to your future teammates. Short, distinctive, and discoverable.
0
0
0
If rollbacks are your hobby, we can help you find a new one. Metadata‑first, test‑heavy pipelines FTW.
0
0
0
Your backlog isn’t big because your team is small—it’s big because work isn’t reusable. Solve it in patterns.
0
0
0
Impact analysis > surprise outages. See the blast radius of a change *before* merge, then ship with confidence.
0
0
0
SCDs explained in plain language. Where manual SCD2 breaks and how declarative flags + generation make history reliable *and* agile. https://t.co/x2939SrbZ9
varigence.com
Master SCD automation for agile teams: eliminate manual Type 1/2 implementations, generate consistent history logic, and configure changes through metadata.
0
0
0
Governance that ships: owners, tags, and consent flags should travel with attributes, not live in a wiki.
0
0
0
“Self‑service” doesn’t mean DIY pipelines. Give teams stable marts and a glossary that maps to real columns.
0
0
0
Stop pasting SQL for common transforms. Parameterize once; let generators stamp out the rest.
0
0
0
Weekend check: data contracts green, lineage current, SCDs boring. Proceed to hammock.
0
0
0
Dev/test/prod shouldn’t be snowflakes. Promote versioned metadata and rebuild per environment for parity.
0
0
0