FIXED 1 BUG. CREATED 3 MORE.
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
A wide-ranging working stream focused on reviewing a Shopify app before launch, combining chat and merchant-UX refinement, fault diagnosis, and conversion of review findings into a debugging and testing queue inside a custom command center. Practical work covered crashes caused by products without images, disappearing text or attachments, slow replies, alignment problems, contextual actions, and confirmation states. A recurring conclusion was that a local fix is not proof of system readiness: human review and realistic scenario testing remain necessary. Luqman also explored agent-driven debugging through backend tests and log inspection, context management through documentation, state files, and fresh sessions, plus confirmation gates and Git checkpoints to constrain autonomous changes. Audience questions led to substantial discussion of Claude, Codex, OpenCode, OpenRouter, local models, and agentic coding tools. The practical view was that model choice depends on the task, quality, cost, and familiarity with the project, while benchmark tables must be interpreted through their methods rather than a single ranking. Many multi-model and cheaper-routing ideas remained proposed experiments rather than completed findings. The stream also covered validating product ideas with landing pages, taking products to market instead of repeatedly building, and moving from a useful first release toward scaling based on real usage. Visual brainstorming and interface design, SEO and GEO, precise product descriptions, and an Arab knowledge-sharing community were additional useful threads. Open questions remained around some latency and timeout causes, classifier-context cost trade-offs, automation reliability, and several fixes and tool trials that were not conclusively validated.
155 moments from the stream
- 6:32:34
Documenting a Regression Before a New Change
The speaker documents an earlier regression where the chat UI printed text and then hid it, says another session was used to address it, and warns against reintroducing the problem during the next change.
- 6:33:29
How SEO and GEO Relate
The speaker argues that SEO will remain important while describing GEO as optimization for visibility in AI channels such as ChatGPT, Perplexity, and Gemini. He sees substantial overlap with some differences and personally predicts broader GEO adoption by late 2026.
- 6:36:43
Choosing a UI Effect, Then Revisiting Speed
After reviewing a new concept, the speaker favors one option and its hover effect, then moves on to investigate the speed issue.
- 6:39:03
Precise Product Descriptions for Search and AI
Discusses describing products with precise, quotable language while reducing marketing fluff that can weaken clarity and usefulness for search engines and AI systems.
- 6:42:43
Turning App Review into a Debugging and Testing Queue
Explains a workflow where review findings are collected in a command center and converted into fixes, debugging issues, and manual stress-testing tasks. The speaker emphasizes that this phase requires patience and persistence.
- 6:47:34
A Practical Comparison of AI Coding Tools
The speaker says one tool produced good design work, but found the Superpowers plugin with Claude more comfortable for his workflow. This is a personal preference, not a benchmark.
- 6:48:15
Mapping Merchant Intent to Actionable Controls
Describes logic that classifies a merchant request as asking, recommending, or executing, with monitoring considered as a possible later category. Recommendation and execution responses should expose clear options and buttons for the merchant to act.
- 6:49:31
Does Hosting Region Affect Chat Latency?
The speaker considers whether round trips to backend services hosted in a distant region add chat latency. A test through a North American VPN did not remove the delay, so the cause remained unresolved.
- 6:50:36
Diagnosing Chat Latency by Request Type
Discusses processing text before submission to reduce delay, while questioning whether the idea is worthwhile or compliant until verified. It distinguishes acceptable latency for a request requiring reasoning from unjustified delay on a simple greeting, and notes that the day’s changes had not yet been tested.
- 6:52:56
Hardening the Chatbox Without Debugging Context Switching
The speaker treats the chatbox as a central flow that needs to be robust and notices a new issue through the logs. He cautions against jumping between bugs and losing focus on the current debugging path.
- 6:56:24
Sharing a Command-Center Template to Build Community
Discusses preparing material about the command center and intending to share its template file through a community group so interested users can access it. The plan was prospective; the captions do not establish that it was published.
- 7:00:37
Redesigning a Vibe-Coding Command Center
An interface redesign experiment for a simple vibe-coding command center with tasks and a swimlane, using a dark background, prominent white cards, and a background color aligned with the top banner. The design was proposed for testing, not presented as a validated final result.
- 7:06:19
Candid Review of a YouTube Thumbnail
A brief review of a YouTube thumbnail concludes that it still feels unsatisfactory and should be iterated on rather than accepted despite a perceived design problem.
- 7:08:49
Balancing Visual Consistency and Clickability
A design discussion about blending an element with the surrounding page while highlighting it enough to make its clickability clear.
- 7:10:54
Contextual Quick Actions with Confirmation Gates
The discussion explores making quick-action buttons part of the conversation and showing a confirmation gate before the relevant action proceeds. Most buttons are described as context-dependent, alongside a limited set of fixed page suggestions, and an SVG diagram is requested to visualize the distinction.
- 7:14:45
Comparing Interface Card Styles
A visual review compares card, border, arrow, and emoji treatments, ending with a preference for the white-card option and a brief observation about its appearance on Telegram.
- 7:17:35
Invitation to a Telegram Community
Current and future viewers are invited to join a Telegram community through a link placed in the bio or chat.
- 7:18:07
A Community for Sharing Tools and Advice
The speaker proposed building a Telegram community where members could help one another and exchange tools and advice.
- 7:18:31
Testing and Debugging a Product-Enrichment Workflow
The speaker tested an assistant for enriching product data, noting UI improvement while identifying remaining speed, logic, and task-count update issues. He also tried analyzing images for material data and enriching products lacking descriptions, and mentioned fixes made during the session without establishing a comprehensive final validation.
- 7:23:08
Multimodal Inputs for the Assistant
The speaker discussed adding voice and vision plus support for image, Excel, and PDF uploads, while emphasizing scope control and avoiding excessive feature expansion.
Got a question about something in this stream?
Ask in the group