Teaching professional designers their tools.
This archive matters because it shows an early combination of technical craft, pedagogy, production and entrepreneurship before design leadership became the visible story.
Why it belongs here
Teaching software is a design problem. The instructor has to understand the tool, the learner, the sequence of concepts and the moments where people get lost. The NeatSphere archive shows Stephen working with 3D, architectural visualisation and structured learning before the portfolio shifted toward product leadership.
That foundation is relevant to AI-enabled design today because new tools do not become useful automatically. Teams need models, examples, sequencing and judgement. Teaching professional tools is early evidence of the same instinct: make capability legible so people can use it well.
Public training videos
The YouTube material makes the archive feel less like a claim and more like a working record: public 3ds Max and AutoCAD lessons where tool fluency is broken into teachable decisions.
3ds Max: Build a 3D House
An intermediate 3ds Max project playlist tied directly to the architectural visualisation thread.
Open video3ds Max: Getting Started
Chapter-one 3ds Max Essential Skills material: orientation, setup and the foundations of tool fluency.
Open video3ds Max: Modelling with 3D Geometry
A 3ds Max Essential Skills chapter on constructing objects from geometry and sequencing concepts clearly.
Open videoAutoCAD: Taking the Tour
A direct introduction to the AutoCAD working environment and how learners find their way around a professional tool.
Open videoAutoCAD: Creating Layouts
A production-focused lesson on turning working drawings into organised, shareable output.
Open videoStephen Rea YouTube playlists
The public NeatSphere playlist archive, including 3ds Max chapters and AutoCAD training.
Open videoDrawing as structure
Before the interface, there was the discipline of making systems visible.
The AutoCAD side of the archive matters because it sits close to architectural thinking: plans, elevations, details, conventions, reusable components and output that other people can understand. It is not just software training. It is evidence of a craft habit that still matters in product work: make the structure clear enough for someone else to use.