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
- 0:02:03
Tracking Work and Debugging in a Command Center
Shows Command Center updates, including a calendar for visualizing work and progress and a review page for tracking debugging tasks.
- 0:03:05
Warp Update: Vertical Terminals and Multiple Sessions
An initial hands-on reaction to Warp’s updated interface: vertical terminal tabs, terminal renaming, and multiple sessions for switching between work contexts. The speaker was initially hesitant because the layout was unfamiliar, then found the organization useful, while expressing unresolved concern about possible future terminal sandboxing.
- 0:06:38
Building a Project-Specific Command Center
Explains an idea for providing a phased Markdown specification that a coding agent can use to build a Command Center skeleton, which developers then tailor to their own projects. The preference is to share the structure and guidance instead of a finished repository because each project has different needs.
- 0:09:07
Separating Server and Debugging Work into Terminal Sessions
Applies Warp’s multiple-session feature to organize terminals by purpose, such as keeping server processes in one session and debugging in another, reducing clutter and making each work context easier to reach.
- 0:10:04
Organizing Development Sessions with Warp’s Vertical Tabs
The speaker separates building, debugging, and server work into distinct sessions, finding that Warp’s vertical tabs make many terminals easier to distinguish and less confusing.
- 0:11:46
Hardening the Chat UI Before Release
The speaker reviews the chat interface, prioritizing removal of major UI crashes before release, separating essential work from redundant items, and considering whether the floating bubble should open an embedded chat or lead to the assistant.
- 0:14:16
Agent-Assisted Debugging Through Logs and Responses
The speaker describes an experimental loop in which an agent sends a prompt, reads the classifier log and response, monitors them, and reports possible problems. He considers the approach promising but uneven and agrees that operational human review is necessary.
- 0:16:06
Testing Coding Models Gradually in a Multi-Session Workspace
The speaker proposes a multi-session OpenCode workspace for comparing different models one at a time on simple tasks such as backend work, debugging, and security, rather than trying all of them at once. Some model names are unclear in the captions, and no completed test results are reported.
- 0:18:13
Embedded Chat Bubble vs. Linking to the Assistant
The speaker frames a product-design question about the tradeoffs of opening a real conversation inside the page from the bubble versus using it as a direct link to the assistant, noting that embedded chat was not the original intention.
- 0:20:26
Choosing the Assistant Button’s UI Behavior
He considers whether the home-page bubble should open an embedded compact chat or navigate to the full assistant page. He chooses the simpler starting point: navigate to the assistant page and make the button rectangular.
- 0:22:16
A Command Center for Focused Debugging
He describes organizing an app review into UI polish, UX flows, and backend fixes. Issues found during testing can be recorded under fixes and pushed to a task board, helping him finish the current flow step by step instead of getting diverted by every newly discovered bug.
- 0:25:16
Building a Project Command Center from an Instruction File
He outlines the idea of placing a Markdown prompt file in a project so an agent can use it to build the command-center structure, and said during the stream that he intended to explain the setup from scratch in a separate video.
- 0:27:08
Asking a Model to Explain a Task Before Acting
He begins trying another model with a constrained request: inspect a task, explain what it means, and report its understanding before acting. The page does not show the result or establish how well the model performed.
- 0:27:54
The Value of Building in Public and Learning Live
He says his priority is providing practical value rather than repeatedly asking for engagement, and that working live in public also helps him gain experience.
- 0:29:17
Beyond Building: Shipping, Marketing, and Selling Apps
He explains that building an app is not the end of the journey. His broader educational aim is to cover what follows—shipping to market, marketing, and selling—rather than stopping at coding or vibe coding.
- 0:30:08
Product Value as the Basis for Marketability
Drawing on his marketing experience, the speaker argues that an application is very difficult to market without genuine user value, even though marketing still requires work and investment.
- 0:31:17
A Command Center for Switching Between Projects
The speaker outlines a command center intended to persist across the workflow, with a switcher that moves the user between different projects from one interface.
- 0:32:07
Checking Whether a Homepage Task Was Implemented
The speaker asks for a task to be analyzed and the homepage checked to determine whether character and emoji changes were already applied, then looks for where they appear in the interface.
- 0:33:31
Documenting a Command Center Build in Public
The speaker explains that the command center was built incrementally during public streams and that viewers need not watch every part of the long-form journey. He also mentions an intended shorter walkthrough rebuilding it from scratch with a guide file.
- 0:35:59
Updating Completed Task Statuses
The speaker directs that previously discussed tasks be marked completed rather than left in review.
Got a question about something in this stream?
Ask in the group