INSIGHTS · 14 PIECES · UPDATED OCT 2026
Field notes from the work.
What we changed for clients, how we built it, and what we think about the tools. Written by the people who did the work.
RULE ENGINE & AUTOMATIONSHIPPED FOR AZCORP
After launchmanual routing work−50%average handling time18 → 7 mininternal escalations−35%saved per week across the team~14 h
A flexible rules structure with conditional routingDELIVERED ✓Audit-friendly decision trackingDELIVERED ✓
FEATURED · CASE STUDYCLIENT-REPORTED
−50%manual routing workCustom rule engine for operational decisioning
A configurable rule engine that replaced manual, inconsistent routing decisions.OPERATIONS · 4 MINRead the case →Latest
SHOWING 10 OF 14Q: Postgres or DynamoDB for orders?Call: Postgres, 2026-10-23, KYWhy: joins today, scale not yet a problem
ENGINEERING NOTE
Decision logs people actually read
One line for the question, one for the call, one for the reason. Anything longer goes unread, and an unread log is just a diary.6 MIN · OCT 2026 · KESHAV YADAVdef done(feature): return works(feature) and runbook(feature) and someone_else_can_deploy(feature)
ENGINEERING NOTE
Handover is a feature
Write the runbook while you build, not after. If your team can't run it without the people who built it, it isn't finished.7 MIN · OCT 2026 · KESHAV YADAVsprint = Fixed(weeks=2, price=quoted_upfront)sprint.outputs = [plan, prototype, fixed_quote]sprint.may_conclude("don’t build this")
ENGINEERING NOTE
Pricing a discovery sprint honestly
Fix the time, name the outputs, and say upfront what you might find out. How to buy, or sell, the first few weeks of a project without surprises.7 MIN · OCT 2026 · KESHAV YADAVexcept Unmatched as item: queue.add(item, owner="AP team", due=hours(24), reason=item.why)
ENGINEERING NOTE
The exception queue nobody owned
Automations rarely fail on the work they were built for. They fail on the few items that don't fit. Give exceptions an owner and a deadline first.7 MIN · OCT 2026 · KESHAV YADAVcost = buildcost += upkeep * years_in_servicecost += incidents * hours_to_diagnose
ENGINEERING NOTE
The hidden cost of one more integration
Every integration is a dependency you will maintain for as long as it runs. Price the upkeep, not just the build.7 MIN · OCT 2026 · KESHAV YADAVif rules_cover(task) and must_explain(result): use(rules)else: consider(model, with_review=True)
ENGINEERING NOTE
When not to use AI
If a rule can do it and someone has to explain the result, use the rule. A practical test for where AI helps and where it gets in the way.7 MIN · OCT 2026 · KESHAV YADAVcandidates.sort(key=lambda t: t.runs_per_week)first = candidates[-1] # dull, frequentassert first.rules_fit_on_one_page
ENGINEERING NOTE
Why your first automation should be boring
Pick the dull, high-volume task first. Boring wins compound, and they buy the trust you need for the interesting ones.6 MIN · OCT 2026 · KESHAV YADAV−40%routing incidents
CASE STUDYCLIENT-REPORTED
Custom reverse proxy for routing, access and reliability
A custom reverse proxy for reliable routing, access control and observability.FOUNDATION · 4 MIN~11 hsaved per week on admin
CASE STUDYCLIENT-REPORTED
AI automation and MCP set-up for internal workflows
AI automations built around the team’s real workflow, connected with MCP.OPERATIONS · 4 MINEVERY FIGURE CARRIES ITS PROOF LABEL
INSIGHTS · NEWSLETTER
One practical email a month. No filler.
SJK Engineering Notes: a lesson, an annotated artifact and a checklist, from work we actually shipped.
SJK NOTESOCT05Handover is a featureSJK NOTESOCT06Pricing a discovery sprint honestlySJK NOTESOCT07The exception queue nobody owned