Skip to content
View MasterCodeMFE's full-sized avatar

Block or report MasterCodeMFE

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
MasterCodeMFE/README.md

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."

🧑‍💻 About Me

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
  - Networking

I 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.


⚡ My Stack

🐧 Systems



⚙️ DevOps



💻 Programming



📊 Observability


🧠 man manuel

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.

🚀 Featured Projects

📂 ft_ls

My own implementation of the Unix ls command

$ ./ft_ls -laRt

drwxr-xr-x   systems/
drwxr-xr-x   linux/
drwxr-xr-x   curiosity/
-rwxr-xr-x   build_it_myself

A modular recreation of ls written in C to dive into filesystem internals, directory traversal and metadata management.

⚡ Features

  • -l Long format
  • -a Hidden files
  • -R Recursive traversal
  • -t Modification-time sorting
  • -r Reverse ordering
  • Symbolic links
  • Multiple paths
  • File metadata
  • Unix file types
  • Error handling

Core concepts

C · GNU/Linux · POSIX · stat() · lstat() · dirent · Filesystems


🖥️ ft_select

Building an interactive terminal UI from scratch

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


🎥 ft_script

Exploring pseudo-terminals and Unix I/O

Terminal
   │
   ▼
  PTY
 ┌─┴─────────────┐
 │               │
 ▼               ▼
Parent          Child
 │               │
Recorder        Shell
 │               │
 └──────┬────────┘
        ▼
      Output

Built around:

PTY · TTY · fork() · wait() · read() · write()

process management · file descriptors · terminal I/O


🐳 Inception

Infrastructure built with containers

                 Internet
                    │
                    ▼
               ┌─────────┐
               │  NGINX  │
               └────┬────┘
                    │
                    ▼
              ┌───────────┐
              │ WordPress │
              └─────┬─────┘
                    │
                    ▼
               ┌─────────┐
               │ MariaDB │
               └─────────┘

Exploring:

  • Docker containers
  • Container networking
  • Persistent volumes
  • Reverse proxies
  • Service isolation
  • Infrastructure configuration

🌐 Webserv

HTTP server built from scratch in C++

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


🐚 Babuterm

Because apparently using Bash wasn't enough.

manuel@Babuterm$ echo "Hello world" | grep world > output.txt
manuel@Babuterm$ cat output.txt
Hello world

My own Unix shell implementation exploring:

  • Processes
  • Pipes
  • Redirections
  • Environment variables
  • Built-ins
  • Signals
  • File descriptors

🎓 42 Madrid

From Hello World to "why is this file descriptor still open?"

                          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

🔭 DevOps × Systems Programming

This is where things get interesting.

                     ┌───────────────┐
                     │     DEVOPS    │
                     └───────┬───────┘
                             │
           ┌─────────────────┼─────────────────┐
           │                 │                 │
           ▼                 ▼                 ▼
        Linux          Observability       Automation
           │                 │                 │
           │         ┌───────┼───────┐         │
           │         │       │       │         │
           │     Prometheus Grafana SNMP    Scripts
           │                                   │
           └─────────────────┬─────────────────┘
                             │
                             ▼
                 ┌─────────────────────┐
                 │ SYSTEMS PROGRAMMING │
                 └──────────┬──────────┘
                            │
              ┌─────────────┼─────────────┐
              ▼             ▼             ▼
              C           POSIX          UNIX
              │             │             │
              └─────────────┼─────────────┘
                            │
                            ▼
                    UNDERSTAND IT.

🔬 /proc/manuel/status

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

💭 Engineering Philosophy

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?

📊 GitHub Telemetry



🐍 My Contributions

Snake animation

📈 Contribution Activity


🧩 Current Quest

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...

🎯 The Goal

DevOps engineer with a systems programmer mindset.

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."


🌐 Connect



🐧 Linux · ⚙️ DevOps · 📊 Observability · 💻 Systems Programming



manuel@linux:~$ exit

Process still running...

Pinned Loading

  1. MasterCodeMFE MasterCodeMFE Public

    1

  2. FdF FdF Public

    C 1

  3. push_swap push_swap Public

    Shell 1

  4. get_next_line get_next_line Public

    Develop a function for reading a line from a file descriptor.

    C 1