[ { "id": "universal-cable-tester", "title": "Universal Cable Tester", "category": "Manufacturing Automation", "status": "Working prototype", "period": "2026", "featured": true, "public_ready": "Review employer details", "evidence": "Code + working hardware + fault-display photos", "summary": "A configurable production-floor tester for continuity, pin mapping, intentional opens, branched cables, Ethernet, and generator/stator harnesses.", "problem": "Production cable verification had become a repetitive pin-by-pin task. A simple continuity beep was not enough: some harnesses included intentional opens, branches, Ethernet mappings, or specialized generator and stator connections.", "solution": "Built an Arduino-based fixture that drives and senses up to 32 channels per side through multiplexers, compares readings against selectable cable profiles, and reports pass/fail conditions on an OLED interface.", "tech": [ "Arduino Uno", "4× CD74HC4067", "SSD1306 OLED", "C/C++", "3D-printed enclosure", "DB9", "RJ45", "Custom fixtures" ], "image": "projects/universal-cable-tester/01.webp", "detail": true, "highlights": [ "Profile-driven validation for multiple cable families", "Handles intentional open pins and branch-specific tests", "Flash optimization for the ATmega328P", "Public case study intentionally omits proprietary pinouts" ], "description": "I built a profile-driven test fixture around an Arduino Uno, four CD74HC4067 multiplexers, an OLED, and purpose-built connectors. The tester drives one conductor at a time, senses the far side, compares the measured map with the selected profile, and reports opens, crosses, unexpected connections, or a pass.", "iterations": [ "Started with direct one-to-one DB9 testing and a minimal menu.", "Expanded the channel plan to cover DB9, RJ45, generator sense points, spring terminals, and stator posts.", "Added profiles for intentional opens and branched Y-cables instead of treating every unconnected pin as a fault.", "Removed duplicate Ethernet profiles after confirming that continuity sees pin numbers, not T568A/T568B colors.", "Reworked physical channel mappings after real fixture wiring exposed assumptions that were correct in code but wrong at the connector.", "Reduced flash use on the ATmega328P and simplified navigation so the full feature set fit on an Uno." ], "result": "A working production-floor prototype that guides connector setup, tests the selected cable profile, and reports specific opens, wrong destinations, and shorts instead of reducing every defect to a continuity beep.", "lessons": [ "The fixture, connector labeling, and operator flow matter as much as the scan algorithm.", "Expected opens must be modeled explicitly or a correct cable looks defective.", "A profile database is more scalable than writing separate test logic for every cable.", "Public documentation should show the architecture without exposing employer pinouts or proprietary harness names.", "Specific fault reporting is what turns a tester into a useful production tool." ], "gallery": [ { "src": "projects/universal-cable-tester/01.webp", "caption": "Completed profile-driven cable tester in its 3D-printed enclosure, showing the top-level cable-category selector.", "review_required": false }, { "src": "projects/universal-cable-tester/02.webp", "caption": "Real failure output identifying multiple shorts and an incorrect destination pin instead of returning a generic fail state.", "review_required": false }, { "src": "cable-tester.webp", "caption": "Earlier fixture view showing the physical connector and enclosure development.", "review_required": false } ], "public_note": "Employer names, proprietary identifiers, exact pinouts, and confidential production details are intentionally omitted." }, { "id": "netcrate", "title": "NetCrate 1.2a", "category": "Networking", "status": "Field deployed", "period": "2024–Present · first commercial delivery 2026", "featured": true, "public_ready": "Yes", "evidence": "Product + documents + deployment", "summary": "A rugged portable emergency internet kit combining Starlink compatibility, three-carrier cellular support, isolated Wi-Fi networks, and battery-backed operation.", "problem": "Small response teams can arrive before fixed communications are restored or larger communications assets are established. Personal hotspots and a single carrier leave the operation dependent on one path.", "solution": "Designed and built a preconfigured field gateway with redundant internet paths, separate operational/public networks, external antennas, AC/DC/battery power, and rapid setup.", "tech": [ "Raspberry Pi 5", "SIM7600G-H", "Linux", "NAT64/CLAT", "Multi-WAN", "Starlink", "T-Mobile", "Verizon", "AT&T", "LiFePO4" ], "image": "netcrate.webp", "detail": true, "highlights": [ "Under-five-minute deployment target", "256Wh LiFePO4 battery", "Eleven external cellular/Wi-Fi antennas", "First deployment with Disaster Aid USA" ], "description": "NetCrate is a rugged, preconfigured field gateway combining Starlink compatibility, support for T-Mobile, Verizon, and AT&T cellular paths, separate operational and guest/public Wi-Fi, external antennas, Linux routing, and AC/DC/battery operation.", "iterations": [ "Moved from a collection of networking components to a single case that could be opened, powered, and deployed quickly.", "Built a Raspberry Pi gateway around an IPv6-only LTE environment, including NAT64/CLAT and local routing.", "Separated operational and public traffic instead of treating every connected user the same.", "Added external antenna and power architecture for a self-contained field unit.", "Shipping and field handling exposed mechanical weak points, leading to rework of retention, internal layout, and deployment readiness.", "Converted one-off technical work into documentation, pricing, evaluation agreements, procurement materials, and customer support planning." ], "result": "Model 1.2a was commercially delivered and field-deployed with Disaster Aid USA in March 2026. The current system is designed for under-five-minute setup after service activation.", "lessons": [ "A field product is hardware, network configuration, power, documentation, packaging, training, and support—not just a router in a case.", "Redundancy is valuable only when failover behavior is tested under real constraints.", "Physical ruggedization can be as important as software reliability.", "Customer discovery changed the positioning from “internet in a box” to an early-operations continuity tool." ], "gallery": [ { "src": "netcrate.webp", "caption": "NetCrate 1.2a project image.", "review_required": false } ], "public_note": "", "url": "https://nexaer.tech/", "url_label": "View the live NetCrate site" }, { "id": "aroma-alchemist", "title": "Aroma Alchemist", "category": "Embedded Systems", "status": "Active prototype", "period": "2026", "featured": true, "public_ready": "Yes", "evidence": "Code + hardware discussions", "summary": "An ESP32-S3 precision scent-mixing platform with a capacitive touch interface, audio feedback, and electronically controlled fragrance channels.", "problem": "A digital scent system needs repeatable dosing, a usable interface, and a delivery mechanism that can mix multiple scent channels without turning the prototype into an unmanageable plumbing project.", "solution": "Developed a touch-driven embedded interface around a Freenove ESP32-S3 display and evaluated atomizer, heated-wick, servo-valve, and duty-cycle mixing approaches.", "tech": [ "ESP32-S3", "LVGL", "ILI9341", "FT6336U", "I2S audio", "PWM", "Servos", "Atomizers", "Arduino" ], "image": "embedded.svg", "detail": true, "highlights": [ "240×320 capacitive touch UI", "Custom action sounds and I2S debugging", "Multiple mechanical scent-delivery architectures evaluated", "Designed around severe GPIO and enclosure constraints" ], "description": "Aroma Alchemist is an ESP32-S3 touchscreen prototype exploring controlled fragrance delivery through atomizers, heated wicks, servo valves, duty-cycle mixing, and guided recipes.", "iterations": [ "Brought up the 240×320 capacitive touchscreen and built the operator interface in LVGL.", "Reworked labels and layouts after early screens overflowed or hid important controls.", "Added action sounds and then chased I2S compatibility issues across ESP32 Arduino core versions.", "Evaluated atomizers, heated-wick tubes, and servo-controlled routing rather than locking into the first mechanical concept.", "Designed around the unusually limited exposed GPIO on the selected display board." ], "result": "A functional embedded UI and hardware architecture with the remaining work concentrated in the physical scent-delivery and calibration system.", "lessons": [ "The most visually impressive interface cannot compensate for inconsistent dosing.", "Board-package and library versions are part of the hardware design when audio and displays depend on them.", "Mechanical architecture should be selected by repeatability and cleaning requirements, not novelty." ], "gallery": [], "public_note": "" }, { "id": "beedi-cloud", "title": "BeeDI Cloud", "category": "Software", "status": "Live product / in development", "period": "2025–2026", "featured": true, "public_ready": "Yes", "evidence": "Application code + website", "summary": "A live hosted retail EDI portal that turns 850, 855, 856, SSCC-label, BOL, 810, and 997 workflows into a guided process for smaller suppliers.", "problem": "Small suppliers can be forced into retailer EDI workflows without the staff, budget, or vocabulary of a large enterprise integration team.", "solution": "Built a web platform around the 850 → 855 → 856 → SSCC/BOL → 810 → 997/999 workflow, plus a local AI marketing/coding agent for founder-led operations.", "tech": [ "PHP", "Python", "Streamlit", "Ollama", "EDI X12", "HTML/CSS/JS", "Windows/XAMPP", "SSL", "SEO" ], "image": "software.svg", "detail": true, "highlights": [ "End-to-end retail supplier workflow design", "Local LLM agent with product brain and content tools", "Custom website and hosting configuration", "Built for usability rather than raw EDI jargon" ], "description": "BeeDI Cloud is a live hosted retail EDI portal organized around the work a supplier must complete: receive readable purchase orders, acknowledge them, build ASNs and SSCC labels, create BOLs and invoices, track acknowledgments, certify retailer mappings, and move from sandbox to production.", "iterations": [ "Mapped the product around the supplier’s operational sequence instead of a generic document inbox.", "Built the web application and hosting stack on PHP, JavaScript, SQL, Windows/XAMPP, and SSL.", "Added a local Ollama-powered workspace for product knowledge, content, outreach, SEO, campaign planning, and coding.", "Reworked prompts after small coding models produced malformed marketing output.", "Separated the product website, agent tooling, and customer workflow so each could evolve independently." ], "result": "A publicly launched product site and application direction with a defined retailer-onboarding flow, hosted document workflow, and custom-integration path.", "lessons": [ "The product must translate EDI into the user’s job, not ask the user to become an EDI specialist.", "Local AI is useful when it is constrained by a maintained product brain and explicit output rules.", "SSL, deployment hygiene, and onboarding are product features, not hosting chores." ], "gallery": [], "public_note": "", "url": "https://beedi.cloud/", "url_label": "Visit BeeDI Cloud" }, { "id": "artist-commerce-platform", "title": "Your Disabled Friend — Artist Storefront", "category": "Software", "status": "Completed build / production integration pending", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Full application + security audit + domain", "summary": "A branded storefront and private publishing studio built for the YouTube artist behind Your Disabled Friend to sell his photography as print-on-demand products.", "problem": "The creator needed a simple way to sell his photographs without having to understand SKUs, variant IDs, product templates, upload URLs, webhooks, or the internal language of a print-on-demand platform.", "solution": "Built the Your Disabled Friend storefront and private studio for yourdisabledfriend.shop, with photo upload, product-format selection, pricing, publishing, cart behavior, Fourthwall integration hooks, webhook processing, security controls, and a visual identity based on the artist’s own work.", "tech": [ "PHP", "JavaScript", "CSS", "Fourthwall API", "Webhooks", "CSRF protection", "File locking", "Responsive UI" ], "image": "software.svg", "detail": true, "highlights": [ "Built for the YouTube artist behind Your Disabled Friend", "Photo upload → choose formats → set prices → publish", "Public storefront and private creator studio", "Production transaction test awaits live Fourthwall credentials" ], "description": "I built a branded public shop and a deliberately simple private studio so the artist could upload a photograph, choose the products or print formats he wanted to offer, set pricing, add a title or description, and publish without touching Fourthwall’s internal product data.", "iterations": [ "Reduced the creator workflow to upload photo, choose formats, set prices, add basic listing information, and publish.", "Separated the artist-facing controls from platform internals such as SKUs, region IDs, media IDs, variant IDs, API tokens, upload URLs, and webhook payloads.", "Added storefront cart behavior, Fourthwall integration hooks, normalized order handling, and webhook deduplication.", "Added session hardening, CSRF protection, upload isolation, file locking, and safer error handling.", "Rebuilt the visual system around the artist’s blue-green grounds, dark marks, cobalt accents, off-white surfaces, and circular logo language rather than a generic ecommerce theme.", "Tested responsive layouts, long titles, cart behavior, invalid routes, signed events, and retry behavior; the final live-shop acceptance test still requires production credentials." ], "result": "A complete branded storefront and creator publishing workflow for yourdisabledfriend.shop. The application was audited and repaired; the remaining launch boundary is a real end-to-end Fourthwall transaction using the artist’s production shop credentials.", "lessons": [ "The best accessibility improvement is often removing unnecessary system knowledge from the workflow.", "Good software can hide platform complexity while preserving the choices the creator actually needs to make.", "A small private studio still needs serious session, upload, webhook, and file-integrity controls.", "A project should state its external launch dependency honestly rather than treating an untested integration as complete." ], "gallery": [], "public_note": "Project identity: this is the artist storefront associated with yourdisabledfriend.shop; it is not a separate archive project." }, { "id": "industrial-diagnostics", "title": "Industrial Diagnostics & Fabrication", "category": "Industrial Repair", "status": "Ongoing field work", "period": "Ongoing", "featured": false, "public_ready": "Yes", "evidence": "Photos + service records", "summary": "Hands-on diagnosis, repair, modification, and fabrication across vending equipment, vehicles, exhaust systems, small engines, and electromechanical assemblies.", "problem": "Real equipment failures cross electrical, mechanical, control, fitment, wear, and human-use boundaries. Replacing the most obvious part is often expensive and wrong.", "solution": "Use measured diagnosis, teardown, wiring analysis, repair, fabrication, and iterative testing to move from symptom to root cause.", "tech": [ "Multimeter diagnostics", "Control boards", "Coin mechanisms", "Welding", "Exhaust fabrication", "Small engines", "Vehicle repair", "Mechanical fitting" ], "image": "fabrication.webp", "detail": true, "highlights": [ "Vending electrical and controller diagnosis", "Custom exhaust cutting, fitting, and welding", "Vehicle and small-engine troubleshooting", "Field-service mindset: diagnose before replacing parts" ], "description": "This body of work covers field diagnosis and repair across vending equipment, vehicles, small engines, exhaust systems, electronic controls, and electromechanical assemblies.", "iterations": [ "Start with the symptom and isolate subsystems instead of ordering parts immediately.", "Use measurements, unplug tests, scan data, teardown, and visual inspection to narrow the fault.", "Fabricate, adapt, weld, or rewire when the unavailable part is not the real engineering constraint.", "Retest under the conditions that produced the original failure." ], "result": "A growing record of paid diagnostics, repaired equipment, restored vehicles, and one-off solutions that could not be found in a service manual.", "lessons": [ "A good diagnosis saves more money than a fast parts swap.", "Temporary test setups are valuable when they answer one clear question.", "Mechanical and electrical evidence should agree before a repair is considered complete." ], "gallery": [ { "src": "fabrication.webp", "caption": "Industrial Diagnostics & Fabrication project image.", "review_required": false } ], "public_note": "" }, { "id": "encoder-validator", "title": "Motor Encoder Validator", "category": "Manufacturing Automation", "status": "Prototype / concept refinement", "period": "2026", "featured": false, "public_ready": "No public project photos yet", "evidence": "Concept architecture and development notes", "summary": "A dedicated fixture for validating replacement motor encoders and detecting incorrect or defective units before installation.", "tech": [ "Encoders", "Motor feedback", "Fixture design", "Quality control" ], "image": "embedded.svg", "problem": "A replacement motor encoder can look physically correct while still being electrically incompatible, defective, misaligned, or mapped differently. Discovering that after installation wastes assembly and troubleshooting time.", "description": "The validator concept turns encoder inspection into a repeatable pre-installation check: verify supply, output behavior, direction, channel relationship, pulse consistency, and physical alignment before the part reaches the machine.", "iterations": [ "Began as a production-quality-control concept after seeing how expensive late discovery can be.", "Separated visual/physical inspection from electrical signal validation.", "Defined a fixture approach that can compare known-good and replacement behavior.", "Added the idea of clear operator pass/fail output instead of requiring oscilloscope interpretation for every unit." ], "result": "A documented fixture architecture ready for continued bench development. The current public page intentionally excludes employer-specific part numbers or interfaces.", "lessons": [ "The right place to catch a bad component is before installation.", "A test fixture should convert expert interpretation into an operator-safe decision.", "Encoder mounting and signal behavior must both be checked; either one can create the same field symptom." ], "gallery": [], "public_note": "The vending-machine rotary feedback assembly is documented under the vending controller diagnosis; it is not imagery from this manufacturing fixture.", "detail": true }, { "id": "aerohive-sentinel", "title": "AeroHive Sentinel — Air Bio-Load", "category": "Research", "status": "Fabricated PCB prototype / grant-stage research", "period": "2025–2026", "featured": false, "public_ready": "Yes", "evidence": "Prototype board + PCB design + proposal materials", "summary": "An airborne biological-load sensing platform developed through PCB design, prototype fabrication, and an NIH R03 research pathway.", "tech": [ "Air sampling", "Biosensing", "Embedded systems", "Research design" ], "image": "projects/aerohive-sentinel/hero.webp", "problem": "Airborne biological risk is difficult to monitor continuously with a compact field device, especially when laboratory infrastructure and reliable connectivity are unavailable.", "description": "AeroHive Sentinel combines air sampling, selective biological sensing, embedded processing, and local decision support. I designed the electronics, ordered the first prototype board, and used the first bring-up failure to tighten the review process for the wider Sentinel research platform.", "iterations": [ "Developed the scientific and operational problem statement for an NIH R03 pathway.", "Separated the air-handling, sensing, power, and embedded-inference problems before committing to a board.", "Captured the electronics design, laid out the PCB, reviewed the assembled-board model, and fabricated the first AeroHive prototype through JLCPCB.", "First power-up exposed an incorrect chip-pin orientation that routed supply to ground and destroyed the board.", "Turned the failure into a staged bring-up checklist covering package verification, rail checks, current limiting, and subsystem-by-subsystem power-up." ], "result": "A fabricated AeroHive Sentinel prototype board, documented PCB-design work, and a structured research proposal. It is presented as a real prototype—not as a validated finished biological detector.", "lessons": [ "Grant writing is system design: every unsupported claim becomes an experiment that must be planned.", "A board can pass design-rule checks and still fail electrically if symbol, footprint, or pin-orientation assumptions are wrong.", "Current-limited staged bring-up should be part of the design process before the board arrives.", "A useful field sensor needs sampling, selectivity, calibration, interpretation, and maintenance—not only a sensing material." ], "gallery": [ { "src": "projects/aerohive-sentinel/01.webp", "caption": "The fabricated AeroHive Sentinel prototype board in hand.", "review_required": false }, { "src": "projects/aerohive-sentinel/02.webp", "caption": "PCB layout work in EasyEDA during development of the Sentinel research electronics.", "review_required": false }, { "src": "projects/aerohive-sentinel/03.webp", "caption": "Assembled-board render used to review component placement, headers, power, and mechanical clearances before fabrication.", "review_required": false } ], "public_note": "Prototype evidence is shown openly; sensing performance, selectivity, and field accuracy remain research questions that require controlled validation.", "detail": true }, { "id": "b4-sentinel", "title": "B4 Sentinel — Confined Space", "category": "Research", "status": "Prototype architecture", "period": "2025–2026", "featured": false, "public_ready": "Yes", "evidence": "BOM + design notes", "summary": "A multi-gas confined-space monitoring platform using electrochemical front ends and multiplexed sensing.", "tech": [ "AD5940", "ADG704", "ESP32", "Electrochemical sensors", "PCB design" ], "image": "research.svg", "problem": "Confined-space crews need multi-gas information in environments where sensor cross-talk, analog front-end complexity, and unreliable connectivity can undermine a simple detector design.", "description": "B4 Sentinel is a multi-gas architecture using electrochemical sensing, AD5940 front ends, ADG704 multiplexing, and an ESP32-class controller. Its controller and board work shares the broader Sentinel research PCB platform while keeping the electrochemical analog front end specific to confined-space sensing.", "iterations": [ "Built the sensor-channel and analog-front-end architecture.", "Worked through BOM cost and board partitioning for low-volume prototypes.", "Designed the system around local processing rather than a mandatory cloud connection.", "Used the first sensor-board bring-up failure elsewhere in the platform to create a stricter schematic and power-up review process." ], "result": "Prototype architecture, BOM, and board-design work prepared for further fabrication and validation.", "lessons": [ "Electrochemical sensing quality depends heavily on the analog front end and calibration plan.", "Shared platforms reduce cost only when channel isolation and failure modes are designed deliberately." ], "gallery": [], "public_note": "", "detail": true }, { "id": "battery-decomposition", "title": "Battery Decomposition Early Warning", "category": "Research", "status": "Concept / grant fit", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Research notes", "summary": "An early-warning sensing concept intended to detect precursors to lithium battery decomposition and thermal events.", "tech": [ "Gas sensing", "Thermal-event detection", "Signal processing", "Research planning" ], "image": "research.svg", "problem": "Thermal runaway is a late, destructive event. The more useful question is whether chemical or thermal precursors can be detected early enough to change the outcome.", "description": "This research concept explores gas, thermal, and signal-pattern sensing for early warning of lithium-battery decomposition before a full thermal event. The concept shares the broader Sentinel embedded research platform, while its sensor selection and evidence requirements remain specific to battery decomposition.", "iterations": [ "Compared the concept with other grant directions and selected it as a stronger fit for a broader engineering research pathway.", "Separated precursor detection from conventional smoke or temperature alarm behavior.", "Outlined sensor fusion and signal-processing needs instead of assuming one threshold sensor would be sufficient." ], "result": "A focused research direction with the next step being controlled decomposition data and sensor-selection experiments.", "lessons": [ "Early-warning claims require carefully defined lead time and false-positive testing.", "A compelling hazard does not automatically create a valid sensor; the measurable precursor must be proven." ], "gallery": [], "public_note": "", "detail": true }, { "id": "biosensor-board", "title": "Sentinel Research PCB Platform", "category": "Embedded Systems", "status": "Prototype platform / board designs in development", "period": "2025–2026", "featured": true, "public_ready": "Yes", "evidence": "PCB layout + assembled-board render + fabricated AeroHive prototype", "summary": "A shared embedded research-board platform supporting AeroHive, confined-space sensing, and battery-decomposition early-warning concepts.", "tech": [ "EasyEDA", "JLCPCB", "ESP32-class MCU", "Sensor interfaces", "Power regulation", "Edge inference", "PCB bring-up" ], "image": "projects/sentinel-research-pcb/02.webp", "problem": "Three sensing programs needed a practical electronics foundation: regulated power, embedded processing, sensor interfaces, local storage, communications, and enough flexibility to support different experiments without starting from zero each time.", "description": "I developed a shared Sentinel research-board approach spanning schematic capture, component selection, PCB layout, assembled-board review, fabrication, and first-board bring-up. The platform supports AeroHive biological sensing, B4 confined-space sensing, and battery-decomposition research while allowing each program to use its own sensors and front-end circuitry.", "iterations": [ "Defined common functions that could be reused across the sensor programs instead of designing three unrelated controllers.", "Captured the board design and routed the PCB in EasyEDA while balancing sensor interfaces, power distribution, headers, storage, and mechanical mounting.", "Used assembled-board rendering to catch placement and access problems before ordering hardware.", "Fabricated the first physical board for AeroHive Sentinel through JLCPCB.", "A first-power-up failure caused by incorrect chip-pin orientation led to a stricter schematic, footprint, rail, and current-limited bring-up process for later designs." ], "result": "One fabricated AeroHive prototype board, two additional research-board designs in development, and a repeatable review and bring-up process that now carries across the Sentinel program.", "lessons": [ "Shared platforms save effort only when common functions and project-specific sensor front ends are separated deliberately.", "3D board review catches mechanical mistakes that schematic review cannot.", "Power-tree validation and package-pin verification deserve their own sign-off step.", "A failed first board can still produce durable engineering value when the process changes afterward." ], "gallery": [ { "src": "projects/sentinel-research-pcb/01.webp", "caption": "Dense research-board layout work in EasyEDA, including embedded processing, analog interfaces, storage, power, and external headers.", "review_required": false }, { "src": "projects/sentinel-research-pcb/02.webp", "caption": "Assembled-board render used to inspect component placement and mechanical access before fabrication.", "review_required": false } ], "public_note": "These images represent the broader Sentinel research-board program. The physical board shown on the AeroHive page is the fabricated AeroHive Sentinel prototype.", "detail": true }, { "id": "drone-payload", "title": "Micro-Drone Camera & Power Experiments", "category": "Embedded Systems", "status": "Experimental", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Hardware photos + troubleshooting", "summary": "Weight-constrained camera, battery, regulator, antenna, and stability experiments on a low-cost micro drone.", "tech": [ "LiPo batteries", "Power regulation", "RF antennas", "Payload integration", "Failure analysis" ], "image": "embedded.svg", "problem": "A low-cost micro drone had almost no payload, power, or RF margin, but the goal was to add a camera and improve useful range without making it unflyable.", "description": "A series of camera, battery, capacitor, regulator, antenna, and waterproofing experiments on a weight-constrained consumer drone.", "iterations": [ "Added a camera and investigated blackouts under sustained load.", "Compared protected and unprotected LiPo cells and considered current-limiting behavior.", "Added bulk capacitance, then learned that stored energy did not solve a battery/current-path limitation.", "Soldered a short wire to the antenna pad; the change increased instability and control problems rather than producing a clean range improvement.", "Explored oil-filled camera housings as a pressure-equalization concept for depth." ], "result": "An experimental record that identified the real constraints—power delivery, RF tuning, control stability, and weight—without pretending the final drone was successful.", "lessons": [ "Adding an antenna wire without matching and layout knowledge can make RF behavior worse.", "A capacitor cannot compensate for a battery or protection board that cannot sustain the load.", "The cheapest platform often leaves too little margin for meaningful payload development." ], "gallery": [], "public_note": "", "detail": true }, { "id": "rust-companion", "title": "Rust+ Companion Display", "category": "Embedded Systems", "status": "Concept / UI prototype", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Interface mockups + community validation", "summary": "A standalone ESP32 display concept for Rust+ information, maps, alerts, and companion features.", "tech": [ "ESP32", "Game APIs", "Touch UI", "Product validation" ], "image": "projects/rust-companion/01.webp", "problem": "Game companion information can be useful away from the main screen, but a product only matters if the community sees enough value to buy and use it.", "description": "A standalone display concept for Rust+ maps, alerts, status, and companion functions, paired with rapid community validation.", "iterations": [ "Created menu and screen mockups for a dedicated hardware display.", "Presented the idea directly to the target community.", "Separated criticism of the visual mockup process from criticism of the actual product value.", "Stopped further hardware investment when the market signal did not justify it." ], "result": "A fast product-validation exercise that prevented a deeper build into a weakly supported market.", "lessons": [ "A technically possible project is not automatically a product.", "Hostile feedback can still contain a useful demand signal.", "Validation before hardware spend is part of engineering discipline." ], "gallery": [ { "src": "projects/rust-companion/01.webp", "caption": "Concept render for a standalone Rust companion display showing server, team, event, map, camera, device, and alert navigation. Concept visualization—not a completed physical prototype.", "review_required": false }, { "src": "projects/rust-companion/02.webp", "caption": "Camera-control screen concept with live view, PTZ controls, presets, and persistent navigation. Concept visualization.", "review_required": false }, { "src": "projects/rust-companion/03.webp", "caption": "Critical raid-warning concept showing breach location, detected time, threat level, camera access, and alert actions. Concept visualization.", "review_required": false } ], "public_note": "The polished device images are concept renders created to validate interface and product demand; they are not photographs of completed hardware.", "detail": true }, { "id": "minecraft-companion", "title": "Minecraft Companion Display", "category": "Embedded Systems", "status": "Concept", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Concept notes", "summary": "A single-player companion screen concept for maps and contextual game information without occupying the in-game map slot.", "tech": [ "Game integration", "ESP32", "Display UI", "Local data" ], "image": "embedded.svg", "problem": "A player may want persistent map and contextual information without occupying the in-game map slot or constantly switching interfaces.", "description": "A concept for a local companion display that could show maps and contextual single-player data on a dedicated screen.", "iterations": [ "Expanded the initial “external map” idea into a broader companion feature set.", "Compared the concept against the weak demand signal from the earlier Rust display exercise.", "Kept the project at concept stage instead of manufacturing hardware without evidence of demand." ], "result": "A documented product concept awaiting a stronger integration path and user-validation case.", "lessons": [ "Reuse of hardware is not enough; the software integration and user benefit must be clear.", "A project can remain valuable as an architecture exercise without being pushed into a product." ], "gallery": [], "public_note": "", "detail": true }, { "id": "vr-obsidian", "title": "VR Obsidian Knowledge Viewer", "category": "Software", "status": "Concept architecture", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Product concept", "summary": "A Quest 2 visualization that explodes an Obsidian vault into a spatial knowledge graph with an inbox orb for unfiled documents.", "tech": [ "Meta Quest 2", "VR UI", "Knowledge graphs", "Obsidian" ], "image": "software.svg", "problem": "A large knowledge vault can become a directory tree that is technically organized but cognitively invisible.", "description": "A Quest 2 concept that turns Obsidian notes into a spatial graph, with unfiled material represented as a floating inbox orb that must be placed into the knowledge structure.", "iterations": [ "Started from frustration with a visually flat vault.", "Defined a spatial representation rather than another 2D dashboard.", "Added a meaningful interaction loop: unfiled documents remain visible until categorized.", "Scoped the target hardware to Meta Quest 2 for a concrete implementation path." ], "result": "A product and interaction architecture for a VR knowledge viewer; implementation remains open.", "lessons": [ "Visualization should expose unfinished work, not only make finished organization look attractive.", "A strong metaphor can turn file maintenance into a usable interaction model." ], "gallery": [], "public_note": "", "detail": true }, { "id": "arbitrage-monitor", "title": "Cross-Exchange Arbitrage Monitor", "category": "Software", "status": "Design request / prototype scope", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Architecture discussion", "summary": "A real-time order-book monitor designed to compare executable spreads after trading fees and rebalancing cost.", "tech": [ "Exchange APIs", "Order books", "Fee modeling", "Real-time UI" ], "image": "software.svg", "problem": "Displayed exchange spreads can be fake opportunities once fees, order-book depth, transfer constraints, and rebalancing costs are included.", "description": "A real-time monitoring architecture intended to compare executable cross-exchange opportunities rather than headline prices.", "iterations": [ "Required live order-book analysis instead of ticker-price comparison.", "Included trading fees and the cost of keeping balances distributed across exchanges.", "Designed around stale-data prevention and continuous refresh.", "Separated monitoring and decision support from automatic execution until risk controls are defined." ], "result": "A scoped software architecture and UI concept, not a claim of profitable unattended trading.", "lessons": [ "The spread is not the profit.", "Liquidity and inventory placement are core parts of an arbitrage system.", "Automation should come after observability and controls." ], "gallery": [], "public_note": "", "detail": true }, { "id": "nexaer-web", "title": "Nexaer Web Platform & SEO", "category": "Software", "status": "Live public product and procurement site", "period": "2025–2026", "featured": false, "public_ready": "Yes", "evidence": "Site packages + audits", "summary": "The live Nexaer/NetCrate web platform: product positioning, specifications, pricing, procurement resources, field-test documentation, support, and technical content.", "tech": [ "PHP", "HTML/CSS/JS", "SEO", "Structured content", "cPanel hosting" ], "image": "software.svg", "problem": "Nexaer began as a company site dominated by one product, which made it difficult to represent custom engineering, research, and future products without confusing buyers.", "description": "I built and operate the public NetCrate web presence under Nexaer, including product architecture explanations, transparent service models, specifications, procurement pages, field-test documentation, quote pathways, support content, and search-focused technical articles.", "iterations": [ "Built and repeatedly revised the original NetCrate-focused site.", "Audited deployment hygiene and removed development artifacts, duplicate apps, logs, and credential risks from public web root.", "Reworked page titles, buyer language, image delivery, and render-blocking resources.", "Split the company architecture so NetCrate could remain a product while Nexaer became the broader engineering brand.", "Added procurement and evaluation language based on real buyer behavior." ], "result": "A live buyer-facing system that does more than describe the hardware: it supports technical evaluation, procurement justification, pricing review, and contact conversion.", "lessons": [ "Site architecture follows business architecture.", "Security and deployment hygiene are part of credibility.", "SEO works best when pages answer a real buyer question instead of repeating a product name." ], "gallery": [], "public_note": "", "detail": true, "url": "https://nexaer.tech/", "url_label": "Visit Nexaer / NetCrate" }, { "id": "beedi-agent", "title": "Local AI Marketing & Coding Agent", "category": "Software", "status": "Working application", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Python code", "summary": "A local Ollama-powered Streamlit workspace with product knowledge, strategy, content, outreach, SEO, campaign, coding, and library tools.", "tech": [ "Python", "Streamlit", "Ollama", "Local LLM", "Prompt systems" ], "image": "software.svg", "problem": "A solo founder needed consistent product knowledge, content, outreach, SEO, and code generation without sending every workflow to a cloud service or rebuilding context each time.", "description": "A local Streamlit application using Ollama with a maintained product profile and separate workspaces for strategy, ideas, targets, content, images, outreach, SEO, campaigns, coding, and a library.", "iterations": [ "Created a product brain as the source of truth.", "Added task-specific prompt functions instead of one generic chatbot box.", "Tuned GPU, context, batch, and model settings for local hardware.", "Added strict plain-English output rules after coder models produced corrupted marketing text.", "Separated coding requests from marketing requests so each could use a more appropriate model." ], "result": "A working local founder-operations tool with saved outputs and a clear expansion path.", "lessons": [ "Model choice matters more than model size when the task type changes.", "A maintained context object is more reliable than repeatedly explaining the business.", "Local tools still need validation, error handling, and UX boundaries." ], "gallery": [], "public_note": "", "detail": true }, { "id": "habbo-rp", "title": "Retro Hotel + RP World", "category": "Software", "status": "Active concept / environment build", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Screenshots + design notes", "summary": "A hybrid classic social-hotel and outside roleplay world with jobs, police, courts, businesses, groups, and player-run events.", "tech": [ "Game systems", "World design", "Community design", "Web game development" ], "image": "software.svg", "problem": "Classic social-hotel gameplay alone has limited modern reach, but a full roleplay world is too large for one person to launch all at once.", "description": "A hybrid retro-hotel and outside roleplay world combining familiar building, events, and social systems with jobs, police, courts, businesses, groups, auctions, and player-run activity.", "iterations": [ "Preserved the recognizable hotel experience rather than replacing it.", "Designed an outside roleplay zone to create progression and player-owned systems.", "Evaluated realistic player numbers and recognized that a full launch exceeded one-person capacity.", "Shifted attention toward recruiting collaborators and defining a smaller initial scope." ], "result": "An active world and systems concept with clear scope and community constraints.", "lessons": [ "A world is not content-complete just because the systems exist.", "Community operations and moderation are product requirements.", "The correct scope for a solo builder is the smallest loop that can attract collaborators." ], "gallery": [], "public_note": "", "detail": true }, { "id": "fix-it-pros", "title": "Fix-It Pros Vending Service", "category": "Industrial Repair", "status": "Service concept / paid diagnostic work", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Flyers + customer work", "summary": "A Dayton-area vending repair service covering coin mechanisms, bill acceptors, electrical issues, control boards, and general maintenance.", "tech": [ "Vending systems", "Coinco", "Electrical diagnosis", "Field service" ], "image": "fabrication.svg", "problem": "Vending owners lose revenue while a machine sits down, but many do not know whether the failure is a coin mechanism, bill acceptor, motor circuit, controller, wiring, or simple setup issue.", "description": "Fix-It Pros packaged local vending diagnostics into a clear Dayton-area field-service offer with paid diagnosis before unnecessary repair work.", "iterations": [ "Defined the service around coin mechanisms, bill acceptors, control boards, electrical issues, and general repair.", "Created multiple flyer versions and refined the value proposition from generic repair to reduced downtime and honest diagnosis.", "Completed paid field diagnostics and used real calls to improve pricing and boundaries." ], "result": "A tested service concept with paid customer work and reusable diagnostic experience.", "lessons": [ "The first product is often diagnosis, not repair.", "Clear scope and service-call pricing prevent open-ended unpaid troubleshooting.", "Honesty about what should not be repaired builds trust." ], "gallery": [], "public_note": "", "detail": true }, { "id": "coinco-3000", "title": "Coinco 3000-S / Vending Controller Diagnosis", "category": "Industrial Repair", "status": "Completed diagnostic", "period": "2026", "featured": true, "public_ready": "Yes — customer details anonymized", "evidence": "Photos + diagnosis notes", "summary": "Troubleshooting a vending machine that auto-vended at the credit threshold, including motor isolation, display behavior, and bypass-switch reasoning.", "tech": [ "Coin mechanisms", "Motor circuits", "AC/DC measurement", "Fault isolation" ], "image": "projects/coinco-3000/01.webp", "problem": "A vending machine automatically triggered one selection when credit reached $0.50. The symptom could have come from the motor circuit, bypass wiring, selection logic, controller, or credit system.", "description": "I isolated the fault by observing the exact trigger condition, disconnecting the affected motor, measuring the two-wire display circuit, inspecting the controller electronics, and tracing the machine’s rotary position/feedback mechanism instead of replacing parts blindly.", "iterations": [ "Confirmed that the unwanted vend occurred at the credit threshold.", "Disconnected the selection motor and verified that the automatic vend stopped, narrowing the problem to that path.", "Measured both DC and AC behavior on the two-wire display and investigated how changing display information could be carried over two conductors.", "Inspected the controller PCB, motor-driver circuitry, and a suspect surface-mount area for physical evidence of failure.", "Examined the vending mechanism’s rotary position/feedback assembly to understand how the controller knew where the mechanism was located.", "Considered the bypass/free-vend switch hypothesis and tested whether unplugging it should remove the symptom.", "Separated the completed paid diagnostic from an optional free-vend conversion the customer declined." ], "result": "The service call produced a defensible fault-isolation record, documented the internal controller and feedback hardware, and preserved a clear scope boundary without forcing a conversion the customer did not want.", "lessons": [ "A repeatable trigger condition is valuable diagnostic evidence.", "Unplug tests are powerful when each one answers a specific topology question.", "Customer choice and scope control are part of a professional repair." ], "gallery": [ { "src": "projects/coinco-3000/01.webp", "caption": "Coca-Cola vending machine used for controller and vend-circuit diagnosis.", "review_required": false }, { "src": "projects/coinco-3000/02.webp", "caption": "Close inspection of a suspect surface-mount area on the vending controller PCB.", "review_required": false }, { "src": "projects/coinco-3000/03.webp", "caption": "Controller-board detail showing the L298N motor driver, logic ICs, heat sinking, and surrounding components.", "review_required": false }, { "src": "projects/coinco-3000/04.webp", "caption": "Rotary position/feedback assembly from the vending mechanism—not the separate manufacturing encoder-validator project.", "review_required": false } ], "public_note": "", "detail": true }, { "id": "vending-encoder-replacement", "title": "Vending Motor Encoder Replacement Module", "category": "Embedded Systems", "status": "Working bench prototype / reverse engineering", "period": "2026", "featured": true, "public_ready": "Yes", "evidence": "Motor hardware + channel test photos + Arduino logic", "summary": "A replacement feedback module for a vending motor assembly, built by separating motor power from position sensing and decoding the existing feedback channels.", "problem": "The vending mechanism depended on a difficult-to-source position-feedback assembly. Replacing the whole vend system was wasteful; the real need was a dependable module that could recognize movement and home position while the existing controller continued to drive the motor.", "description": "I inspected the motor-mounted feedback hardware, identified the separate motor and sensor conductors, tapped the feedback channels, and built Arduino-side logic to observe the channel states and reconstruct a repeatable vend/home sequence.", "tech": [ "Arduino", "Hall / position feedback", "Two-channel state decoding", "Vending motors", "Reverse engineering", "Bench diagnostics" ], "image": "projects/vending-encoder-replacement/01-motor-feedback.webp", "detail": true, "highlights": [ "Separated motor drive from position feedback", "Observed live channel-state transitions", "Worked toward a drop-in replacement instead of redesigning the whole machine", "Documented the physical motor and bench-test output" ], "iterations": [ "Confirmed that the vending controller powered the motor while the attached sensor assembly only reported position.", "Identified and tapped the existing feedback conductors without relying on the motor-power wires.", "Read the two feedback channels as changing A/B states during movement.", "Used the observed sequence and timing to distinguish motion from the home/end position.", "Moved the concept toward a dependable replacement module rather than a one-off external timer." ], "result": "A bench-tested foundation for replacing an obsolete vending feedback assembly while preserving the existing motor and vend mechanism.", "lessons": [ "The most useful repair often replaces the unavailable subassembly, not the entire system.", "Power and feedback must be understood as separate signal paths before reverse engineering begins.", "A repeatable state sequence is more reliable than timing the motor alone." ], "gallery": [ { "src": "projects/vending-encoder-replacement/01-motor-feedback.webp", "caption": "Vending motor with the original mounted position-feedback assembly and harness exposed for tracing.", "review_required": false }, { "src": "projects/vending-encoder-replacement/02-channel-test.webp", "caption": "Live A/B channel-state output during bench testing used to understand the feedback sequence.", "review_required": false } ], "public_note": "This is separate from the medical-manufacturing motor encoder validator and from the Coinco service-call diagnosis." }, { "id": "vehicle-repair", "title": "Vehicle Repair & Rebuild Work", "category": "Industrial Repair", "status": "Ongoing", "period": "Ongoing", "featured": true, "public_ready": "Yes", "evidence": "Photos + teardown history + return-to-road work", "summary": "Hands-on engine, timing, CVT, electrical, suspension, front-end, and return-to-road repair work across multiple salvage and high-mileage vehicles.", "tech": [ "Automotive diagnostics", "Engine repair", "Transmission work", "Electrical" ], "image": "projects/vehicle-repair/01.webp", "problem": "Salvage and high-mileage vehicles rarely have one clean failure. Mechanical damage, electrical faults, drivetrain wear, suspension work, and previous repairs interact.", "description": "Independent vehicle work spanning OBD-II diagnosis, engine teardown, timing and oil-pump access, CVT disassembly, CV axles, suspension, brakes, subframes, electrical systems, collision repair, and return-to-road validation.", "iterations": [ "Used scan data and symptoms to separate transmission-control issues from mechanical failure.", "Removed front suspension, CV axle, steering, and subframe assemblies when external checks were insufficient.", "Opened and organized CVT components—including case halves, valve body, pulley/belt assemblies, and fasteners—for inspection and comparison.", "Performed deep front-engine teardown to access timing components and the oil-pump area rather than treating a low-pressure symptom as a simple external fault.", "Reassembled timing and front-cover systems in stages, verifying alignment and component placement before closing the engine.", "Completed front-end and cooling-package work in difficult outdoor conditions when shop space was unavailable.", "Returned salvage and failed vehicles to usable condition through staged mechanical, electrical, suspension, brake, and road-test work." ], "result": "Multiple vehicles were moved from salvage, drivetrain failure, or major disassembly toward roadworthy use. The work created practical experience across complete systems rather than isolated parts replacement.", "lessons": [ "A scan code is a lead, not a diagnosis.", "Access and teardown planning can determine whether a repair is economical.", "Roadworthy completion requires the whole system—brakes, steering, electrical, cooling, and drivetrain—not only the failed part." ], "gallery": [ { "src": "projects/vehicle-repair/01.webp", "caption": "Front suspension, CV axle, steering, and brake-area teardown.", "review_required": false }, { "src": "projects/vehicle-repair/02.webp", "caption": "Removed front subframe ready for inspection, repair, or replacement.", "review_required": false }, { "src": "projects/vehicle-repair/03.webp", "caption": "Engine-bay repair work with front structure and support components exposed.", "review_required": false }, { "src": "projects/vehicle-repair/04.webp", "caption": "Removed transmissions and drivetrain assemblies stored for diagnosis and parts work.", "review_required": false }, { "src": "projects/vehicle-repair/05.webp", "caption": "Nissan sedan staged outdoors during major engine and drivetrain work.", "review_required": false }, { "src": "projects/vehicle-repair/06.webp", "caption": "The same repair setup from farther back, showing the temporary work area and full vehicle context.", "review_required": false }, { "src": "projects/vehicle-repair/07.webp", "caption": "Chevrolet Express engine bay during front-engine teardown and repair.", "review_required": false }, { "src": "projects/vehicle-repair/08.webp", "caption": "Timing chains, guides, phasers, and front-engine components exposed during diagnosis.", "review_required": false }, { "src": "projects/vehicle-repair/09.webp", "caption": "Front timing system reassembled during the repair sequence.", "review_required": false }, { "src": "projects/vehicle-repair/10.webp", "caption": "CVT teardown with case sections, pulley and belt assembly, valve body, and fasteners organized for inspection.", "review_required": false }, { "src": "projects/vehicle-repair/11.webp", "caption": "Front-end and cooling-package repair performed outdoors in winter conditions.", "review_required": false }, { "src": "projects/vehicle-repair/12.webp", "caption": "Chevrolet Express van after major mechanical and front-end work.", "review_required": false }, { "src": "projects/vehicle-repair/13-broken-link.webp", "caption": "Failed steering or suspension link hardware removed during diagnosis.", "review_required": false }, { "src": "projects/vehicle-repair/14-suspension-parts.webp", "caption": "Replacement control arms, links, and steering components organized before installation.", "review_required": false }, { "src": "projects/vehicle-repair/15-engine-work-context.webp", "caption": "Hands-on engine repair context with the front of the engine opened for mechanical work.", "review_required": false } ], "public_note": "", "detail": true }, { "id": "small-engine", "title": "Small-Engine Restoration & Flips", "category": "Industrial Repair", "status": "Ongoing", "period": "Ongoing", "featured": false, "public_ready": "Yes", "evidence": "Sales + repair records", "summary": "Diagnosis, revival, repair, and resale of mowers, blowers, pressure washers, grills, and related equipment.", "tech": [ "Carburetion", "Ignition", "Fuel systems", "Mechanical repair" ], "image": "projects/small-engine/01.webp", "problem": "Low-value outdoor equipment is often discarded because it will not start, even when the real issue is fuel delivery, ignition, compression, controls, or neglected maintenance.", "description": "A repeatable repair-and-resale workflow for mowers, blowers, pressure washers, grills, and related equipment.", "iterations": [ "Acquire inexpensive or free equipment with a clear resale ceiling.", "Check fuel quality, carburetion, spark, compression, cables, safety controls, and mechanical drag before buying parts.", "Repair only where the parts and time still make sense against expected resale value.", "Clean, test under load, photograph, price, and list the finished equipment." ], "result": "Multiple mower and small-equipment revivals, practical diagnostic speed, and a low-cost way to turn repair skill into cash flow.", "lessons": [ "Economics are part of the repair specification.", "A running engine is not enough; safety controls and usable load performance matter.", "A consistent intake checklist reduces time lost on hopeless equipment." ], "gallery": [ { "src": "projects/small-engine/01.webp", "caption": "Tecumseh-powered mower during small-engine repair work.", "review_required": false }, { "src": "projects/small-engine/02.webp", "caption": "Craftsman mower evaluated for ignition, fuel, and mechanical condition.", "review_required": false }, { "src": "projects/small-engine/03.webp", "caption": "Murray mower in the repair and resale workflow.", "review_required": false } ], "public_note": "", "detail": true }, { "id": "boat-project", "title": "Boat Revival & Interior Rebuild", "category": "Industrial Repair", "status": "Running project", "period": "2026", "featured": true, "public_ready": "Yes", "evidence": "Photos + registration work", "summary": "A low-cost fiberglass boat revival combining title and trailer logistics, marine troubleshooting, interior panel fabrication, upholstery, trim restoration, and return-to-use work.", "tech": [ "Marine systems", "Outboard troubleshooting", "Interior panels", "Upholstery", "Wood finishing", "Trailer systems" ], "image": "projects/boat-project/01.webp", "problem": "The boat was inexpensive because it bundled several problems: unknown mechanical condition, title and trailer logistics, worn interior materials, damaged panels, missing or degraded trim, and years of deferred maintenance.", "description": "The project combined getting the 115 hp outboard running with rebuilding the cockpit and cuddy interior through new panel templates, upholstery, carpet, wood refinishing, hardware, and reassembly.", "iterations": [ "Secured boat and trailer paperwork instead of treating registration as an afterthought.", "Brought the outboard back to running condition and evaluated the trailer.", "Removed deteriorated interior pieces and used the remaining geometry to make new panel templates.", "Cut replacement panels, created openings for speakers and hardware, and rebuilt upholstered sections.", "Refinished and reinstalled wood trim, latches, hinges, controls, and storage access.", "Reassembled the cockpit and cuddy while preserving service access and usable seating." ], "result": "A running, titled boat with a substantially rebuilt interior and a documented transformation from neglected project to usable recreational asset.", "lessons": [ "Marine interiors are assemblies: substrate, fasteners, drainage, upholstery, trim, and access all affect durability.", "Paperwork can be as decisive as mechanical repair on an inexpensive vehicle or boat.", "Templates and staged dry fitting prevent expensive upholstery and panel mistakes." ], "gallery": [ { "src": "projects/boat-project/00-before-seat.webp", "caption": "Original deteriorated seat and upholstery material before replacement and interior rebuild work.", "review_required": false }, { "src": "projects/boat-project/01.webp", "caption": "Reassembled cockpit and cabin access after interior work.", "review_required": false }, { "src": "projects/boat-project/02.webp", "caption": "Forward cabin cabinetry, wood trim, and interior panels.", "review_required": false }, { "src": "projects/boat-project/03.webp", "caption": "Rebuilt rear seating structure and blue upholstery.", "review_required": false }, { "src": "projects/boat-project/04.webp", "caption": "Re-covered side panel with reinstalled controls and trim.", "review_required": false }, { "src": "projects/boat-project/05.webp", "caption": "Reinstalled gunwale trim and hardware.", "review_required": false }, { "src": "projects/boat-project/06.webp", "caption": "Panel templates and raw sheet material during fabrication.", "review_required": false }, { "src": "projects/boat-project/07.webp", "caption": "Cuddy cabin cushions and sleeping area.", "review_required": false } ], "public_note": "", "detail": true }, { "id": "mini-dirt-bike", "title": "Mini Dirt Bike Repair", "category": "Industrial Repair", "status": "Hands-on repair project", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Photos + teardown inspection", "summary": "Mechanical inspection and repair work on an SSR mini dirt bike covering fuel, controls, chain drive, brakes, and chassis condition.", "problem": "The bike’s condition was uncertain, and a quick “does it start?” check would not cover fuel delivery, controls, chain, brakes, wheel condition, fasteners, or chassis safety.", "solution": "Inspected the bike as a complete system, verified engine and control basics, evaluated fuel delivery, chain and sprockets, braking hardware, fasteners, and chassis condition, then prioritized the work needed to return it to dependable operation.", "tech": [ "Small engines", "Carburetion", "Chain drive", "Brakes", "Controls", "Mechanical inspection" ], "image": "projects/mini-dirt-bike/01.webp", "highlights": [ "Whole-system inspection before parts replacement", "Fuel, controls, drivetrain, and chassis evaluated together", "Repair scope prioritized around safety and dependable operation" ], "description": "A system-level inspection and repair project on an SSR mini dirt bike, approached like a small machine rather than a single engine.", "iterations": [ "Photographed and assessed the complete bike before disassembly.", "Checked engine, fuel, throttle, kill-switch, chain, sprockets, wheels, brakes, and chassis condition.", "Prioritized safety-critical and reliability work before appearance.", "Used the repair as another example of small-engine diagnostics transferring across equipment types." ], "result": "A documented repair project with a clear mechanical scope and reusable inspection process.", "lessons": [ "Small equipment still deserves a complete safety inspection.", "A running engine does not prove the drivetrain, controls, or brakes are ready." ], "gallery": [ { "src": "projects/mini-dirt-bike/01.webp", "caption": "SSR mini dirt bike during mechanical inspection and repair.", "review_required": false }, { "src": "projects/mini-dirt-bike/02.webp", "caption": "Opposite-side view showing engine, chain, controls, and chassis.", "review_required": false } ], "public_note": "", "detail": true }, { "id": "home-renovation", "title": "Residential Renovation", "category": "Fabrication", "status": "Completed major renovation", "period": "2024", "featured": true, "public_ready": "Yes", "evidence": "Before/during/after photos", "summary": "An owner-led whole-house renovation combining demolition, repair, drywall, paint, flooring, trim, ceilings, stairs, electrical work, and project sequencing across multiple rooms.", "tech": [ "Carpentry", "Drywall", "Paint", "Electrical repair", "General renovation" ], "image": "projects/home-renovation/02-after-bedroom.webp", "problem": "The house required broad repair and finishing work across multiple trades, with limited money and the need to sequence work so one improvement did not destroy another.", "description": "I took a heavily worn interior through demolition, wall repair, electrical and fixture work, paint, flooring, trim, suspended-ceiling installation, stair refinishing, cleanup, and final room assembly while keeping material cost and livability in view.", "iterations": [ "Removed damaged finishes and opened walls where hidden access, electrical, or repair work was required.", "Repaired and refinished walls before committing to flooring and trim.", "Rebuilt rooms in sequence: surfaces and utilities first, then ceilings, paint, floors, baseboards, doors, and final cleanup.", "Installed a suspended ceiling around existing ductwork and utilities to preserve future access.", "Reworked the stairway from worn carpeted treads to a durable dark finished surface.", "Repeated paint and finish work where early passes did not meet the final standard." ], "result": "A visibly transformed, functional interior completed through owner-led multi-trade work rather than a single cosmetic refresh.", "lessons": [ "Demolition reveals the real scope; budgets and schedules must adapt to what is behind the surface.", "Finish quality depends on preparation and sequencing more than the final coat or flooring alone.", "Access to utilities should be designed into the finished space, not covered permanently.", "Before-and-after documentation turns broad renovation work into verifiable evidence." ], "gallery": [ { "src": "projects/home-renovation/01-before-room.webp", "caption": "One room before renovation, with damaged walls, removed fixtures, exposed openings, and stripped flooring.", "review_required": false }, { "src": "projects/home-renovation/02-after-bedroom.webp", "caption": "Finished bedroom with repaired walls, fresh paint, baseboards, door, and new carpet.", "review_required": false }, { "src": "projects/home-renovation/03-utility-room.webp", "caption": "Utility area during finish work with new resilient flooring installed around the water-heater and service area.", "review_required": false }, { "src": "projects/home-renovation/04-drop-ceiling.webp", "caption": "Completed suspended ceiling installed around existing mechanical and electrical infrastructure.", "review_required": false }, { "src": "projects/home-renovation/05-stairs-before.webp", "caption": "Stairway before final refinishing, showing worn treads and carpet inserts.", "review_required": false }, { "src": "projects/home-renovation/06-stairs-after.webp", "caption": "Stairway after refinishing with a uniform dark finish.", "review_required": false }, { "src": "projects/home-renovation/07-room-after.webp", "caption": "Main room after wall, trim, floor, and door work.", "review_required": false }, { "src": "projects/home-renovation/08-loft-after.webp", "caption": "Upper room after paint, baseboard, and carpet installation.", "review_required": false }, { "src": "projects/home-renovation/09-living-after.webp", "caption": "Living and kitchen area after flooring, wall, beam, and finish work.", "review_required": false } ], "public_note": "", "detail": true }, { "id": "beehive-cosmetics", "title": "Beehive Cosmetics", "category": "Product & Business", "status": "Built and operated", "period": "2022–2025", "featured": false, "public_ready": "Yes", "evidence": "Product photos + sales materials", "summary": "A small-batch cosmetics manufacturing operation covering formulation, pigments, packaging, production equipment, ecommerce, and creator/customer validation.", "tech": [ "Product development", "Packaging", "Branding", "E-commerce", "Retail operations" ], "image": "projects/beehive-cosmetics/01.webp", "problem": "Turning nail-polish concepts into a real product line required repeatable color and effect development, batch equipment, packaging, branding, ecommerce, shipping, creator relationships, and enough maintenance capability to keep a small operation running.", "description": "Beehive Cosmetics was a hands-on product and manufacturing venture. I developed and sampled colors and effects, built the operating workflow, packaged orders, maintained and modified production equipment, created retail presentation, and learned how product performance looked in real customer and creator use.", "iterations": [ "Developed color families, metallic effects, stamping formulas, glow pigments, marbling combinations, and sample swatches before committing to batches.", "Tested products through nail wheels, low-light/UV photography, and creator or customer manicures to see how formulas behaved outside the bottle.", "Built packaging and fulfillment workflows for multi-bottle orders and promotional sets.", "Procured, rebuilt, and maintained production equipment instead of relying on expensive OEM support.", "Diagnosed a failed hydraulic-press transformer and sourced a compatible replacement.", "Designed and built a custom ball mill using chain and sprocket drive, 3D-printed mounts, and rotating jar supports.", "Created programmable signage, retail displays, ecommerce materials, and the surrounding brand system." ], "result": "A functioning small-batch cosmetics operation with real products, customer-facing packaging, creator/customer use, custom equipment, and direct experience spanning manufacturing, maintenance, branding, fulfillment, and sales.", "lessons": [ "A cosmetic product is a repeatable batch process, packaging system, customer experience, and support burden—not only a color idea.", "Sample boards and real-use photos reveal behavior that bottle photography cannot.", "Custom equipment can unlock a process when commercial machinery is unaffordable.", "Maintenance capability protects a small operation from service costs and downtime." ], "gallery": [ { "src": "projects/beehive-cosmetics/01.webp", "caption": "Beehive Cosmetics orders packed as coordinated multi-bottle sets.", "review_required": false }, { "src": "projects/beehive-cosmetics/02.webp", "caption": "Glow-effect sample swatches photographed in low light to compare intensity and coverage.", "review_required": false }, { "src": "projects/beehive-cosmetics/03.webp", "caption": "Glow polish shown on nails under low-light conditions.", "review_required": false }, { "src": "projects/beehive-cosmetics/04.webp", "caption": "Halloween stamping manicure using Beehive Cosmetics polish; creator attribution remains visible in the image.", "review_required": false }, { "src": "projects/beehive-cosmetics/05.webp", "caption": "Metallic blue, purple, and gold effect photographed in customer or creator use.", "review_required": false }, { "src": "projects/beehive-cosmetics/06.webp", "caption": "Blue UV-reactive nail effect with creator attribution preserved.", "review_required": false }, { "src": "projects/beehive-cosmetics/07.webp", "caption": "Neutral marbling effect using layered polish lines; creator attribution remains visible.", "review_required": false }, { "src": "projects/beehive-cosmetics/08.webp", "caption": "Purple-and-green striped metallic effect demonstrating color separation and finish.", "review_required": false }, { "src": "projects/beehive-cosmetics/09.webp", "caption": "Product-development workspace with bottles, nail wheels, loose samples, and color tests.", "review_required": false } ], "public_note": "", "detail": true }, { "id": "beehive-wallet", "title": "Beehive Wallet", "category": "Product & Business", "status": "Built and operated", "period": "January 2021–January 2024", "featured": true, "public_ready": "Needs dates", "evidence": "Resume history", "summary": "A consumer software/product venture that reached more than 10,000 users.", "tech": [ "Product development", "User growth", "Operations", "Customer support" ], "image": "business.svg", "problem": "Users of smaller cryptocurrencies lacked a simple multi-coin wallet and staking interface, while many supported networks required custom node and API integration.", "description": "I built and operated a production web wallet with responsive frontend, PHP/MySQL backend, blockchain APIs and full nodes, balance and transaction processing, staking, masternode features, server operations, security, and customer support.", "iterations": [ "Launched the first usable wallet and expanded supported networks over time.", "Integrated coins with different node, transaction, staking, and codebase behavior.", "Added responsive web and mobile access, balance tracking, staking rewards, and operational tooling.", "Operated Linux and Windows infrastructure, VPNs, hardening, uptime, and incident response.", "Scaled to more than 10,000 users across a three-year operating life." ], "result": "A real production financial application operated from January 2021 through January 2024. The service is now discontinued.", "lessons": [ "Operating a custodial or financial service creates obligations far beyond feature development.", "Uptime, security, support, communication, and an orderly lifecycle are all part of the product.", "A future expanded case study should document the shutdown and user transition with the same honesty as the build." ], "gallery": [], "public_note": "", "detail": true }, { "id": "netcrate-business-development", "title": "NetCrate Go-to-Market System", "category": "Product & Business", "status": "Active", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Outreach database + proposals", "summary": "Founder-led discovery, outreach, quoting, deployment partnerships, procurement positioning, and emergency-management market research.", "tech": [ "B2B outreach", "Procurement", "SAM.gov", "Grant pathways", "Proposal writing" ], "image": "network.svg", "problem": "A novel technical product can be real and still fail if the builder does not understand who owns the problem, how agencies buy, what evidence they require, or where the product fits operationally.", "description": "A founder-led system for discovery interviews, targeted outreach, quoting, evaluation agreements, grant and procurement research, channel planning, and deployment follow-up.", "iterations": [ "Conducted hundreds of direct conversations with emergency-management, public-safety, nonprofit, consulting, and field-operations professionals.", "Narrowed the use case around the early window before larger assets are established.", "Built quotes, spec sheets, capability statements, evaluation terms, and procurement language.", "Registered and positioned Nexaer for public-sector pathways.", "Used rejected, ignored, and positive responses to refine audience and message." ], "result": "Commercial delivery, formal quotes to public-sector prospects, a large research database, and a clearer understanding of the gap between product capability and procurement reality.", "lessons": [ "Market research is strongest when it asks how the work is done today.", "A technical founder must document evidence, limitations, pricing, and support.", "No response is not validation; it is a signal to change target, message, proof, or channel." ], "gallery": [], "public_note": "", "detail": true }, { "id": "manufacturing-outreach", "title": "Custom Manufacturing Development Practice", "category": "Product & Business", "status": "Early market validation", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Outreach messages", "summary": "A Nexaer service direction focused on solving repetitive testing, automation, fixture, and industrial workflow problems for small manufacturers.", "tech": [ "Discovery outreach", "R&D services", "NDA-aware development", "Industrial automation" ], "image": "business.svg", "problem": "Small manufacturers often live with repetitive tests and improvised fixtures because the problem is too specialized for off-the-shelf automation and too small for a large integrator.", "description": "A Nexaer service direction for custom testers, fixtures, electronics, software, and workflow tools built around real production pain.", "iterations": [ "Started with broad “what problem would you fix?” outreach.", "Narrowed the message to specific manual cable and encoder verification workflows.", "Contacted named production and engineering people at local companies instead of generic inboxes.", "Recognized that proprietary pinouts and processes require NDA-aware development.", "Positioned the work as paid R&D and problem solving rather than free speculative builds." ], "result": "Early market validation, direct conversations, and a clear portfolio-backed service offer still in development.", "lessons": [ "Specific observed pain creates a better conversation than a broad capability list.", "A portfolio reduces the amount of trust that cold outreach must create from zero.", "Financial discipline matters: prototype after commitment, not before." ], "gallery": [], "public_note": "", "detail": true }, { "id": "environmental-cleanup", "title": "Community Cleanup Media Project", "category": "Product & Business", "status": "Active community project", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Photos + engagement metrics", "summary": "Documented multi-bucket park and shoreline cleanup work through short-form social content and community calls to action.", "tech": [ "Field work", "Content production", "Social media", "Community engagement" ], "image": "business.svg", "problem": "Litter near water and parks is visible but easy for everyone to assume someone else will handle.", "description": "A hands-on cleanup and short-form media project that documented repeated bucket-by-bucket removal and invited others to participate.", "iterations": [ "Cleaned high-impact areas near the water.", "Documented each bucket and tested short-form video and photo posts.", "Tracked view counts across platforms and adjusted captions, calls to action, and audio.", "Kept the physical result—the cleaner park—as the primary metric." ], "result": "At least five buckets of waste removed and a growing public record of local cleanup work.", "lessons": [ "Content performs inconsistently; the real-world result still counts.", "Visible repetition creates credibility more effectively than one announcement." ], "gallery": [], "public_note": "", "detail": true }, { "id": "mystery-rock-box", "title": "Mystery Rock Box", "category": "Product & Business", "status": "Product concept", "period": "2026", "featured": false, "public_ready": "Yes", "evidence": "Concept mockup", "summary": "A playful direct-to-consumer product concept: three “certified cool rocks” with certificates and themed packaging.", "tech": [ "Product concept", "Packaging", "Marketplace testing", "E-commerce" ], "image": "business.svg", "problem": "Interesting rocks are abundant, but “cool” is subjective and ordinary specimens have little value without curation, story, presentation, and fun.", "description": "A playful product concept: three certified cool rocks, individual certificates, and themed packaging sold as a surprise experience rather than a mineral investment.", "iterations": [ "Defined the product around delight and curation rather than scientific rarity.", "Set an initial three-rock, $30 concept.", "Explored marketplace fit and the risk of shipping cost overwhelming the product value.", "Identified certificates and packaging as the real differentiator." ], "result": "A clear testable product concept ready for a small marketplace experiment.", "lessons": [ "The experience can be the product when the raw material is common.", "Small physical products must be designed around shipping and repeatable presentation." ], "gallery": [], "public_note": "", "detail": true } ]