I’m a self-taught developer from France.

Most of my work is around FiveM/QBCore, server infrastructure, defensive security, web tooling and local AI experiments.
I like building systems that are practical, readable and useful in real environments — not just impressive on a screenshot.

I’m still learning, testing and improving every day, but I try to keep one simple direction:

Build useful things.
Keep the code understandable.
Share what can help others.
Improve quietly, step by step.

This is where I spend most of my time.

I build and improve resources for FiveM servers, with a focus on clean configuration, server-side logic, NUI interfaces, performance and moderation tools.

Some areas I work with:

• Lua client/server scripting
• QBCore resources
• NUI interfaces
• SQL persistence
• Admin and moderation tools
• Discord logs and webhooks
• Performance-aware scripts
• Gameplay systems for RP / freeroam environments

I’m also interested in server protection, monitoring and visibility.

Not from a “magic security tool” point of view, but from a practical one: logs, alerts, hardening, suspicious behavior detection and safer infrastructure habits.

Things I work on:

• Linux server administration
• Docker-based setups
• Apache / Nginx reverse proxy configs
• Fail2Ban / CrowdSec workflows
• Web scanner detection
• Honeypots
• Discord alerting
• Integrity checks
• Basic defensive automation

I build small web platforms, dashboards, APIs and internal tools when they help a project become easier to manage.

Main tools I use or experiment with:

• React / TypeScript
• JavaScript
• Python
• FastAPI
• Node.js
• PostgreSQL / SQLite
• Redis
• Docker
• REST APIs

I’m interested in local AI workflows, assistant-like tools and automation systems that can help speed up development without replacing understanding.

I use AI mostly as a way to structure ideas, debug faster, document better and turn rough concepts into cleaner systems.

Areas I explore:

• Local LLM workflows
• AI-assisted development
• Prompt-to-system architecture
• Automation scripts
• Audio / media workflows
• FFmpeg tooling
• Self-hosted experiments

Open-source FiveM/QBCore admin and security toolkit.

The goal is simple: provide a transparent, auditable and practical defensive layer for server owners who need better visibility, moderation tools and staff workflows.

It includes:

• Compact NUI admin interface
• Player inspection tools
• Staff actions and moderation workflow
• Runtime monitoring
• Screenshot evidence support
• Config-driven behavior
• QBCore-friendly structure
• Documentation-first approach

Security should not be a luxury.
A small server should still be able to understand, audit and improve the tools it depends on.

Repository:
https://github.com/Lens931/visionary-shield

A community-oriented FiveM/QBCore marketplace resource.

The idea behind this project is to provide a clean, configurable marketplace system that can be understood and adapted by other server owners.

Main focus:

• QBCore integration
• Marketplace listings
• Sales history
• Withdrawable earnings
• SQL persistence
• Discord logs
• Configurable economy
• Clean NUI direction

Repository:
https://github.com/Lens931/qb-marketplace-community

An experimental project around prompt structure, AI workflows and turning ideas into clearer systems.

This project reflects how I like to work with AI: not just asking for output, but trying to create repeatable workflows, better structure and cleaner development direction.

Repository:
https://github.com/Lens931/PLANG

I don’t pretend to know everything.
Most of my progress comes from testing, breaking things, fixing them, documenting better, and slowly improving the way I build.

What I care about:

Languages & scripting

Frontend

Backend & data

Infrastructure

• Cleaner FiveM/QBCore resources
• Better NUI interfaces with lower overhead
• More readable public documentation
• Practical server-side validation
• Defensive tooling for smaller communities
• Local AI workflows for development
• Self-hosted infrastructure habits
• Open-source releases that are easier to audit and improve

Discord: Lens93

Building practical systems, learning in public, and improving quietly.