Spawn // Omar
4+ years across software development, server administration, networking and IT operations. I take products from requirements and UI/UX through development, QA and deployment, and I run the infrastructure that keeps them online.
Where I work, end to end:
Crafting // Stack
Each recipe combines the tools I use into the capability they produce. No skill bars, just what goes into the work.
Disciplines
Crafted
Choose a discipline to craft it.
Mine // Projects
Selected case studies. Confidential client work is described without naming the client.
E-commerce storefront for a Lebanese coffee roastery, with customer accounts, a categorised catalogue, online ordering handed to WhatsApp and an admin back office.
Marketing website and purpose-built content management system for an Abu Dhabi photo and video production studio.
Website for a Gulf cuisine restaurant and caterer in Abu Dhabi, with a searchable menu, online ordering and a showcase of its catering services.
Members-only discount club connecting subscribers with local vendors, with role-based dashboards and a shared verification code that rotates every 5 seconds.
Lab // Architecture
How a Laravel API request becomes a response.
Client. Browser or React Native app sends an HTTPS request with a token or session cookie.
Route + Middleware. The router matches the endpoint; middleware handles authentication, CSRF and rate limiting.
Validation. A Form Request validates and normalises input. Invalid data returns 422 before any logic runs.
Business logic. A service class applies the rules of the domain, inside a transaction when several writes must succeed together.
Database. Eloquent issues parameterised queries to MySQL; indexes and eager loading keep them cheap.
Response. An API Resource shapes the JSON so the client contract stays stable when the schema changes.
Who you are is not the same as what you may do.
User. A person or device asks for a protected resource.
Authentication. Identity is proven: credentials, session or token, with MFA where the risk calls for it.
Authorization. Policies and roles (RBAC) decide whether this identity may perform this action on this record.
Service. Only authorised calls reach the service layer, which never trusts the client for permissions.
Database. Queries are scoped to what the user is allowed to see, so a missed check does not leak other data.
AI generates possibilities. Review decides what ships.
Spec + prompt. Requirements are written down first, then turned into a precise prompt with context and constraints.
Claude Code. The AI tool drafts code, tests or a UI from the design. Fast, but a draft.
Generated code. Output is treated like a pull request from a fast junior: useful, unverified.
Engineering review. Read line by line for correctness, security and architecture fit. Rejected work goes back to the prompt.
Testing. Automated and manual tests confirm behaviour, edge cases and failure states.
Deployment. Shipped, monitored and supported like any other code.
What happens between power-on and a working desktop.
Workstation. A domain-joined PC boots onto the office network.
DHCP. It leases an IP address and learns its gateway and DNS servers.
DNS. DNS service records locate a domain controller for the domain.
Active Directory. The domain controller authenticates the user with Kerberos.
Group Policy. GPOs apply security settings, drive mappings and software rules by role.
Resources. The user reaches only the shares and apps their groups allow.
AI accelerates the build. Engineering judgment decides what ships.
Ops // Infrastructure
I run the servers, identity and networks that software depends on. It changes how I build: I know what happens after deploy.
Central accounts, role-based access and policy applied to every machine and user.
Physical hosts and virtual servers, kept healthy down to the cooling.
Addressing, name resolution and segmentation that everything else depends on.
Company-wide IT policies and security protocols, written and enforced.
Mailboxes, licensing, compliance and sign-in conditions for every employee.
Automated and manual backups so data survives hardware that does not.
Hashi Central Food LLC
Nov 2025 - Present · 1 yr
PCIS Company
Jan 2025 - Aug 2025 · 8 mos
Center Café Noel
Nov 2021 - Present · 5 yrs
Hall // Experience
Development and infrastructure have run in parallel since 2023. The overlap is the point: the same person designs the app and keeps its servers healthy.
Hashi Central Food LLC / Madinat Zayed, UAE
Nov 2025 - Present · 1 yr
Designed and run the IT architecture for a 33+ person company.
PCIS Company
Jan 2025 - Aug 2025 · 8 mos
Windows Server, Active Directory and Microsoft 365 administration for a 44+ person organisation.
Freelance / Remote
2023 - Present · 3 yrs 10 mos
End-to-end delivery of web systems, SaaS services and mobile apps for clients in 10+ industries.
Center Café Noel / Remote
Nov 2021 - Present · 5 yrs
Remote IT support and financial reporting across three branches.
Bachelor of Science in Information Technology
With Honor
Lebanese International University (LIU)
Oct 2021 - Jul 2024
Portal // Contact
Full-stack product work, infrastructure, or a role that needs both. Email is the fastest way to reach me.
