manuel@linux:~$ whoami
Manuel Fernández
manuel@linux:~$ cat current_role.txt
DevOps
42 Madrid Student
Linux & Systems enthusiast
manuel@linux:~$ cat interests.txt
Linux Internals
Observability
Automation
Networking
Containers
Systems Programming
manuel@linux:~$ echo $PHILOSOPHY
"Understand the infrastructure I operate,
not just the tools running on top of it."name: Manuel Fernández
username: MasterCodeMFE
role:
- DevOps
- Systems Programming Enthusiast
- 42 Madrid Student
location: Madrid, Spain
current_focus:
- Linux
- Observability
- Infrastructure
- Automation
- Networking
- Systems Programming
languages:
- C
- C++
- Bash
- Python
systems:
- GNU/Linux
- Debian
- Ubuntu
learning:
- Unix Internals
- POSIX
- TTY / Termios / Termcaps
- Containers
- Monitoring
- NetworkingI like knowing what is happening underneath the abstraction.
If a tool already exists, there's a good chance I want to rebuild a smaller version of it just to understand how it works.
MANUEL(1) USER COMMANDS MANUEL(1)
NAME
manuel - devops engineer obsessed with understanding systems
SYNOPSIS
manuel [--linux] [--devops] [--monitor] [--build-from-scratch]
DESCRIPTION
Works with Linux systems, infrastructure, automation,
monitoring and low-level programming.
Usually found investigating how something works internally
instead of accepting that "it just works".
OPTIONS
--linux
Explore GNU/Linux and Unix internals.
--devops
Automate infrastructure and improve deployments.
--monitor
Prometheus, Grafana, SNMP and infrastructure monitoring.
--c
Build things dangerously close to the operating system.
--break
Discover undocumented features.
--debug
Turn those undocumented features back into working software.
--coffee
Required dependency.
EXIT STATUS
0 Everything works.
1 It's probably DNS.
42 The answer.
$ ./ft_ls -laRt
drwxr-xr-x systems/
drwxr-xr-x linux/
drwxr-xr-x curiosity/
-rwxr-xr-x build_it_myselfA modular recreation of ls written in C to dive into filesystem internals, directory traversal and metadata management.
-lLong format-aHidden files-RRecursive traversal-tModification-time sorting-rReverse ordering- Symbolic links
- Multiple paths
- File metadata
- Unix file types
- Error handling
Core concepts
C · GNU/Linux · POSIX · stat() · lstat() · dirent · Filesystems
No GUI.
No framework.
Just the terminal.
Keyboard
│
▼
read()
│
▼
termios
│
▼
Application
│
├── Selection
├── Signals
├── Resize
└── Rendering
▼
TTY
Working directly with:
termios · termcaps · TTY · signals · ioctl
raw input · terminal resize · dynamic rendering
Terminal
│
▼
PTY
┌─┴─────────────┐
│ │
▼ ▼
Parent Child
│ │
Recorder Shell
│ │
└──────┬────────┘
▼
Output
Built around:
PTY · TTY · fork() · wait() · read() · write()
process management · file descriptors · terminal I/O
Internet
│
▼
┌─────────┐
│ NGINX │
└────┬────┘
│
▼
┌───────────┐
│ WordPress │
└─────┬─────┘
│
▼
┌─────────┐
│ MariaDB │
└─────────┘
Exploring:
- Docker containers
- Container networking
- Persistent volumes
- Reverse proxies
- Service isolation
- Infrastructure configuration
Client
│
│ HTTP Request
▼
┌─────────────┐
│ Webserv │
├─────────────┤
│ Parser │
│ Sockets │
│ CGI │
│ Routing │
└──────┬──────┘
│
▼
HTTP Response
Built to understand:
HTTP · TCP/IP · Sockets · Non-blocking I/O
CGI · Configuration parsing · Client/Server architecture
manuel@Babuterm$ echo "Hello world" | grep world > output.txt
manuel@Babuterm$ cat output.txt
Hello worldMy own Unix shell implementation exploring:
- Processes
- Pipes
- Redirections
- Environment variables
- Built-ins
- Signals
- File descriptors
42 Madrid
│
┌─────────────────┼─────────────────┐
│ │ │
▼ ▼ ▼
C UNIX C++
│ │ │
┌──────┼──────┐ ┌────┼─────┐ CPP Modules
│ │ │ │ │ │
Libft printf GNL shell IPC signals
│
▼
Systems Programming
│
┌────────────┼─────────────┐
│ │ │
▼ ▼ ▼
ft_ls ft_script ft_select
| Area | Projects |
|---|---|
| 🧱 C Foundations | Libft · ft_printf · get_next_line |
| 🧠 Algorithms | push_swap |
| 📡 IPC | minitalk |
| 🐚 Unix | Babuterm |
| 🧵 Concurrency | Philosophers |
| 🎨 Graphics | FdF · cub3d |
| ⚙️ C++ | CPP Modules |
| 🌐 Networking | Webserv |
| 🐳 Infrastructure | Inception |
| 🌍 Web | ft_transcendence |
| 🐧 Linux Internals | ft_ls · ft_script · ft_select |
This is where things get interesting.
┌───────────────┐
│ DEVOPS │
└───────┬───────┘
│
┌─────────────────┼─────────────────┐
│ │ │
▼ ▼ ▼
Linux Observability Automation
│ │ │
│ ┌───────┼───────┐ │
│ │ │ │ │
│ Prometheus Grafana SNMP Scripts
│ │
└─────────────────┬─────────────────┘
│
▼
┌─────────────────────┐
│ SYSTEMS PROGRAMMING │
└──────────┬──────────┘
│
┌─────────────┼─────────────┐
▼ ▼ ▼
C POSIX UNIX
│ │ │
└─────────────┼─────────────┘
│
▼
UNDERSTAND IT.
Name: Manuel Fernández
Username: MasterCodeMFE
State: R (running)
Threads: probably too many
Shell: bash
Editor: vim
Coffee: enabled
Curiosity: 100%
Linux: enabled
Monitoring: enabled
Automation: enabled
C: segmentation fault
Debugging: in progress
Uptime: learning since boot
while (alive)
{
understand();
build();
break_things();
debug();
automate();
learn();
}I don't want to know only which command fixes the problem.
I want to understand:
Why did it break?
│
▼
What is actually responsible?
│
▼
How does it work internally?
│
▼
Can I reproduce it?
│
▼
Can I monitor it?
│
▼
Can I automate it?
│
▼
Can I make it better?
manuel@linux:~$ ./current_quest
[+] Master Linux internals
[+] Build monitoring systems
[+] Automate repetitive infrastructure
[+] Understand networking deeply
[+] Keep building things in C
[+] Break fewer production systems
[+] Break more test systems
[+] Never stop learning
Status: RUNNING...Not only:
"I know how to use the tool."
But:
"I understand why the tool works."
And eventually:
"Let me see if I can build it myself."

