Ashiq S — Developer Skills in Dubai, UAE

How I use this stack

Every skill on this page has shipped in a production project, not just a tutorial. Over 4+ years as a Full Stack Developer in Dubai, UAE, I've moved between backend architecture, e-commerce integrations, and self-hosted infrastructure — often on the same project in the same week. The sections below explain how each area fits into the work I actually do, rather than just listing buzzwords.

Backend & Laravel

Laravel is my primary framework — I build REST APIs, admin panels with Filament, and reactive interfaces with Livewire without reaching for a separate JavaScript framework. I've used this stack to build an HRMS platform, e-commerce stores, and custom middleware that keeps WooCommerce and Shopify inventories in sync. Where Laravel isn't the right fit — legacy systems, or roles that require it — I also work in ASP.NET and Python Flask, and I'm comfortable reading and extending WordPress plugin code in PHP.

Frontend & UI

On the frontend I lean on Livewire and Alpine.js for interactivity and Tailwind CSS for styling — this portfolio is built that way. I've also shipped interfaces in React and Next.js, and spent years customizing WordPress themes with Elementor for client sites that needed a visual editor rather than a full custom build. The common thread is picking the lightest tool that solves the actual UI problem instead of defaulting to the heaviest framework available.

E-commerce & Integrations

A large part of my recent work is integration engineering: syncing products, orders, and customer records between WooCommerce, Shopify, and custom Laravel backends, plus wiring up payment gateways and automating order processing so staff don't re-key data between systems. This is the kind of work that doesn't show up as a pretty screenshot, but it's usually what actually saves a business time — see the WooCommerce/Shopify sync write-up on the blog for a concrete example.

Infrastructure, Docker & Self-Hosting

This site itself runs on a Raspberry Pi behind a Cloudflare Tunnel — I containerize services with Docker and Docker Compose, run my own reverse proxy, and monitor uptime myself rather than outsourcing every piece to a managed platform. That home-lab habit carries into client work: I'm comfortable on Ubuntu Server, setting up networking and storage (NAS, Nextcloud, Jellyfin), and debugging infrastructure issues instead of treating the server as a black box. Read more in Self-Hosting on a Raspberry Pi with Docker.

Databases & Data

MySQL and PostgreSQL cover most of my production database work, with schema design done through Laravel migrations and Eloquent relationships rather than hand-written SQL wherever possible. I've also worked with MongoDB on projects that needed a document store, and I'm used to reasoning about query performance and indexing once an application's data volume grows past what a naive schema can handle comfortably.

Outside the day job

Alongside client and employer work, I build side projects to learn adjacent fields — computer vision with YOLOv3 and OpenCV for traffic vehicle detection, an IoT accident-alert system built on Arduino and LoRaWAN, and embedded cryptography experiments with RFID tags. None of that is client work, but it's where I pick up skills — sensor integration, protocol design, hardware debugging — that don't come up in a typical Laravel ticket. The full write-ups are on the blog.

Workflow & tooling

Day to day, that means Git and GitHub for version control, Postman for API testing, and a self-hosted reverse proxy setup for staging and internal tools rather than paying for every preview environment. On the CMS side, I still maintain and extend WordPress sites — theme customization, plugin development, and keeping WooCommerce stores stable through core and plugin updates — so I can move between a fully custom Laravel build and a client's existing WordPress install without needing a ramp-up period. Telegram bot integrations for internal notifications (order alerts, contact form submissions, deployment pings) show up in several of my projects, including this site's own contact form.

Why this matters for hiring

If you're evaluating me for a Software Engineer or Full Stack Developer role in Dubai, the practical takeaway is this: I can own a feature end to end — database schema, backend logic, frontend UI, and the server it deploys to — without handing pieces off to a specialist for each layer. That's useful for teams that need one person to move fast across the stack, and it's the same reason I keep building and documenting side projects: it's how the skill list above stays current instead of going stale. See the full work history or browse projects built with this stack.

Picking up a new stack

I don't treat this list as fixed. Most of it was learned on the job — WooCommerce and Shopify integration work started because a client needed it, not because I planned it in advance, and the same is true for ASP.NET and Python Flask on earlier projects. When a role needs a tool I haven't used in production yet, my approach is the same one behind the side projects above: read the official docs first, build a small working version before touching the real codebase, and lean on the parts of my stack (Laravel's conventions, REST API design, relational data modelling) that transfer regardless of the specific framework.