Engineering development
Formal study paired with practical investigation across mechanical, electrical, control, safety, and systems thinking—turning hands-on intuition into stronger engineering judgement.
Perth, Western Australia · Professional record
Engineering ideas.Built into working systems.
I'm Warren Nelson—an engineering student and systems builder developing practical projects across physical systems, software, automation, and product development, then documenting what each build teaches me.
Grounded in 10+ years of CNC, manufacturing, machinery, and hands-on technical work.
The record
What I'm building toward
A growing account of ideas taken beyond theory: what I built, how I reasoned through it, and what comes next.
Open engineering notes →
Systems & product building
Software, automation, data, and physical projects developed as complete systems—not isolated demos—with attention to architecture, interfaces, users, and the path from concept to useful product.
Rapid prototyping
Fast, focused experiments used to test an idea, expose constraints, and create evidence for the next decision—across code, electronics, automation, fabrication, and AI.
Industrial foundation
Grounded in 10+ years of CNC, manufacturing, machinery, and hands-on technical work—experience that keeps engineering decisions connected to how things are built, used, maintained, and improved.
Selected work
Evidence, not just claims
Manufacturing practice
CAD/CAM and machine-aware design
Models, drawings, toolpaths, and sample work shaped by real tooling, workholding, material, and setup constraints.
Open record →
Engineering documentation
Ground resistance field reference
A practical technical reference that turns research, measurement methods, and real constraints into clear, reusable engineering documentation.
Open record →
Software prototype
NodeOne local AI assistant
An evolving desktop prototype exploring local models, agent routing, memory, interfaces, and maintainable system boundaries.
Open record →Working method
From question to working system
- 1
Define
Start with the real problem, the user, the constraints, and what a useful result must do.
- 2
Build
Create the smallest useful model, fixture, script, test, or working prototype.
- 3
Verify
Test the result against physical, technical, and human constraints—not just a clean demo.
- 4
Document
Leave a record of the reasoning, outcome, and next iteration.
Writing & notes
The reasoning behind the work
Engineering concepts, design decisions, prototypes, build logs, and honest post-project notes.
Browse the notebook →Follow the record
Built in public, updated over time
For professional context, source code, or a conversation about the work, use the links below.