update readme
This commit is contained in:
@@ -2,102 +2,246 @@
|
||||
|
||||
# Hi, I'm Julien
|
||||
|
||||
**Rust Systems Engineer**
|
||||
*Edge · Embedded · Local AI · Healthcare*
|
||||
**Clinical Orthotist · Systems Engineer · MedTech**
|
||||
*Healthcare systems · Edge · Embedded · Physical devices*
|
||||
|
||||
I build software and systems that connect code to the real world.
|
||||
I am a state-qualified orthotist with four years of clinical experience in France and Canada, followed by a second path into software engineering, Linux systems, edge computing, electronics, and embedded technologies.
|
||||
|
||||
My interests sit at the intersection of **Rust**, **Linux**, **embedded systems**, **edge infrastructure**, **local AI**, and **healthcare technology**. I like working on things that are fast, reliable, useful, and close to the field — from backend services and on-prem inference to hardware integration and real-world deployment.
|
||||
I build systems that connect:
|
||||
|
||||
**clinical needs, software, infrastructure, and physical equipment.**
|
||||
|
||||
Since January 2026, this self-managed Gitea instance has been my primary environment for active development, infrastructure repositories, technical documentation, and CI/CD workflows.
|
||||
|
||||
---
|
||||
|
||||
## What I’m into
|
||||
## My direction
|
||||
|
||||
- Rust backend and systems programming
|
||||
- Edge and on-prem infrastructure
|
||||
- Embedded / IoT systems
|
||||
- Local AI and inference
|
||||
- Real-time communication
|
||||
- Healthcare and interoperable systems
|
||||
- Projects involving both software and hardware
|
||||
My work is progressively specializing in healthcare and medical technology.
|
||||
|
||||
I am particularly interested in systems that improve:
|
||||
|
||||
- clinical workflows;
|
||||
- medical device integration;
|
||||
- mobility and rehabilitation;
|
||||
- autonomy and assistive technologies;
|
||||
- local and secure healthcare infrastructure;
|
||||
- communication between software and physical equipment;
|
||||
- measurement, instrumentation, and real-world deployment.
|
||||
|
||||
My long-term direction is to contribute to non-invasive technologies that assist or restore human function.
|
||||
|
||||
---
|
||||
|
||||
## A bit about me
|
||||
## Clinical background
|
||||
|
||||
My background is unusual on purpose.
|
||||
Before working in software and systems engineering, I spent four years as a clinical orthotist.
|
||||
|
||||
Before moving into software and systems engineering, I worked in **orthotics**, which gave me a strong connection to real users, real constraints, and real-world problem solving. Today, I bring that same mindset into engineering: build things that are technically solid, physically deployable, and actually useful.
|
||||
My work included:
|
||||
|
||||
I’m especially interested in systems that leave the screen:
|
||||
**devices, sensors, readers, edge nodes, local servers, field deployment, and critical workflows**.
|
||||
- patient assessment and biomechanical analysis;
|
||||
- design and fabrication of custom orthoses;
|
||||
- casting, thermoforming, fitting, and finishing;
|
||||
- device adjustment and patient follow-up;
|
||||
- collaboration with physicians, surgeons, and physiotherapists;
|
||||
- understanding comfort, morphology, materials, and real-world use.
|
||||
|
||||
This experience remains central to the way I approach engineering.
|
||||
|
||||
A technically successful device is not necessarily a useful device. It must also fit the user, the environment, the clinical need, and the actual workflow.
|
||||
|
||||
---
|
||||
|
||||
## Things I build
|
||||
## Systems and engineering background
|
||||
|
||||
### Real-time systems
|
||||
Backend services in Rust with fast decision loops, device communication, and production-oriented reliability.
|
||||
I later trained in software development and progressively moved toward systems engineering and technologies closer to the physical layer.
|
||||
|
||||
### Edge and on-prem setups
|
||||
Self-hosted and privacy-friendly architectures with local control, secure networking, and minimal cloud dependency.
|
||||
My current areas of work include:
|
||||
|
||||
### Local AI
|
||||
Experimenting with local inference, RAG pipelines, embedded AI, and practical LLM deployments.
|
||||
- Rust systems and backend development;
|
||||
- Linux-based systems;
|
||||
- edge and on-premise infrastructure;
|
||||
- communication with physical devices;
|
||||
- embedded and IoT experimentation;
|
||||
- secure deployment and remote maintenance;
|
||||
- system integration and interoperability;
|
||||
- technical documentation and reproducible deployment.
|
||||
|
||||
### Healthcare-oriented tools
|
||||
Software that combines technical engineering with healthcare domain understanding, especially where interoperability and clinical reality matter.
|
||||
I prefer projects where software has a direct effect on a device, a process, or a real-world environment.
|
||||
|
||||
---
|
||||
|
||||
## Current focus
|
||||
## Enuxia Health
|
||||
|
||||
- Rust systems programming
|
||||
- Embedded and hardware-oriented projects
|
||||
- Local AI tooling
|
||||
- Healthcare software
|
||||
- Building projects that connect software, machines, and real usage
|
||||
I co-founded **Enuxia**, a technology project now specializing in healthcare systems.
|
||||
|
||||
Enuxia aims to design, integrate, secure, and maintain systems connecting:
|
||||
|
||||
- healthcare software and data;
|
||||
- local and edge infrastructure;
|
||||
- APIs and interoperability layers;
|
||||
- physical equipment;
|
||||
- sensors and embedded systems;
|
||||
- professionals and real-world workflows.
|
||||
|
||||
The technical core includes:
|
||||
|
||||
- Linux and local services;
|
||||
- containerization and automated deployment;
|
||||
- edge computing and offline operation;
|
||||
- integration and interoperability;
|
||||
- secure networking and observability;
|
||||
- embedded systems, firmware, and device protocols.
|
||||
|
||||
The project is being developed progressively, from healthcare infrastructure and system integration toward clinical instrumentation, assistive devices, and active orthotics.
|
||||
|
||||
---
|
||||
|
||||
## Selected technologies
|
||||
## Current work
|
||||
|
||||
**Languages**
|
||||
Rust · Python · C++ · JavaScript
|
||||
### Production Rust systems
|
||||
|
||||
**Systems / Backend**
|
||||
Axum · Tokio · WebSocket · MQTT · Linux
|
||||
Design and deployment of systems using:
|
||||
|
||||
**Infra / Edge**
|
||||
Docker · Proxmox · Traefik · VPN · Self-hosting
|
||||
- Rust;
|
||||
- Axum;
|
||||
- Tokio;
|
||||
- WebSocket communication;
|
||||
- real-time decision logic;
|
||||
- communication with physical readers and devices.
|
||||
|
||||
**Local AI**
|
||||
Candle · Burn · HuggingFace · llama.cpp · GGUF · RAG · Embeddings
|
||||
One production system is currently used by an institutional client and connects backend software with equipment deployed in the field.
|
||||
|
||||
**Health Tech**
|
||||
HL7 · FHIR · DICOM
|
||||
### Healthcare edge infrastructure
|
||||
|
||||
Work around:
|
||||
|
||||
- Linux-based local servers;
|
||||
- Docker and service orchestration;
|
||||
- Proxmox virtualization;
|
||||
- secure VPN access;
|
||||
- monitoring and remote maintenance;
|
||||
- Raspberry Pi and edge nodes;
|
||||
- offline and locally controlled architectures;
|
||||
- healthcare-oriented self-hosted services.
|
||||
|
||||
### Embedded and physical systems
|
||||
|
||||
Projects and experimentation involving:
|
||||
|
||||
- microcontrollers;
|
||||
- embedded Linux;
|
||||
- GPIO;
|
||||
- sensors;
|
||||
- communication protocols;
|
||||
- hardware integration;
|
||||
- firmware;
|
||||
- test benches;
|
||||
- diagnostics and observability.
|
||||
|
||||
### Digital health education
|
||||
|
||||
I also teach digital health topics to Bachelor’s and Master’s students.
|
||||
|
||||
Topics include:
|
||||
|
||||
- connected medical devices;
|
||||
- cloud versus edge computing;
|
||||
- health data sovereignty;
|
||||
- healthcare cybersecurity;
|
||||
- interoperability;
|
||||
- artificial intelligence in healthcare;
|
||||
- medical device regulation.
|
||||
|
||||
---
|
||||
|
||||
## Featured work
|
||||
## Technical interests
|
||||
|
||||
### Enuxia
|
||||
Systems engineering, edge infrastructure, local AI, and real-world deployments.
|
||||
### Systems programming
|
||||
|
||||
### Orthotics decision-support software
|
||||
A project at the crossroads of clinical experience and software engineering.
|
||||
`Rust` `C` `Python` `Linux` `Axum` `Tokio`
|
||||
|
||||
### FPV drone build
|
||||
A personal project that reflects what I enjoy most: understanding systems end-to-end, including hardware.
|
||||
### Communication and integration
|
||||
|
||||
`WebSocket` `MQTT` `REST APIs` `GPIO` `Device Protocols`
|
||||
|
||||
### Infrastructure and edge
|
||||
|
||||
`Docker` `Proxmox` `Traefik` `VPN` `Git` `CI/CD` `Raspberry Pi`
|
||||
|
||||
### Embedded and hardware
|
||||
|
||||
`Embedded Linux` `Microcontrollers` `Sensors` `Electronics` `IoT`
|
||||
|
||||
### Healthcare and MedTech
|
||||
|
||||
`Orthotics` `Biomechanics` `Medical Devices` `Digital Health`
|
||||
`HL7 / FHIR concepts` `DICOM concepts` `Health Data Protection`
|
||||
|
||||
### Applied AI
|
||||
|
||||
Local inference and AI may be used when they provide a measurable benefit, particularly for local processing, decision support, or device-related workflows.
|
||||
|
||||
They are tools, not the core identity of the project.
|
||||
|
||||
---
|
||||
|
||||
## Connect
|
||||
## Engineering principles
|
||||
|
||||
### Usefulness before technology
|
||||
|
||||
No sensor, AI model, or connected feature should be added only to make a system appear innovative.
|
||||
|
||||
### Field reality matters
|
||||
|
||||
A system must work with real users, real devices, imperfect networks, maintenance constraints, and existing workflows.
|
||||
|
||||
### Local control when it matters
|
||||
|
||||
Healthcare systems may require privacy, offline capability, predictable operation, and reduced dependence on external cloud services.
|
||||
|
||||
### Progressive complexity
|
||||
|
||||
Start with a limited and useful system. Validate its value before increasing technical or regulatory complexity.
|
||||
|
||||
### Honest engineering
|
||||
|
||||
Clearly distinguish between:
|
||||
|
||||
- production-ready work;
|
||||
- prototypes;
|
||||
- experiments;
|
||||
- skills currently being developed;
|
||||
- long-term ambitions.
|
||||
|
||||
---
|
||||
|
||||
## Repository organization
|
||||
|
||||
This Gitea instance is used for:
|
||||
|
||||
- active development repositories;
|
||||
- infrastructure-as-code;
|
||||
- Docker and deployment configurations;
|
||||
- CI/CD workflows;
|
||||
- embedded and edge projects;
|
||||
- internal tools;
|
||||
- technical documentation;
|
||||
- prototypes and research work.
|
||||
|
||||
Some repositories may remain private because they contain client-specific, infrastructure, security, or early-stage project information.
|
||||
|
||||
Selected public projects may also be mirrored on GitHub for professional visibility.
|
||||
|
||||
---
|
||||
|
||||
## External profiles
|
||||
|
||||
[](https://github.com/LuuNa-JD)
|
||||
[](https://www.linkedin.com/in/julien-denizot-dev/)
|
||||
[](https://enuxia.com)
|
||||
[](mailto:denizot.j@enuxia.com)
|
||||
|
||||
---
|
||||
|
||||
> I like building systems that don’t stop at the screen.
|
||||
> Building healthcare technology that understands the field, the device, and the person using it.
|
||||
Reference in New Issue
Block a user