Skip to main content
ZombieMutex

30 results · ↑ ↓ navigate · Enter open · Esc close

Workbench / Issues

Bug & investigation tracker

Real build notes, test investigations and recorded fixes, with filtering and links to the full write-ups.

Engineering issue notebook

8 documented / 8 total
Tested
Measured accessibility after the entrance animation settles

The fade-in reduced effective text contrast while an automated accessibility scan sampled the middle of the transition. The steady-state contrast test now waits until animations complete; a separate test checks reduced-motion behavior.

What I learned

An animation can change contrast during its timeline. Accessibility testing needs intentional timing and a reduced-motion path.

Documented
Added lightweight motion without a new runtime

Implemented CSS-only page entrances, hover treatments for cards and social icons, logo motion, and accessible reduced-motion handling.

What I learned

Prefer transform and opacity, finite durations, and prefers-reduced-motion over a heavy animation library.

Documented
Changed Contact from business intake to a personal hello

Replaced the project-qualification form with optional name and subject, a message, and an email draft generated locally. Added strict HTTPS/domain validation for owner-provided public profile/invite links.

What I learned

A personal site should let someone say hello without requiring a company, budget or project scope.

Documented
Made Life a focused home for eight interests

Grouped hiking, cooking, robotics, IoT, mobile engineering, technology and travel under Life. Combined social identities in one place.

What I learned

A clear set of subjects is easier to navigate than publishing every optional calendar hobby as if it were a finished project.

Fixed
Closed a hydration race in the browser labs

Disabled user controls until hydration and URL-scenario restoration finish. Verified that stateful lab controls work after a production static export, not just inside the development server.

What I learned

Interactive static sites still have startup state boundaries. A control shouldn't accept input before its scenario is restored.

Documented
Published a browser-local Debugging Studio and three reference investigations

Added JWT decoding, HTTP policy checks, a TLS explorer, and a token-rotation model. Published independently testable public challenge, idempotency and refresh-token demos with explicit production limitations.

What I learned

Explain precisely what a simulation proves—and what it does not. Decode-only JWT views must never be described as signature verification.

Documented
Introduced the engineering Workbench

Added reference snippets, architecture diagrams, guided challenges, a glossary, an evidence index and a local reading library. Separated public inspectable source from conceptual case studies.

What I learned

A source link and a reproducible test say more than a generic claim of reliability.

Documented
Established interactive labs and full-text engineering search

Built browser-local reference models for nonce replay, API retries and session recovery, with discoverable technical topics, journal links and searchable documentation.

What I learned

A small working model can teach a failure boundary faster than a static diagram, provided its assumptions are visible.

This indexes real, dated build notes—not GitHub Issues or an open issue backlog. No public submissions or private trackers.