"The illusion of an answer is more dangerous than no answer at all."
On chat-with-data & semantic layers
WIP · v0.15 · 06.02.26
"The illusion of an answer is more dangerous than no answer at all."
On chat-with-data & semantic layers
"Obsessed with rigorously connecting what I'm building to business value — by working backwards from understanding the business."
Most data work asks 'is this elegant?' — Nick asks 'is this the right question?'
"I don't buy into the logical fallacies of the experts or the majority in the slightest."
Not contrarian — first-principles by default
"With another candidate, the next thing is the next thing. With me, maybe — but the thing after that is in great peril."
Forward-thinking, not just execution
"A data pipeline's time-to-value was never limited by writing joins — it's limited by understanding the business."
Where data value actually comes from
"I don't have grumpy days at the office, or days I let my standards down."
Consistency as a differentiator
"So much human capital wasted moving numbers around to make a board deck sound better — regardless of the business health underneath."
On where analytics effort goes to die
"Not everyone is capable of being a data analyst. Nor does everyone want to be. And nor should they."
— Nick, on the consumption layer. see source
The rule it setsHand people a tool and they use it the way it fits, not the way you meant — every shape crammed in the square hole. Know who's really using it before you ship.
In funnel order. Stand-alone reading; skim or commit.
In Nick's words — lightly edited for clarity. The full transcripts live in the Q&A.
I'm at heart a positive, optimistic, energetic, extroverted person who gets energy from being around people and solving problems. Hard to talk about myself without mentioning real ADHD-hyperfocus tendencies — I take a new problem and work at it until I find a solution. Serious about the mission, but myself: mixing in positive energy and awkward jokes that are often more confusing than funny.
Where I separate myself in data and analytics: I'm obsessed with rigorously connecting what I'm building to business value — by working backwards from understanding the business. A lot of smart people build elegant solutions stakeholders love; that doesn't mean they're providing real business value.
On the negative side, I tend to over-engineer — to build for the abstraction too much. Things that aren't complex to me can be overly complex to others, and I don't always predict that well. Sometimes there's a simpler path to value.
And I don't care much what the trends or "consensus" best practices are. Not overtly contrarian — but I don't buy into the logical fallacies of the experts or the majority in the slightest.
One engagement — three years architecting, leading, and managing the data modernization of a 300+ location automotive collision-repair operator (Manager at SDG). Eight workstreams; client anonymized, outcomes as delivered.
Cloud data platform
On-prem warehouse → cloud-native. Near-live, under 15 minutes, for nearly every flow.
Azure · Snowflake · dbt · Qlik
Cash Application automation
~97% of electronic payments auto-matched. Manual allocation, gone.
UiPath · Snowflake External Functions · dbt · Qlik
NetSuite accounting integration
Swapped a packaged connector for a pipeline finance actually owns.
Snowflake External Access · NetSuite · SOAP · Azure Data Factory
UKG HRMS event-driven pipeline
A system with no push API, turned into near-live HR events.
Azure Durable Functions · Snowflake · UKG · FreshService
Central Review estimate-scoring API
Every estimate scored in under 15 seconds — before a carrier sees it.
Azure Functions · Snowflake · Streamlit · Qlik
Next-Best-Action conversational analytics
ML flags what's shifting; operators get the next move — no analyst required.
Snowflake · ML anomaly + trend detection · multi-agent LLM · Qlik
Insights Hub & KPI analytics
One screen: your top 3, your bottom 3, where you rank.
Qlik · Snowflake · normalized KPI store
Estimate Recommendation Engine
Learns from history to fix estimates before they're sent.
Python · association rules · anomaly detection · Snowflake
Three projects, all in active development. Each ships something real — but the real artifact is the disciplined, AI-assisted process behind it.
A local-first recurring-event tracker built to test one idea: that lists, habits, tasks, and timers are all the same primitive viewed differently. Everything is one event-sourced items row — behaviors drive logic, labels drive display. Less a finished app than an exploration of how far a few primitives stretch before complexity is forced.
A local-first desktop tool to capture work items across Azure DevOps and Jira in seconds — hotkey, voice, or paste. A half-sentence becomes a fully-fielded ticket via a Claude pipeline with per-field confidence. The deeper experiment: a governance layer around the AI agent — principles, invariants, decision records — making the codebase a proving ground for disciplined agent-driven development.
Turns Claude Code from a coding tool into a stateful project manager. One bootstrap command and 11 questions render a project skeleton: up to 19 custom slash-command skills, a versioned doc spine, and hooks enforcing consistency every turn. Not "can an AI write code?" but "can an AI run the project?"
Six industry trends, reacted to from first principles — the short version. One throughline: the illusion of an answer is more dangerous than no answer at all.
A position — POV plus why-not-yet, not a backlog.
Coming soon
The full interviews, by theme — the receipts behind every claim on this page. Every chatbot citation links straight here.
A chat trained on the full corpus — every answer cites its source in the Q&A. Always in the top bar, anytime.