Hi, I'm Anurag Kumar
The person behind TechWilla. I write the tutorials you read here.
About the Author
Anurag Kumar
DevOps Engineer & Technical Writer
With 5+ years of hands-on experience in cloud infrastructure, Linux systems administration, and container orchestration, I've built and maintained production environments serving millions of users. I hold certifications including AWS Solutions Architect and Linux Foundation Certified Administrator.
Expertise & Certifications
Amazon Web Services
System Administrator
Container Specialist
CKA Certified
What I Write About
- Cloud Infrastructure: AWS, Azure, GCP deployment guides and best practices
- Linux Administration: System setup, security hardening, package management
- Containerization: Docker, Kubernetes, container orchestration
- Home Lab: Self-hosting, Proxmox, network infrastructure
- Security: VPN setup, SSH hardening, firewall configuration
My Story
It started with a hand-me-down laptop that barely ran Windows. I was curious, and someone mentioned "Linux" on a forum. So I downloaded Ubuntu onto a burned CD (remember those?), messed up the partition table on my first try, lost all my data, panicked, and then... Did it again. This time, it worked.
That feeling of typing a command and watching something actually happen was addictive. Years later, I'm still chasing that feeling. I've set up home servers, broken more things than I can count, configured VPNs at 3 AM, and learned that the best way to understand something is to explain it to someone else.
That's why I started TechWilla. Not to be another "copy these 5 commands" site, but to share the understanding I wish I had when I was starting out. The kind of tutorials where you finish reading and actually know what you did, not just that it worked.
Why I Write These Tutorials
Most tutorials online tell you what to do. They're step-by-step recipes. And that's fine until something goes wrong – which it always does. Then you're stuck because you never understood the why.
I write differently. I try to explain the mental model first. What is this thing actually doing? Why does this flag exist? What are the common ways people mess this up, and how do you fix them? I include the troubleshooting sections other tutorials skip because "it should just work."
It takes longer to write this way. But I've been the frustrated person searching Stack Overflow at midnight, and I remember what it felt like. If my tutorials save even one person that frustration, they're worth it.
What I Actually Know
Areas where I've hands-on experience, not just surface-level familiarity.
Linux Administration
Debian, Ubuntu, CentOS – package management, systemd, bash scripting, permissions, and the random edge cases you only learn from experience.
Docker & Containers
Compose files, networking, volumes, building images that aren't 2GB. Mostly self-hosted stuff, not Kubernetes (yet).
Cloud (AWS, mostly)
EC2, S3, VPCs, security groups. I've run small production workloads and helped others avoid surprise $500 bills.
VPNs & Networking
WireGuard, OpenVPN, Tailscale. Firewalls, DNS, and the joy of debugging "why can't I ping this?"
How I Create These Tutorials
Full transparency about my editorial process and testing methodology.
Testing Environment
I test every tutorial on real hardware. My homelab includes: a Dell OptiPlex mini PC running Proxmox, a Raspberry Pi 4, multiple ESP32 dev boards, and AWS Free Tier + minimal paid instances. No simulated environments — if I say a command works, I've run it myself.
AI-Assisted, Human-Verified
I use AI tools to help with research and outlining — it speeds up the boring parts. But every command, configuration, and troubleshooting step is manually tested and verified on real systems. I fact-check version numbers, update outdated information, and add the "this is what actually went wrong when I tried it" notes that AI can't provide.
Update Policy
Tech moves fast. I revisit popular tutorials every few months to verify commands still work with the latest versions. Each tutorial shows a "Last verified" date. If you find something outdated, let me know — I'll fix it within 48 hours.
No Sponsored Content
I don't accept money to recommend specific products. If I mention a tool like Tailscale or Pi-hole, it's because I actually use it — not because someone paid me. Display ads help keep the site running, but editorial content stays independent.
Want to Get in Touch?
Found an error? Have a tutorial suggestion? Just want to say hi? I read every message.