SEND HELP (more bugs) 🐜
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 practical work on organizing development through a customizable Command Center and multiple Warp sessions, including a plan to turn its core structure—swim lane, task board, agent hub, and calendar—into a reusable Markdown specification. Much of the review centers on Talkstore and Content Ops: inventorying use cases, inspecting logs and classification, tracing confirmation-gate, action-chip, and reply-layout bugs, and designing merchant actions that respond to conversational context. Early content-writing and product-enrichment attempts were shown, but they did not produce a complete success; UI regressions, missing product images, catalog-processing latency, and unexpected post-execution chips still required verification. Luqman also discusses a proposed on-demand self-testing diagnostic agent with human review, considers plan mode as a possible safeguard before aggressive fixes—while noting that it was not used in the described case—and contemplates bootstrapping regression baselines for later review, though some setup details remained unclear. Authentication, correlating agent outputs, and defining passing results also remain open challenges. Broader discussion includes qualified opinions about coding tools and usage plans, the importance of genuine product value, validating SaaS demand before building, and extending the learning journey beyond coding into shipping, marketing, and selling.
53 moments from the stream
- 1:35:27
Returning to Planning After an Approval-UI Failure
After the approval button appeared late and the interface seemed to have crashed, the speaker stopped execution and chose to reassess the problem, reference relevant files, and prepare an implementation plan and handoff brief before another attempt.
- 1:36:59
A Multi-Session Workflow in Warp
The speaker praised Warp’s voice input and described using parallel terminal sessions for roles such as multi-model work, server tasks, builds, and review. He also relayed another person’s preference for an alternative tool that he had not tried himself.
- 1:38:51
Handling a Confirmation Gate Before Content Creation
The speaker explained that the agent presented a draft and requested confirmation before creating a hidden blog post, while a confirmation-gate problem was still being fixed. He was unsure whether the operation had counted toward usage.
- 1:42:20
Running Agent Tests on Demand
The speaker proposed running agent test prompts on demand while debugging a particular part of the application. Autonomous scheduled runs several times per day or week were described only as a possible future setup.
- 1:43:48
Question About AI Coding-Tool Pricing
A brief question asked whether an unclearly named tool was inexpensive relative to Codex and Qwen, with Qwen described as reportedly cheap. The page provides no answer or verified comparison.
- 1:44:52
Reviewing a Handoff Brief Before Implementation
The speaker asked for option B from a Markdown handoff brief to be implemented, while explicitly allowing an independent implementation plan to be prepared first.
- 1:54:14
Turning a Command Center into a Reusable Specification
Luqman outlines studying the Command Center’s codebase, files, tools, and tabs, then documenting them in a Markdown prompt that others could adapt to recreate the system for their own projects.
- 1:57:15
A Diagnostic Agent and a Later Test Runner
Luqman discusses a diagnostic agent that reads relevant code, creates test prompts, and checks classifications and results. He distinguishes it from a test runner that could be built later, and considers both periodic checks to catch bugs early and automatic post-build diagnosis for relevant chat-UI tasks.
- 2:01:16
Scoping a Four-Tab Command Center
Luqman narrows the proposed prompt specification to four areas: a swim lane, task board, agent hub, and calendar, while excluding other sections. The goal is to discuss how to capture the required implementation and integration details before generating the file itself.
- 2:05:05
Refining UI Alignment and Content Width
A review of an improved design identifies remaining alignment work: the button and box should match the response width above, while the content container should stay compact within a sensible maximum width.
- 2:07:12
Comparing AI Tool Plans by Usage Limits
A general comparison of AI-tool subscriptions based on usage capacity, especially for Codex, with the qualification that some increased limits may be temporary offers and the details were not fully certain.
- 2:09:17
Testing Demand for SaaS Ideas Before Building
A proposed strategy filters several consumer SaaS ideas using criteria such as high margins and limited competition, then tests comparable landing pages with Facebook ads. Signals such as the cost of acquiring interest, spot reservations, and email sign-ups are compared to select the idea showing the strongest demand before development; this is proposed advice, not a documented test result here.
- 2:12:00
An Opinion on Opportunities in the Shopify App Ecosystem
The speaker argues that a Shopify app delivering genuine value may have a viable revenue opportunity and that software economics can leave room for advertising. The emphasis is on building a strong, useful product rather than a gimmick; these are estimates and opinions, not a demonstrated guarantee.
Got a question about something in this stream?
Ask in the group