@mdsaqueib profile picture
Saqueib @mdsaqueib

Web developer and tech freak who spends his time chasing new technologies and trends in web & mobile development.

Joined January 2011
  • Tweets 205
  • Following 84
  • Followers 156
26 Photos and videos
I wrote about Eloquent filtering from the maintenance side, not the syntax side. Scopes look clean early. Then a few extra filters later, your API starts behaving like… Read the full post: qcode.in/advanced-eloquent-f…

Advanced Eloquent Filtering Without Turning APIs Into Query Spaghetti

Compare Eloquent scopes, query objects, relationship filters, JSON filters, and package-based filtering to keep Laravel APIs clean.

qcode.in
1
1
I wrote about where `Bus::bulk()` actually helps in Laravel and where it quietly creates new problems. Dispatch gets faster, but failure handling, queue pressure, observability, and… Read the full post: qcode.in/laravel-bus-bulk-wh…

Bus::bulk() in Laravel: When Bulk Dispatch Helps and When It Hurts

Laravel Bus bulk can speed up large job fan-out, but it also changes failure handling, queue pressure, idempotency, and observability.

qcode.in
1
1
31
I keep seeing teams try to "fix" Eloquent by building a second ORM next to it. A better path is adding typed objects at the boundaries where raw models start leaking too much.… Read the full post: qcode.in/typed-eloquent-boun…

Typed Eloquent Boundaries Without Rewriting Your Laravel App

A practical Laravel guide to adding typed Eloquent objects around messy models without building a parallel ORM or drowning in mapping code.

qcode.in
22
I wrote about a feature that looks harmless in admin panels but gets messy fast: drag-and-drop ordering. The UI is easy. Keeping order truthful across pagination, concurrent… Read the full post: qcode.in/the-hidden-cost-of-…

The hidden cost of adding drag-and-drop ordering to admin tools

Laravel drag-and-drop sorting in admin tools looks simple, but it creates hidden costs in scope, concurrency, pagination, auditability, and accessibility.

qcode.in
3
A lot of teams create a second backend for AI features way too early, then spend the next few months rebuilding auth, queues, logging, and data sync for no good reason. I wrote… Read the full post: qcode.in/how-to-add-ai-featu…

How to Add AI Features Without Creating a Second Backend

A practical guide to adding AI features inside your full stack app without prematurely creating a second backend and months of architectural overhead.

qcode.in
1
Most AI 3D demos look better in benchmarks than they do in products. I wrote about the part that matters after the benchmark: product-specific evals, geometry failure modes,… Read the full post: qcode.in/how-to-build-ai-gen…

How to build AI-generated 3D tools without trusting benchmarks

Benchmarks can shortlist AI 3D models, but product-specific evals, geometry validators, and failure gates are what make CAD-like tools safe to ship.

qcode.in
14
I wrote about the PHP pipe operator from a Laravel developer's point of view. Some uses are genuinely cleaner. A lot of examples are not. If a collection chain, service… Read the full post: qcode.in/php-pipe-operator-p…

PHP pipe operator patterns Laravel developers should actually use

A practical long-form comparison of where PHP's pipe operator helps Laravel code, where collections and services still win, and how to adopt it safely.

qcode.in
11
A lot of Laravel developers treat frontend like optional pain. I think that’s a mistake. You probably don’t need to learn everything. But you do need a clear roadmap: Livewire vs… Read the full post: qcode.in/frontend-events-are…

Frontend events are still worth it for Laravel developers

A practical Laravel frontend roadmap for 2026: where Livewire, Inertia, AI UI patterns, accessibility, and state management actually matter.

qcode.in
20
I compared Qwen3.7-Max and Claude Code on the work that actually matters: repo-level tasks, not benchmark screenshots. The interesting gap isn't raw model quality. It's task framing,… Read the full post: qcode.in/qwen3-7-max-vs-clau…

Qwen3.7-Max vs Claude Code for repo-level coding tasks

Qwen3.7-Max vs Claude Code for repo-level coding tasks: a practical comparison of task framing, context handling, patch quality, permissions, review burden, and cost.

qcode.in
42
AI watermark removal tools are a symptom, not the real problem. The bigger issue is product teams treating provenance, moderation, and asset trust like separate concerns. I… Read the full post: qcode.in/ai-watermark-remova…

AI watermark removal tools expose a bigger product trust problem

AI image provenance is not just about watermark detection. Product teams need explicit trust pipelines for logging, labeling, moderation, and media verification.

qcode.in
10
Frontend talks are shifting because AI features stopped being demos and started becoming product plumbing. I wrote about the frontend skills that still matter when… Read the full post: qcode.in/frontend-conference…

Frontend conference talks are changing because AI is now product plumbing

AI frontend development now depends on state modeling, streaming UX, forms, accessibility, and framework choices that survive real product workflows.

qcode.in
1
9
Not every repo-wide change needs an agent. If the transformation is deterministic, I usually trust a script more. It's cheaper, easier to review, and less likely to get… Read the full post: qcode.in/claude-code-vs-loca…

Claude Code vs local scripts for repo-wide mechanical changes

Claude Code is useful for repo-wide edits with edge cases, but local scripts often win for mechanical changes because they’re safer, cheaper, and easier to review.

qcode.in
7
I like Redis, but a lot of Laravel apps reach for it before they need to. This piece is about where Laravel storage cache is actually good enough, where it starts to hurt, and why… Read the full post: qcode.in/laravel-storage-cac…

Laravel Storage Cache patterns for cheap, durable app caching

Laravel storage cache can be the right first cache layer. Learn when filesystem-backed caching works, where it breaks, and how to design keys and invalidation.

qcode.in
13
In aging codebases, the better coding agent is usually the one that respects test boundaries and fails cautiously. I compared Claude Code and Codex through test-first… Read the full post: qcode.in/claude-code-vs-code…

Claude Code vs Codex for test-first refactors in aging codebases

Claude Code vs Codex is a different debate in fragile repos. Here’s which agent is safer and faster for test-first refactors in aging codebases.

qcode.in
24
WebSockets can make agent loops feel much faster. They can also make the system much harder to reason about. Once state starts leaking across what used to be clean… Read the full post: qcode.in/agentic-workflows-g…

Agentic Workflows Get Faster with WebSockets, but Harder to Reason About

WebSockets speed up agentic workflows, but they also hide state, complicate caching, and make concurrency harder to debug. Here are the real tradeoffs.

qcode.in
3
A lot of AI fallback modes are technically valid and still terrible for users. The feature vanishes, progress resets, and momentum dies. I wrote about building fallback paths… Read the full post: qcode.in/how-to-build-ai-fal…

How to build AI fallback modes that preserve user momentum

Most AI fallbacks kill momentum. Learn how to design degraded AI modes that preserve progress, context, and useful next steps when models fail.

qcode.in
4
Cache invalidation gets a lot messier when multiple teams share the same frontend. At that point, stale data is not just a bug. It is a coordination failure. I… Read the full post: qcode.in/full-stack-cache-in…

Full Stack cache invalidation gets political when teams share one frontend

Frontend cache invalidation stops being just technical when multiple teams share one product surface. Here is a strategy that treats freshness as shared ownership.

qcode.in
6
Laravel API starter kits make the first release feel clean. The harder question is what happens when you need to break something later. I wrote about designing starter… Read the full post: qcode.in/laravel-api-starter…

Laravel API Starter Kits Hide the Hard Part: Breaking Changes Later

Laravel starter kits speed up API launch, but real pain starts later. Here is a Laravel API versioning strategy that makes breaking changes survivable.

qcode.in
15
Coding-agent skills feel reusable right up until they start steering from an old version of the repo. That drift is easy to miss and expensive to keep. I wrote about why… Read the full post: qcode.in/claude-code-skills-…

Claude Code Skills Will Rot Unless Teams Track Their Expiry Dates

Claude Code skills quietly rot as repos, standards, and tooling change. Here is how to add expiry signals and review cadences before stale guidance degrades output.

qcode.in
1
1
18
Pagination feels simple until one list endpoint starts feeding search, exports, admin screens, and sync jobs. Then the real question stops being page size and… Read the full post: qcode.in/full-stack-paginati…

Full Stack Pagination Patterns That Survive Exports, Search, and Admin Tools

Pagination breaks once one dataset powers search, exports, jobs, and admin tools. Here are the production patterns that actually hold up.

qcode.in
8
Load more