Welcome to sudo make vibe
You found this site. That means you are probably building something.
Maybe you are using AI to move faster and wondering why the output keeps breaking in production. Maybe you are setting up a homelab and figuring out what actually runs on a Pi 5 or an old Lenovo laptop. Maybe you are somewhere in between — curious about the gap between a working demo and a system you can actually trust.
That gap is what this site is about.
Who built this and why
My name is Farooq. I have spent over 25 years in enterprise networking technology — from Cisco service provider and FSI accounts to Red Hat’s Telco accounts in Canada. I have seen infrastructure at scale. I have seen what happens when it breaks.
A while back, I started watching something that bothered me. AI-generated code was being celebrated as finished work. Scripts that worked once. Containers that did not scale. Systems that collapsed the moment they touched real conditions. Everyone was talking about the speed of AI. Not many people were talking about what happens after the prompt window closes.
So I built a homelab on a couple of Raspberry Pi 5s and some old Lenovo laptops. Installed Fedora, Ubuntu, and Kali servers. Set up a K3s cluster. Added a Kali node for security research. Started running Ollama for local inference and InstructLab for model customization. Started breaking things on purpose to understand how they actually work.
Then I built this site to document what I am learning along the way.
What you will find here
This is not a tutorial site. It is a working lab. You will see AI-generated starting points, systems that fail, debugging steps, and improvements over time. Not everything will be polished. That is intentional — because real systems are not built in a straight line.
The topics that live here:
- Vibe coding — using AI as an accelerator, not a replacement. Prompt engineering, workflow discipline, and the gap between generated and production-ready.
- Linux and open source — the foundation everything else runs on. Terminal workflows, config management, and why visibility matters more than convenience.
- Homelab — the physical lab where all of this gets tested. Raspberry Pi 5s, K3s, WireGuard, Ollama, InstructLab, and whatever breaks next.
- Kubernetes — not as a starting point, but as where things go when they need to scale, survive, and be taken seriously.
- Cybersecurity — because security is not a layer you add later. It is part of how you build from the start.
Where to start
If you are new here, the manifesto is the right place to start. It explains the philosophy behind everything on this site in about five minutes.
If you want to see what is being built, the projects page shows the current lab work — what is active, what is in progress, and what is planned.
This site will grow as the lab grows. Come back when something breaks. That is usually when the most interesting writing happens.