The focus is the work between “something is broken” and “we can explain what happened.” That means useful commands, small reproducible experiments, careful release habits, and clear limits on what a test proves.
Written from a systems administration background
Romeo is a systems administrator based in the Philippines, with a BS in Computer Engineering. His hands-on work includes Linux/LAMP hosting, Apache, PHP-FPM, MySQL, DNS, and Google Workspace administration. He is developing cloud and delivery automation skills through GitLab CI/CD, Ansible, and Docker.
This journal documents that learning path. It does not claim certifications, years of experience, or independent test results that have not been verified.
Start with one useful thread
The first connected series follows Linux troubleshooting into reliable deployments. Cloud and architecture notes remain available as supporting foundations.
How the notes earn trust
Explanations and captured results are labeled separately. Lab notes include their source, commands, environment, failure case, and limitations. AI assistance is disclosed. Client names, credentials, and private operational data do not belong in a public tutorial.
Read the testing and editorial policy, or send a question or correction.