Hi, I’m Ahamed Rasel. I make complicated software make sense.
Most people open documentation at their worst moment — something’s broken, they’re frustrated, and they need an answer now. Everything I do serves that moment: writing that gets people unstuck, and the systems that keep it trustworthy long after I’ve hit publish.
Docs are the product
I don’t treat documentation as the thing you write once the product ships. It is the product — the place a user quietly decides whether to trust you or walk away. So I hold it to a product standard: clear enough to finish, accurate enough to rely on.
The hard part is scale. I look after the knowledge base for a suite of WordPress tools running on more than 1.47 million sites, where every release silently ages something already published. You can’t win that race by hand. So I stopped trying — and built AI agents and n8n workflows that draft, review, and audit the docs as fast as the product moves.
That’s the short version of who I am: a writer who thinks like an engineer.
How I work
- I write for the person who’s stuck, not the one I’m trying to impress.
- I automate the repetitive half of documentation so the thinking half gets the attention it deserves.
- I stay close to product, engineering, and support — because accurate docs are a team sport, not a solo one.
Beyond the docs
The automation work pulled me deep into practical AI: designing agent pipelines, wiring them together in n8n, and figuring out what actually holds up when you put a language model inside a real production system. It’s become a craft of its own — and a lot of what I write about.
Let’s talk
If you care about clear documentation, AI workflows, or automating the boring parts of knowledge work, I’d enjoy the conversation.
- Email — rasel.ahm55@gmail.com
- LinkedIn — md-rasel-ahamed
- GitHub — ah-rasel5
Prefer the formal version — roles, dates, credentials? Here’s my résumé (PDF).