01 / About

What the title
leaves out.

Enterprise systems analyst and integration architect. Accurate enough for a heading. Several decisions missing.

Context

Between
the systems.

I work where a business process crosses from one system into another and something gets lost.

My background spans ERP development, systems integration, infrastructure, and business analysis. I have built internal applications, reports, services, and automation for manufacturing. More of my work now involves deciding what capability is missing, how to supply it, and who will maintain it.

That includes requirements, vendor coordination, technical standards, and documentation. Software that only its author can explain leaves the next person with a second job: reconstructing the first.

I also write fiction, read philosophy, play Magic, and listen to music. Those belong in the account without needing to justify themselves as professional development.

Working habits

Questions before conclusions.

01

Check the running system.

A correct configuration file once kept me occupied while a running process used an old port. I have a specific reason to distinguish configured state from observed behaviour.

02

Find the manual step.

Why is someone doing this by hand? I want to establish whether the task needs judgment, an integration, or removal before I automate it.

03

Trace the handoff.

What information leaves one system? What arrives in the next? Who notices when it fails? An integration needs answers to all three.

04

Account for the exception.

The detail that contradicts my explanation needs an answer. Calling it an edge case does not supply one.

05

Leave a record.

I copied shared code into several applications. Two versions diverged without a record of which was intended. The next person should not have to infer a decision from matching filenames.

06

Name the test.

What result would make me abandon this explanation? If every possible result confirms it, I need a better test.

Convictions

What follows
from them.

I am a Christian, an empiricist, and a rationalist in the broad sense. A belief does not earn an exemption from examination because I am attached to it.

I care about human agency. If I help someone understand their options, the decision remains theirs. They are allowed to choose differently.

Understanding a person’s reasons does not erase what their actions caused. Ignoring their reasons leaves the account incomplete. I want both in view, including when the person is me.

Precision and kindness place demands on how I speak: identify the error, explain the consequence, and give the person room to answer. Being correct does not require contempt.

Conversation

Enough detail to disagree.

  1. Name the claim.

    We can disagree more usefully once we know which proposition is in dispute.

  2. Include what does not fit.

    A contradiction is useful information. Leave it in.

  3. Allow a considered answer.

    I sometimes need to write a response before I know whether I agree with it.

Correspondence

Bring the real question.

Technical problems, arguments, or something you are still trying to put into words.

Get in touch ↗