Rachid Dahir
Software Architect · Technical Author · Educator
The short version
Rachid Dahir designs systems for the long haul. A software architect, technical author, and educator based in Morocco, he has spent over a decade building enterprise-grade .NET solutions in financial services, healthcare, and large-scale enterprise environments — where reliability, performance, and clean architecture are not optional.
His books are written for developers who are ready to move beyond tutorials: rigorous, production-grounded, and clear enough that advanced topics never feel out of reach.
How the books are written
Three principles, applied to every chapter of every title.
-
01
Production-grade code only
Listings come from a companion repository that builds from a clean clone. Nothing in the text is pseudocode, and nothing is simplified past the point where it would still work at work.
-
02
Explain, demonstrate, practice
Each idea is explained in prose, shown in running code, and then handed back to you as an exercise. Reading about a technique and being able to use it are two different things.
-
03
No gatekeeping — only clear teaching
Hard subjects are hard enough without deliberate obscurity. Terms get defined the first time they appear, and one of the four books is free so nobody is priced out of starting.
The imprint
AviSoft Technical Publishing is the imprint under which these books are written, edited and released. It is a small operation in Rabat, Morocco — there is no acquisitions committee and no house style imposed from outside.
That has a practical consequence: the person who writes the code is the person who writes the prose and ships the corrections. When a framework changes, a new version goes out to everyone who already bought the book.
Titles are published through Leanpub as PDF, with the companion code kept in public repositories on GitHub.
At a glance
- Imprint
- AviSoft
- Based in
- Rabat, Morocco
- Books published
- 4
- Store
- Leanpub
- Companion code
- GitHub
Get in touch
Questions about a book, team licensing, or a problem in the companion code? Write directly — the mail goes to the author, not to a queue.