Backend Engineer · Full-Stack Developer · SaaS Builder
Welcome to my corner of GitHub. Please keep your hands inside the Docker container.
I'm a backend-focused full-stack developer who turns complicated business workflows into usable products. APIs, databases, background jobs, authentication, deployment pipelines: basically everything that gets blamed when the button stops working.
I build with Python (Django, FastAPI) and PHP (Laravel), publish Flutter apps, and explore LLMs, RAG, and AI agents that do useful work. A chatbot that confidently invents your refund policy is technically a feature. Just a very expensive one.
My happy place: multi-tenant SaaS, clear system boundaries, and software the next developer can maintain without opening a missing-person investigation.
class EslamKamel:
stack = ("Python", "Django", "FastAPI", "Laravel", "Flutter")
interests = ("SaaS", "RAG", "AI agents", "DevOps")
def build(self, idea):
return {
"architecture": "boring in all the right places",
"tests": "because vibes are not a test suite",
"deployment": "docker compose up -d",
"documentation": "a gift to future me, who remembers nothing",
}
def debug(self, bug):
return "Check the logs. Question assumptions. Then check the logs again."My engineering philosophy: Be clever enough to solve the problem. Be kind enough to leave readable code. Future me is tired and has questions.
| Step | What I actually do | What my inner monologue says |
|---|---|---|
| 🧭 Understand | Map the domain and business rules. | “Before we add AI, what does the button do?” |
| 🧱 Design | Define contracts, boundaries, and failure modes. | “What if the user clicks it twice? They will.” |
| 🛠️ Build | Ship practical APIs, jobs, and interfaces. | “This abstraction could have been a function.” |
| 🧪 Verify | Test behavior and challenge assumptions. | “Happy path? Lovely. Now unplug something.” |
| 🚀 Deploy | Bring Docker, CI/CD, and observability along. | “May your logs be useful and your pager silent.” |
Multi-tenant SaaS → Keeping tenants isolated. Like good neighbors.
LLMs + RAG → Giving AI receipts before giving it responsibility.
AI agents → Automating workflows, supervising the enthusiasm.
DevOps → Making “release day” sound less like a disaster movie.
Flutter apps → Yes, the backend person is touching the pixels again.
Embedded systems → Long-term curiosity. Smaller computers, same questions.
🐛 Open the totally official developer FAQ
I enjoy building the systems behind the interface. Also, databases rarely ask me to make the logo bigger.
Yes: Flutter, Livewire, Vue, React, and Tailwind. I can center a div. I may need a moment of silence first.
Whatever the formatter says. I choose my battles, and whitespace has home-field advantage.
Asking “What assumption did I make?” Usually followed by “Ah. That one.”
Of course. Let’s meet its twelve undocumented business rules first.
An entire year of contributions. One very hungry code reviewer. Zero respect for my green squares.
Generated from my GitHub contribution calendar with Platane/snk and refreshed daily by GitHub Actions. The snake has a better meal schedule than I do.
Commits are activity, not a personality test. Some of my best work is deleting code.
Live typing, badges, and streak stats use external services; they may occasionally take a coffee break. The terminal and workflow animations live in this repo.
Let's turn it into something real. Backend, SaaS, mobile, or AI-powered workflows—I'm interested in the problems behind the pitch deck.
Explore my portfolio · Connect on LinkedIn · Browse my code
Thanks for scrolling. You have successfully completed onboarding. 🎉
No production databases were harmed in the making of this README.

