Prazwal Bhattarai

I build and operate the systems that keep software running — and I like to understand them all the way down to the kernel.

$ id

uid=1000(prazwal) gid=1000(devops) groups={{ gr.name }}{{ gr.sep }}

$ uptime

up {{ uptime }} at Gurzu, 1 user, load average: boring, boring, boring

$ date

{{ dateLine }} +0545

$ printf '%s\n' "$ROLE" "$HOST"

DevOps Engineer @ Gurzu
Nepal · UTC+5:45 (NPT)

status: open to talk

❯~cat /etc/motd

I keep the path from a developer's commit to production short, boring, and reliable. Boring is the point — a deploy should be the least eventful part of anyone's day.

What pulls me in is the layer below the one I work in — the Linux kernel, how NGINX juggles thousands of connections, what actually happens between typing a URL and seeing a page.

I'd rather understand a system all the way down than trust it as a black box.

$ echo $FOCUS | tr ':' '\n'

❯~ls -la ~/writing

total 3 · prazwal.hashnode.dev

{{ p.perm }} prazwal {{ p.size }} {{ p.date }} {{ p.file }} {{ p.blurb }}

❯~systemctl status gurzu.service

● gurzu.service — DevOps Engineer @ Gurzu

Loaded: loaded (/etc/prazwal/roles.d/gurzu.service; enabled)

Active: active (running) since Mon 2023-12-01; {{ uptime }} ago

Main PID: 1 (delivery-pipeline)

Tasks: 4

CGroup: /roles.slice/gurzu.service

{{ t.tree }} {{ t.name }} — {{ t.note }}

# earlier roles & detail pending — will expand from CV

❯~tmux split-window -h

0:endpoints.txt↗

→ {{ l.k }} {{ l.v }}

1:ls ~/now↗

^b prefix ←→ switch o next z zoom

❯~mail -s "let's talk systems"

Working on something at the infrastructure layer, or just want to trade notes on how things actually work underneath? My inbox is open.

bprazwal678@gmail.com curl -O cv.pdf ↓

❯~

[prazwal]

"nepal" {{ npt }}