01 / A starting point

The compressed
version is
misleading.

A résumé lists positions. It leaves out the decisions.

A label names a category and drops the exceptions. Both are useful until you mistake what survived compression for the whole account.

I build software, connect business systems, and investigate what happens when they disagree. This notebook includes the decisions, failures, and convictions that a job title leaves out.

02 / The questions underneath

Check the explanation.

Three questions I use when an explanation sounds complete but something still refuses to fit.

I.What is the system actually doing?

I once spent several sessions debugging a reverse proxy whose interface and configuration file both looked correct. The running process was still using an old port. I had been checking what the system was told to do. It was doing something else.

The reverse-proxy lesson →
II.Why does this work need to happen manually?

Before automating a task, I want to know why it exists. Does someone need to make a judgment, or are they carrying information between systems that cannot talk? Writing code before making that distinction can preserve a process that should have been removed.

Processes and integrations →
III.What would change my mind?

If I cannot say what would change my mind, I have not finished examining the belief. That applies to a diagnosis, an argument, and a conviction I would prefer to keep.

How I think →

03 / Further in

An incomplete index.

01AboutHow I think. What I value. How to disagree with me. 02Projects & practiceERP, integrations, a runtime fault, and an account of what failed. 03MethodsIdentity, evidence, and how much trust is justified. 04Favorite quotesSelected passages, their context, and my reading of them. 05Favorite moviesHard Lessons. Loves. 06MusicA listening notebook. Selections still to come. 07CorrespondenceTell me what happened and what does not add up.
∴

The details belong here because they can change the verdict.