Setup · Stack · Tools · Andenne, Belgium
$ cat uses.txt
My setup: the tools I reach for every day.
A classic /uses page: the system, the languages, the development stack, the DevOps tooling and the security toolbox I use to build, deploy and audit. Nothing invented, exactly what runs across my engagements.
System
Linux, terminal and vim
OS & environment
Linux all day (Ubuntu, Debian). Everything flows through the terminal: shell, multiplexer, and vim as the editor: the vim/tmux-style status bar on this site is no accident. Keyboard-first workflow, scripted whenever it repeats.
Languages
TypeScript and JavaScript up front for the web, Python for tooling and automation, SQL for data, Bash for everything that glues the infrastructure together.
Development
The stack that builds the applications
Backend, frontend & data
Node.js and Express on the server, React and Next.js on the interface, Tailwind for styling. PostgreSQL and MongoDB databases, GraphQL via Hasura. REST APIs, microservices architecture, third-party integrations.
DevOps & Infra
What ships the code to production
Containers, CI/CD & servers
Docker and Docker Compose for packaging, Nginx as reverse proxy, F5 as load balancer. CI/CD with self-hosted GitLab CE. On the servers: systemd and cron to orchestrate services and scheduled tasks.
Security
The offensive & defensive toolbox
Pentest, IAM & monitoring
OWASP Top 10 as the reference for web pentesting, OSINT for reconnaissance, CVSSv3 scoring for reports. KeyCloak for IAM/SSO. Monitoring and observability with Prometheus and Grafana.
Contact
A setup is worth a chat
A question about one of these tools, a mission, a project? Write to me directly.