§ 06/09

Resources

Field guides you can use today — with or without us.

G1 · 7 MIN

A systems inventory in one day

Before integrating anything, write down what you have. Make a table with columns: system, internal owner, data created there, data only read, how it can be accessed (API, export, UI only).

  1. Walk one typical order from first contact to payment and delivery. Every system you touch is a row.
  2. For each key object (customer, product, price, order) mark one system as the source of truth.
  3. Mark where someone copies data by hand. These are the first automation candidates.
  4. Note frequency: does data need to arrive instantly, hourly or daily?

The result is a draft systems map. It speeds up any project, because it answers questions that otherwise take several meetings.

G2 · 6 MIN

Webhooks that don’t create duplicates

Most services resend a webhook if they don’t get a quick reply. If your handler creates a record every time, you get duplicate orders or payments.

  1. Store the unique event ID and check it before processing.
  2. Reply 2xx fast and do heavy work asynchronously from a queue.
  3. Verify the request signature if the service provides one.
  4. Log the result with a human-readable error reason.
if (seen(event.id)) return 200;
queue.push(event); markSeen(event.id);
return 200;

G3 · 8 MIN

Checklist before submitting to App Store and Google Play

Store rules change; check current requirements in official documentation before each submission.

G4 · 5 MIN

Forms usable without a mouse