Full-stack developer & growth strategist — Zanzibar / Muscat

Uses.

A practical stack for writing, shipping, reviewing, and keeping product work moving without excess ceremony.

Hardware

Hardware.

A simple, reliable setup built for long build sessions, parallel context, and frequent travel.

Primary laptop

My daily driver for development, writing, and client review. Chosen for battery life and thermal reliability during long sessions.

External display

One large monitor for layouts, code, and side-by-side QA. Two windows is enough; more becomes noise.

Keyboard and mouse

Comfort-first peripherals. The right setup makes a material difference across 8-hour build days.

Noise control

Closed-back headphones for focused work and calls. Silence is a productivity tool.

Build stack

Build stack.

The tools I reach for depending on the brief — chosen for reliability, flexibility, and real-world production performance.

WordPress + PHP

Primary platform for content-driven sites, operational tools, and custom plugin work. ACF-driven architectures, custom themes, and WooCommerce extensions are standard.

Next.js + React + TypeScript

Used for performance-critical web apps, JAMstack sites, and any project that needs SSR, SSG, or a modern component-based architecture at scale.

Laravel

Back-end work requiring clean MVC structure, robust API design, or a PHP framework that can grow with the product rather than fighting against it.

GitHub

Source control, version history, and deployment coordination. Every project — regardless of size or stack — lives in a repo.

Workflow

Workflow.

A practical delivery loop built around clarity, speed, and fewer moving parts than most agencies use.

Notion

Scoping documents, client briefs, operating notes, and lightweight project tracking. One place, low friction.

Figma

Quick interface exploration and content structure checks before development begins. Reduces back-and-forth once build starts.

Lighthouse

Used early in every project — not only at the end. Performance discipline only works when it is embedded from the first commit.

Cloudflare

DNS management, CDN, caching, and edge-layer hygiene. A standard layer on any site that takes performance seriously.

SEO tools

SEO tools.

The toolkit behind technical audits, on-page work, and the search improvements that show up in rankings over time.

Yoast SEO / Rank Math

On-page SEO management, schema output, and sitemap control inside WordPress. Configured properly, not left on default settings.

Google Search Console

The source of truth for how a site is being crawled and indexed. Checked at every stage of an SEO engagement, not just at the start.

Screaming Frog

Technical audits, crawl analysis, and identifying structural issues that hurt rankings. Indispensable for any serious site review.

Ahrefs

Keyword research, backlink analysis, and competitive benchmarking. Used to frame the SEO strategy before a word of content is written.

AI and automation

AI and automation.

Used as operational leverage — to move faster, think more clearly, and reduce repetitive work without replacing judgment.

Claude

Long-form reasoning, content review, and systems thinking support. The tool I trust most for nuanced work that requires contextual depth.

OpenAI

Drafting, synthesis, and workflow integrations inside larger systems. Strong for structured output at scale.

n8n

Connecting tools, automating repetitive operational steps, and building lightweight internal systems without engineering overhead.

Prompt libraries

Reusable, versioned instructions for repeatable internal workflows. Saves time and keeps AI output consistent across projects.

See current focus Open work index GitHub

Contact

The stack stays simple on purpose.

Tooling matters less than judgment, but good tools do remove drag. If you need both, send the brief.

Currently available for web builds, technical SEO projects, and select growth engagements. Capacity is limited — brief early.

Start a project conversation hello@abdulazizbimany.com

Instagram