Website screenshot / before-after slot
Reserve this for a real client build, redesign comparison, or ContactSetup example once a project is ready to show.
Systems Developer and Simulation Designer
start here / web systems / simulation
Systems Developer and Simulation Designer
I build small business web systems, PHP tools, physics simulations, and game-system prototypes.
This is the front entrance for my client web work, technical experiments, and long-term game technology direction.
Web systems, PHP structure, simulation work, proof building, and long-term game technology.
start here
osvaldovaldez.com is the main domain
overview
My work is split into practical client systems and deeper technical systems.
For clients, I build clean websites, domain setups, contact forms, hosting structures, email forwarding, and simple tools that make a business easier to find and easier to reach.
For technical work, I build and study physics simulations, reusable PHP structures, game-system prototypes, engine architecture, low-level graphics, and persistent-world ideas.
main paths
client-facing work first, technical depth behind it
proof layer
screenshots / GIFs / code / case studies
Reserve this for a real client build, redesign comparison, or ContactSetup example once a project is ready to show.
A visible spot for the contractor demo, future barber demo, and any niche template that proves the service quickly.
Use this for a repository, PHP engine snippet, tool screenshot, or short explanation of a working system.
Use this for a simulation clip, game-system prototype, engine test, or physics visualization when ready.
active direction
A plain list of what I am building, studying, and tightening right now.
method
I build in layers so the work can be understood, changed, and reused.
A website should guide the visitor quickly: what it is, who it is for, what to do next, and why it should be trusted.
A simulation should be built from rules, constraints, data, and systems that can interact over time instead of feeling like a visual trick.
The common rule is structure first, presentation second, polish always.
design / MVC shell
The visual side uses Contrast, Repetition, Alignment, and Proximity. The technical side uses a small PHP MVC shell. One guides how the page feels; the other keeps the code reusable.
The goal is to keep pages visually clear, technically organized, and easy to expand without repeating the same layout code everywhere.
timeline
Client web systems, reusable MVC shell improvements, ContactSetup offer refinement, and technical proof sections.
Dead Insomniac studio direction, engine concepts, and persistent-world system planning.
Web systems, local business tooling, client-focused technical work, and reusable site structure.