pro
Kyle Tully
Integration engineer who builds and documents ops systems
New to Contra
Kyle is ready for their next project!
A one-way sync has a clear story: system A changes, system B follows. A two-way sync has a failure mode one-way syncs literally cannot have. The two directions can trigger each other.
Picture Zendesk tickets linked to Salesforce cases. An agent escalates, which writes a case in...
github.com
public-portfolio/03-salesforce-zendesk-case-escalation/case-escalation-spec.md at main · nodrel-dev/public-portfolio
Integration and systems documentation samples for SaaS ops teams — runbooks, specs, and architecture decision records, written from the codebase. - nodrel-dev/public-portfolio
Here's a bug that ships to production silently and only shows up half the year.
You build an "Add to calendar" link. You test it in winter, it's perfect. Come summer, every event lands an hour off, and nobody can reproduce it on demand because whether it breaks depends on the...
I scoped the same internal staffing tool on two no-code platforms this week. Same app, completely different price, and actual usage had nothing to do with it.
Here's the trap nobody mentions: no-code is cheap until you need the two things every real internal tool needs. Your own...
Most integration documentation is written from interviews. Someone explains how the system is supposed to work, a writer transcribes it, and the doc captures the memory, not the system.
I do it the other way. I read the actual workflow exports, configs, and source, then document...
