We’ve all seen the LinkedIn posts. The "perfect" microservices architecture, the flawless CI/CD pipelines, and the diagrams that look like they were handed down from the heavens. In those worlds, everything follows the manual to the letter, and "best practices" are never questioned.
But if you’ve spent five minutes in a real server room or a high-stakes sprint, you know the truth: Production is messy.
Defining the "Tkhwira"
In the Moroccan streets, Tkhwira might mean messing around. But in high-level software architecture, a Tkhwira is something else entirely.
A Tkhwira is a creative engineering compromise. It’s that custom middleware you wrote because the AWS service wouldn't behave. It’s the "temporary" reverse proxy that’s been running for two years because it actually works. It’s the art of winging it with enough experience to ensure it doesn't break at 3 AM.
Why "GhiKankhewer"?
I’m a Solution Architect and a Tech Lead. I’ve spent over a decade building systems, navigating AWS costs, and managing Node.js/Angular stacks. And through it all, I’ve realized that the most valuable lessons didn't come from the successes—they came from the Tkhawer.
GhiKankhewer is a space for:
- The Unfiltered Truth: What happens when the "clean code" becomes a nightmare.
- Pragmatic Wisdom: Real tips on Node.js and AWS that you won't find in a certification guide.
- The Engineering Mindset: Applying these principles to everything—from building a SaaS to rebuilding a bridge in the Douar.
We don't "khewer" because we are lazy. We "khewer" because we are pragmatists. We know that a working "Tkhwira" in production is worth more than a perfect diagram that never gets built.
Welcome to GhiKankhewer. Let’s figure it out together.
