How engineering decisions hold up in practice.

Replacing Credential Sprawl with Organizational Memory

A structured WordPress database replaced scattered credentials and memory-dependent access.

Principle: Organizations should own their operational knowledge rather than depend on individual memory.

Building an Integrated Sign Ordering Operation

A custom WordPress platform connected CRM, vendor ordering, Kanban tracking, process stages, and employee work.

Principle: An operational system should make the whole workflow visible, not digitize isolated fragments.

Making Site Launches Repeatable

A structured checklist turned launch knowledge into a consistent team process.

Principle: Reliable outcomes should not depend on which experienced person happens to perform the work.

Designing Backup Redundancy People Will Maintain

Quarterly off-host backups and preserved launch states extended recovery beyond a one-month hosting window.

Principle: Simple and maintained beats comprehensive and abandoned.

Creating Client Instructions and an Audit Trail

Client guidance and project history replaced undocumented decisions and memory-dependent support.

Principle: Documentation should help the client act and help the team reconstruct what happened.

Turning Ad Hoc Estimates into a Repeatable Process

A collaboratively refined estimate template made project scoping more consistent and faster.

Principle: A useful standard improves through real use rather than pretending to be complete on day one.

AI as Team, Not Tool

AI becomes more useful when treated as differentiated perspectives rather than a single assistant.

Building Reliability Into Scheduled Systems

WP-Cron failures rarely announce themselves. They quietly stop scheduled imports, stale listings accumulate, and support tickets arrive days later. Reliability often means designing around silent failure.

Cleaning Up After a WordPress Compromise: A Systematic Approach

A repeatable methodology for triage, cleanup, and prevention after a WordPress compromise.

Measuring What Aging Looks Like

The absence of errors is not the presence of health.

Recognizing a Web Shell Before You Know What It Is

Detection through expected state rather than malware signatures.

When Software Assumes Cooperation

Shared infrastructure built for cooperation deployed into an environment defined by competition.

When the Calendar Becomes the Attack Surface

Bot attacks, the economics of defenders and attackers, and a plugin built from two live incidents.

When the Calendar Becomes the Attack Surface, Part 2

What happened overnight on the first real deployment, and why the plugin ended up with a self-healing state machine.