Senior Solutions Architect
Software product company · Jan – Apr
This year
2026 in work.
What changed, what got built, and what it taught. Commit counts are non-merge commits across the repositories I work in, de-duplicated by hash.
Roles in 2026
Director of Technology & Innovation
Software product company · Apr – now
Projects in flight
Assessment delivery platform, v5
2007 – present · See projects
Assessment delivery platform, v6
2011 – present · See projects
Highlights by quarter
Q1 · 2026January – March · 352 commits
A test suite and a report builder
March. Two proofs of concept that stuck: a browser test suite with generated role checks, and a rebuilt report builder that shows the SQL before it runs.
Read the test suite note →Q2 · 2026April – June · 731 commits
Stepped into Director of Technology & Innovation
April, as listed on LinkedIn.
See the experience →A framework and messaging upgrade
May to June. Moved an integration service and a core app to a current framework and a new message broker, in many small merges.
Read what broke →Q3 · 2026July – September · 861 commits
Integration resiliency
July. Partner request timeouts made configurable and visible.
Read the note →CRM events in both directions
August to September. Decided what identifies a record when two systems both think they own it.
Read the note →Planning the next upgrade
September. A written plan for upgrading a large application with almost no tests.
Read the plan →Q4 · 2026October – December · 785 commits
Moving a very large file set
October. A resumable export with an audit log and a read-only check of what landed.
Read the migration →A CRM backup you can browse
November. A read-only backup of configuration, records and files, plus a small app to search it.
Read the note →Built the Kulkarni Inc. stack as code
November. CRM setup, AWS hosting for six hostnames, a brand system, and four sites with a blog.
Read the build log →
Learning and growth
Lessons from the year.
Write the status document on day one
On a long migration the dated status page was the most useful thing produced. People read it. Nobody reads a log.
Read the post →Pin behavior before touching it
Characterization tests record what code does today, odd parts included, so an extraction has something to be checked against.
Read the post →Treat every external ID as a design decision
When two systems share a record, pick one place that owns the identity and send only what you know to be true.
Read the post →Render before you approve
The first logo looked like a Q once drawn large. Looking at it at size caught what the sketch hid.
Read the post →Make scripts safe to run twice
Create-or-update beats create. A dry run shows what will change before it does.
Read the post →Writes are not instantly searchable
Search results lag behind writes, so the check polls until the count settles.
Read the post →Know what --delete deletes
One deploy flag would have wiped the other sites. Certificates cannot be edited either.
Read the post →