Infrastructure was not where I started

Infrastructure was not where I started.

I started in C. Pointers, arrays, strings, then memory allocation, linked lists, and eventually a shell. For months the work was small and low level: read a line, parse it, fork, exec, wait. Debug a segfault until it finally made sense. Recompile.

At the time it did not feel like infrastructure. It felt like fighting the machine. The compiler disagreed with me constantly. Memory had to be handed back by hand. Almost nothing was convenient.

Then I moved into Linux administration, Docker, CI/CD, and running production systems. And I kept noticing that the hard part was familiar.

When a container exits with code 137, that is the OOM killer, and it helps that I once had to think about how memory is actually used. When a process will not die, signals stopped being mysterious back in the shell project. When a service will not start, reading the log and following the failure chain is the same skill as tracing why a pointer wrote to the wrong place.

The language changed. The habit did not. The habit is this: understand the layer below the one you work in, so that when something breaks you can reason about why instead of guessing.

That is the thing ALX actually gave me, more than any single technology. It made being lost normal, and it made me comfortable opening the box.

If you are in the middle of the low level work right now, and it feels disconnected from the jobs you want, this is what I would say. The specific skills transfer less than you expect. The instincts transfer more. And the instincts are the part nobody can take from you.

Still learning. Still running small things on a single box more often than not.