Skip to content

Writing

Writing

Notes on how production systems are designed, published, and kept honest after launch. New essays appear alongside project work and research.

Read

More essays

2026-09-12SaigaVision · Field intelligence

A Bounding Box Is Not a Census

A wildlife survey becomes useful when detections become identities over time, not when a model draws attractive boxes on video.

Read
2026-09-10UAV field systems · Security architecture

Telemetry Is Not Trusted Because It Arrived

A packet can be present, well-formed, and still unsafe to treat as truth. The architecture has to make observation and command different paths.

Read
2026-09-09ANGA · Attribution systems

The Conversion Did Not End at WhatsApp

When a visitor leaves a bilingual site to talk to a person, the engineering problem is keeping the useful context alive without pretending the handoff is a pageview.

Read
2026-09-06Jamal Najem · Personal brand systems

A Career Is Not a CV

A long executive career becomes more useful when visitors can see the decisions, transitions, and point of view instead of scrolling through a formatted list.

Read
2026-09-05Middlelink · Healthcare operations

The Calendar Cannot Belong to CRM

When booking, patient flow, CRM, and ERP each keep a private version of the day, staff become the integration layer.

Read
2026-09-04Manufacturing operations · Anonymized

Company Before Factory

A shared factory floor can still contain several legal realities. The system has to know which company owns the movement before it reports the result.

Read
2026-09-03Operational CRM · Migration

The Graph Before the Screen

A CRM becomes useful when it can express the relationships the team actually works with, not just the screens a legacy system happened to provide.

Read
2026-09-01Practice · Editorial governance

How Case Studies Are Published

A public work record should explain the engineering without turning confidentiality into a missing section or a marketing excuse.

Read
2026-08-31Practice · Reliability writing

Failure Conditions in the Record

A system description that only records the happy path is a brochure. The useful record names the trigger, the detection, and the response.

Read
2026-08-30Practice · Production

After a System Launches

Deployment is the moment the system starts meeting operators, failures, backups, migrations, and the person who did not build it.

Read
2026-08-29Practice · Decision making

Architecture Before Accumulation

A new service can be a solution, a liability, or a way to avoid naming the real boundary. The first question is whether the complexity has a job.

Read
2026-08-27Practice · Security and ownership

Explicit Boundaries Keep Systems Honest

The boundary between observe and command, patient and contact, company and plant, or role and record should be visible in the architecture.

Read
2026-08-26Practice · Systems correctness

Evidence Over Presentation

A successful response, a polished screenshot, or a high-confidence box is not the same as the business process producing the right result.

Read
2026-08-25Research · Field security

From UAV Research to Production Systems

The research questions are not separate from the production work: who can trust a telemetry path, where can it fail, and what should a detector prove?

Read