Engineering judgment.
Research discipline.
Systems that hold up in practice.
I’m Harun Lucas. My work moves between the workshop, the classroom, and the codebase — across mechanical engineering, technology education research, and engineering systems development. This page sets out how those three connect, and what that means in practice.
Harun Lucas
Why these three disciplines, together
Most of what I work on starts as a practical problem: a machine that needs to run reliably, a process that needs to scale, a concept that’s hard to teach.
01 — Mechanical Reasoning
Mechanical engineering gives me the fundamentals to reason about that problem physically — forces, materials, tolerances, failure modes.
02 — How People Learn & Apply Knowledge
Technology education research asks a different question about the same problem: how is it actually understood, and what does it take to teach it well enough that someone else can act on it.
03 — Building Practical Systems
Engineering systems development is where both answers get tested — turning a design or a teaching approach into software or hardware that has to work outside a controlled setting.
None of these are separate lanes. A maintenance system has to be explainable to the people operating it — that’s a research question before it’s a code problem. A teaching method has to survive contact with real equipment — that’s an engineering question before it’s a curriculum one.
The connecting thread is that I don’t treat a solution as finished until it has been reasoned through mechanically, checked against how people actually learn and use it, and built into something that runs. That’s the practice this site documents.
Practice Flow
- 01
Mechanical Reasoning
- 02
Learning & Application
- 03
Practical Systems
Each stage feeds the next — and questions raised downstream send judgment back upstream.
One practice, three angles
These aren't three separate service lines — they're one practice, viewed from three angles. Each discipline changes how I approach the other two.
Mechanical Engineering
The foundation for how I reason about a problem before I touch a system — statics, materials, thermodynamics, and applied mechanics as the baseline for every design or repair judgment.
In Practice
Material selection, tolerance analysis, mechanical design review
Technology Education Research
Studying how technical and engineering knowledge is actually learned, not just delivered — where explanations fail, what makes a concept usable rather than merely correct, and how it transfers.
In Practice
Curriculum structure, applied teaching methods, technical communication
Engineering Systems Development
Where a mechanical design or a teaching approach gets tested against reality — turned into software, automation, or a physical build that has to keep working outside a controlled setting.
In Practice
Python-based tooling, automation, systems integration
A system I build has to be mechanically sound, explainable to the people who use it, and reliable in the field — that requirement is what keeps these three connected rather than kept in separate boxes.
The same path, every project
Whether the outcome is a mechanical fix, a research finding, or a piece of software, the work moves through the same disciplined stages — from open question to something tested in the field.
- 01
Research
Exploring open questions and prior work
- 02
Problem Definition
Framing the real constraint to solve
- 03
System Design
Architecting the approach and components
- 04
Development
Building the working implementation
- 05
Testing
Verifying behaviour against requirements
- 06
Practical Application
Deploying into real, working systems
Where the practice currently concentrates
Mechanical Systems
Design, analysis, and troubleshooting of mechanical components and assemblies.
CNC & Manufacturing
Machining processes, G-code, and practical manufacturing workflows.
Maintenance & Reliability
Keeping equipment running safely and predictably over its lifecycle.
Predictive Maintenance
Condition monitoring and data-driven methods for anticipating failure.
Technology Education
How technical and engineering concepts are taught and understood.
Python Systems
Scripts, tools, and applications built to support engineering and research work.
AI & Automation
Applying machine learning and automation to real engineering problems.
Engineering Research
Investigating open questions at the edge of practice and theory.
What guides the decisions
Practical Relevance
Work that solves a real, present problem — not a hypothetical one.
Technical Clarity
Explaining a system so someone else can understand and act on it, not just admire it.
Research-Informed Decisions
Testing assumptions before committing to them, in the workshop and in the literature.
Responsible System Development
Building systems that fail safely and stay maintainable after I've moved on.
Continuous Learning
Treating every project as a chance to update what I think I know.
Teachable, Reusable Knowledge
Documenting decisions so the next person — or my future self — doesn't start from zero.
Looking for digital services?
Commercial websites, custom software, business systems and automation are delivered through HarunLucas Dev.
Open to what’s next
I'm open to conversations across research, engineering, and education — reach out if any of this overlaps with what you're working on.