Building a per-repo wiki that actually gets read
Building a per-repo wiki that actually gets read TL;DR - Our docs were not missing. They were in READMEs, internal docs folders, and even in the comments of our CI/CD workflows. The CI/CD was fully automated. And yet one specific teammate kept ping...
Written by
What I learned the hard way. So you do not have to.
Hi, I am Vineeth (VNK). I am a software developer and DevOps engineer based in Kochi, India. I work across backend (Node.js, NestJS, PHP), infrastructure (Docker, MySQL, Linux), and frontend (Vue, React). I am currently building and operating products with BEO, where I do everything from architecture decisions to staging deployments to fixing the things that break at 9 PM on a Friday. I write about real problems from real work - the kind of things you do not find in tutorials. Production incidents, hard-won architecture lessons, team and process notes, and the occasional opinion piece. If something I shipped, broke, or learned might save someone else half a day, it goes here. No fluff. No ghostwritten thought leadership. Just notes from the terminal.
Responses
Markdown supported · ⌘↵ to post
No responses yet.