The rule it setsHand people a tool and they use it the way it fits, not the way you meant. If every shape fits in the square hole, that's where it's gonna go. Know who's really using it before you ship.
Contents
What's here.
Quickest read first, deepest last. Jump anywhere; each section stands alone.
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.
02 · Built
What I've built.
Three years architecting, leading, and managing the data modernization of a 300+ location automotive collision-repair operator across eight workstreams (Manager at SDG). Client anonymized, outcomes as delivered.
01 / 08platform · foundation
Cloud data platform
On-prem warehouse → cloud-native. Near-live, under 15 minutes, for nearly every flow.
Azure · Snowflake · dbt · Qlik
02 / 08finance · automation
Cash Application automation
~97% of electronic payments auto-matched. No more manual allocation.
Three working side projects where I'm actively exploring vibe coding and AI-assisted development flows.
React Native · Expo · SQLite · TypeScript
Custom Productivity App
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: increasing both the speed and quality of vibe coding through detailed documentation of requirements and architecture decisions.
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. Key point: the illusion of an answer is more dangerous than no answer at all.
Not built (yet). Five architectures I've worked through end to end, with the business case already made. Three stack into one data platform: owned ingestion, an agile scorecard, a best-/worst-case ROI engine. Leaner bets on PR-review throughput and cross-system workflow sit beside them. Open any for the full thinking.