5 TASKS IN 7 HOURS
Want to back the stream? The «داعم» membership on YouTube is EGP 60 a month: badges, emoji, and I answer your questions first on stream. Become a supporter
The gist
The stream follows work on a Shopify app and a multi-agent “Command Center” workflow that divides exploration, implementation, and auditing while keeping the human responsible for setup and sensitive decisions. Practical work centered on connecting AI APIs, aligning environment variables across Railway and Supabase, configuring Sentry for production monitoring, and troubleshooting deployment, authentication, trial, approval, and cancellation flows. Some deployments and checks were reported complete, but issues including an HTTP 500 error and parts of the user flow remained unresolved, illustrating the limits of automation and the value of clear logs, staged audits, and CI/CD. Luqman also discussed choosing coding tools by task, retained context, and usage limits; his comparisons of Codex, Claude, and Kimi K2 were framed as limited workflow impressions rather than controlled benchmarks. Broader topics included designing defensible scores for stores’ visibility in AI answers, the unsettled GEO-versus-AEO terminology relative to SEO, and validating markets, pricing, distribution, and product economics before accelerating development. Research-oriented discussion extended to LLM interpretability and the lottery ticket hypothesis, as well as Luqman’s views on Chinese and US model ecosystems, reliance on NVIDIA chips, and the need for accessible Arabic models and local pricing. Audience discussions covered AI’s effect on developer roles, code comprehension and debugging, parallel milestones and dependencies, agent-rule context costs, productivity habits, and peer learning. This portion also included additional practical discussions about workstation and operating-system choices, stream latency, development practices before AI, and programmatic video creation with Remotion. Preparing Shopify submission media and polishing the Command Center for a possible GitHub release remained future plans, not completed outcomes.
127 moments from the stream
- 7:08:57
Reviewing AI API Integration and Deployment Work
A work recap covers wiring core APIs, including Gemini and OpenAI, and adjusting part of the deployment workflow; the name of another service is unclear in the captions.
- 7:10:37
Diagnosing a 500 Error During Subscription Cancellation
An attempt to diagnose an HTTP 500 error triggered when cancelling a subscription, including looking for the relevant error log, discussing the need to verify the database through SQL and Supabase tooling, and clarifying the web-service URL and Sentry setup before further fixes. The error remained unresolved by the end of the attempt.
- 7:18:42
Why AI-Assisted Work Slows Down Early in a Project
He explains that account and observability setup, deployment verification, and matching environment variables across services such as Sentry, Supabase, and Railway require more operator involvement than coding, building, and auditing tasks that agents can handle more autonomously. Task counts alone therefore do not represent difficulty or delivery speed.
- 7:23:09
Isolating a 500 Error While Keeping a Backend-First Scope
The work focuses on an HTTP 500 error in a cancellation flow. He notes that the issue crossed UI and backend boundaries even though the early milestones were intended to remain backend-focused, illustrating the value of narrowing debugging scope and protecting milestone boundaries.
- 7:26:23
Moving from Setup Tasks to Autonomous Agent Execution
After the labor-intensive setup work, he expects a later milestone to be more suitable for agents to execute automatically, task by task. This is a forward-looking expectation rather than evidence that the automation had already succeeded.
- 7:28:24
Preparing Media for a Shopify App Submission
He discusses preparing marketing content, videos, and images for a Shopify app submission. At the time of recording, he hoped to finish by April 30 and considered May 4 a more realistic estimate; these were historical projections, not confirmed outcomes.
- 7:29:07
A Developer Community for Mutual Learning and Support
He invites viewers to a Telegram community where developers help one another and exchange knowledge, noting that the joining link is available through his public channels.
Got a question about something in this stream?
Ask in the group