Human judgment.AI leverage.Real-world proof.

I turn ideas into tested software, physical systems, images, games, and practical workflows—using AI to move faster without handing it the final say.

AI-assisted productionHuman-directed image, content, and workflow creation with quality control.
Context systemsPortable, drift-resistant project knowledge built for repeatable AI use.
AutomationSmall-business systems, software, documentation, and delivery tools.
VerificationReal-device tests, source truth, release evidence, and explicit limits.
One stance across every project

AI can widen what one person is capable of building.

It does not remove the need to choose the right problem, set constraints, or reject a convincing mistake.

The portfolio is the evidence trail: idea, direction, implementation, failure, correction, and result.

AI is leverage, not autopilot.

Good automation still needs clear intent, accurate inputs, tight constraints, and review. The goal is to ship useful systems and assets without letting speed replace judgment.

01

Define the real job.

Start with the outcome the artifact must create—not the model, app, or feature that sounds impressive.

02

Separate truth from noise.

Identify authoritative references, real constraints, damaged inputs, assumptions, and what remains unknown.

03

Direct the build.

Use AI to accelerate exploration, reconstruction, coding, documentation, and production while preserving human control.

04

Test where it matters.

Run the software, install it on the device, print the part, show it to a user, or put the result into the environment it must survive.

05

Correct and document.

Preserve failures, explain limitations, record what was actually verified, and ship only what the evidence supports.

This page is part of the proof.

This design began as an AI-assisted pilot. Brian set the direction, supplied reference material, tested versions, and approved the V6 design. The site now uses shared source files, with browser testing and owner feedback shaping the implementation.

The result demonstrates the same operating rule as the projects: conversation can accelerate production, but ownership, judgment, and publication authority stay human.

01Describe

Explain the audience, goal, constraints, and desired experience in ordinary language.

02Prototype

Turn the conversation into working copy, visuals, code, and interactions.

03Test

Open it in a browser, use it, compare it, and expose what did not work.

04Approve

Keep the useful result, revise the misses, and publish only after human review.

The project atlas.

One place to understand the breadth of the work. Public pages open directly; private and unfinished systems are labeled instead of being disguised as launches.

Warm 1980s-inspired basement maker room with a workbench and a skeletal whale model

Practical AI for people who do not think they are “AI people.”

The first education offer is intentionally small: an in-person Oxnard workshop where beginners bring an everyday problem, learn to add context, inspect the answer, correct it, and know when to verify.

Built by a working photographer, maker, and AI-directed product builder.

I did not begin as a traditional software engineer. I began with problems I wanted to solve and projects I wanted to build. The site should make that journey legible: not “trust me, I know AI,” but “here is the artifact, here is what failed, here is what changed, and here is what actually works.”

The public pages remain useful on their own. The redesign gives them one shared identity, one navigation system, one status language, and one honest way to distinguish finished work from active prototypes and research.

This redesign is itself an AI-assisted case study: a conversational brief became a working pilot, then changed through direct browser testing and owner feedback before any live update was allowed.

Capabilities

Built around practical execution.

  • AI-assisted workflows and prompt systems
  • Product image production and Photoshop finishing
  • Context packaging and reusable project memory
  • Schema, documentation, and release notes
  • Small-business operations and customer-facing delivery
  • Verification-minded publishing and support surfaces

Have a real problem worth building around?

For AI-assisted workflows, visual production, documentation, product experiments, or beginner AI education.