Fixing Broken Code
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
This portion centers on developing a Shopify app and preparing it for submission, with a brand “manifesto” presented as an optional profile that can guide content personalization across the product. The discussion covers questionnaire design, terminology and approval actions, manifesto visibility, and locked research states, while pushing back on feature creep in favor of finishing backend wiring, debugging, mobile review, and compliance work. The build and final testing were not completed: upload and draft actions were tested without a documented final result, while unexpected localization behavior and a batch-update bug were identified. The speaker stresses human visual QA after each milestone because automation alone had allowed bugs to accumulate. This portion also explores coding-agent workflows, including session handoffs, multi-agent orchestration, unresolved sequential-versus-parallel tradeoffs, environment contention and wait time, and why large refactors should not be assumed to finish autonomously. Audience questions prompt cautious opinions on B2B versus B2C pricing, acquisition and conversion economics, two-sided marketplace growth, advertising-platform feasibility, and researching profitability before building. Additional discussion touches on marketing automation, learning through practice, agent-tool choices, and trying different AI models, while keeping economic claims, model-capability inferences, and interpretations of AI-policy reports explicitly uncertain or opinion-based.
65 moments from the stream
- 0:03:10
Structuring the Debugging Workflow
The speaker describes a structured debugging workflow: finish prerequisite backend and page work, postpone QA until after merge and deployment, then review the results while continuing debugging in parallel.
- 0:06:46
Investigating Mobile Readiness in a Shopify Polaris App
The speaker requests a handoff for a fresh session to research Shopify Polaris behavior on mobile, sweep the codebase for existing mobile work, and collect findings from several angles. The app is currently desktop-optimized, and webhooks are also mentioned as an area needing review.
- 0:09:27
Why Debugging with Agents Feels Messy
The speaker observes that implementation work is easier to organize than debugging because debugging requires iterative back-and-forth with agents, making the workflow feel less orderly.
- 0:11:19
Building Does Not Require Expensive Tool Subscriptions
Responding to a question about monthly subscriptions, the speaker advises against copying his spending and says building products does not necessarily require costly subscriptions; the choice depends on each person's means.
- 0:12:19
Mocking Up a Settings Entry Point
The speaker notes that the interface offers a call to review and generate the manifesto but lacks a clear route to settings, so he requests a visual mockup of the proposed user flow.
- 0:13:20
Learning Digital Marketing Through Practice
The speaker says that entering the market and gaining hands-on experience taught him more about digital marketing than formal study, explicitly presenting this as his personal opinion rather than a universal rule.
- 0:14:08
A Brand Manifesto as the Basis for App Personalization
The speaker explains that creating a manifesto is optional, but it can guide the app's behavior and content so they become more consistent, refined, and aligned with the user's store brand.
- 0:15:00
Security, Scaling, and Marketing a Shopify App
Answering a question about non-functional requirements, the speaker says that Shopify's review process reduces the security burden in his view. He then contrasts hands-on growth through outreach, email, and social content with faster but costlier paid advertising, while noting the importance of reviews.
- 0:19:10
AI Content Personalization Through Manifesto Questions
The speaker describes a system that uses store data such as niche and products to form an initial understanding and guide product, page, and article content. He adds that a merchant's answers to manifesto questions provide more precise context than automated inference alone.
- 0:20:28
An Automated Manifesto for Understanding a Merchant
The speaker describes an automated “manifesto,” or business profile, designed to understand a merchant more precisely and guide downstream work such as article writing, product optimization, and AI prompting. In his view, asking only for a business description and social profiles is insufficient for that level of understanding.
- 0:23:01
Checking Upload, Draft, and Interface-Language Behavior
While working, the speaker tries to determine what happens when the upload and draft actions are selected, then notices that the interface or text unexpectedly appears in Arabic. The excerpt documents a practical UI check but does not establish a final resolution.
- 0:30:47
Refining the Brand and Audience Questionnaire
A review of important questionnaire fields, including content tone and language and target-audience attributes such as gender, age, and location, to improve brand setup.
- 0:38:25
Balancing Competitor Research and Product Scope
The discussion proposes asking users about their biggest competitor to support additional research, then rejects adding more features at this stage in favor of limiting scope growth and completing the application submission.
- 0:40:05
Emphasizing the Full Manifesto Link
A UI note suggests making the “read the full manifesto” option more prominent. A follow-up question begins, but its meaning is incomplete on this page.
- 0:41:57
Highlighting the Manifesto and Clarifying the Publish Action
The discussion proposes making the full manifesto PDF link more prominent because it is central to the review and approval flow, while reconsidering “Make live” because users may find the phrase ambiguous.
- 0:43:14
Matching Product Value to Its Price
The stated view is that the challenge is not adding more features, but ensuring the delivered value matches the price; at this stage, the page or feature was considered sufficient without further expansion.
- 0:44:36
Mobile View and Compliance Review for a Shopify App
A mobile-view issue was discussed and considered manageable, alongside the need for a full application review against Shopify policies. An unclearly named tool intended for that review was mentioned, with a personal expectation that it might return.
- 0:46:43
Leading With “Manifesto” and Explaining It to Users
“Manifesto” was preferred as a strong and accurate term for this context, even if unfamiliar to some users. The proposal was to use wording such as “Build your manifesto,” add a tooltip explaining it, and keep “brand brain” as a supporting rather than leading term.
- 0:49:32
Preventing Bug Accumulation and Differentiating With a Manifesto
The discussion advocates building incrementally so bugs do not pile up and presents manifesto creation as a simple, high-value differentiator. In the speaker’s assessment, competing tools often infer a company’s niche and offerings from product data, while the manifesto adds a clearer layer for defining identity.
- 0:50:34
Building a Guided Manifesto Instead of Offering Blind Regeneration
The manifesto acts as a reference for content generation, so the speaker argues that dissatisfaction may indicate missing or inaccurate questionnaire answers rather than a need for repeated free regeneration. The proposed flow guides users to review their inputs and then commit to a suitable draft.
Got a question about something in this stream?
Ask in the group